
ASAI and Feature Interactions
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
Table
Vector Step or |
|
| Contents1 |
Command | Event Report | When Sent | |
When Call Enters Vector | Call Offered to Domain2 | encountered | Note A |
Queue to main | Queued or | successfully queues | cause - |
| Reorder/Denial | queue full | queue full |
|
|
|
|
Check backup | Queued or | successfully queues | cause - |
| Reorder/Denial | queue full | queue full |
|
|
|
|
Messaging split | Queued or | successfully queues | cause - |
| Reorder/Denial | queue full | queue full |
|
|
|
|
Announcement | none |
|
|
|
|
|
|
Wait | none |
|
|
|
|
|
|
GoTo | none |
|
|
|
|
|
|
Stop | Call Ended3 | encountered | cause |
Busy | Busy | encountered | cause - |
|
|
| busy |
|
|
|
|
Disconnect | Disconnect/Drop | facility dropped | cause - |
|
|
| busy |
|
|
|
|
Go To Vector | none |
|
|
|
|
|
|
Route To Number | Alerting | when successful |
|
(internal) |
|
|
|
|
|
|
|
Route To Number | Cut Through/ | PRI Interworking/ |
|
(external) | trunk seized |
| |
|
|
|
|
Adjunct Routing | route4 | encountered | Note B |
Collect digits | none |
|
|
|
|
|
|
Route To Digits (internal) | Alerting | when successful |
|
|
|
|
|
Note A: See the ‘‘Event Reports’’ on page
Note B: See‘‘ASAI and Call Routing’’ in Chapter 7.
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.”