I need to add a warning regarding Record_Route as it relates to ACK. The
opensource PBX asterisk has a bug where it does _not_ ignore RR in the ACK.
It seems that most UAs send an RR list with the ACK and if it is the same as
the original list, it causes no harm. Some UAs like Twinkle do not send RR
with the ACK and asterisk will create a null route set. Subsequent messages
will be misrouted.
There is a recent patch for asterisk but who knows how many have been updated.
See
, bug #11545.
On Sunday 09 March 2008, Vikas CG. wrote:
Thanks Robert Dyck,
For the suggestion.
Thanks,
Vikas C.G.
-----Original Message-----
From: Robert Dyck [mailto:rob.dyck@telus.net]
Sent: Sunday, March 09, 2008 4:56 AM
To: users(a)lists.openser.org
Cc: Vikas CG.
Subject: Re: [OpenSER-Users] Not adding record-route for ack
The route is determined by the INVITE as it makes it's way from the UAC
to UAS
while collecting Record-Route's as it goes. The UAS then forwards the
Record-Route list back to the UAC in the 200 OK. Both ends are now aware
of
the route set which will not be altered in this dialogue. Any further
messages in this dialogue must follow the route set. If in-dialogue
messages
contain Record_Route the Record-Route must be ignored.
The short answer is that ACK may contain Record_Route but it will be
ignored.
On Saturday 08 March 2008, Vikas CG. wrote:
Hi all,
We have built an SIPALG and using openser server as outbound proxy
for testing,
When call is made,
Ack message contains the route for openser,
After receiving the message he is forwarding to next route, but
not
making it has record-route.
Is this behavior is right?
Other servers will add record-route after forwarding to next
route.
> So please suggest for this?
>
> Thanks,
> Vikas C.G.