Cisco Bug: CSCuq34040 - CallInfo is incorrect after call has been in a second conference
Jul 03, 2017
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: A second conference call causes extra LINE_NEWCALL and IDLE event for the remaining call Conditions: - Using MonRec application - After the first conference is dropped and another call is made for the second conference, the CallInfo value is ONHOLD state, which is incorrect on the remaining call.
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