Co-resident CVP Call Server/VXML Server - Using Call.RoutingClient
I recall looking at this a while ago (see the SRND page 12-2) and thinking it provides a neat solution for sites without a CSS or ACE to completely balance the VXML load.
The VXML Application (Studio app) would always run on the same machine as the Call Server handling the call, providing some degree of fault tolerance. If the whole machine is down, the SIP Proxy or SRV won't choose that Call Server from the voice gateway, so there would be no attempt to run the VXML app on the box. And if you had the Web server there too, you can send Call.RoutingClient to the VXML app to make it look for WAV files on the same box. Logs for the one call would be on the same box too.
The idea is simple: set the ECC variable media_server to concatenate("http://",Call.RoutingClient,":7000/CVP") and create a matching ip host table entry - something like
ip host CVP1.RC 192.168.0.2
ip host CVP1.RC-backup 192.168.0.3
It works very nicely for calls from the PSTN.
But I was experimenting with this for Recording Agent Greetings - and this call comes from the agent's phone/desktop. Surprisingly, it did not work. And the reason: even though there is a Send To VRU to get the call from CUCM to CVP, CUCM is still the routing client so we can't use the same trick.
Somehow I thought the Send To VRU would change the RC.
The method also won't work for other CUMC-originated calls: such as warm transfer to a Studio app or calling a self-service Studio app from an IP phone.
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.