ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
For an alternate answering position that is a domain-controlled station, the
Alerting and Connected Event Reports are returned to its domain-control
association.
The Call Redirected Event Report is sent to the principals domain-control
association when an analog principals call goes to coverage.  The
Disconnect/Drop Event Report is sent for the coverage stations domain-control
associations when the call which had been alerting at both the principal and the
coverage is picked up at the principal.
Switch-classified calls placed to local destinations whose coverage criteria are
met do not go to coverage, they remain at the called party.  Switch-classified
calls delivered to originators whose coverage criteria are met follow the
originators coverage path (provided they are not priority calls).
Direct-agent calls follow the agents coverage path rather than the splits.  This is
different from regular ACD calls.
An adjunct-routed call is allowed to go to coverage as usual.  If the coverage is
busy, the user hears a busy tone and the adjunct is notified with the Route End
capability (cause CS0/16 Ð Normal Clearing).
If a call covers and rings at a station with domain-control, then the Alerting Event
will indicate Call Coverage in a Cause IE.  The possible causes are: Send All
Calls Cover All or Go to Cover (CS3/31), Principal Station is Busy (CS3/26), and
Principal Station Not Answering (CS3/28).
When a call is redirected via Redirect Call, the coverage timer is restarted. Thus,
if the destination does not answer, the call will go to the coverage point for the
principal.  The subsequent Redirection No Answer timer is also restarted when a
call is redirected from a coverage point via Redirect Call.
Call Coverage Path Containing VDNsbbbbbbbbbbbbbbb
When a call is redirected to a station/split coverage path and the coverage path
is a VDN, the switch provides the following event reports for the call:
Call Redirected Event Report (for the Third Party Domain (Station) Control
association monitoring/controlling the station):
A call redirected event can also be sent if the call provides events to an
Event Notification association and the VDN in the coverage path has
Event Notification active.  The VDN with active notification receives a Call
Offered to Domain Event Report.  If the VDN in the coverage path is not
monitored (Event Notification active), then no call redirected event is sent
to the active Event Notification association providing event reports for the
call.
Call Offered to Domain Event Report:
This report is only sent if the VDN in the call coverage path has an Event
Notification association active (is being monitored).  If this is not the case,
the report is not sent.
12-14  Issue 4  September 1995 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
All types of calls (user-classified, direct-agent, and switch-classified) are
permitted to follow the VDN in the coverage path if the coverage criteria has
been met.  The call to an on-switch originator of a switch-classified call is never
permitted to go to coverage.
All other event reports associated with calls in a VDN (for example, Queued and
Alerting Event Reports) are provided to all monitoring and controlling
associations active for the call.
Call Forwarding All Callsbbbbbbbb
Users at controlled stations can activate and deactivate the Call Forwarding All
Calls feature from the voice terminal or via an ASAI adjunct.  Activation and
deactivation from the voice set and an ASAI adjunct may be intermixed.
A Third Party Make Call, Third Party Auto Dial, or Route Select to a station with
the Call Forwarding All Calls feature active redirects to the ``forwarded to
station.  No Call Redirected Event Report is sent on a Domain Control
association for the forwarding station, since the call does not alert the extension
that has Call Forwarding activated.  This is only if the call was placed directly to
the ``forwarded to station.
A direct-agent call forwards if the destination split has call forwarding activated.
While Call Forwarding is active at a station, agent status value queries will show
that the agent is busy.
When an agent activates call forwarding, existing direct-agent calls waiting in the
queue for the agent are 
not forwarded.  Only new direct-agent calls entering the
split after the agents activation are forwarded. (Note that regular ACD calls
never follow the agents call forwarding.)
Switch-classified calls placed to local destinations with Call Forwarding All Calls
active do not forward, but remain at the called party.  Switch-classified calls
delivered to originators with Call Forwarding All Calls active are forwarded, even
if the forwarding number is off-PBX.
If a monitored call is forwarded off-PBX over a non-PRI facility, the Trunk Seized
Event Report is generated.
If a call forwards and rings at a station with domain-control, then the Alerting
Event will indicate Call Forwarding in a Cause IE (cause=CS3/32).
Redirecting via Redirect Call to an endpoint with Call Forwarding activated will
fail.
Issue 4  September 1995  
12-15 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Call Parkbbbbbbbb
A controlled station can activate Call Park.
A call may be parked manually at a station by use of the ``call park button (with
or without the conference and/or transfer buttons), or by use of the feature
access code and the conference and/or transfer buttons.
When a call is parked by using the ``call park button without either the
conference or the transfer buttons, there are no event reports generated.  When
the conference or transfer buttons are used to park a call, the Call Conferenced
or Call Transferred Event Reports are generated.  In this case, the ``calling and
the ``called number in the Call Conferenced or Call Transferred Event Reports
are the same Ð that of the station on which the call was parked.
When the call is unparked, a Connected Event Report is generated with the
``calling and ``called numbers indicating the station on which the call had been
parked, and the ``connected number is that of the station unparking the call.
Call Pickupbbbbbbbb
A call alerting at a controlled station may be picked up using Call Pickup.  The
station picking up (either the principal or the pickup user or both) may be
domain-controlled.  A Connected Event Report is sent to all active associations
on the call when this feature is used.  When a pickup user picks up the principals
call, the principals set (if multifunction) retains a simulated bridge appearance
and is able to connect to the call at any time.  No event report is sent for the
principal unless the principal connects in the call.
When a call has been queued first and then picked up by a pickup user, it is
possible for an adjunct to see a connected event without having seen any prior
alerting events.
The switch does not allow call pickup to be used to pick up a switch-classified
call that terminates on an internal station extension.
12-16  Issue 4  September 1995 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Call Vectoringbbbbbbbb
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. Interactions between event reporting and call vectoring are shown in the
following table.
Table 12-1.  Interactions Between Feedback and Call Vectoring
bbbbbbbbbbbbbbbbbbbbbbbb
Vector Step or Command Event Report When Sent Contents**
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
When Call Enters Vector Call Offered encounteredNote 1
to Domain*
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Queue to main Queued or successfully queues 
Reorder/Denial queue full cause - queue full
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Check backup Queued or successfully queues 
Reorder/Denial queue full cause - queue full
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Messaging split Queued or successfully queues 
Reorder/Denial queue full cause - queue full
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Announcement nonebbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Wait nonebbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
GoTo nonebbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Stop Call Ended*** encountered causebbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Busy Reorder/Denial encountered cause - busybbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Disconnect Disconnect/Drop facility dropped cause - busybbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Go To Vector nonebbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Route To (internal) Alerting when successfulbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Route To (external) Cut Through/ PRI Interworking/
trunk seized Non-PRI trunk seized
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Adjunct Routing route**** encounteredNote 1bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Collect digits nonebbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Route To Digits (internal) Alerting when successfulbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Route To Digits (external) Cut Through when trunk is seizedc c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c
c c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c
c c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c
Note 1: Included in the message are the called party, calling party (ANI/SID/CLI), prompting digits collected,
lookahead interflow, optional UUI, optional trunk group number, and an indication that Flexible Billing is available.
*  Only reported over an active notification association
**  All event reports include an ASAI call_id.
***  Unless call is queued. If it is queued, no report is provided.
**** The ASAI 
Route capability and response are not event reports, but are
        initiated using the vector command ``adjunct routing.
