I have a simple IVR configuration that works fine, but the users are asking why they see the CTI route point information during call alerting instead of the caller's caller-id. They do see the caller's caller-id after they connect, but not during alerting.
Does anyone know how I can get the caller's caller-id to show up during alerting instead of the CTI route point?
This is a fundamental limitation to CCX and how it offers calls to an agent. The caller remains on a CTI Port of the CCX box until an agent accepts the call. At that point the call is transferred. Because of this, the Calling Party information is that of the CTI Port until the agent takes the call. My understanding is that this is possible with ICM/UCCE but I'm not familiar with the method that ICM uses to achieve this. I would recommend having your CAM submit a feature request.
There is some scripting that you can do to get around this. The way I do it is that when I select the agent, I don't connect. I set the agents extension to a string, then do a call redirect to that string. That will present the caller id to the agent, but causes some other issues.
If I understand correctly, you're doing a call redirect to a hunt pilot on CM? When you have a call redirect script, it is like a blind transfer where it will send the caller-id of the original caller, not the CTI port forwarding the call.
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.