ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
   
						

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbb
ASAI and Call Routing
7
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
This chapter describes the Routing Capability Group. The capabilities in this
group allow the switch to ask for and receive routing instructions for a call.
These instructions, issued by the adjunct, are based upon the incoming call
information provided by the switch.
The following capabilities are available:
RouteThis capability lets the switch ask the adjunct
for the best route for an incoming call.
Route SelectThis capability lets the adjunct answer the
switch and provide route information for a
call.
Route EndThis capability lets the switch end the Route
Request and informs the adjunct about the
outcome of the route.
U-Abort (User Abort)See Chapter 3, ``Common Capabilities.
Issue 4  September 1995  
7-1 
						

							ASAI and Call Routingbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Routebbbbbbbb
This capability allows the switch to request routing information from the adjunct.
The adjunct provides it based upon incoming call information.  This feature may
be used independently of or in conjunction with call monitoring (Event Notification
turned on).
For G3V3 and later, the ASAI-Requested Digit Collection feature gives an
adjunct the ability to request that a DTMF tone detector (TN744) be connected to
detect user-entered digits.  The request is made via an option of the Route
Select message.  The digits collected as a result of this feature are passed to
ASAI monitoring and/or controlling adjuncts for action.  The switch handles these
digits like dial-ahead digits.  The digits are collected while the call is not in vector
processing; they are sent to an ASAI adjunct, and/or they may be used by Call
Prompting features.
Information Flowbbbbbbbbbbbbbbb
The switch sends a route request to the adjunct.  The adjunct does not return an
acknowledgment to the switch upon receipt of the routing request, but rather the
adjunct sends a Route Select capability when a route is available.
Route Parametersbbbbbbbbbbbbbbb
Calling Party
Number/Billing
Number (CPN/BN)For incoming call over PRI facilities Ð ``calling
number from the ISDN SETUP message
For incoming calls over non-PRI facilities, the
calling party number is generally 
not provided. In
this case, the Trunk Group number is provided
instead.
For calls originated at a bridged call appearance Ð
the principals extension
For incoming DCS calls, if the DCS calling party
information is available to the switch (if a station
with a display gets it), this information is also made
available to ASAI.  Otherwise, the calling party
information is provided as the default.
Called Party
number (DNIS)
For incoming calls over PRI facilities, the Called
Party Number is from the ISDN SETUP message.
For incoming calls over PRI facilities to a VDN that
does lookahead interflow on calls, if the lookahead
interflow attempt fails, the called number provided
is the principal extension of the dialed number.
7-2  Issue 4  September 1995 
						

							ASAI and Call Routingbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
For incoming calls over non-PRI facilities, the
Called Party Number is the principal extension
[may be a group (TEG, PCOL, hunt group, VDN)
extension
1].
call_id[mandatory] This parameter is the internal call identifier
unique in the switch.
domain IE[optional] This parameter is the VDN extension through
which the Route Request is made.
user-entered
information/
collected digits[optional] This parameter represents the digits that may
have been entered through call prompting or the
ASAI-collected digits feature (G3V3 and later).
lookahead
interflow[optional] This parameter ensures that calls do not
interflow to a remote location that cannot accept calls.
uui_info[optional] UUI information received in an ISDN setup,
ASAI Third Party Make Call, ASAI Auto Dial, or ASAI
Route Select Message on the ASAI link is stored by the
switch with the call for the life of the call or until
overwritten by a previous Route Select associated with
the call.
Flexible BillingSpecifies that the billing rate can be changed for an
incoming 900-type call.  Present if the feature is allowed
for the call and the Flexible Billing customer option is
assigned to the switch.
ACK (Positive Acknowledgment)
Parameters
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Causesbbbbbbbbbbbbbbb
The adjunct might deny (NAK) a route request with adjunct-specific causes.  See
the 
DEFINITY Communications System Generic 3 Call Vectoring/EAS Guide,
555-230-520, for a description of the adjunct routing vector step.
aaaaaaaaaaaaaaaaaaa
1.  If the switch is administered to modify the DNIS digits, then the true DNIS is not passed.
Issue 4  September 1995  7-3 
						

							ASAI and Call Routingbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Protocol Error (NAK) Causesbbbbbbbbbbbbbbb
