Cisco Bug: CSCum92449 - MTP allocated for conference call with MCU result in audio call
Feb 04, 2017
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: Party A & Party B are in point to point Video call. Part A conferences Party C into the call. This should result in Video conference. However, Party B fail over to audio only call. During the conference, when Party A is trying to dial to Party C, Party B is kept on Hold. When Party A completes the conference by pressing Conference tab again, Party B is disconnected from MoH & connected into the conference. As Party B`s CSF Device is getting re-directed to MCU Conference Bridge, CSF disconnects to the MOH it was previously connected. 33855119.000 |07:54:39.740 |SdlSig |SIPStopStreaming |active |SIPCdpc(2,100,75,9960) |SIPInterface(2,100,69,6342) |2,100,34,1.21^*^* |[R:N-H:0,N:3,L:0,V:0,Z:0,D:0] ClearType=0 StoppedBy=0 DisconnecType=0 StopStreamingReason=0 stackIdx=0 ReconnectPending=F forceStop=F SIPInterface of CSF sends disconnect to SIPCdpc of CSF , which results in the resetting of DTMF. Later for INACTIVE Offer/Answer Exchange, to break the media(CSF and MOH), SIPCdpc resets the DTMF value with the Default Values, ie OOB and reports the same To CallControl via CcUpdateRegistration signal. This results in DTMF mis-match resulting in MTP being allocated for the call. Hence, the Party B`s call in the conference is audio only. Conditions: During video conference initiation the end-point put on hold during the conference is a SIP endpoint.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases