[asterisk-bugs] [Asterisk 0018058]: SIP session timers do not transmit session expiry or refresher timer in 200 OK

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Oct 5 04:11:03 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18058 
====================================================================== 
Reported By:                legranjl
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18058
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
JIRA:                       SWP-2307 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-09-27 00:34 CDT
Last Modified:              2010-10-05 04:11 CDT
====================================================================== 
Summary:                    SIP session timers do not transmit session expiry or
refresher timer in 200 OK
Description: 
When acting as uac the 200ok replay to uas does not include the sessoin
expiry and refresher timer. This turns the timer off.

RFC4028, chapter 7.2:
   "If the 2xx response did not contain a Session-Expires header field,
   there is no session expiration.  In this case, no refreshes need to
   be sent.  A 2xx without a Session-Expires can come for both initial
   and subsequent session refresh requests.  This means that the session
   timer can be 'turned-off' in mid dialog by receiving a response
   without a Session-Expires header field.


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

---------------------------------------------------------------------- 
 (0127689) legranjl (reporter) - 2010-10-05 04:11
 https://issues.asterisk.org/view.php?id=18058#c127689 
---------------------------------------------------------------------- 
Hi,

Attached I have the requested info.

For Clarity
Endpoint 192.168.8.234 to Asterisk 192.168.8.144 to Intrerconnect customer
192.168.250.127.

The timer between endpoint and Asterisk are working fine execpt that it is
still incorrect. Below is my evaluation

In packet 6 the Interconnect side receives INVITE message from Asterisk
side with Session-Expires headers In packet 11 the Interconnect side
answers with 200OK with "Session-Expires: 95;refresher=uas", means
interconnect side is (UAS) will refresh the session after 95/2=47,5
seconds. At packet 19 (47.5 sec. later) Interconnect side is sending
reINVITE for session refresh with"Session-Expires: 95;refresher=uac", means
Interconnect side (now UAC) will refresh the session. At packet 21 the
asterisk side answers with 200OK without any Session-Expires field.
This effectively means terminate sessions. The correct responce should be
to coppy the Session-Expires: 95;refresher=uac" header in the reINVITE and
add it in the 200ok response. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-05 04:11 legranjl       Note Added: 0127689                          
======================================================================




More information about the asterisk-bugs mailing list