The adjunct might deny (NAK) a route request, if the request is invalid, with
adjunct-specific causes.  See the 
DEFINITY Communications System CallVisor
ASAI Protocol Reference
, 555-230-221, for more information.
Considerationsbbbbbbbbbbbbbbb
A routing request is only administrable through the Basic Call Vectoring feature.
(See the 
DEFINITY Communications System Generic 3 Feature Description,
555-230-204, and the 
DEFINITY Communications System Generic 3 Call
Vectoring/EAS Guide
, 555-230-520, for more information.)  The Route capability
is initiated by the switch when it encounters the adjunct routing command in a
call vector.  This command specifies an ASAI links extension (adjunct) through
which the switch sends the Route capability.
Multiple adjunct routing commands are allowed in a call vector.  In G3V3 and
later, the Multiple Outstanding Route Requests feature allows 16 outstanding
Route Requests per call.  The Route Requests can be over the same ASAI links
or different ones.  The requests are all made from the same vector.  They must
be specified back-to-back, without intermediate steps (wait, announcement, goto,
or stop).  If the adjunct routing commands are not specified back-to-back,
pre-G3V3 adjunct routing functionality applies (that is, previous outstanding
Route Requests are cancelled when an adjunct routing vector step is executed).
The first Route Select response received by the switch is used as the route for
the call, and all other Route Requests for the call are cancelled.
If the adjunct denies the request (for example, replies with a NAK), the switch
continues vector processing.
Event Reports for calls are not affected by the adjunct Route Request.
7-4  Issue 4  September 1995 
						

							ASAI and Call Routingbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Route Selectbbbbbbbb
This capability allows the adjunct to provide the switch with the destination
address to which the call should be routed.  In addition, the adjunct can request
the switch to route the call as a direct-agent call and/or a priority call.  The first
Route Select received cancels all other outstanding requests.
For G3V3 and later, the following features provide additional functionality:
ASAI-Provided Digits allows an adjunct to include digits in a Route
Select capability.  These digits are treated as dial-ahead digits for the call,
which are stored in a dial-ahead digit buffer. They can be collected one at
a time or in groups using the collect digits vector command(s).
ASAI-Requested Digit Collection gives an adjunct the ability to request
that a DTMF tone detector (TN744) be connected to detect user-entered
digits.  The request is made via an option of the Route Select message.
The digits collected as a result of this feature are passed to ASAI
monitoring and/or controlling adjuncts for action. The switch handles these
digits like dial-ahead digits.
These digits are collected while the call is not in vector processing.  They
are sent to an ASAI adjunct, and/or they may be used by Call Prompting
features.
User to User Information (UUI) allows distributed CallVisor ASAI and
ACD users to associate caller information with a call.  This information
may be a customer number, credit card number, alphanumeric digits, or a
binary string.  It is propagated with the call whether the call is transferred
or routed to a destination on the local switch or to a destination on a
remote switch.  Up to 32 bytes are allowed.
An ASAI adjunct can include the UUI for a call in a Route Select.  If the
call is routed to a remote switch over PRI trunks, the switch sends the UUI
in the ISDN SETUP message used to establish the call.  The local and
remote switches include the UUI in the Call Offered to Domain and
Alerting Event Reports and in any Route Requests sent by the switch for
the call.
Information Flowbbbbbbbbbbbbbbb
The adjunct sends the destination address to the switch.
The switch accepts and reroutes the call if vector processing is executing either a
wait time or announcement steps.  If the destination address is invalid, the switch
returns a Route End with cause CS0/28 (Invalid number) and continues vector
processing (cancelling any ``wait or ``announcement steps in progress).
Issue 4  September 1995  
7-5 
						

							ASAI and Call Routingbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Route Select Parametersbbbbbbbbbbbbbbb
