anyone knows how to configure the automatic fallback on a cucm cluster? so when the first call agent of a CM Group becomes available again the phone re-register with it again automatically without administrator intervention.
yes I know that for HA the cluster must have cm groups with the call agents that you want to use, but I am asking for fallback configuration, after a phone unregister with the primary call agent because this is unavailable, register with the second call agent and when the primary become available again how to fallback to this call agent, I want to configure this fallback automatically.
When you configure CM group then you dont need to configure anything to have automatic fallback.
When a phone registers to secondary call agent in case of primary call agent dont acknowledges SCCP/TCP keepalive messages sent by phone, that time phone also keep sending keepalive messages to its older primary call agent and when it (call agent) starts to ACKd then phone re-register to its old primary call agent automatically.
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.