Cisco Bug: CSCta76413 - CTI does not receive CtiOpenLogicalChannelNotify from StationD
Feb 22, 2014
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: After the PGs had been rebooted and Mobile Agents, whose CTI Ports (LCPs and RCPs) were affected, logged in they were not able successfully establish any calls. When an affected Mobile Agent goes into a ready state and a call is delivered to and answered by the agent, the audio/media may never establish and the call may fail with cause code "47" (Resource Unavailable) after the 12 second MXTimer pops. Conditions: The customer had two PGs opening/registering affected CTI Ports at various times in FirstParty and ThirdParty modes during the time when both PGs were rebooted. Both of these PGs were using the same application user and only one of the PGs would be active at any given time. The customer also had a 3rd party call recording/monitoring application named Witness which had the same affected devices open in ThirdParty mode on various nodes in the cluster. It is believed that this configuration and sequence of events triggered StationD to lose knowledge about the correct node(s) which should have received the media events such as CtiOpenLogicalChannelNotify.
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