I do understand the when a voice gateway is operating in MGCP mode and the WAN fails, the MGCP will fallback to h.323 and all calls on the PRI will fail becuase the gateway has no vision into the q.931 messages becuase it is backhauled to CallManager. However, once the WAN comes back online, will the calls on the PRI get bumped again becuase the gateway needs to reregister with CM and backhaul the q.931 to CM. I initially thought the switchback (immediate or graceful) defined the operation for coming out of MGCP Fallback/SRST but I now realize it is for primary/secondary failover. Is there anyway to configure it so MGCP Fallback/SRST does not knock current calls off when the CM comes available again.
The entire purpose of CM moving to MGCP (back in 3.1) was because of MGCP's call preservation capabilities.
When the MGCP gateway registers, CM sends a Audit Endpoint (AUEP) to the gateway asking it 'do you have any active calls'. The gateway responds with the active channels, and CM then knows not to mess around with them.
When the call clears, the gateway notifies CM and the gateway operates as normal.
MGCP gateway fallback supportAll active MGCP analog and T1 CAS calls are maintained during the fallback transition. Callers are unaware of the fallback transition, and the active MGCP calls are cleared only when the communicating callers hang up. Active MGCP PRI backhaul calls are released during fallback.
that was the point I was making, it has also been my experience that it works that way, the "I don't believe so" was in response to your previous post which asked if there was a away to avoid this behavior. If you do find a way please post it up here.
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.