<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt">Hi Anca<br><br>Thank you, the latest revision did solve that issue, the ACK is now being relayed properly. Although I seem to have another issue now with Opensips retransmitting the 200 right throughout the call, even after it has received and relayed the ACK?!<br><br>Here is a new SPI trace:<br><span><a target="_blank" href="http://pastebin.com/Xit26Gkk">http://pastebin.com/Xit26Gkk</a></span><br><br>And a new Debug:<br><span><a target="_blank" href="http://pastebin.com/ZB5xTsvj">http://pastebin.com/ZB5xTsvj</a></span><br><br>Thanks,<br>Bruce<br><div><br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight:
bold;">From:</span></b> Anca Vamanu <anca@opensips.org><br><b><span style="font-weight: bold;">To:</span></b> users@lists.opensips.org<br><b><span style="font-weight: bold;">Sent:</span></b> Thu, 10 June, 2010 10:42:48<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [OpenSIPS-Users] B2B Ack issue<br></font><br><meta http-equiv="x-dns-prefetch-control" content="off">
<title></title>
Hi Bruce,<br>
<br>
It is clear now what happens - you have to upgrade the b2b modules to
the svn version because there is a problem in the stable release. <br>
In there the from tag in the generated is constructed as the
concatenation of from tag and callid from the initial request. The
problem is that most clients put in the callid '@ip address' and @ is
an illegal character in from tag. So the from tag in you case was:<br>
<br>
From:
<a rel="nofollow" class="moz-txt-link-rfc2396E"><sip:0100000715@41.x.x.66></a>;tag=call-F1030790-3656-2D10-1919-AB@192.x.x.154c0a8c89a-4f7<br>
<br>
And the destination uri for the ACK became:<br>
<br>
DBG:tm:t_uac:
next_hop=<a rel="nofollow" class="moz-txt-link-rfc2396E"><sip:41.x.x.33;lr=on;ftag=call-F1030790-3656-2D10-1919-AB@192.x.x.154c0a8c89a-4f7;vsf=AAAAAFlyXxh7QkwaAQVydAUfHAADHxsbGAA2></a><br>
<br>
The parser then concluded that the domain was the string after '@':
192.x.x.154c0a8c89a-4f7 - and it tried doing a look up on this.<br>
<br>
This problem is fixed in the svn branch as illegal characters are not
allowed anymore. Please update.<br>
<br>
Regards,<br>
<pre class="moz-signature">-- <br>Anca Vamanu<br><a rel="nofollow" class="moz-txt-link-abbreviated" target="_blank" href="http://www.voice-system.ro">www.voice-system.ro</a></pre>
<br>
On 06/10/2010 01:35 AM, Bruce Borrett wrote:
<blockquote type="cite">
<div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">
<div>Hi<br>
<br>
I have copied a config from one of the B2B tutorials, and only made one
or two small changes to it. The problem I am having is that when an ACK
is sent by the caller after receiving a 200, opensips tries to do a dns
lookup on the source ip of the ACK for some reason. I do not have dns
set up and am not using domain names anywhere. <br>
<br>
Here is a sip trace of the call:<br>
<span><a rel="nofollow" target="_blank" href="http://pastebin.com/iDvVgk2B">http://pastebin.com/iDvVgk2B</a></span><br>
<br>
And here is a debug:<br>
<span><a rel="nofollow" target="_blank" href="http://pastebin.com/teSuTp7E">http://pastebin.com/teSuTp7E</a></span><br>
<br>
Thank you in advance..<br>
<br>
Regards,<br>
Bruce<br>
</div>
</div>
<br>
<pre><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Users mailing list
<a rel="nofollow" class="moz-txt-link-abbreviated" ymailto="mailto:Users@lists.opensips.org" target="_blank" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a rel="nofollow" class="moz-txt-link-freetext" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature"></pre>
<meta http-equiv="x-dns-prefetch-control" content="on"></div></div>
</div><br>
</body></html>