Search this Blog

Friday, July 30, 2010

How can we configure the Route patterns in Call manager without RGL?

We would like to set that all calls to a specific destination, were commuted to a Gateway A, and if all lines are busy, these calls are switched by Gateway B.

We have the following configuration :

Actual RP:

Route Pattern* : 9199.XXXXXX Partition: Outgoing Call Gateway or Route List: 10.201.30.250

New Configuration (In mind....)

Route Pattern* : 919953.XXXX Partition: Outgoing Call Gateway or Route List: Gateway A
Route Pattern* : 919953.XXXX Partition: Outgoing Call Gateway or Route List: Gateway B
IP Address Gateway A: 10.201.30.250
IP Address Gateway B: 172.17.20.10

We had thought to create a Route Group List with the two Routers (GW 10.201.30.250 and 172.17.20.10), but the actual configuration of the Route Patterns in the Call Manager, is using the Gateways in the configuration of Route Pattern (in the configuration RGL are not set).

How can we configure this requirements without RGL?

With this configuration:

Route Pattern* : 919953.XXXX Partition: Outgoing Call Gateway or Route List: Gateway A
Route Pattern* : 919953.XXXX Partition: Outgoing Call Gateway or Route List: Gateway B
If the lines in the Gateway A are busy the call is switched to the Gateway B? Or this is achieved only by setting RGL?

Cisco Call Manager version: 4.2

Tips:

Q/ New Configuration (In mind....)

Route Pattern* : 919953.XXXX Partition: Outgoing Call Gateway or Route List: Gateway A
Route Pattern* : 919953.XXXX Partition: Outgoing Call Gateway or Route List: Gateway B
A/ You can not have two identical route patterns on the same partition.

Q/ We had thought to create a Route Group List with the two Routers (GW 10.201.30.250 and 172.17.20.10), but the actual configuration of the Route Patterns in the Call Manager, is using the Gateways in the configuration of Router Pattern (in the configuration RGL are not set).

A/ If you want redundancy in Call Manager, then you need route group and route list. If you can not add your routers to a route group is because they're already associated with route pattern(s). First, dissociate them from all route patterns, then create the route group and finally the route list. Now you can associate your route pattern(s) to the new route list. Final configuration should look similar to:

Route Group Name: My_Route_Group

Current members: 10.201.30.250

172.17.20.10

Route List: My_Route_List

Selected Groups: My_Route_Group
Route Pattern: 9199.XXXXXX Partition: Outgoing Call Gateway or Route List: My_Route_List
Route Pattern: whatever Partition: Outgoing Call Gateway or Route List: My_Route_List

Q/ If the lines in the Gateway A are busy the call is switched to the Gateway B? Or this is achieved only by setting RGL?

A/ If your gateways are H.323, there's a way to achieve redundancy without involving Call Manager. This is done with redundant dial peers. I do not recommend it because that will not achieve the highest possible redundancy for your calls. For example, if gateway A is down, calls would never be routed to router B. However, if you configure a route list then Call Manager will be able to route your calls to gateway B without problem.

Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

WT24A7JA6FWC

No comments :

Post a Comment

 
/* Google Analytics begin ----------------------------------------------- */ /* Google Analytics end ----------------------------------------------- */