Configuring CUCM outbound GW failover (there is more than

one way)
Leave a commentPosted by Randall Saborio on August 23, 2011
On CUCM, when we want to route out calls through a group of alternalte H.323 gateways, we
are usually required to set the following service parameter:
Stop Routing on Unallocated Number : False (Default: True)
Description: This parameter determines routing behavior for intercluster trunk calls to an
unallocated number. An unallocated number represents a dialed directory number that does
not exist in a Cisco cluster. Valid values specify True or False. When the parameter is set to True
and a call that is being routed to a remote Cisco cluster through a route list is released by a
remote Cisco CallManager because of the unallocated number, a local Cisco CallManager will
stop routing the call to a next device in the route list. When the parameter is set to False, the
local Cisco CallManager will route the call to the next device.
The reason for this is because when you sent out a call to an H.323 gateway, and for example,
the PRI circuits on the gateway are down for whatever reason, the H.323 gateway will mark the
outbound pots dial-peers as down so they are not taken into account for dial-peer matching.
In my opinion, the correct would be for the gateway to return us that the circuits are
busy/unavailable instead of Unallocatd Number.

How to accomplish this

Method 1
Using the global command no dial-peer outbound status-check pots
VG1(config)#no dial-peer outbound status-check pots
VG1#show dial-peer voice sum
AD
TAG

PRE PASS
TYPE MIN OPER PREFIX

10

pots up up

11

pots up up 1

911

OUT

DEST-PATTERN
0

FER THRU SESS-TARGET

down 3/0:23

91[2-9]..[2-9]..- 0

down 3/0:23

09[1-4,6-9]..- 0

down 3/0:23

.
901
.

pots up up

STAT PORT

902

pots up up

09[1-9]..

down 3/0:23

903

voip up up

09[1-4,6-9]..- 0 syst ipv4:192.168.207.10

voip up up

09[1-9]..

.
904

20001 pots up up

0 syst ipv4:192.168.207.10

A001$

50/0/1

20002 pots up down

50/0/2

20003 pots up down

50/0/3

20004 pots up down

50/0/4

20005 pots up down

50/0/5

500

voip up down

0 syst

Now dial-peers with OUT STAT set to down will still be matched for dial-peer matching. If the
matching dial-peers are down, the gateway will now return a Circuits busy to CM.
Source:
http://www.cisco.com/en/US/partner/docs/ios/voice/command/reference/vr_d1.html#wp145913
9

Method 2
Using q850 cause code mapping on gateway
This can have many other purposes as well, as allows us to map any q850 disconnect cause to
any other we would like.
In this example, we would map the cause code 1 to cause code 17.
CUCM-3845-B#conf t
Enter configuration commands, one per line. End with CNTL/Z.
CUCM-3845-B(config)#applic
CUCM-3845-B(config)#application
CUCM-3845-B(config-app)#map
CUCM-3845-B(config-app)#map
CUCM-3845-B(config-app-map)#q850
CUCM-3845-B(config-app-map)#q850-cause 1 q
CUCM-3845-B(config-app-map)#q850-cause 1 q850-cause 17
Can you comment on specific cases where you have used either method or on possible pros or
cons for each?