Guest

Preview Tool

Cisco Bug: CSCvu39579 - CUBE with external SIP trunk registration unexpectedly reloads during config removal

Last Modified

Sep 25, 2020

Products (1)

  • Cisco IOS

Known Affected Releases

16.6.7

Description (partial)

Symptom:
This defect was created to address a possible incomplete fix in CSCvj16209.  This defect (CSCvu39579) addresses the same issue identified in CSCvj16209 for when Cisco Unified Border Element (CUBE) is configured instead.


A voice class tenant, credentials, and registrar IP address are configured.

When checking the status of SIP registrar:

eg,
voice class tenant x
  registrar 1 ipv4:xxxxx  expires xxxxx tcp
  credentials username xxxxx password 7 xxxxx realm sip.beeline.ru
  authentication username xxxxx password 7 xxxxx realm sip.beeline.ru
  timers buffer-invite xxxxx 
  bind control source-interface GigabitEthernetxxx
  no pass-thru content custom-sdp

Router# sh sip-ua register status tenant 

--------------------- Registrar-Index  1 --------------------- 
Line                             peer      expires(sec) reg survival  P-Associ-URI
================================ ========= ============ === ========  ============
xxxxx                             xxxxx          xx      no normal                     >>>>>>>>>>>> SIP Line 

Tenant:  11 
--------------------- Registrar-Index  1 --------------------- 
Line                             peer      expires(sec) reg survival  P-Associ-URI
================================ ========= ============ === ========  ============
xxxxx                              -1         xxxxx     no  normal                     >>>>>>>>>> CUBE trying to register to ITSP.


After removing the registrar using "no voice class tenant <x>", the CUBE line gets cleared immediately, but the phone line remains for some time afterwards.  When the line tries to send its next registration after the "expires" timer runs out, it tries to find the registrar but it is no longer there (since we removed it).

This results into an unexpected reload to recover as the device doesn't know how to handle the critical exception.
 
This is a timing issue. The expectation is that whenever we clear the entry of a registrar, it should clear the entry for phone line immediately.

Conditions:
It's a timing issue: if we clear the registrar shortly before the phone sends a REGISTER retry, it will unexpectedly reload.
Bug details contain sensitive information and therefore require a Cisco.com 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.