I have a two server call manager cluster. I have my router with PRI setup with two dialpeer's, the first one sends calls to the publisher and the second one sends calls to the subscriber.
This morning we took the publisher down to test failover to the subscriber. When we did that, inbound calls did not work. If I shut down the dial-peer that points to the publisher, then inbound calls worked.
Could you possibly post the relevant configurations from you voice gateway?
A sample dial-peer config that I know works:
dial-peer voice 2001 voip
description Connection to Primary CM
session target ipv4:10.3.4.21
dial-peer voice 2002 voip
description Connection to Secondary CM
session target ipv4:10.3.4.20
The key is that you want to make sure that the destination-patterns are the same. If the dial-peer to your publisher was more specific and matched the ingress calls, it would always be preferred which would lead to a situation like the one you describe.
You could also look at tweaking the TCP setup timers (using "h225 timeout tcp establish" command) though if you say the calls are completely failing, look at your dial-peer destination-patterns first.
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.