Guest

Preview Tool

Cisco Bug: CSCuj82211 - No Ringback to Remote Destination phone using Jabber Extend and Connect

Last Modified

Nov 27, 2020

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

10.0(1.10000.24) 9.1(1.20000.5) 9.1(2.10000.28)

Description (partial)

Symptom:
Jabber Windows client is configured to use Extend and Connect feature. With this feature, calls can be answered on any of the remote destination (Mobile, Home)that is configured on the CTIRD device (which is a device type in CUCM). Calls made from Jabber client to the PSTN number will first ring on the Remote Destination. Remote destination answers the call and then a second call is initiated by CUCM towards the actual Called number on PSTN. 

The ringback received in the form a 183 Progress message for the actual called party ringing, should be relayed by the CUCM to the remote destination. 

However, this does not happen & the calling party at the remote destination hears dead air until the call is answered by the actual called party. 

When the call is answered by the called party, there is two-way audio.

Note that the issue only occurs when the actual called number is a external PSTN number & the ringback is received in the form of 183 progress message where the telco wants to play the ringback message.

Conditions:
When using extend & Connect feature
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.