Guest

Preview Tool

Cisco Bug: CSCta35991 - SIP and SCCP devices behave differently when re-register fails

Last Modified

Jun 29, 2015

Products (1)

  • Cisco IP Communicator

Known Affected Releases

7.0

Description (partial)

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)
  • 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.