Interactions for Attendant Vectoring

Last Updated : Sep 29, 2016 |

This section provides information about how the Attendant Vectoring feature interacts with other features on the system. Use this information to ensure that you receive the maximum benefits of Attendant Vectoring in any feature configuration.

Centralized Attendant Service (CAS)

You cannot use Attendant Vectoring with the Centralized Attendant Service (CAS) feature. Therefore, the Attendant Vectoring field cannot be set to y if either the CAS Branch field or the CAS Main field on the Optional Features screen is set to y.

Meet-me Conference

You cannot use Attendant Vectoring with the Meet-me Conference feature. Therefore, the Attendant Vectoring field and the Meet-me Conference field cannot both be set to y at the same time.

Call Coverage and Tenant Partitioning

If a covered call does not route to an attendant in the first tenant group, you can route it to an attendant group of a different tenant partition. For example, you can reroute a call to Tenant Group B if the call is to cover to an attendant for Tenant Partition A  but does not route to the attendant or is received out of hours when Attendant Group A is unstaffed.

To reroute the covered calls to another tenant attendant group, Tenant Attendant group B in this example,

  1. In the vector for the tenant A attendant vectoring VDN, add a failure branch to a route-to ldn_number with cov y if unconditionally step for the LDN extension for the tenant group B TN number.

  2. Set the with coverage parameter of the route-to step must be set to cov y because the calls are covered. Else, the calls don’t route to the VDN. Also, set the Cvg Enabled for VDN Route-to party? field of original coverage path, which covers to Tenant A Attendant vectoring VDN, to y.