Guest

Preview Tool

Cisco Bug: CSCvu39334 - APNS not working after SDL Link OOS Event Leads to Duplicate Device Condition

Last Modified

Sep 30, 2020

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

11.5(1.10000.6) 12.0(1.10000.10) 12.5(1.10000.22)

Description (partial)

Symptom:
Devices with Push Notifications enabled stop receiving notifications after running in the background.  An SDL Link OOS event between the primary and secondary nodes for the jabber client leads to a condition where APNS Notifications stop being sent to the jabber client.

Conditions:
Jabber client with Push Notification enabled running in the background on the iPhone and an SDL Link out of service event between the secondary and primary nodes for the jabber client.  While the SDL Link is down we create a new instance of LineControl for the Jabber DN on the secondary node. Then when the link comes back up we detect a duplicate device condition since we have two instances of LineControl for the same DN.  We stop both LineControls and create a new one on the primay node.  However, we do not inform this new LineControl that the DN for the jabber client is APNS enabled.  As a result when future calls come in for this DN, CallManager will not send out an APNS notification to the jabber client.
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.