<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: #000000'>Hello again Anca,<br><br>I've done more debugging, and I've found that the REFER packets are all targeting my B2BUA address and getting a 404 response. It seems to still be working, but I'm wondering if this is what is causing the problem after the 2nd transfer.<br><br>In my log at http://www.woollum.com/temp/opensips_trace.html, you can see the 404 Not Found's occurring at packet 9177. This one in particular is generated for the packet above it (9175) that has "sip:b2bua@1.2.3.4" in the header of the packet. <br><br>I've configured my B2BUA module with this entry:<br><font style="font-family: Courier New,courier,monaco,monospace,sans-serif;" size="2">modparam("b2b_entities", "server_address", "sip:b2bua@1.2.3.4:5060")<br></font><br>and this is the config file that is creating the errors:<br><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">if (uri==myself) {</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> if (method=="REGISTER") {</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> save("location");</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> exit;</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> };</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> # native SIP destinations are handled using our USRLOC DB</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> if (!lookup("location")) {</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> <span style="font-weight: bold;">xlog("USRLOC LOOKUP: ERROR 404 - NOT FOUND $fu->$ru");</span></span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> sl_send_reply("404", "Not Found");</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> exit;</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> };</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> append_hf("P-hint: usrloc applied\r\n"); </span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> };</span></font><br><br>And this is what is generated in the OpenSIPS log:<br><font style="font-family: Courier New,courier,monaco,monospace,sans-serif;" size="2">Oct 18 22:56:42 sip01 /usr/local/sbin/opensips[4425]: USRLOC LOOKUP: ERROR 404 - NOT FOUND sip:1000@1.2.3.4->sip:b2bua@1.2.3.4:5060<br></font><br>Is there something I need to add to my configuration that handles packets with "b2bua@1.2.3.4" as the destination ($ru)?<br><br><div><span style="font-family: arial,helvetica,sans-serif;">Brett Woollum</span><br style="font-family: arial,helvetica,sans-serif;"><span style="font-family: arial,helvetica,sans-serif;">Brett@Woollum.com</span><br></div><br><br>----- Original Message -----<br>From: "Brett Woollum" <brett@woollum.com><br>To: "OpenSIPS users mailling list" <users@lists.opensips.org><br>Sent: Monday, October 18, 2010 5:09:34 PM GMT -08:00 US/Canada Pacific<br>Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)<br><br><style>p { margin: 0; }</style><div style="font-family: Arial,Helvetica,sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Hi Anca,<br><br>I set debug=6 but it does not appear to print any more detailed information to my log (/var/log/messages).<br><br>I reviewed the sip trace I posted at http://www.woollum.com/temp/opensips_trace.html and I still cannot find any packets that are missing the header. The error log I posted at http://www.woollum.com/temp/opensips.txt says that the To field, From field, and RR field could not be parsed. It seems as though the B2BUA module tried to open a new leg but didn't send the information along? Does that make sense?<br><pre style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><font size="2">From the log earlier:<br>Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char [<] in status 5: <<<>> .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:b2b_entities:b2b_prescript_f: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char [<] in status 5: <<<>> .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:pv_get_from_attr: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ROUTE STARTING INVITE <null> sip:sales@1.2.3.4
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char [<] in status 5: <<<>> .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:rr:record_route: From parsing failed
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char [<] in status 5: <<<>> .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:tm:new_t: no valid From in INVITE
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:tm:t_newtran: new_t failed
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: unexpected char [<] in status 5: <<<>> .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: ERROR:core:parse_to: unexpected char [<] in status 5: <<<>> .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:pv_get_from_attr: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: ERROR:b2b_entities:b2b_tm_cback: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ROUTE 8 ENDING INVITE <null> sip:sales@10.20.1.225:5062
Oct 12 19:34:17 sip01 /usr/local/sbin/opensips[5168]: ERROR:b2b_entities:b2b_prescript_f: No dialog found, callid= [B2B.50.3250981], method=REFER
</font></pre><span style="font-family: arial,helvetica,sans-serif;">Brett Woollum</span><br style="font-family: arial,helvetica,sans-serif;"><div><span style="font-family: arial,helvetica,sans-serif;">Brett@Woollum.com</span><br></div><br><br>----- Original Message -----<br>From: "Anca Vamanu" <anca@opensips.org><br>To: users@lists.opensips.org<br>Sent: Thursday, October 14, 2010 12:45:19 AM GMT -08:00 US/Canada Pacific<br>Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)<br><br>
Hi Brett,<br>
<br>
You need to run a network trace and catch the message for which you get
this error:<br>
<br>
ERROR:core:parse_to: unexpected char [<] in status 5:
<<<>> <br>
<br>
You can run opensips in debug mode ( set 'debug=6' ) to see info from
the message and be able to find it in the network trace. <br>
<br>
>From the logs it seems that a message ( possibly REFER ) has a bad From
header and OpenSIPS is not able to process right.<br>
<br>
Regards,<br>
<pre class="moz-signature">--
Anca Vamanu
<a class="moz-txt-link-abbreviated" href="http://www.voice-system.ro" target="_blank">www.voice-system.ro</a></pre>
<br></div><br>_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
</div></body></html>