Filter
Top Products
ASAI and Feature Interactions
12-22 Issue 7 May 1998
Call Vectoring
A VDN can be an active notification domain. It can also be the destination of a call
placed by Auto Dial, or of a User-Classified call placed by Third Party Make Call.
Also, a VDN can be the originator of a switch-classified call by Third Party Make
Call. Interactions between ASAI and call vectoring are shown in the following
table.
1. All event reports include an ASAI call_id.
2. Only reported over an active notification association
3. Unless call is queued. If it is queued, no report is provided.
4. The ASAI
Route
capability and response are not event reports,
but are initiated using the vector command “adjunct routing.”
Table 12-1. Interactions Between ASAI and Call Vectoring
Ve ct or St ep or
Command Event Report When Sent Contents
1
When Call Enters Vector Call Offered to Domain
2
encountered Note A
Queue to main Queued or
Reorder/Denial
successfully queues
queue full
cause -
queue full
Check backup Queued or
Reorder/Denial
successfully queues
queue full
cause -
queue full
Messaging split Queued or
Reorder/Denial
successfully queues
queue full
cause -
queue full
Announcement none
Wait none
GoTo none
Stop Call Ended
3
encountered cause
Busy Busy encountered cause -
busy
Disconnect Disconnect/Drop facility dropped cause -
busy
Go To Vector none
Route To Number
(internal)
Alerting when successful
Route To Number
(external)
Cut Through/
trunk seized
PRI Interworking/
Non-PRI trunk seized
Adjunct Routing route
4
encountered Note B
Collect digits none
Route To Digits (internal) Alerting when successful
Note A: See the ‘‘Event Reports’’ on page 3-2 in Chapter 3.
Note B: See‘‘ASAI and Call Routing’’ in Chapter 7.