ASAI and Feature Interactions

Table 12-1. Interactions Between Feedback and Call Vectoring — (Continued)

Vector Step or

 

 

Contents1

Command

Event Report

When Sent

Route To Digits (external)

Cut Through

when trunk is seized

 

 

 

 

 

Converse Vector Command

Queued Event

if the call queues for the agent or

 

 

 

automated attendant (VRU)

 

 

Alerting Event

when the call is delivered to an agent

Cause-

 

 

or the automated attendant

remains in queue

 

Connected Event

when the call is answered by the agent or

 

 

 

automated attendant

 

 

Drop Event

when the call disconnects from the agent

 

 

 

or automated attendant

 

 

 

 

 

1.All event reports include an ASAI call_id.

A call may not be redirected via Redirect Call while in vector processing.

If a call is selective disconnected, it cannot also be in vector processing. The reason is that a call in vector processing can only have one party.

Adjunct Routing

Adjunct routing is only administrable by the call vectoring feature. When vector processing encounters an adjunct routing command in a call vector, a Route capability is invoked by the ECS to request a preferred route. The adjunct provides a preferred route to be used by invoking the Route Select capability.

If the dest_addr in the Route Select provided by the adjunct is a valid extension and the call is a monitored non-ISDN PRI call, then the Called Party number provided in the Event Reports is that of the dest_addr provided by the adjunct in the Route Select. If the call is an ISDN PRI call, then the Called Party number provided in the Event Reports is the original called number provided in the ISDN Setup Message. This functionality is consistent with that of the route-to-digits-with-coverage vector step. For more information on this step, see the DEFINITY Enterprise Communications Server Administration and Feature Descriptions, 555-230-522.

If the dest_addr in the Route Select capability is invalid or if the ECS is unable to route the call to the dest_addr, a Route End along with the cause is returned to the adjunct. If vector processing encounters steps that queue the call, or if the call leaves vector processing, the ECS sends a Route End to the adjunct indicating the termination of the request.

For G3V3 and later, the Multiple Outstanding Route Requests feature allows multiple route requests for the same call to be active at the same time. The Route Requests can be over the same or different ASAI links. The requests are all made

Issue 7 May 1998 12-23

Page 325
Image 325
Lucent Technologies 555-230-220 manual Adjunct Routing