Considerations for implementing percentage allocation routing

Last Updated : Sep 20, 2012 |

  • Modification to the table while calls are being routed to the VDN(s) that the PRT is assigned to can result in calls being miss-routed, miss-appropriated or other indeterminate actions. To prevent such a situation from occurring, create a new PRT table with the required changes and replace the old version.

  • The following are the valid entries in the Period field:

    • 100_count (default): The call count, displayed in percentage, is reset after the total calls for the PRT reach 100 which is when the total calls match the target routing pattern percentages. This ensures that the routing points have equal distribution of calls all the time.

    • max_count: The call count is maintained until calls delivered to one of the VDNs exceed 65,400. At that point, calls are continued to be distributed over the VDNs, but the call counts are reset when the actual percentages equal the targets for all of the VDNs at the same time.

    • Half-hour: Resets the call count at the top of the hour and at the 30 minute point.

    • Hour: Resets the call count at the top of the hour.

    • Daily: Resets the call count at midnight, every night.

    • Weekly: Resets the call count at midnight on Saturday.

  • The actual percentage and the call count are reset whenever the PRT screen is changed.

  • Calls are routed to the VDN destination that is farthest from meeting its target allocation.

  • Calls are routed based on the actual call count, not on the actual percentage. When there is no actual call count, at startup or after reset, the route point with the highest target is selected.

  • Calls routed through a PRT are reported to BCMS, CMS, and Avaya IQ as though the calls were routed to a VDN assigned to vector 0. VDN reports can be created using the existing CMS custom reporting capabilities to show the percentages and the number of calls that have been distributed among the destination VDNs. Avaya IQ provides additional reporting including what VDN the call was routed to, the PRT table number and the type used, and the matched percentage.

  • A PRT can be assigned to multiple VDNs. There is no restriction on the VDN that can be entered as a route point.

  • There are limits for the number of PRT tables that can be defined and there is a system routing point (PRTs x VDN destinations) limit. Both the limits can be found in the Communication Manager System Capacity tables and displayed on the Display Capacity screen.

  • In addition to add, change, display, list, and remove, the following commands also support PRT:

    • list vdn: Displays destination type, Vector or PRT.

    • list usage policy-routing-table: Lists the VDNs that use the specified PRT.

    • list history: Displays the history of add and change policy-routing-table commands.

    • list trace vdn: Displays calls to a PRT.

  • When the destination is a PRT, the Attendant Vectoring and Meet-Me Conferencing fields do not appear.

  • Routing through the PRT to the selected VDN is considered as a route to command operation and this triggers the Allow VDN Override rule that is assigned the previous VDN.

  • For VDN domain monitoring with CTI/ASAI, a call to a VDN, that is, routed via a PRT. appears as if the call was routed to the destination VDN by a route-to number command in a vector assigned to the original VDN.

  • To evenly distribute calls across three routing points, administer the routing points with a 33 percent target, add a fourth routing point that routes back to the PRT with a target of 1 percent. Set the Period field to 100_count and calls are distributed evenly.