ASAI versus the converse vector step
The Converse Vector Step (CVS) allows the switch to maintain control of a call while capabilities of the Avaya IR system are being used. Whether to use ASAI or the CVS depends on several factors, including cost, traffic, and desired functionality. For example, the CVS feature, used in an application, could support a low-cost ANI routing application. Large volumes of traffic may require an ASAI-based solution due to the more efficient ASAI adjunct routing. See Converse vector step routing, for more information about the CVS.
The following provides a list of the capabilities and limitations of using the two features on telephony lines.
- Both ASAI and CVS provide the delivery of ANI, DNIS, and switch call prompting digits for calls. The CVS provides this information on an in-band basis while ASAI makes the data available on an out-of-band basis. The ASAI out-of-band exchange of data is faster.
Note:
CVS allows a maximum of two parameters to be delivered.
- The Avaya IR system ASAI external functions A_Event and A_RouteSel can be used in monitoring and routing applications even if the calls are delivered via the CVS.
In addition, both ASAI and the CVS have some unique properties that may influence the decision as to which feature to use:
- ASAI properties
- When the Avaya IR system is used as a gateway for switch-to-host applications, the A_Tran external function simplifies call-flow development using screen pops based on data collected by the Avaya IR system.
- Dynamic port allocation is simpler because ANI and DNIS service administration is supported.
- CVS properties
- CVS allows a call to remain in a live agent queue while interacting with the Avaya IR system.
- Queue position and administered digit string can be passed to the Avaya IR system using the CVS. Queue position could be used as the basis for an anticipated delay announcement. An administered digit string could be used to identify specific announcements to be played to callers.
