CUCM: Outgoing call restriction with route pattern

The cisco 2951 is a 2-RU size router with 4x FXOs module. One phone provider carrier line was connected to the FXO ports. The Cisco 2951 was configured as MGCP, which was registered to CUCM server cluster. This post shows how call can be initiated from internal to the external such as mobile phone and external fixed line. When internal users attempt to make an outgoing call, user has to dial 9 then followed by the number that the user is calling.

Cisco 2951 configuration

The external phone line was connected to the 1st port of the FXO.

Primary and secondary CUCM server was configured in the router, a dial-peer was configured for the external phone line. The router was configured as a MGCP gateway.

Below is the sample configuration related to voice gateway.

The ccm-manager is the call manager which is for gateway to register itself, the mgcp call-agent is to facilitate outgoing and incoming call.

interface GigabitEthernet0/0
 ip address
 no ip route-cache
 duplex auto
 speed auto
voice-port 0/1/0
 timing hookflash-out 50
ccm-manager redundant-host
ccm-manager mgcp
no ccm-manager fax protocol cisco
ccm-manager music-on-hold
ccm-manager config server
ccm-manager config
mgcp call-agent 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
mgcp package-capability sst-package
mgcp package-capability pre-package
no mgcp package-capability res-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp validate call-agent source-ipaddr
mgcp fax t38 inhibit
mgcp profile default
dial-peer voice 999010 pots
 service mgcpapp
 port 0/1/0

Cisco 2951 Gateway

The next thing to do is to provision the gateway onto CUCM. The process is the same as adding VG224 and VG204 which I have written the post, adding gateway is relatively easy, simply go to Device > Gateway.

Route pattern

Before creating route pattern, the followings have to be created first.

1. Parition

2. Route Group

3. Route List

The created route pattern has to be associated with partition and route list. The route group is associated with route list. There are many dependencies like these in CUCM which makes CUCM complicated to configure.

Route group
From CUCM, Call Routing > Route Group.

Name the route group.

Route List
Create the route list and associate it with the route group.

From CUCM, Call Routing > Route List

Click Add Route Group and add the created route group.

Route Pattern

From CUCM, Call Routing > Route Pattern

These are the patterns which I have previously created.
The route pattern is to specify the pattern of the dial. “9.” means to dial out press 9, the dot is a delimiter for CUCM to remove the prefix, anything before the dot is removed by CUCM. “[689]” is the regular expression, which means number that starts with 6,8 or 9, “XXXXXXX” is the arbitrary number which user will press, each “X” represents one unknown number.
Under Called Party Transformation, select Predot in Discard Digits. Whichever number is before the dot will be discarded.
Finally save the route pattern

Parition has to be created before creating Route Pattern, creating partition go to Call Routing > Partition.

Create partition.
Associate Calling search space with partition.

Associate calling search space to IP phone

Lastly choose the IP phone and associate the phone with the calling search space that contains the partition which is associated with route pattern. Now this is another example showing CUCM is very complicated to configure.

Forced authorization code

You can enforce password/PIN if a user is attempting to make an outgoing call. From CUCM, Call Routing > Forced Authorization Code

A created Forced Authorization Code profile.

Creating new forced authorization code.
In the route pattern, check the box which says “Required Forced Authorization Code”, and put in the Authorization Level number.

One thought on “CUCM: Outgoing call restriction with route pattern

  1. Pingback: CUCM 12 - blog

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s