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

[Kovar, William (Bill)]

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/20070110/07b12857/attachment.htm>