<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'>Anca, <br><br>I've discovered that the REFER messages sent from the phones to the OpenSIPS server/B2BUA are not receiving a 202 Accepted reply from the B2BUA module, and as a result, the phones continue to re-send the REFER's. The B2BUA module doesn't recognize the additional REFER's because it has already torn down the original call leg. As a result the additional REFER's are processed in the route script which is wrong and causes the 404 Not Found errors.<br><br>Here is what's happening: (assume a call already exists):<br>The phone sends a REFER to the B2BUA<br>The B2BUA sends BYE back to the phone<br>The B2BUA invites the new leg of the call to the other phone<br>The original phone continues to send REFER's to the B2BUA module, which responds with 404 Not Found's<br><br>I believe there should be a 202 Accepted sent from the B2BUA module to the phone in response to the first REFER message, not a BYE (or maybe both Accepted and BYE). But there is no 202 Accepted coming from the B2BUA module to the phone.<br><br>Scroll to the bottom of http://www.woollum.com/temp/opensips.txt to view my B2BUA XML config, which specifies that the B2BUA should respond with a 202 Accepted before ending the call leg. This is not happening like it should....<br><br>I am running OpenSIPS 1.6.3 on CentOS 5.5 x64 (on an AMD platform).<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: "Anca Vamanu" <anca@opensips.org><br>To: users@lists.opensips.org<br>Sent: Tuesday, October 19, 2010 2:20:15 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>
No, you needn't add anything else in your configuration file except for
the b2b_init_request for the initial Invite and the B2BUA should know
to handle the REFER that comes inside that dialog. What happens is the
the B2BUA does not find a matching dialog for that REFER message .. I
don't know why that is. I will examine the traces you posted and try to
reproduce this in the following days and let you know. <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>
On 10/19/2010 09:05 AM, Brett Woollum wrote:
<blockquote cite="mid:174978345.7381287468348192.JavaMail.root@mail">
<style>p { margin: 0; }</style>
<div style="font-family: Arial,Helvetica,sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">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 <a class="moz-txt-link-freetext" href="http://www.woollum.com/temp/opensips_trace.html" target="_blank">http://www.woollum.com/temp/opensips_trace.html</a>, 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
<a class="moz-txt-link-rfc2396E" href="about:blank" target="_blank">"sip:b2bua@1.2.3.4"</a> 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",
<a class="moz-txt-link-rfc2396E" href="about:blank" target="_blank">"sip:b2bua@1.2.3.4:5060"</a>)<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
<a class="moz-txt-link-freetext" href="about:blank" target="_blank">sip:1000@1.2.3.4</a>-><a class="moz-txt-link-freetext" href="about:blank" target="_blank">sip:b2bua@1.2.3.4:5060</a><br>
</font><br>
Is there something I need to add to my configuration that handles
packets with <a class="moz-txt-link-rfc2396E" href="mailto:b2bua@1.2.3.4" target="_blank">"b2bua@1.2.3.4"</a> 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;"><a class="moz-txt-link-abbreviated" href="mailto:Brett@Woollum.com" target="_blank">Brett@Woollum.com</a></span><br>
</div>
<br>
<br>
----- Original Message -----<br>
From: "Brett Woollum" <a class="moz-txt-link-rfc2396E" href="mailto:brett@woollum.com" target="_blank"><brett@woollum.com></a><br>
To: "OpenSIPS users mailling list" <a class="moz-txt-link-rfc2396E" href="mailto:users@lists.opensips.org" target="_blank"><users@lists.opensips.org></a><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
<a class="moz-txt-link-freetext" href="http://www.woollum.com/temp/opensips_trace.html" target="_blank">http://www.woollum.com/temp/opensips_trace.html</a> and I still cannot find
any packets that are missing the header. The error log I posted at
<a class="moz-txt-link-freetext" href="http://www.woollum.com/temp/opensips.txt" target="_blank">http://www.woollum.com/temp/opensips.txt</a> 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:
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> <a class="moz-txt-link-freetext" href="about:blank" target="_blank">sip:sales@1.2.3.4</a>
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> <a class="moz-txt-link-freetext" href="about:blank" target="_blank">sip:sales@10.20.1.225:5062</a>
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;"><a class="moz-txt-link-abbreviated" href="mailto:Brett@Woollum.com" target="_blank">Brett@Woollum.com</a></span><br>
</div>
<br>
<br>
----- Original Message -----<br>
From: "Anca Vamanu" <a class="moz-txt-link-rfc2396E" href="mailto:anca@opensips.org" target="_blank"><anca@opensips.org></a><br>
To: <a class="moz-txt-link-abbreviated" href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a><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>
</div>
</div>
</blockquote>
<br>_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
</div></body></html>