[OpenSIPS-Devel] [opensips] ACK propagated with wrong CSeq number (#680)

[pwakano]

Problem: Transfer scenario causes Opensips to use the wrong CSeq number to propagate an ACK.
Scenario: Call is established, in-dialog pings are sent, user does a blind transfer which causes the transmission of a Re-Invite immediately followed by an Update. These requests are answered but the ACK for the Re-Invite gets propagated with the CSeq number of the Update and not with the CSeq of the correponding Re-Invite.

Reference: http://lists.opensips.org/pipermail/users/2015-October/032859.html

---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/680
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20151021/4bf60550/attachment.htm>