AT&T 555-230-520 Medical Alarms User Manual


 
Call Vectoring Commands
A-16 Issue 4 September 1995
Calling number information. DNIS number provided by ISDN-PRI
facilities, or by the administered destination for other trunk facilities. If the
call originates from a local switch extension, this extension is the number
dialed (after digit translation).
Called number. Originally called extension (if a call is forwarded to a
VDN), or the first VDN through which the call was routed (if the call was not
forwarded to the VDN).
Routing VDN. Last VDN that routed the call to the vector that contains the
adjunct routing
command.
Call identifier. ASAI identifier that permits the ASAI adjunct to track
multiple calls via either Event Notification or Third Party Call Control. (See
DEFINITY Communications System Generic 3 Feature Description
,
555-230-204 or
Generic 3 CallVisor ASAI Technical Reference
for more
information on ASAI.)
Look-Ahead Interflow information (if any). Includes the original VDN
display information and the priority level of the call at the originating
switch. (See Chapter 8.)
Digits collected via Call Prompting (if any). Digits are collected by the
most recent
collect digits
command. (See Chapter 5.)
If the call is queued, the
adjunct routing
step is ignored, and vector processing
continues at the next vector step.
If the ASAI link specified in the
adjunct routing
step is down, the step is skipped.
An ASAI link failure can change the manner in which subsequent treatment (that
is,
announcement
and/or
wait-time
) steps (if any) in the vector are usually
processed. In some cases, such processing is influenced by the position that the
treatment steps occupy in the vector. In other cases, the positioning of these
commands along with their relationship to specific
goto
commands come into
play. For example, any
announcement
or
wait-time
step that immediately follows
an
adjunct routing
step whose ASAI link is down is skipped.
NOTE:
The second step after the
adjunct routing
step is often implemented as a
default treatment (for example, a route-to an attendant). If the ASAI link is
down, the default step executes immediately. Otherwise, the step executes
only if the application does not respond with a route within the time period
specified by the
wait-time
step.
On the other hand, if a
goto
step follows such an
adjunct routing
step, the switch
executes the
goto
step and then skips various treatment steps according to their
position in the vector and based on the performance of the
goto
step.
Specifically, if the
goto
step
succeeds
, the switch skips any
announcement
or
wait-time
step that is the first non-
goto
step branched to by the
goto
step.