16 Nov
2007
16 Nov
'07
7:13 p.m.
On Friday 16 November 2007, Juha Heinanen wrote:
Klaus Darilion writes:
Perhaps it would be useful if openser could be configured to preserve the RR
list. I encountered a situation where the ACK was not being delivered during
re-INVITE. Since the UAC had the correct route set for the re-INVITE, the ACK
should have followed the same route. I found that this behaviour occurred
when the UAS did not send an RR list with its 200 OK. The spec says within a
dialogue the UAS MAY send RR. It also says the route set must remain
unchanged once the dialogue is established. It would seem that in this case
the UAC is creating an empty route set when it does not receive an RR list,
thus destroying the proper route set.
Would it be useful to create a module parameter in TM such
as "preserve_RR_list.
PS: the UAC mentioned is a PSTN gateway. It is not identified but I think it
is an Asterisk.
MAybe we should stay away from SIP :-)
not necessarily. you just as proxy operator don't take responsibility
of brain damaged sip user agents. people who use them assume the risks
by themselves. if user agent is willing to speak with anyone, then of
course it has to protect itself by itself.