Ask The Expert - CUCM 10.0.1
Multiple Local Route Group
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
1
Purpose
 Prior to 10.0 CUCM release, the administrator could have only
one Local Route Group for a given Device Pool.
 This limits the capabilities and the admin would have to
configure different Route lists for different purpose like
emergency routing and secondary routing.
 With this feature we give an additional capability to add
multiple Local Route Groups and associate them with Route
Groups.
 This will reduce the number of the Route lists to be created.
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
2
Previous Release
(CUCM Admin page)
 CUCM supported only one Local Route Group to be associated
with any Device Pool. As highlighted below.
 The admin could choose to associate a Route group to this “Local
Route Group” on the Device Pool page or choose to leave it blank.
 e.g., we name this device pool as DP_SiteA and associate Local
route group with RG_SiteA.
.
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
3
Previous Release
(CUCM Admin page)
 On the Route List page, this was being displayed as :
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
4
Feature Overview (Previous Release )
CUCM B/PSTN
Route List to Site D
Cluster A
9.XXXX (Pattern)
DP_A:
Standard Local Route Group – RG_A – SIP_SiteD
Preference Order in RL
1 Standard Local Route
Group
2 RG_SiteD - MGCP_SiteD
Phone1 at Site A
DP_B:
Standard Local Route Group – <None>
Phone2 at Site B
Phone4 at Site D
DN 1000
(Emergency Route 1 )
8.XXXX (Pattern)
Preference Order in RL
CUCM C/PSTN
1 RG_A_to_E
DP_C:
Standard Local Route Group – <None>
(Emergency Route 2 )
7.XXXX (Pattern)
Phone5 at Site E
Phone3 at Site C
Preference Order in RL
DN 2000
1. RG_B_to_E
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
5
Feature Overview (Previous Release )
Without the enhancement :
 If administrator wish to create a route to a PSTN/CUCM B
from particular site then he could simply have a Route list
with Standard Local Route Group.
 If the administrator has to add another emergency route to
CUCM C/PSTN then using Standard Local Route Group
would not help and he would have to make site specific
Route list and Route patterns.
 eg: 8.XXXX pattern would be used by device on site A to
reach site E using RG_A_To_E
 7.XXXX Pattern would be used by device on site B to reach
site E using RG_B_To_E
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
6
Enhancements made
(CUCM Admin page)
 In order to give administrator an option to configure more Local
Route Groups, in CUCM 10.0 release, a new page has been added
under Call Routing - > Route/Hunt -> Local Route Group Names.
 In this page the admin adds the names of Local Route Groups.
 Note that these are just names that will be used instead of “Local
Route Group” on Device Pool or Route List configuration pages.
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
7
Enhancements made
(CUCM Admin page)
These are Local Route Group names added by Administrator
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
8
Enhancements made
(CUCM Admin page)
These are the same names that
were added on Local Route Group
Names Page.
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
9
Enhancements made
(CUCM Admin page)
While configuring a Route List and associating Route Groups with that, notice the
“(Local Route Group)” tag appended after the Local Route Group names added
on the new page to differentiate the Local Route Group Names from normal
Route Group Names.
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
10
Feature Overview (With Enhancements)
CUCM B/PSTN
Route List to Site D
Cluster A
9.XXXX (Pattern)
DP_A:
Standard Local Route Group – RG_A – SIP_SiteD
Emergency Route Group - RG_A_toE
Phone1 at Site A
Preference Order
1 Standard Local Route
Group
2 RG_SiteD - MGCP_SiteD
Phone4 at Site D
DN 1000
DP_B:
Standard Local Route Group – <None>
Emergency Route Group - RG_B_toE
CUCM C/PSTN
Phone2 at Site B
Emergency Route List
8.XXXX (Pattern)
DP_C:
Standard Local Route Group – <None>
Emergency Route Group - <None>
Preference Order
1
Phone3 at Site C
2
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
Emergency Route
Group
RG_General
Phone5 at Site E
DN 2000
11
Feature Overview Contd..
With Enhancement :
 With this feature the limitation that we had with a single local route
group is removed.
 The administrator can add as many Local Route Group names as he
wants and those will reflect on the Device Pool page as shown.
 On the Device Pool page, he can choose to associate the Emergency
Route with a route group or leave it blank.
 This will reduce the number of route list and route patters to be
created.
 Let us see how it works.
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
12
Example Deployment Contd…
Case1: Phone 1 calls Phone 5 via Route List “Route List to Site E”
 When Phone 1 (DP_A) calls Phone 5 using route pattern 8.XXXX
 Route list layer check that the first route group in the preference order is
“Emergency Route Group (Local Route Group)”.
 It then checks the route group associated with “Emergency Route Group”
on DP_A.
Here we have associated with route group “RG_A_toE”.
Route list layer uses this route group to route the call to Site E.
Case2: Phone 1 calls Phone 4 via Route List “Emergency Route List”
 When Phone 1 (DP_A) calls Phone 4 using route pattern 9.XXXX
 Route list layer check that the first route group in the preference order is
“Standard Local Route Group (Local Route Group)”.
 It then checks the route group associated with “Standard Local Route
Group” on DP_A.
Here we have associated with route group “RG_A – SIP_SiteD”
Route list layer using this route group to route the call to Site D.
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
13
Example Deployment Contd…
Case3: Phone 3 calls Phone 5 via Route List “Route List to Site E”
 When Phone 3 (DP_C) calls Phone 5 using route pattern 8.XXXX
 Route list layer check that the first route group in the preference order is
“Emergency Route Group (Local Route Group)”.
It then checks the route group associated with “Emergency Route Group”
on DP_C.
Here we have not associated “Emergency Route Group” with any route
group .
Hence the Route list layer would check of for next member in the route list
And try routing the call via “RG_General”.
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
14
Interaction With LRG Forwarding Enhancement
 As a part of LRG Enhancement done in 9.0, a new Service Parameter
(“Local route group for redirected calls”) was added. This parameter
specifies the local route group to be used when there is a redirected call.
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
15
Interaction With LRG Forwarding Enhancement
 Let us say Phone1 calls Phone2, Phone2 has a CFNA set to Phone3.
Phone3 in turn has a CFNA set to Phone4 over the Route List to Site D.
 In such a scenario, Phone1 is the Calling Party, Phone2 is the Original
Called Party and Phone3 is the Last Redirecting Party.
Use Case1:
WhenService Parameter: Local route group for redirected calls is set to
“Local route group of calling party”.
 For routing the call in this case, the default behavior will be followed. The
Local Route Group settings on the Device Pool of the Calling Party i.e.
DP_A of Phone1 will be used and hence the call will be routed via
SIP_SiteD.
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
16
Interaction With LRG Forwarding Enhancement
Use Case2:
When Service Parameter: Local route group for redirected calls is set to
“Local route group of original called party”.
 For routing the call in this case, theLocal Route Group settings on the
Device Pool of the Original Called Party i.e. DP_B of Phone2 will be used.
 Since no route group has been associated with “Standard Local Route
Group” on DP_B, the call will be routed to Phone4 via MGCP_SiteD.
Use Case3:
When Service Parameter: Local route group for redirected calls is set to
“Local route group of last redirecting party”
 For routing the call in this case, the Local Route Group settings on the
Device Pool of the Last Redirecting Party i.e. DP_C of Phone3 will be used.
 Since no route group has been associated with “Standard Local Route
Group” on DP_C, the call will be routed to Phone4 via MGCP_SiteD in this
case as well.
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
17
Thank You
EDCS-834794
© 2006 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
18