×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

ISDN PRI Failover with a VoIP gateway

Unanswered Question
Nov 14th, 2013
User Badges:

Hello,


I am trying to configure failover in ISDN trunks with CISCO CME. Actually failover configuration works. But because of the design of the system we have an issue:


CME---0/0/0--->Telco PRI Modem

CME---0/0/1--->VoIP Gateway PRI PORT--->VoIP


Our preference is to use port 0/0/1. And trunk group has been set in that way. If I turn off the VoIP gateway it fails over Telco PRI (0/0/0) successfully.

But if I keep the VoIP gateway turned on and just remove its network port (VoIP) it doesn't fail over to Telco since CME still sees port 0/0/1 up.


The vendor says VoIP gateway is generating cause code 34 if network is down. What should be the config on CME to make it failover to Telco PRI when it gets cause code 34 from one PRI port?


Please see the sample config below:


trunk group XXX

hunt-scheme sequential


interface Serial0/0/0:15

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn incoming-voice voice

trunk-group XXX 20

no cdp enable


interface Serial0/0/1:15

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn incoming-voice voice

trunk-group XXX 15

no cdp enable


dial-peer voice 12 pots

trunkgroup XXX

description Connection to PTT

destination-pattern 9T

direct-inward-dial


Regards,

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Ayodeji Okanlawon Fri, 11/15/2013 - 14:38
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Batuhan,


You can use IP SLA and Embedded event manager..Configuration details below...


1. First setup some IP SLA monitoring on the VOIP interface(s)


ip sla 201

icmp-echo 10.x.x.1 source-interface Loopback1


2. Then setup some tracking on the SLA object


track 200 ip sla 201 reachability


3. Then use EEM to shut down the interface Serial0/0/1:15  based on your track list:


event manager applet VoIPInterfaceDOWN
event track 200 state down
action 0 cli command "enable"
action 1 cli command "conf t"
action 2 cli command "interface Serial0/0/1:15"
action 3 cli command "shutdown"
action 4 cli command "end"
action 5 syslog priority errors msg "10.x.x.1  unpingable; shutdown serial0/1/0"

!
event manager applet VoIPInterfaceUP
event track 200 state up
action 0 cli command "enable"
action 1 cli command "conf t"
action 2 cli command "interface Serial0/0/1:15"
action 3 cli command "no shutdown"
action 4 cli command "end"
action 5 syslog priority errors msg "10.x.x.1 pingable(recovered); bringing up serial0/1/0"


Or you could also use syslog event to trigger a shut down of the serial port..Ie, when the router generates a syslog message that the VOIP interface is down, it should shut down the E1 interface in question..



event manager applet VoIPInterfaceDown

event syslog pattern "Interface FastEthernet0/1, changed state to down"

action 1.0 cli command "enable"

action 1.1 cli command "config terminal"

action 1.2 cli command "interface Serial0/0/1:15"

action 1.3 cli command "shut"

action 1.4 syslog msg "FastEthernet0/1 is unreachable; Shutting down Primary E1"



event manager applet VoIPInterfaceUP

event syslog pattern "Interface FastEthernet0/1, changed state to Up"

action 1.0 cli command "enable"

action 1.1 cli command "config terminal"

action 1.2 cli command "interface Serial0/0/1:15"

action 1.3 cli command "no shut"

action 1.4 syslog msg "FastEthernet0/1 is reachable; Bringing up Primary E1"


Please rate all useful posts


"opportunity is a haughty goddess who waste no time with those who are unprepared"

Actions

This Discussion