Did anybody have success in deploying CVP survivability tcl script?
I tried to follow CVP 3.1 SRND, the call can not be transferred to an IP phone. The testing scenario is, if the call sent to CVP/ICM doesn't get label, the cvp survivability tcl takes over, and send call to pre-defined DN. If this number is for PSTN, it is fine, however if it points to CCM/IP phone, it fails. I can see the dial-peer is triggered, but it goes nowhere.
The voice gateway is 2851 and IOS is 12.4(3b) ip voice, which is recommended in CVP 3.1 Bill of Materials.
Nice to see you have your CCIE Voice. Well done :)
This is a defect that I had found in my current deployment. Current news is it is fixed in 12.4(7c) due out soon........
A workaround I have used is to reply with labels that are prefixed with a digit. Then use Call manager to do a translation to the real numbers. This way the unregistered numbers do not effect you. A not elegant workaround but it works.
Thanks for the information. I loaded IOS 12.4(7b) into gateway, it still doesn't work, the symptom becomes, the ip phone can be rung, however, when picked up, the call is not connected, returned 'fast busy' tone. It seems the signaling path is established, but rtp is not.
This H323 code is the same for all the platforms (5x, 3x, 2x gateways).
1. Turn on "debug h225 asn1" on the 2851 (only turn on off-hours since it is very verbose) and make sure you see the H225 setup message going out to CCM with a guid that does not contain all zeroes. If it looks like a valid guid, then the bug is fixed.
2. Does the phone ring? If it does and then drops, it is a different issue and sounds more like a codec incompatibility. What codec does the phone support when talking to the 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.