Guest

Preview Tool

Cisco Bug: CSCuo48985 - transfer a secure call from SIP secure-device to non secure phone fails

Last Modified

Feb 02, 2017

Products (7)

  • Cisco Unified Communications Manager (CallManager)
  • Cisco Intercompany Media Engine
  • Cisco Unity Connection Version 9.1
  • Cisco Business Edition 5000 Version 9.1
  • Cisco Business Edition 6000 Version 9.1
  • Cisco Unified Communications Manager Version 9.1
  • Cisco Unified Communications Manager Session Management Edition

Known Affected Releases

9.1(2)

Description (partial)

Symptom:
Call flow

SIP Jabber (security) -> native queue cucm -> Annunciator (security) -> SCCP (no security, BiB)

Once the jabber is transferred to the SCCP phone the call drops with a disconnect code = 47

On the traces we can see
00626681.019 |16:46:25.216 |AppInfo |!!ERROR!! -AgenaInterfaceBase-(310)::sendErrorToMX,
ERROR handleOLC - crypto mismatch and peer has rtp profile only

It means that one side is using security and the other side it is not

CUCM should negotiate the call between jabber and SCCP without security

after sending out a 183 progress message to the jabber client, the sip device layer does not stop an internal timer.   Because we do not stop the timer, when the timer fires we send another update with SDP out to the jabber client and this causes the problem

Conditions:
CUCM 9.1.2.12034-1

jabber with security enable  >  queue in CUCM > ANN > SCCP (no security and BiB)
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.