Re: Intercluster problem between CCM3.1(3a) and 3.3(3)
I have seen starnge behaviour when using ICT's with 3.3 and 3.1. make sure that the Call Manager that you soecified in the gateway config is the same that the phone is registered to. Hope that makes sense. It seems that you need to enter the Call Manager in the setup in 3.1 that the phones/ gateways are registerd to.
Two clusters, one with CCM 3.3 and the other with a previous release, are linked by a gatekeeper- controlled trunk. In CCM 3.3, multiple gatekeeper controlled trunks can be configured and routing
is done according to port (each trunk will have its own port). In previous releases, there is only
one gatekeeper controlled anonymous trunk and it utilizes a known port number. When routing
between the clusters, the port numbers will not coincide and the routing will fail.
Further Problem Description:
The problem has been resolved by introducing a new Call Manager Service
Parameter "Device Name of GK Controlled Trunk that will use Port 1720" that will allow a Gatekeeper Controlled trunk to use the well known port 1720. However, this imposes the restriction that a Gatekeeper Controlled Inter-Cluster Trunk and a Non-Gatekeeper Controlled Inter-Cluster Trunk should not be configured together between the same CallManager pair, i.e. If a Gatekeeper Controlled Inter-Cluster Trunk is configured then no other Non-Gatekeeper Controlled Inter-Cluster Trunk should be configured between the same Call Manager pair.
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.