Can you get these debugs? It will shed more light on what is happening from the gateway perspective. The GW may not be sending an alerting if it never gets it from the other side.
debug h225 asn1
debug h245 asn1
debug voip ccapi inout
debug isdn q931
Collect the debugs in the following manner:
Router(config)# service sequence Router(config)# service timestamps debug datetime msec Router(config)# logging buffered 10000000 7 Router(config)# no logging con Router(config)# no logging mon Router(config)# voice iec syslog Router# term len 0 Router# sh logg
Basically, since the call was failing, I wanted to see what the VoIP signaling behavior was to determine the root cause of the disconnect. i.e. I just needed more information than was in the original post.
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.