To simplify call routing and dial plan management, local route groups provide a logical way to process calls according to settings specific to the device pool of the originating device.
To implement a local route group for use with a device pool, perform the following:
Add a new route list that will serve as the link to the local route groups (Call Routing | Route/Hunt | Route List).
Click on Add New to add a new route list.
Type in a name and select a Call Manager Group in the drop-down with which the route list will be associated:
Click on Save.
Once the page reloads, click on Add Route Group and a new page will open.
Select Standard Local Route Group from the Route Group drop-down menu then click on Save. You will be returned to the Route List page:
Finally, click on Save to save the Route List.
Add a new route group containing the gateway or trunk (Call Routing | Route/Hunt | Route Group).
Find and select your gateway or trunk under the Find Devices to Add to Route Group section. Then click on Add to Route Group. You should now see the device in the Selected Devices list:
Click on Save. The device will show up under Route Group Members.
Assign the route group you created in the previous step to the device pool by navigating to the device pool (From the menu, System | Device Pool) configuration page and selecting the route group from the Local Route Group drop-down under the Device Pool Settings section:
Click on Save.
Prior to the introduction of local route groups in CUCM, dial plans relied on route patterns pointing to specific gateways and route lists in site-specific partitions. By utilizing local route groups with device pools we can simplify call routing and reduce the number of route patterns needed throughout the system, thereby making the overall system simpler and maintenance easier.
When a call is placed on the system it matches a route pattern that informs the system where to send the call, typically a route list containing trunks and gateways. When the system is told to send the call to a route list containing the Standard Local Route Group, the egress gateway is determined by information pulled from the device pool settings of the device that initiated the call, and routes it accordingly.