In the Cisco CallManager 5.1(1), when a call is parked, it cannot be retrieved on any extension.
In addition, when the conference button is hit during a call in order to bring in a third participant, the third participant can be called, but a conference is not established between the three participants when the conference button is hit again. When the conference fails, the Cannot complete conference error message appears and the original called party is dropped from the call, but the second call remains active.
This issue occurs in these IP Phones:
In order to resolve this issue, disable the Advertise G.722 Codec Cisco CallManager Enterpise Service Parameter, and reset the device pools that contain these phone types:
This is further documented in Cisco bug ID CSCsi61965.
When the service parameter is enabled, it allows these TNP/third generation Cisco IP Phones to negotiate and use the G.722 codec when calls are within the same region. Because of a lack of support for the codec type, this causes interoperability problem symptoms, such as call disconnects, for these features:
Instructors are struggling with student participation in the virtual instructional world. We do not require students to have their cameras on because we don't want students to feel uncomfortable with the locations they are accessing their courses fr...
My org just received the 40.10.6 update, and although I think that version should allow for the hard muting of attendees in a Webex Meeting it does not seem to be a feature yet. Is there somewhere this needs to be enabled? I looked at site settings but do...
My organization is using Webex Teams UC Calling in multiple instances. Webex Teams Desktop for WindowsWebex Teams VDI in a XenApp environment (Windows based)Webex Teams VDI in a XenDesktop environment (Windows based) Users are having to in...