Preview Tool

Cisco Bug: CSCuj49936 - CUCM need to send SE header in every outgoing UPDATE and ReInvites

Last Modified

Feb 25, 2019

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

8.5(1.98000.42) 9.1(1.20000.5)

Description (partial)

Call scneario:

1. CUCM sends a SIP Invite to cube 
2. CUBE responds with a 200 OK with session expires = 1800 and refresher = uas 
3. After 900 seconds, CUCM sends an Update message to CUBE . And CUBE responds with 200 OK (with no session expiry timer) disabling the session timer. 
4. However, after 1800 seconds, CUCM disconnects the call with the reason "star_SIPSessionExpiresRefreshTimer: RefreshReq not rcvd"

According to RFC4028,"The default value of the Session-Expires header field is undefined.  This means that the absence of the Session-Expires header field  implies no expiration of the session, using the mechanism defined in  this specification."
CUCM should sent UPDATE/ReInvite with SE header.

CUCM sends UPDATE without SE header which makes the CUBE to assume refresh timing should be disabled.
.  In order to ensure that we do not inadvertently cause the far end to assume that refresh timing should be disabled,  CUCM sends SE header in  all outgoing UPDATE/ReInvite requests

Related Community Discussions

CUBE SIP 'session-expires' missing at first refresh.
Hi, We've been testing the UPDATE method for refreshes since we removed it on the CUBE at initial install some years ago. Our interrop team has requested us to help test if we can re-enable the UPDATE method between CUBE and SP but we are still faced with calls being dropped at 1/2 session-expires timer setting, same as all those years ago. Since our initial install we've upgraded our CUBE IOS from 15.1 to 15.4 so I was hoping it would work this time around. Here are my findings: LAB Setup: MIN-SE ...
Latest activity: Nov 27, 2015
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.