Associate a Local Route Group to a Device Pool¶
This procedure associates a local route group with an existing device pool for each site.
This allows calls from a device that is tied to a device pool to go out on a specific route group based on the call type. For example, you can associate multiple local route groups such as Emergency Route Group, Primary Local Route Group (for site A), Secondary Local Route Group (for site A), Primary Local Route Group (for site B), and Secondary Local Route Group (for site B).
Local Route groups allow you to specify different route groups for each site (site A and site B) for the respective device pool. Also, you can define a separate call routing option for emergency calls when you associate the Emergency Route Group with a different route group. Hence you can easily define separate call routing options for emergency calls and PSTN calls.
Perform these steps:
Log in as provider, reseller or customer administrator.
Warning
When associating a local route group, ensure that you select a valid site under your customer in the hierarchy node breadcrumb at the top of the view. If you attempt to associate a local route group at any other node in the hierarchy, a popup alerts you to select a site hierarchy node.
Choose an option:
If you logged in as provider or reseller administrator, choose Apps Management > CUCM > Device Pools.
If you logged in as customer administrator, choose Apps Management > Advanced > Device Pools.
Click the device pool to be associated.
From the Cisco Unified CM Group drop-down menu, select a specific Cisco Unified Communications Manager group or leave the Cisco Unified CM Group as Default.
Click the Local Route Group Settings tab.
In the grid, from the Local Route Group drop-down menu, select the local route group.
In the grid, from the Route Group drop-down menu, select the route group or gateway.
To save the new local route association, click Save.