The problem is more complicated than you think. It is not a question of stopping and starting mgcp on the router, we have over 100 PSTN gateways, i can not be going this for all the routers. The question is what does rebooting the subscriber force the gateway to register with the publisher and what should i add to the config so that when the subscriber does come back up the gateway should register back to the subscriber. Any Cisco Best practices would be highly appreciated.
above is the command we issue our gateway to register with secondary or primary in case primary or secondary goes down.
Cisco IOS gateways can maintain links to up to two backup Cisco Unified CallManager servers in addition to a primary Cisco Unified CallManager. This redundancy enables a voice gateway to switchover to a backup if the gateway loses communication with the primary. The backup server takes control of the devices that are registered with the primary Cisco Unified CallManager. The second backup takes control of the registered devices if both the primary and first backup Cisco Unified CallManager fail. The gateway preserves existing connections during a switchover to a backup Cisco Unified CallManager.
When the primary Cisco Unified CallManager server becomes available again, control reverts to that server. Reverting to the primary server can occur immediately, after a configurable amount of time, or only when all connected sessions are released.
Switchback is the process a voice gateway uses to reestablish communication with the primary Cisco Unified CallManager server when the server becomes available again. Switchback can occur immediately, at a specified time after the last active call ends, or after a specified length of time.
See it should be there in config and the recommnend practice is you should set it to graceful instead of immediate bcoz in a gracefull state once the server will come back it will wait for the calls to end and then it will register with the rite server however if you will set it to immediate it will drop an ongoin calls and then will register to the server..
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.