[asterisk-bugs] [Asterisk 0018380]: On session-timers refresh, after 422 response Asterisk set modified From/To/Contact on next re-INVITE

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18380 
====================================================================== 
Reported By:                Sergeykrd
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18380
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                       SWP-2659 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 296306 
Request Review:              
====================================================================== 
Date Submitted:             2010-11-25 14:02 CST
Last Modified:              2010-12-14 10:22 CST
====================================================================== 
Summary:                    On session-timers refresh, after 422 response
Asterisk set modified From/To/Contact on next re-INVITE
Description: 
Call was established from Panasonic PBX to Asterisk over SIP trunk.
In this call asterisk has 'session-refresher=uas' which made refresher
role to swap after each refresh. After some refreshes, Panasonic declined
Session-Expires: 90 (which it offered first) with 422 response - it is
strange but it is not violate RFC4028.
Then Asterisk sending another re-INVITE with modified Session-Expires
(this is ok with part 7.3 of RFC4028) and modified (or more like 'resets')
From/To/Contact. Last is SHOULD NOT be modified (same part 7.3 of RFC4028),
unless knowing what doing.
So after that INVITE Panasonic starts new call.

In spirit of RFC4028, Asterisk should not modify this fields on
INVITE/422-INVITE.


====================================================================== 

---------------------------------------------------------------------- 
 (0129601) jorrit at infopact nl (reporter) - 2010-12-14 10:22
 https://issues.asterisk.org/view.php?id=18380#c129601 
---------------------------------------------------------------------- 
We are facing similar problems on asterisk 1.6.2.13 with ... tum tum tum ..
a Panasonic PBX as well. 

Looking at the code we noticed that the proc_422_sp calls
transmit_invite(), while I believe this should be
transmit_reinvite_with_sdp(). This would also explain the reset of other
headers.

We will investigate this later this week, but it would be much appreciated
if anyone could give us any pointers on why transmit_invite() was used in
the first place. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-14 10:22 jorrit at infopact nlNote Added: 0129601                       
  
======================================================================