Issue 4  September 1995  12-17 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Table 12-1.  Interactions Between Feedback and Call Vectoring  (continued)bbbbbbbbbbbbbbbbbbbbbbbb
Vector Step or Command Event Report When Sent Contents**
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
if the call queues for the
agent or automated
attendant (VRU) Converse Vector Command Queued Event
when the call is delivered
to an agent or the
automated attendant Alerting Event
when the call is answered
by the agent or automated
attendant Connected Event
when the call disconnects
from the agent or
automated attendant Drop Event
c c c c c
c
c
c c c
c
c
c c c
c c c c c
c
c
c c c
c
c
c c c
c c c c c
c
c
c c c
c
c
c c c
Note 1: Included in the message are the called party, calling party (ANI/SID/CLI), prompting digits collected,
lookahead interflow, optional UUI, optional trunk group number, and an indication that Flexible Billing is available.
*  Only reported over an active notification association
**  All event reports include an ASAI call_id.
***  Unless call is queued. If it is queued, no report is provided.
**** The ASAI 
Route capability and response are not event reports, but are
        initiated using the vector command ``adjunct routing.
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
A call may not be redirected via Redirect Call while in vector processing.
Call Promptingbbbbbbbbbbbbbbb
Up to 16 digits collected from the last collect digit vector command are passed
to the adjunct in the Call Offered to Domain Event Report and the Route ASAI
capabilities.
Lookahead Interflowbbbbbbbbbbbbbbb
This feature is activated by encountering a route to vector command, with the
route to destination being an off-PBX number, and having the ISDN-PRI,
Vectoring (Basic), and Lookahead Interflow options enabled on the Customer
Options form.
For the originating PBX, the interactions are the same as for any call being
routed to an off-PBX destination by the route to vector command.
For the receiving PBX, the lookahead interflow Information Element in the ISDN
message is included in all subsequent Call Offered to Domain Event Reports and
Route ASAI capabilities for the call, when the information exists, and when the
call is adjunct-monitored.
12-18   Issue 4  September 1995 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Adjunct Routingbbbbbbbbbbbbbbb
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 switch 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 
AT&T
DEFINITY Communications System Generic 3 Feature Description
,
555-230-204.
If the dest_addr in the Route Select capability is invalid or if the switch 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 switch 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 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, G3V2 routing functionality applies
(that is, previously outstanding route requests are cancelled when an adjunct
routing vector step is executed).
This capability increases the redundancy options available with ASAI. Previously,
adjunct routing applications that wanted to have a backup link had to test
whether or not the primary link was down and then execute the adjunct routing
command for the backup link with a vector.  With this enhancement, multiple
adjuncts can route the call without waiting for the first route attempt to fail.
In addition, the application can use this feature to distribute the incoming call
load evenly across adjuncts, based on the adjuncts CPU load.
Multiple Split Queuingbbbbbbbbbbbbbbb
A Queued Event Report is sent for each split that the call queues to; therefore,
multiple call queued events could be sent to the adjunct for one call.
If a call is in multiple queues and abandons (caller drops), one drop event (cause
normal) is returned to the adjunct followed by a Call Ended Event Report or a
Third Party Call Ended capability.
Issue 4  September 1995  
12-19 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
When the call is answered at a split, the call is removed from the other splits
queue.  No other event reports for the queues are provided in addition to the
Alerting and Connected Event Reports.
Third Party Make Callbbbbbbbbbbbbbbb
Third Party Make Call cannot have a VDN as the originator.
With the OCM/EAS feature enabled, a VDN extension can be an originator for a
switch-classified call.
Vector-Controlled Splitsbbbbbbbbbbbbbbb
A vector-controlled split may not be used as a domain for Request Notification.
Call Waitingbbbbbbbb
When an analog station is administered with this feature and a call comes in
while the user is busy on another call, the Alerting Event Report is sent to the
adjunct. This call is eligible for redirection via Redirect Call.
Class of Restriction (COR)bbbbbbbb
Direct Agent Calling is a field on the Class of Restriction (COR) form that must
be set to ``y for both the destination and originator.  If either the originating or
destination party of a direct-agent call does not have the proper COR, then the
call is permitted but is not a direct ACD agent-type call.
In the case of adjunct routing, the COR of the associated VDN is used for calling
party restriction checks.
For direct-agent calls, the agents COR is used for the termination party
restriction checks, whereas regular ACD calls use the splits COR for the
termination party restriction checks.
Third Party Auto Dial and Third Party Make Call calls are originated by using the
originators COR.
For switch-classified calls, the COR associated with the ASAI link is used to
determine permissions.  If the COR check fails, the call is dropped, and a Call
Ended Event Report is sent to the adjunct with cause CS0/21.
12-20  Issue 4  September 1995 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Class of Service (COS)bbbbbbbb
The Class of Service (COS) for the originator is never checked in conjunction
with any ASAI capabilities.
Conferencebbbbbbbb
Manual conference from a domain-controlled station is allowed, subject to the
features restrictions.  The Hold Event Report is provided as a result of the first
button push or first switch-hook flash.  The Conference Event Report is provided
as a result of the second button push or second switch-hook flash, and only if the
conference is successfully completed.  On a manual conference, the Call
Conferenced Event Report is sent to all the active associations for the resultant
call.  For conference from another association, the requesting association
receives a positive acknowledgement (ACK), and all other associations for the
call or endpoints receive the Call Conferenced Event Report.
See Chapter 3, ``Common Capabilities for more information on merged calls.
For a complete list of cause values, see the 
DEFINITY Communications System
CallVisor ASAI Protocol Reference
, 555-230-221.
Consultbbbbbbbbbbbbbbb
When the covering user presses the Conference or Transfer feature button and
receives dial tone, a Hold Event Report is returned to all adjuncts monitoring the
call.  A Call Initiated Event Report is then sent to the covering user on the
domain-control associations monitoring the covering user.  After the Consult
button is pressed by the covering user, Alerting and Connected Event Reports
are returned to associations monitoring the principal and covering user.  The
covering user can then conference or transfer the call.
Data Callsbbbbbbbbbbbbbbb
Data calls cannot be originated via the Third Party Make Call or Third Party Auto
Dial capabilities.  Analog ports equipped with modems can be domain-controlled
and calls to and from these ports can be controlled and monitored.  However,
Call Control capabilities may cause the call to be dropped by the modem.
DCSbbbbbbbb
With respect to ASAI event reporting, calls made over a DCS network are treated
as off-PBX calls and only the Call Initiated, Trunk Seized, Call Ended, and/or
Disconnect/Drop Event Reports are returned.  DCS/UDP extensions that are
local to the PBX are treated as on-PBX stations.  DCS/UDP extensions
connected to the remote nodes are treated as off-PBX numbers.
Issue 4  September 1995  
12-21 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
ASAI does not currently support DCS calls completely.  DCS calls may or may
not provide accurate information to an ASAI adjunct.  In a pure DCS
environment, 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, calling party information is provided as the default (*****).
With DCS on ISDN, the same rule (as above) applies.  This means that even
though there may be information in the ISDN message, it is not passed to ASAI.
Only calling party information from the DCS message is passed to ASAI (DCS
prevails over ISDN).
Since there can be other side-effects of using ASAI in a DCS environment, it is
best to avoid using such setups.
SAC or CF features may not be activated over an ASAI link for an off-PBX DCS
extension.
Direct Agent Callingbbbbbbbb
Direct-agent is a special type of ACD call that is directed to a specific ACD
agent, rather than to any available agent in the split.  It is invoked by specifying
the direct_agent_call option in the Third Party Make Call or Route Select
capabilities.  This section covers the similarities and differences between the
direct-agent call and a regular ACD call; these similarities and differences are
independent of whether the direct-agent call is adjunct-monitored or
nonadjunct-monitored.  Therefore, the following sections on Direct Agent Calling
apply to both types of direct-agent calls.  Direct Agent Calling may be invoked.
Agent Work Modes with ACDbbbbbbbbbbbbbbb
All ACD agent work modes operate the same for direct-agent calls as for regular
ACD calls; that is:
An agent can answer a direct-agent call destined for him/her by becoming
available in the split the direct-agent call is associated with; that is, the
agent must be in the manual-in or auto-in mode for the split.
While on a direct-agent call, the agent becomes unavailable for all
subsequent direct-agent or regular ACD calls.  Multiple call handling can
override this.
After disconnecting from a direct-agent call from a split that the agent was
in auto-in before, then for each split the agent is logged into, the agent
returns to auto-in if he/she was in auto-in mode before, and into manual-in
if he/she was in manual-in mode before.
After disconnecting from a direct-agent call from a split that the agent was
in manual-in before, then the agent enters after-call-work mode for this
split, and is considered unavailable for all other splits.
12-22  Issue 4  September 1995 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Agent Work Modes with EASbbbbbbbbbbbbbbb
An agent can answer a direct-agent call destined for him/her by becoming
available by selecting the manual-in or auto-in work mode.
While on a direct-agent call, the agent becomes unavailable for all
subsequent direct-agent or regular ACD calls.  Multiple call handling can
override this.
After disconnecting from a direct-agent call in auto-in mode, the agent
becomes available for all skills logged into.
After disconnecting from a direct-agent call in manual-in mode, the agent
enters after-call-work mode and is not considered available for
direct-agent or skill ACD calls.
Priority Queuingbbbbbbbbbbbbbbb
There are five possible levels of priority in split queuing. In increasing order of
priority, these are: low, medium, high, top, and direct.  The different priority levels
can be obtained as follows:
1. Low priority:
With vectoring, queue to main command with low as priority
With vectoring, check backup command with low as priority
2. Medium priority:
With vectoring, queue to main command with medium as priority
With vectoring, check backup command with medium as priority
Without vectoring, calls to hunt groups
Without vectoring, nondirect-agent calls to ACD splits
Without vectoring, intraflowed ACD calls without priority on intraflow
Without vectoring, interflowed ACD calls without priority queuing on
the incoming trunks COR
3. High priority:
With vectoring, queue to main command with high priority
With vectoring, check backup command with high priority
Without vectoring, intraflowed ACD calls with priority on intraflow
Without vectoring, interflowed ACD calls with priority queuing on
the incoming trunks COR
4. Top priority:
With vectoring, queue to main command with top as priority
With vectoring, check backup command with top as priority
Issue 4  September 1995  
12-23