[asterisk-bugs] [Asterisk 0014346]: CANCEL gets different via header branch than INVITE

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14346 
====================================================================== 
Reported By:                oej
Assigned To:                oej
====================================================================== 
Project:                    Asterisk
Issue ID:                   14346
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   minor
Priority:                   high
Status:                     assigned
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 171452 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-27 06:05 CST
Last Modified:              2009-01-27 08:22 CST
====================================================================== 
Summary:                    CANCEL gets different via header branch than INVITE
Description: 
Asterisk 1.4 sends one branch in INVITE and one in CANCEL. THis is not
compliant with RFC 3261, that says clearly that the cancel needs the same
branch.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013381 Wrong branch on CANCEL after SIP INFO i...
====================================================================== 

---------------------------------------------------------------------- 
 (0098841) oej (manager) - 2009-01-27 08:22
 http://bugs.digium.com/view.php?id=14346#c98841 
---------------------------------------------------------------------- 
Seems like the patch in revision 142079 somehow did not make it properly,
as the code now creates TWO different branches before the first INVITE, one
stored in p->invite_branch and one in p->branch. This is no good.

Attaching patch that through extra logging clearly shows that this is the
case. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-27 08:22 oej            Note Added: 0098841                          
======================================================================