Callmanager 3.3(2c) crashes when registering trunk with gatekeeper
I m running a scenario with 2 Cisco Callmanager Cluster with a 128 kbps Frame-Relay-Link between them. One cluster is running 3.3(3), while the other is 3.3(2c). I try to configure a Gatekeeper controlled trunk between the clusters. The gatekeeper is running on a 2600series with 12.2.15T release. When I try to register both trunks with the gatekeeper, the 3.3(2c) Callmanager crashes and I can´t bring him up until I delete his trunk at all. The trunk on the 3.3(3) machine is configured the same (except for the zone...) and is running fine.
Re: Callmanager 3.3(2c) crashes when registering trunk with gate
I've been bitten by this one as well, here's the reply that I got from TAC...
It looks like you are hitting this DDTS:
CSCeb13814 - CallManager reinitiated after a H323 trunk reset
When the 3.3(2) spC server resets the gatekeeper from the call manager admin page CCM services
restart. This occurs everytime reset is used.
At the time, the workaround was an Engineering Special (ES). Because the problem was fixed I did not keep up with the current SR that fixes this. Probably just upgrade to the latest, or at least to the other cluster's rev. level and you should be ok.
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.