Vectors 

Introduction

For each message coming into a mailbox, the messaging software tells the DEFINITY ECS to launch a message call using the VDN associated with the mailbox where it found the message. EAS on the DEFINITY ECS then uses the vector associated with that VDN to give the message a proper place in the queue and to select an agent qualified to process the message.

Expanding the routing possibilities

To expand the routing possibilities for each mailbox, the messaging software also provides sorting within a mailbox by up to ten keywords, each with its own VDN. The messaging software searches the subject of the message for each keyword in turn. If it finds none, it uses the default VDN for the mailbox. Keyword sorting is limited to the message subject only, not the message body.

Vectors and reports

CMS uses the VDN associated with a message call in organizing its reports; therefore, each mailbox should normally have its own VDN for successful measurements, even if multiple VDNs all point to the same agent skill set.

To route messages to the correct agents, and to track the management information you require, it is crucial for you to define your VDNs and vectors carefully.

Issues that affect how you define your VDNs

The following issues affect how you define your VDNs:

General guidelines for designing vectors

The following are general guidelines for designing your vectors:

Queue/hold time

Due to the potential rollover of statistical values in DEFINITY ECS, vectors designed to support message calls should ensure that a message call not be queued within a single vector for more than 8 hours.

Hold time should be limited due to rollover of certain message call tracking values in DEFINITY ECS.

CTI interactions

If you are using multiple CTI applications and one or more of the other CTI applications have a need to monitor message calls, there are some guidelines that need to be followed to avoid the possibility that the messaging software will lose monitoring for the message call.

CTI applications that will be monitoring message calls through VDNs, should monitor the same set of VDNs that are being monitored by the messaging software. These VDNs are those that have been assigned to the mailboxes.

If message calls get redirected to subsequent VDNs (through vectoring, through adjunct routing, or by agent transfers/conferences), these subsequent VDNs should not be monitored by the other CTI applications. Both the messaging software and the other CTI applications will continue to receive information about these message calls through monitoring on the initial VDN even though the message calls have been redirected to other VDNs. If the other CTI application monitors these subsequent VDNs, it is possible that the messaging software will lose track of the message call and thus, prevent it from doing a PagePop.

The messaging software will lose track of the message call if the other CTI application either uses a different platform for CTI connectivity to the DEFINITY ECS (for example, CallVisor PC) or uses a separate CTI link. If the other CTI application needs to monitor message calls, it should monitor the initial VDN. If both the messaging software and the other CTI application monitor only the initial VDN, both applications will continue to get events for the message call even if the message call gets redirected to the other VDNs. In some of the sample vectors (see Sample vector for basic message call delivery), message calls are redirected to other VDNs for the purpose of de-queuing/re-queuing message calls. In the following examples, the other CTI application should not be monitoring these subsequent VDNs.

Miscellaneous vector considerations

Consider the following when creating vectors for messaging:

   



Copyright © 2001
Avaya Inc.
All rights reserved.
Modified: March 19, 2001