CUCM -> PRI gateway over SIP trunk failover when PRI goes down

[ripcisco]

Hi all,

I have a financial customer who has requested SIP TLS for all gateway signalling. For failover I have a couple of gateways with a single PRI in each. Is there a neat way to take the SIP trunk out of service if the PRI goes down in the primary gateway so CUCM can failover to the second gateway ? I've considered routing the call back to CUCM from the failed gateway with a steering code & have CUCM reroute out the second gateway but that seems a bit clunky. CUCM10.5 & IOS15.4

Thanks in advance

Paul

[will.alvord]

You can enable options ping under the sip profile for the trunk. I've used options ping on cube for years but haven't used it on cucm yet, so not 100% sure that there's not more to the config then that but that'll be a good start.

[ripcisco]

Thanks will. The trunk to cucm will still be up even if the pri goes down. Can options ping take the sip trunk down from the gateway side if the pri goes down ?

[will.alvord]

Enable OPTIONS Ping to monitor destination status for Trunks with service type "None (Default)"

Check this check box if you want to enable the SIP OPTIONS feature. SIP OPTIONS are requests to the configured destination address on the SIP trunk. If the remote SIP device fails to respond or sends back a SIP error response such as 503 Service Unavailable or 408 Timeout, Cisco Unified Communications Manager tries to reroute the calls by using other trunks or by using a different address.

If this check box is not checked, the SIP trunk does not track the status of SIP trunk destinations.

When this check box is checked, you can configure two request timers.

[Derek Winchester]

There seems to be no resolution to this one, and I am curious as well. The options Ping only monitors when the trunk is down not when the PRI goes down. It seems that there should be an option to bind the isdn status to the sip trunk, but that would be more in lines with a backhaul and for that, there is nothing to bind isdn to sip. 

[Mohammed al Baqari · Accepted solution]

Hi,

Use this configuration on your routers (voice gateways) and it will do the job. Note that you need to change the interface (marked in red) based on your controller type (E1/T1) and controller number (0/0/0 or 0/0/01 etc).

event manager applet SHUTDOWN_SIP
 event syslog pattern "Line protocol on Interface Serial0/0/0:15, changed state to down" period 1
 action 1.0 cli command "enable"
 action 1.1 cli command "config t"
 action 1.2 cli command "voice service voip"
 action 1.3 cli command "sip"
 action 1.4 cli command "call service stop forced"
 action 1.5 syslog msg "SIP Services Brought Down by EEM"

event manager applet BRING_UP_SIP
 event syslog pattern "Line protocol on Interface Serial0/0/0:15, changed state to up" period 1
 action 1.0 cli command "enable"
 action 1.1 cli command "config t"
 action 1.2 cli command "voice service voip"
 action 1.3 cli command "sip"
 action 1.4 cli command "no call service stop"
 action 1.5 syslog msg "SIP Services Brought Up by EEM"

[Trisha Vasquez]