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

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Nov 25 14:02:56 CST 2010


The following issue has been SUBMITTED. 
====================================================================== 
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:                     new
Asterisk Version:           SVN 
JIRA:                        
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-11-25 14:02 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.


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

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-25 14:02 Sergeykrd      New Issue                                    
2010-11-25 14:02 Sergeykrd      Asterisk Version          => SVN             
2010-11-25 14:02 Sergeykrd      Regression                => No              
2010-11-25 14:02 Sergeykrd      SVN Branch (only for SVN checkouts, not tarball
releases) =>  trunk          
2010-11-25 14:02 Sergeykrd      SVN Revision (number only!) => 296306          
======================================================================




More information about the asterisk-bugs mailing list