Adding Aggregation Trunk and Route Group and Associating to Existing Route List and SLRG

In VOSS-4-UC 10.x/11.5(x), the dial plan creates a route list to route the calls to the aggregation for central breakout (CBO). However, the following procedure is required to enable calls to egress to the PSTN network using a SIP trunk. Before adding a SIP trunk using Configure SIP Trunks, you must provision the following:

Note

In step 11, navigate to Device Management > CUCM > Local Route Groups if you are using Cisco Unified CDM 10.6(1).

  1. In VOSS-4-UC 10.x/11.5(x), create a region for the trunk as follows:

    1. Sign in as a provider or reseller and navigate to Device Management > CUCM > Regions Information > Region.
    2. Click Add.
    3. Provide a name in the format Cu<cid>-Trunk-<TrunkName>-Region.

  2. In Cisco Unified Communications Manager, navigate to CUCM System > Device Pool and provision a device pool as follows:

    1. Click Add.
    2. Enter a device pool a name in the format Name Cu<cid>-DP-Trunk.
    3. Choose a CCM group from the dropdown or leave at the default group.
    4. Ensure that the region is set to the name created in step 1.
    5. Set the location to Hub Non.

  3. To create an aggregation SIP trunk, sign in as a provider in VOSS-4-UC 10.x/11.5(x) and perform the following:

    1. Navigate to Device Management > CUCM > SIP Trunks.
    2. Click Add.

  4. In the Device Information tab, perform the following:

    1. Choose the Unified CM from the drop-down list.
    2. Provide a device name; for example, Cu<cid>-Trunk-<TrunkName>.
    3. Set the device pool to the device pool name you created.
    4. Set the region to the name created in step 1.
    5. Set call classification to OffNet.
    6. Click Redirecting Diversion Header Delivery - Inbound.
    7. Click Run On All Active Unified CM nodes.

  5. In the Call Routing Inbound tab, perform the following:

    1. Choose the calling search space by selecting Cu<cid>-IngressFromCBO-CSS from the drop-down list.
    2. Choose the connected party transformation CSS by selecting Cu<cid>-CNPNTranform-CSS from the drop-down list.
    3. Uncheck the Use Device Pool Connected Party Transformation CSS box.
    4. Check the Redirecting Diversion Header Delivery - Outbound box.

  6. In the Call Routing Outbound tab, perform the following:

    1. Choose the called party transformation CSS by selecting Cu<cid>-CDPNTransform-CSS from the drop-down list.
    2. Uncheck the Use Device Pool Called Party Transformation CSS box.
    3. Choose the calling party transformation CSS by selecting Cu<cid>-CGPNTransform-CSS from the drop-down list.
    4. Uncheck the Use Device Pool Calling Party Transformation CSS box.

  7. In the SIP Info tab, provide the destination IP address. It is assumed that the default SIP profile and SIP trunk security profile are used.

  8. Once the aggregation SIP trunk is created, assign it to a route group as follows:

    1. Navigate to Device Management > Route Groups.
    2. Click Add.
    3. Provide a name for the route group in the format Cu<cid>-RouteGroup-<Name>.
    4. Set the distribution algorithm to Top Down.
    5. Add the above trunk as a member of the route group.

    Note

    For line-based routing (LBR), perform steps 9 and 10.

  9. Associate the above route group to the route lists. The assumption is that there is one trunk or route group to the aggregation that is shared by the whole country. However, if there is a trunk per country, then repeat the above step to create trunk and route groups for each country. The country dial plan automatically creates the following LBR route lists for each country for each customer:

    • Cu<cid>-<ISO>Intl-RL . (cid is the customer ID number and <ISO> is the 3-letter alpha code for the countries of the world. For more information on ISO, refer to http://en.wikipedia.org/wiki/ISO_3166-1).
    • Cu<cid>-<ISO>Natl-PL
    • Cu<cid>-<SIO>Mobl-PL
    • Cu<cid>-<ISO>Emer-RL
    • Cu<cid>-<ISO>Serv-RL
    • Cu<cid>-<ISO>Local-RL
    • Cu<cid>-<ISO>PRSN-RL
    • Cu<cid>-<ISO>FPHN-RL
    • Cu<cid>-<ISO>PCSN-RL
    • Cu<cid>-<ISO>SRSN-RL
    • Cu<Cid>-<ISO>Oper-RL

    Note

    The SLRG-Emer local route group must be provisioned even for line-based routing (see step 11).

  10. Update each of the route lists to include the above-created route group as follows:

    1. Navigate to Device Management > CUCM > Route Lists.
    2. Select and enter each of the route list pages from the step above.
    3. Click on the Add Route Group Items and select the above route group.
    4. Save and proceed to the next route list until all the route lists include the route group.

  11. For device-based routing (DBR), nothing is needed for DBR route lists because they already contain the correct well-known local route groups. For each location that uses DBR, update the device pool as follows:

    1. Navigate to Device Management > CUCM > Device Pools.

    2. Select and enter the device pool SLRG page.

    3. Add the following well-known SLGs and associate them to the route group created above.

      • SLRG-Emer

        Note

        SLRG-Emer must be added regardless of whether DBR is used. Emergency call handling depends on this in order to work.

      • SLRG-Intl

      • SLRG-Mobl

      • SLRG-Serv

      • SLRG-Local

      • SLRG-PRSN

      • SLRG-FPHN

      • SLRG-PCSN

      • SLRG-SRSN

      • SLRG-Oper