orig_addrNA (ignored)
dest_addr[mandatory] This parameter is the valid destination for the
call.  If it is an off-PBX number, it can contain the
u/ARS/AAR information.
dest_route_select[optional] Contains the u/ARS/AAR information for
off-PBX destinations.
split_paramIf the direct-agent call option is set to ``yes, then this
parameter must be a valid split extension; the destination
address must be logged into this split.
direct_agent_callThis parameter represents a special type of ACD call that
is directed to a specific ACD agent rather than to any
available agent.  It may be set to ``yes or ``no.
priority_callingThis parameter represents a special type of call that
carries three-burst distinctive ringing and does not go to
the covering point for coverage or send all calls.  It may
be set to ``yes or ``no.
user_entered_codeIncludes the following:
Type of user code = customer-database provided
(cdp)
Collect/collected indication = collected
Timer = all 0s (default Ð not used)
User data = ASCII digits (0-9, *, #)
collect_digits_flagThis parameter indicates that digits should be collected
(via a TTR in DTMF mode).
party_idThis parameter indicates which party on the call the tone
detector should listen to for ASAI-Requested Digit
Collection.  Currently, the call ``originator is the only
option supported.  (If present, this parameter is ignored.)
specific_eventThis parameter indicates when the tone detector used by
the ASAI-Requested Digit Collection feature should be
released.  Options are ``far end answer/connect and
``party disconnect.  Only the ``far end answer option is
currently supported (starting with Release G3V3); other
values are rejected.  When the event option is not present
in the Route Select and the digit collection is specified,
the default is ``far end answer/connect.
7-6  Issue 4  September 1995 
						

							ASAI and Call Routingbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
number_of_digitsThis parameter indicates the total number of digits that
will be collected (1 to 24).  For ASAI-Requested Digit
Collection, every ``# and ``* count as one digit each.  If
the request is not in the valid range, the Route Select fails
with cause CS0/79 Ð Service/option not available.
digit_coll_timeoutThis parameter indicates how many seconds (1 to 31) the
tone detector will continue to collect digits after the first
digit is received for ASAI-Requested Digit Collection.  The
default is no timeout.
uui_info[optional] If an ASAI adjunct provides UUI in a Route
Select, then the switch stores that UUI with the call.  The
UUI overwrites any previous UUI stored with the call.
UUI from a Route Select will be sent in any ISDN PRI
setup for the call, in the Alerting and Call Offered Event
Reports, or in a future Route Select.
ACK (Positive Acknowledgment)
Parameters
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Causesbbbbbbbbbbbbbbb
The switch issues a route end with one of the following reasons as the cause for
denying the request.  Vector Processing continues at the next step.
When Route Select has hunt group as the destination and the hunt group
is in night service and the night service destination is busy, then the cause
value CS0/16 (Normal clearing) is generated when in fact the destination
is busy (CS0/17).
Invalid Association (CS0/81)
This is generated when a Route Select is received after the Route End.
Timer expired (CS0/81)
The switch does not accept digits from a Route Select received after the
corresponding Route Request was cancelled.
Dial-ahead digits in incorrectly built Route Select (CS0/96 or CS0/100)
If dial-ahead digits are received in an invalid Route Select message, they
are discarded and a Route End is sent to the ASAI adjunct.
Route Select with no called number and no dial-ahead digits (CS0/96)
A Route Select received without dial-ahead digits and without a called
number or with an empty called number is denied.
Invalid party_id (CS0/28)
If the party_id parameter is not valid for the call, the switch sends a Route
End and continues with vector processing for the call.
Issue 4  September 1995  
7-7 
						

							ASAI and Call Routingbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Permission denied (CS3/43)
Only incoming trunks (of any type, including ISDN, MFC, and R2MFC) are
eligible for ASAI-Requested Digit Collection.  If the originator is not a
trunk, a Route Select with the ASAI-Requested Digit Collection option is
denied.
Permission denied (CS3/43)
A call prompter/tone detector is not connected if the originating trunk (to
which the tone detector is to be connected) does not have incoming
disconnect supervision administered.  The Route Select fails, the switch
sends a Route End, and the call continues in vector processing.
Call has been terminated (CS0/86)
If the call drops (for example, the caller abandons, a vector disconnect
timeout occurs, a non-queued call encounters a ``stop step, or an adjunct
clears the call), all outstanding Route Requests are cancelled.
Timer Expired (CS0/102)
The switch does not accept digits from a Route Select received after the
corresponding Route Request was cancelled.
Protocol Error (NAK) Causesbbbbbbbbbbbbbbb
None for this capability
Considerationsbbbbbbbbbbbbbbb
If the Route Select is received after a Route End is sent, it is ignored by the
switch and vector processing continues.
7-8  Issue 4  September 1995 
						

							ASAI and Call Routingbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Route Endbbbbbbbb
This capability is sent by the switch to terminate the routing association and
inform the adjunct regarding the outcome of the route.
Information Flowbbbbbbbbbbbbbbb
The switch does not expect a response to the Route End.
Route End Parameter(s)bbbbbbbbbbbbbbb
causeThe switch issues a Route End for one of the following
reasons:
User busy (CS0/17)
The destination is busy and does not have coverage.
For this case, the caller hears either a reorder or busy
tone.
Call with requested identity has been terminated
(CS3/86)
The call was dropped while waiting for a routing
response.
The call has been routed successfully (CS0/16)
The call has been redirected (CS3/30)
The switch has canceled/terminated any outstanding
Route Requests for the call after receiving the first valid
Route Select message.  The switch sends a Route End
with this cause to all other outstanding Routing
associations for the call.
Invalid Information Element Contents (CS0/100)
Either the UUI information element was longer than 32
bytes, or the header was missing.
For the above causes, vector processing does not continue.
In the following causes, vector processing continues.
Cancelling Outstanding Route Requests
All outstanding Route Requests for a call are cancelled
when a step other than ``wait, ``announcement,
``goto, ``stop, or ``adjunct route is encountered
(cause value CS0/102).  In addition, blank vector steps
do not cause outstanding Route Requests to be
cancelled.
Issue 4  September 1995  
7-9