Route Lists and Route Groups

8/7/2019 Route Lists and Route Groups

1/34

1

Route Lists and Route Groups

The information in this presentation is

directly quoted from the

Cisco CallManager Fundamentals book.

Many thanks for the authors and for the

Prentice Hall publishing company for

allowing me to use the book

(information, diagrams, topologies, and

tables) in my presentation.


2/34

2

Why?

When your network grows beyond thecapacity of a single gateway, you areposed with a problem: how do you

configure CM so external calls can useboth gateways, and how can you makeCM choose the correct gateway when onlyone gateway has trunks available?

Route lists and route groups are theanswer.


3/34

3

Route List and Route Group

Operation A route group represents a list of several individualgateways. When a route group receives a call, it offers the call to the first

device in its list. If the device can accept the call, the route

groups job is done. If, however, the device rejects the callbecause it is being fully utilized or it is out of service, the routegroup then offers the call to the next device in its list. Only whenall devices have rejected the call does the route group reject thecall.

A route list is an ordered list of route groups Where a route group sequentially offers calls to devices in its list,

a route list sequentially offers calls to route groups in its list. Aroute list rejects an outgoing call only when no route groups in itslist can accept the call.


4/34

4

Route Lists and Transformations

Route lists provide you with additional routingcontrol

The calling and called party transformations onroute lists allow you to override, on a route-by-route basis, the calling and called partytransformations that you assigned to the routepattern that selected the route list.

You may need to override transformations on aparticular route basis to properly format a

number for the gateway that receives a call. Transformation rules on a route overridestransformation rules on a route pattern

The term Route refers to the association between aroute list and one of its route groups


5/34

5

Route Lists and Route Groups-Case


6/34

6

Case-Continued Company XYZ with two locations: Dallas and San Jose

Two equivalent gateways in San Jose and one gatewayin Dallas

Route Groups: SanJoseRoutGroup:

MGCP Gateway in SJ (VGW1)

H.323 Gateway in SJ (VGW2)

DallasRouteGroup: Voice gateway in Dallas (VGW3)

Route List (Toll Restriction): SanJoseRouteGroup

DallasRouteGroup:

Route Pattern: 9.@ Route Filter: Area-Code ==408

Dialing Transformations on the route: Convert the 12 digit number that the user dials from Dallas to a

7-digit number for routing on the San Jose PSTN

Example: Convert: 9 1408555 1212 to 555 1212


7/34

7

Case-ContinuedW

hen a user in Dallas dials 9 1408

555

1212

the route list performsthe following steps:

1. First, it attempts to offer the call to the first gateway listed I theSan Jose gateways route group. This gateway is an MGCPgateway connected to the San Jose PSTN. Because CMmanages the state of the trunk interfaces of MGCP gateways.The gateway component can immediately reject the call attempt.

2. Second, it attempts to offer the call to the second gateway listedin the SJ gateway route group. This gateway is an H.323gateway, which manages the state of its own trunk interface. CMoffers the call to the gateway, but the gateway rejects the call.

3. The SJ route group rejects the call that the DallasToSanJoseroute list extended, so the DallasToSanJose attempts to route the

call over the PSTN. It extends the call to the Dallas gatewaysroute group. The transformation that the route pattern applied tothe called number to convert it to 555 1212, however, wouldprevent the call from routing from Dallas, so dialing transformationon the route list override the called party transformation the routepattern applied, the route converts the number to 1 408555 1212and then offers the call to the Dallas gateway.


8/34

8

Assigning Gateways to Route Groups

and Route Groups to Route Lists In which order should you build your route

list structure???

First you start by configuring gateways, whichyou then place into route groups. Once the

route groups are organized, you place them in

route lists. Finally, you control routing to

these route lists by assigning route patterns.


9/34

9

Creating Gateways

Types of gateways:

MGCP

H.323

SIP


10/34

10

Assigning Gateways to Route

Groups Each gateway endpoint a CallManager route to can existin , at most, one route group.

An Endpoint differs based on the type of gateway(device Vs interface)

Only gateways that are equivalent for routing purposescan be in the same route groups Example: VGW1 and VGW3 even though they nominally

provide access to the same place, they can not be in the sameroute group because they are not equivalent for routing

purposes: Calls from Dallas to SJ through VGW3 requires 11-digit dialing while calls through VGW1 dont. (same applies forVGW2 and VGW3)

A route group can list its gateways in only one order.


11/34

11

Assigning Route Groups to Route Lists

Route Lists are ordered lists of route groups. Although a given gateway end point can exist in

at most one route group, a route group can exist

in any number of route lists.

A route list is simply a gateway search pattern.Generally, for every unique order in which you

wish to attempt to route calls to gateways, you

need one route list.

The purpose of a route list is wholly determined

by the route pattern you assign to it and the

route groups it contains.


12/34

12

Assigning Route Groups to Route Lists

1 2 3 4


13/34

13

How Calling and Called Party

