I have two CallManager 3.3.3sr4a clusters in a lab environment. Each is separated by a routed network to simulate a WAN connection. I have a gatekeeper router configured on the same subnet as one CallManager. When I configure the Gatekeeper controlled intercluster trunk on the CallManager that is local with the Gatekeeper, I see the ip address of the Gatekeeper in the Gatekeeper Name field at the bottom of the trunk configuration screen in CallManager and can select it. As soon as I save the configuration, CallManager is registered with the Gatekeeper. There is no specific configuration inforamtion in the Gatekeeper that refers to CallManager, only the voice gateways. The second CallManager is on a subnet without the Gatekeeper. When I go thru the same configuration process in CallManager, I never see the ip address of the Gatekeeper in the Gatekeeper name field at the bottom of the trunk configuration screen. Therefore, I cannot save the configuration as it is a required field for CallManager. I have debugged on the Gatkeeper and never see the second CallManager try to register. I have debugged on the router in the middle and do not see a registration attempt. Is there something that must be enabled in the routed network to allow a remote CallManager to register with a Gatekeeper not on the same subnet? Is there something else in CallManager that enables the ip address of the Gatekeeper to show up in the configuration screen? What am I missing?
I assume that both CallManager you mention has publisher and subscriber relationship.
When you add gatekeeper on publisher but you cannot see the same gatekeeper on subscriber, this problem can be database replication issue. The replication issue can be come from the network configuration. Try to update other record on the subscriber and see any error pop up --> you have the problem.
For the issue about gatekeeper registration, CallManager uses device pool to make the decision which CallManager go to register with gatekeeper. In this case, the trunk configuration should have the device pool containing both publisher and subscriber in the right order.
Both CallManager servers are in separate clusters. Each is it's own Publisher. Is it not possible to use a single gatekeeper with separate CCM clusters? Or in order to use a single gatekeeper must all CallManager servers be in the same cluster?
I have tried building the Gatekeeper controlled Intercluster trunk with the IP address and the name. Neither will enable the IP address of the Gatekeeper to show up in the Gatekeeper Name field at the bottom of the configuration screen like it does on the CallManager that is on the same subnet as the Gatekeeper.
In Gatekeeper I have two local zones configured, but neither of them point to either CallManger. The CallManager that is on the local subnet with the Gatekeeper registered immediatley and did not require any other entries for it in the Gatekeeper. My understanding (limited) is that the zone registration commands are for IOS gateways. Is this not correct? Can I build a zone registration for CallManager? If so what is the syntax? When you build an entry for an IOS gateway you have to specify the gateway alias on the gateway so that the Gatekeeper will recognize it. Is this possible with CallManager?
Not sure if there is a difference between 3.3(2) and 3.3.3(sr4a) as this is my first Gatekeeper.
The CallManagers do not have to be on the same subnet as the Gatekeeper (At least not that I am aware of). Is your second CCM on a different domain, or do you just have two different subnets for testing purposes?
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.