官术网_书友最值得收藏!

Implementing local route groups with device pools for E.164 call routing

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.

Getting ready

This recipe assumes you have a gateway or trunk device configured.

How to do it...

To implement a local route group for use with a device pool, perform the following:

  1. Add a new route list that will serve as the link to the local route groups (Call Routing | Route/Hunt | Route List).
  2. Click on Add New to add a new route list.
  3. Type in a name and select a Call Manager Group in the drop-down with which the route list will be associated:
    How to do it...
  4. Click on Save.
  5. Once the page reloads, click on Add Route Group and a new page will open.
  6. 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:
    How to do it...
  7. Finally, click on Save to save the Route List.
  8. Add a new route group containing the gateway or trunk (Call Routing | Route/Hunt | Route Group).
  9. 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:
    How to do it...
  10. Click on Save. The device will show up under Route Group Members.
  11. 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:
    How to do it...
  12. Click on Save.

Tip

These changes will not take effect until you reset the devices in the device pool.

How it works...

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.

There's more...

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.

主站蜘蛛池模板: 墨脱县| 临洮县| 泰兴市| 天全县| 贵定县| 巴彦淖尔市| 丹寨县| 龙泉市| 夏邑县| 长泰县| 祁东县| 潼南县| 革吉县| 册亨县| 肃南| 南部县| 商都县| 安阳市| 且末县| 日照市| 乳山市| 石棉县| 搜索| 峡江县| 鄄城县| 阿拉尔市| 会同县| 麦盖提县| 开化县| 工布江达县| 延吉市| 成都市| 玉林市| 卓尼县| 延边| 叙永县| 芦山县| 星子县| 兴化市| 玉田县| 中卫市|