IPCC Enterprise Gateway Deployments: A conferenced in agent loses the connection when the agent who first received the call hangs up
m (1 revision)
Latest revision as of 23:53, 12 March 2010
A conferenced in agent loses the connection when the agent who first received the call hangs up
|Problem Summary||A conferenced in agent loses the connection when the agent who first received the call hangs up.
The call flow: (1) X initiates a call and the call goes through Unified CVP and then Unified ICME. (2) Unified ICME routes the call to Agent A on Unified CM cluster 1. (3) Agent A conferences the call with Unified IP IVR on Unified CM cluster 2. (4) Agent B on Unified CM cluster 2 becomes available and his phone rings. (5) Agent A releases the call. (6) Agent B answers the call and loses the connection.
|Possible Cause||In the Unified CM configuration for an inter-cluster (non-gatekeeper controlled) trunk, Media Termination Point Required had not been checked.
Media Termination Point Required is used to indicate whether a media termination point (MTP) is to implement features that H.323 does not support (such as hold and transfer).
|Recommended Action||In the Unified CM configuration for an inter-cluster (non-gatekeeper controlled) trunk, you must check (turn on) Media Termination Point Required for the Non-Gatekeeper Controlled ICT trunk on cluster 1 which communicates with Cluster 2 so that the voice path is maintained between Agent B and X (the customer).
For further information on this topic, see Configuring Trunks in the Cisco Unified Communications Manager Administration Guide.
|Release||Release 7.5(1) and 8.0|
|Associated CDETS #||None.|