Guest

Preview Tool

Cisco Bug: CSCta22478 - CUBAC should interpret the CtiProgressingState received from the CUCM

Last Modified

Jul 05, 2015

Products (1)

  • Cisco Unified Attendant Consoles

Known Affected Releases

2

Description (partial)

Symptom:

When CUCM is using SIP as the signaling protocol to generate outgoing calls, the CUCM may receive some 183SDP message with the PRACK method required (require: 100Rel). This is interpreted by the CTI Layer on the CUCM that generates a CtiProgressingState to the CUBAC server. The CUBAC server seems to not interpret this message. 

Observed behavior: 
When CUBAC console generates an outgoing call, the console can see the call but it remains in OffHook state while the destination is Ringing.

Conditions:
When CUCM is using SIP as the signaling protocol to generate outgoing calls, the CUCM may receive some 183SDP message with the PRACK method required (require: 100Rel). This is interpreted by the CTI Layer on the CUCM that generates a CtiProgressingState to the CUBAC server. The CUBAC server seems to not interpret this message.
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.