Cisco Bug: CSCta35991 - SIP and SCCP devices behave differently when re-register fails
Jun 29, 2015
- Cisco IP Communicator
Known Affected Releases
Symptom: SIP and SCCP devices behave differently when re-register fails Conditions: SIP CIPC A places call to SIP 7970 B. During the call make sure that SIP CIPC A loses connectivity towards CUCM, but still has connectivity to SIP 7970 B. RTP packets will flow between SIP CIPC A nad SIP 7970 B. SIP 7970 B must have connectivity to CUCM. When SIP CIPC A tries to re-register to CUCM it will fail and the call will be dropped. This does not happen if SCCP protocol is used.
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