Cisco Bug: CSCur69469 - After fallback, route point 913 doesn't register to pub
Mar 05, 2018
- Cisco Emergency Responder
Known Affected Releases
Symptom: Steps to reproduce: Disable the NIC on the CER Publisher to simulate loss of network connectivity Wait for route point 913 to register to CER Sub. Bring back the CER pub back onto the network. Call Manager GUI does not show the 913 CTI Route Point as registered back to the CER Publisher. However Call Manager CTI traces and CER Jtapi traces show the 913 Route point as re-registered back to the CER Publisher. Conditions: CUCM Version: 188.8.131.5200-12 10.11.32.11 CUCM version: 184.108.40.20600-10 172.29.173.11, 10.128.32.11 CER Version: 220.127.116.1100-3 Abrupt loss of network connctivity. Gracefully stopping and restarting the CER Service will not recreate this issue.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases