Check the following CCM Service Parameter -- StopRoutingOnUserBusyFlag : Specifies when set to true, that if a call being routed through a route list detects the associated ?cause? during the release of the call, no re-routing to the next device in the route list is attempted and the call is released with the associated cause.
If the ports on the first GW have been "busyied out", set the parameter to false before testing.
Only then will subsequent route groups be attempted. Set the StopRoutingOnUserBusyFlag to FALSE.
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.