Hi Bruce,
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.
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:
From:
<sip:[email protected]>;[email protected]
And the destination uri for the ACK became:
DBG:tm:t_uac:
next_hop=<sip:41.x.x.33;lr=on;[email protected];vsf=AAAAAFlyXxh7QkwaAQVydAUfHAADHxsbGAA2>
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.
This problem is fixed in the svn branch as illegal characters are not
allowed anymore. Please update.
Regards,
--
Anca Vamanu
www.voice-system.ro
On 06/10/2010 01:35 AM, Bruce Borrett wrote:
Hi
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.
Here is a sip trace of the call:
http://pastebin.com/iDvVgk2B
And here is a debug:
http://pastebin.com/teSuTp7E
Thank you in advance..
Regards,
Bruce
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
