We can queue and transfer a Call Manager originated call if the CTI Route Point
is called directly from a call manager extension.
If we take a call that originated from CVP and then transfer it to the route
point, the call is queued, but the agent is placed in a reserved state, and the
call is never terminated on the available agent's phone.
We believe that we have a configuration problem on the gateway or gatekeeper.
We need a sample configuration of a working gatekeeper and gateway config for the call manager originated call.
We have tried everything within our limits, and need some urgent help with this
The Gatekeeper is configured with a zone prefix for the translation route DNIS 95* in the CVP zone. This is the only reference on either gateway or gatekeeper. Should we also have a dialpeer configured on the gateway, and if so, can someone provide a sample of what ir should look like.
When I experienced this situation (with a 3rd party IVR using an H.323 integration), I found that a Media Termination Point was needed. Also, check the transfer method used by CVP. CallManager does not support H.450.2 transfers without use of an intermediate hairpin gateway.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.