[OpenSIPS-Users] B2B Ack issue
bruce_borrett at yahoo.com
Tue Jun 15 10:17:01 CEST 2010
Sorry if I have confused the list with all my paste links :)
Anca, if the ACK from 196.x.x.208 is not being matched to a transaction
correctly, then how does B2B module know to route the ACK to 41.x.x.33,
and it is even using the correct call id and from and to tags?
From: Anca Vamanu <anca at opensips.org>
To: users at lists.opensips.org
Sent: Tue, 15 June, 2010 9:49:58
Subject: Re: [OpenSIPS-Users] B2B Ack issue
The first two bugs are no longer valid. You probably looked at an old
trace that the user pasted, I then asked him to update the code and
there are no longer this problems.
With the third, you are right, this is the point of the B2BUA to put
itself in the middle of the call and hide the topology.
On 06/15/2010 02:53 AM, Iñaki Baz Castillo wrote:
> 2010/6/14 Anca Vamanu<anca at opensips.org>:
> In this trace I see 2 bugs (b2bua module bugs?) and a possible third bug:
> 1) The From generated by b2bua is illegal:
> From:<sip:0100000715 at 220.127.116.11>;tag=call-F1030790-3656-2D10-1919-AB at 192.x.x.154c0a8c89a-4f7
> The @ symbol in the "tag" is not valid. A @ can be present in a header
> param if it's enclosed in double quotes, but "tag" doesn't allow
> quotes, it must be just a token.
> 2) The ftag param in Record-Route is illegal:
> Record-Route:<sip:41.x.x.33;lr=on;ftag=call-F1030790-3656-2D10-1919-AB at 192.x.x.154c0a8c89a-4f7;vsf=AAAAAFlyXxh7QkwaAQVydAUfHAADHxsbGAA2>
> The @ symbol in a SIP URI param is not valid. Also, a SIP URI param
> cannot contain double quotes, but just a token.
> 3) The 200 replied to the UAC has no mirrored Record-Route, but I
> expect that this is exactly the desired behaviour of the b2bua module
Users mailing list
Users at lists.opensips.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users