Cisco Bug: CSCvi66491 - CTI Remote Destination not forking second call
Mar 29, 2018
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: Issue related to CTI Remote device with active remote destination. When a CTI RD has an active remote destination and a busy trigger set to 2 a second incoming call is not sent to the active remote destination. Problem When setting "busy trigger" to 2 for the extension above and the configuring "call waiting"on the cell phone of the remote destination. When a second call is placed (after the first one) to the extension above, the second call is not being sent out to the remote destination (cell phone). If the remote destination is not set to active or if a CTI Remote device is not used (just using RDP+Remote destination) this "call waiting" feature works fint. AKA, the second call is sent to the remote destination and the reciever can decide to take the second call or not. Conditions: Second call made to CTI RP does not go through.
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