Transformations Work Each route contain the same calling an called party

transformation that exist on the route pattern itself.

The calling party transformations are : The Prefix Digits

Calling Party Transformation Mask

And the Use External Phone Number Mask

The called party transformations are: Digit Discarding Instructions

Called Party Transformation Mask

And Prefix Digits

When you add a Route Group from the Route ListConfiguration screen, CM Administration opens theRoute Details Configuration screen, where you cancustomize the dialing transformation that CM applieswhen it offers a call to the selected route group from thecurrent route list.


14/34

14

Route Lists and Route Groups and

Toll Bypass A toll bypass configuration requires the dial plan to beable to distinguish types of outside calling. For instance,emergency calls must route out only those gatewayslocal to the calling user. Local calls should preferentially

rout out gateways local to the calling user. On the otherhand, calls to other LATAs where you manage gatewaysneed to route preferentially to those remote gateways.Finally, long distance and international calls can routeout any gateway in the network . The need to distinguish

between types of PSTN calls requires the use ofroutefilters.


15/34

15


Toll Bypass When a user dials along distance number that routes toa remote gateway, usually the number the user dial isnot a valid number when dialed from the remote gatewayitself. From the users point of view, the number is a

long distance number, so CM should accommodate along distance numbering format. For instance, NorthAmerican users typ9cally dial 11 digits when dialinganother geographic region, But the same destination asdialed by a user in the remote location is either seen or

ten digits. Allowing the call to route properly once itreaches a remote location requires using called partytransformations.


16/34

16


Toll Bypass Calling number is also an issue when a call crossesLATA boundaries. If a user in Boston places a tollbypass call through a gateway in Orlando, how shouldCM represent the calling number? If it presents A

Boston calling number, the Orlando central office maycomplain, because it dons no t recognize the number ofthe caller. It is often necessary either to transform thecalling number to an attendant number in the remotelocation or to alias the calling number to a number that is

valid in the remote location, these modifications requirethe use ofcalling party transformations.


17/34

17


Toll Bypass If locations contain more than one gateway,route lists provide a way to maximize gatewayusage.

Users in different locations need to reachdifferent location, even if they dial the same digitstrings. For instance, a user in Dallas who dials911 needs to reach Dallas emergency services,while a Boston user needs to reach Bostonemergency services. Giving different usersdifferent views of the same network requires theuse ofcalling search spaces and partitions.


18/34

18

Example


19/34

19

Example

Company ABC Two Locations Three levels of PSTN Access


20/34


21/34

21

Dallas Location

40000 is the attendant. The gateway is connected to the 555

exchange in the 972 area code. The PSTN has assigned a range of

2000-2999 to the Dallas site. For the purpose of this example, users

in Dallas dial seven digits to make local calls.


22/34

22

Building a Toll bypass configuration

Building a toll bypass configuration occurs intwo phases:

Outbound Dialing: Which includes:

Building route groups and route lists for external access, Creating route filters for different levels of user access, androuting by geographical region,

Transforming the calling and called parties,

And assigning calling search spaces.

Inbound Dialing: whic

h inc

ludes: Building translation patterns to map external phone numbersot internal extensions,

Assigning Calling Search Spaces to control the destinationinbound gateway calls can reach


23/34

23

Outbound Dialing: Route Group

and Route List Creation

Defining the route group:

Assign the SJ gateway to route group

SanJoseGateways and Dallas gateway to

route group DallasGateways.

Before defining the route lists you must

understand the concept offallback:

Fallback is the process of offering a call to alass desirable gateway after all desirable

gateways have been exhausted.


24/34

24

Outbound Dialing: Route Group and Route List Creation


25/34

25

Outbound Dialing: Route Group and Route List Creation


26/34

26

Outbound Dialing: Route Filter Creation and

Route Pattern Assignment

In All cases the route pattern is: 9.@


27/34

27

Outbound Dialing: Partitions

The enterprise rules define two locations and three levels of

outside calling. This argues for six different partitions for outside

dialing plus a partition for company ABC for inside dialing.


28/34

28

Outbound Dialing: Assigning Route

Pattern and Filter to Route Lists


29/34

29

Outbound Dialing: Applying Calling

and Called Party Transformations


30/34

30

Outbound Dialing: Applying Calling

and Called Party Transformations


31/34

31

Outbound Dialing: Calling Search

Space Assignment

Create the calling search spaces and assign them to calling devices


32/34

32

Outbound Dialing: Calling Search

Space Assignment


33/34

33

Inbound Dialing-Defining

Translation Patterns

Although this example permits the use of gateway called party transformations

to convert an inbound phone number to an extension number, configuring themap using translation patterns saves some reconfiguration effort if you ever

purchase another phone number range from the phone company.

San Jose gateways and Dallas gateways need individualized translation

patterns.


34/34

34

Inbound Calling Search Spaces

Route Lists and Route Groups

Documents

Transcript of Route Lists and Route Groups