<html><body><div>I added the log and everything looks fine. It's only adding the PAI to the initial invite which is what I want. The odd thing is there are no issues with the invites, it just looks like the Cancel messages that are being mangled. I posted a separate issue to the list prior to this report but no one responded, I'm not sure it went through correctly but resulting cancel coming out of the B2BUA looked like this:</div><div><br></div><div> Reference:
<br><br>192.168.1.146 = Opensips Proxy
<br>192.168.1.145 = Opensips B2BUA
<br>10.2.3.245 = Carrier
<br><br><br><br>U 2011/12/01 22:51:11.558887 192.168.1.146:5060 -> 192.168.1.145:5090
<br>CANCEL sip:9993512125551212@192.168.1.145:5090 SIP/2.0.
<br>Via: SIP/2.0/UDP 192.168.1.146;branch=z9hG4bK2df7.78db1d81.0.
<br>From: "James Logan" <sip:8884442222@192.168.1.137>;tag=as06eabdcd.
<br>Call-ID: 40c30c6459b3eaa4683991082381cadb@192.168.1.137.
<br>To: "12125551212" <sip:12125551212@192.168.1.146>.
<br>CSeq: 102 CANCEL.
<br>Max-Forwards: 70.
<br>User-Agent: Opensips.
<br>Content-Length: 0.
<br>.
<br><br><br>U 2011/12/01 22:51:11.559378 192.168.1.145:5090 -> 192.168.1.146:5060
<br>SIP/2.0 200 canceling.
<br>Via: SIP/2.0/UDP 192.168.1.146;branch=z9hG4bK2df7.78db1d81.0.
<br>From: "James Logan" <sip:8884442222@192.168.1.137>;tag=as06eabdcd.
<br>Call-ID: 40c30c6459b3eaa4683991082381cadb@192.168.1.137.
<br>To: "12125551212" <sip:12125551212@192.168.1.146>;tag=3330ae74b9cf9aed85afbc9203dd6238-715f
<br>CSeq: 102 CANCEL.
<br>Server: B2BUA.
<br>Content-Length: 0.
<br>.
<br><br><br>U 2011/12/01 22:51:11.559527 192.168.1.145:5090 -> 10.2.3.245:5060
<br>CANCEL ............i...............i.. SIP/2.0.
<br>Via: SIP/2.0/UDP 192.168.1.145:5090;branch=z9hG4bK5421.22999dd2.0.
<br>........B2B.256.3572553sip:+12125551212@10.2.3.245sip:8884442222@192.168.1.1379120d3`.....p..i...........................................q.i............
<br>........ CANCEL.
<br>User-Agent: OpenSIPS (1.7.1-notls (x86_64/linux)).
<br>Max-Forwards: 70.
<br>User-Agent: Opensips.
<br>Init-CallID: 40c30c6459b3eaa4683991082381cadb@192.168.1.137.
<br>Contact: <sip:192.168.1.145:5090>.
<br>. <br><br>On Dec 07, 2011, at 05:18 PM, Ovidiu Sas <osas@voipembedded.com> wrote:<br><br></div><div><blockquote type="cite"><div class="msg-quote"><div class="_stretch">Add a log and print out what are you adding before adding it and you<br> will see if it's good or not.<br> <br> On Wed, Dec 7, 2011 at 5:13 PM, Logan <<a href="mailto:voipmaster@me.com" data-mce-href="mailto:voipmaster@me.com">voipmaster@me.com</a>> wrote:<br> > This is the extent of my local route. If the $var is not present, I do not<br> > add it. Do you see any issue with what I'm doing here?<br> ><br> ><br> > local_route {<br> > #xlog("L_INFO","***** IN LOCAL ROUTE ********\n");<br> ><br> > if (is_method("INVITE")) {<br> > if($var(pai_userpart)) {<br> > append_hf("P-Asserted-Identity:<br> > \"$var(pai_display)\" <sip:$var(pai_userpart)@$Ri>\r\n");<br> > }else{<br> > xlog("L_INFO","PAI is not present, not adding\n");<br> > }<br> > }<br> ><br> ><br> > }<br> ><br> > On Dec 07, 2011, at 04:57 PM, Ovidiu Sas <<a href="mailto:osas@voipembedded.com" data-mce-href="mailto:osas@voipembedded.com">osas@voipembedded.com</a>> wrote:<br> ><br> > You need to be careful when you alter requests in B2B mode (the<br> > received INVITE and the sent INVITE belong to different transactions).<br> > Make sure that you have something valid in those vars before applying<br> > any changes to the outgoing message.<br> ><br> > Regards,<br> > Ovidiu Sas<br> ><br> > On Wed, Dec 7, 2011 at 4:49 PM, Logan <<a href="mailto:voipmaster@me.com" data-mce-href="mailto:voipmaster@me.com">voipmaster@me.com</a>> wrote:<br> >> I'm storing some $vars in route[0] prior to calling b2b_init_request("top<br> >> hiding");<br> >><br> >> Then in my local route Im appending a P-Asserted-Identity header.<br> >><br> >> I can't use the custom_headers modparam because it's going to preserve the<br> >> PAI as it comes in. Most of the time it's not present, or is in the wrong<br> >> format so I'm adding it in local route.<br> >><br> >><br> >> On Dec 07, 2011, at 04:31 PM, Ovidiu Sas <<a href="mailto:osas@voipembedded.com" data-mce-href="mailto:osas@voipembedded.com">osas@voipembedded.com</a>> wrote:<br> >><br> >> Are you trying to perform any msg manipulations during b2b scenarios?<br> >> Also, keep in mind that the b2b server functionality must be kept<br> >> isolated from the proxy server functionality (proxy mode is not<br> >> compatible with b2b mode).<br> >><br> >> Regards,<br> >> Ovidiu Sas<br> >><br> >> -- VoIP Embedded, Inc.<a href="http://www.voipembedded.com" data-mce-href="http://www.voipembedded.com">http://www.voipembedded.com</a><br> >> On Wed, Dec 7, 2011 at 3:41 PM, Logan <<a href="mailto:voipmaster@me.com" data-mce-href="mailto:voipmaster@me.com">voipmaster@me.com</a>> wrote:<br> >>> Hello list this is the second odd thing I've seen with b2bua in opensips<br> >>> 1.7.1 It looks like the b2bua module is mangling the cancel message and<br> >>> is<br> >>> ripping out the callid when sending upstream:<br> >>><br> >>><br> >>> U 2011/12/07 20:15:05.895915 192.168.1.143:5060 -> 192.168.1.145:5090<br> >>><br> >>> CANCEL sip:<a href="mailto:9993518045551212@192.168.1.145" data-mce-href="mailto:9993518045551212@192.168.1.145">9993518045551212@192.168.1.145</a>:5090 SIP/2.0.<br> >>><br> >>> Via: SIP/2.0/UDP 192.168.1.143;branch=z9hG4bKac0e.5a3d2bf1.0.<br> >>><br> >>> From: "8669800222" <sip:<a href="mailto:8669800222@192.168.1.1" data-mce-href="mailto:8669800222@192.168.1.1">8669800222@192.168.1.1</a>>;tag=3532277698-944952.<br> >>><br> >>> Call-ID: <a href="mailto:494823-3532277698-944947@192.168.1.1" data-mce-href="mailto:494823-3532277698-944947@192.168.1.1">494823-3532277698-944947@192.168.1.1</a>.<br> >>><br> >>> To: "18045551212" <sip:<a href="mailto:18045551212@192.168.1.143" data-mce-href="mailto:18045551212@192.168.1.143">18045551212@192.168.1.143</a>>.<br> >>><br> >>> CSeq: 1 CANCEL.<br> >>><br> >>> Max-Forwards: 70.<br> >>><br> >>> User-Agent: Opensips.<br> >>><br> >>> Content-Length: 0.<br> >>><br> >>> .<br> >>><br> >>><br> >>><br> >>> U 2011/12/07 20:15:05.896027 192.168.1.145:5090 -> 192.168.1.143:5060<br> >>><br> >>> SIP/2.0 200 canceling.<br> >>><br> >>> Via: SIP/2.0/UDP 192.168.1.143;branch=z9hG4bKac0e.5a3d2bf1.0.<br> >>><br> >>> From: "8669800222" <sip:<a href="mailto:8669800222@192.168.1.1" data-mce-href="mailto:8669800222@192.168.1.1">8669800222@192.168.1.1</a>>;tag=3532277698-944952.<br> >>><br> >>> Call-ID: <a href="mailto:494823-3532277698-944947@192.168.1.1" data-mce-href="mailto:494823-3532277698-944947@192.168.1.1">494823-3532277698-944947@192.168.1.1</a>.<br> >>><br> >>> To: "18045551212"<br> >>><br> >>> <sip:<a href="mailto:18045551212@192.168.1.143" data-mce-href="mailto:18045551212@192.168.1.143">18045551212@192.168.1.143</a>>;tag=3330ae74b9cf9aed85afbc9203dd6238-e6b7.<br> >>><br> >>> CSeq: 1 CANCEL.<br> >>><br> >>> Server: Opensips.<br> >>><br> >>> Content-Length: 0.<br> >>><br> >>> .<br> >>><br> >>><br> >>><br> >>> U 2011/12/07 20:15:05.896097 192.168.1.145:5090 -> 10.2.3.210:5060<br> >>><br> >>> CANCEL sip:+<a href="mailto:18045551212@65.211.120.23" data-mce-href="mailto:18045551212@65.211.120.23">18045551212@65.211.120.23</a> SIP/2.0.<br> >>><br> >>> Via: SIP/2.0/UDP 192.168.1.145:5090;branch=z9hG4bK0299.252f8e61.0.<br> >>><br> >>> .<br> >>><br> >>> From: <sip:<a href="mailto:7324812444@66.29.74.37" data-mce-href="mailto:7324812444@66.29.74.37">7324812444@66.29.74.37</a>>;tag=418802140f6308e008db76a1e1de765b.<br> >>><br> >>> CSeq: 2 INVITE54.7172739.<br> >>><br> >>> Content-Lengt<br> >>><br> >>> To: sip:+<a href="mailto:18045551212@65.211.120.237" data-mce-href="mailto:18045551212@65.211.120.237">18045551212@65.211.120.237</a>.<br> >>><br> >>> Call- CANCEL.<br> >>><br> >>> User-Agent: OpenSIPS (1.7.1-notls (x86_64/linux)).<br> >>><br> >>> Max-Forwards: 70.<br> >>><br> >>> Init-CallID: <a href="mailto:494823-3532277698-944947@192.168.1.1" data-mce-href="mailto:494823-3532277698-944947@192.168.1.1">494823-3532277698-944947@192.168.1.1</a>.<br> >>><br> >>> Contact: <sip:192.168.1.145:5090>.<br> >>><br> >>> .<br> >>><br> >>><br> >>><br> >>> U 2011/12/07 20:15:05.910842 10.2.3.210:5060 -> 192.168.1.145:5090<br> >>><br> >>> SIP/2.0 400 Missing Mandatory Header Call-Id.<br> >>><br> >>> v: SIP/2.0/UDP<br> >>> 192.168.1.145:5090;branch=z9hG4bK0299.252f8e61.0;received=192.168.1.145.<br> >>><br> >>> l: 0.<br> ><br> > _______________________________________________<br> > Users mailing list<br> > <a href="mailto:Users@lists.opensips.org" data-mce-href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br> > <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" data-mce-href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br> ><br> ><br> > _______________________________________________<br> > Users mailing list<br> > <a href="mailto:Users@lists.opensips.org" data-mce-href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br> > <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" data-mce-href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br> ><br> <br> <br> <br> -- <br> VoIP Embedded, Inc.<br> <a href="http://www.voipembedded.com" data-mce-href="http://www.voipembedded.com">http://www.voipembedded.com</a><br> <br> _______________________________________________<br> Users mailing list<br> <a href="mailto:Users@lists.opensips.org" data-mce-href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" data-mce-href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br></div></div></blockquote></div></body></html>