[reSIProcate] Question about Record-Route headers on re-Invite

[Scott Godin]

It looks like Dialog.cxx is overwriting the routeset on any 200-299
response (ln 557).  This is still a problem in SVN head.  

 

I'll look at fixing this next week.  For a UAC - I think the routeset
should only be set on the 200 response to the initial invite.

 

Good find!

 

Scott

 

From: resiprocate-devel-bounces at list.resiprocate.org
[mailto:resiprocate-devel-bounces at list.resiprocate.org] On Behalf Of
Kovar, William (Bill)
Sent: Wednesday, January 10, 2007 4:22 PM
To: resiprocate-devel at list.resiprocate.org
Subject: [reSIProcate] Question about Record-Route headers on re-Invite

 

I'm seeing a situation where an initial session has been established
with 2 Record-Route's set, i.e. IP1 & IP2.

 

When a re-invite sent, both Routes (IP1 & IP2) are used, however, the
200 OK only sends one (IP1).

 

The subsequent ACK generated only insert Route: IP1 and the final
destination is never reached. This causes retransmission of the 200 OK
over and over.

 

It seems like DUM/resip is over-writing the original Route set
established with the initial session, which is an RFC 3261 violation -
section 12.2

 

As I am on a version of resip prior to resip 1.0, is this a known
problem and fixed??

 

Bill Kovar

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070112/911c1e8b/attachment.htm>