ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbb
Tables
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
3Event Reporting and U-Abort Capabilities
3-1. Use of Event Reports in Associations 3-41
3-2. Call Merge Summary 3-45
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
4ASAI and Call Control
4-1. Call Control Acceptance in Various Call/
Station States 4-3
4-2. Detected SITs 4-10
4-3. Third Party Make Call Options 4-26
4-4. Allowable Originators and Destinations for
Specific Call Options 4-26
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
5ASAI and Domain Control
5-1. Call Control Acceptance in Various Party States 5-4
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
12ASAI and Feature Interactions
12-1. Interactions Between Feedback and Call Vectoring 12-17
12-2. Coverage Interactions for ACD Calls without
Priority Calling 12-27
12-3. Coverage Interactions for ACD Calls with Priority
Calling 12-27
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
13ASAI-Ethernet
13-1. Brouter Table Format 13-8
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
14Installation and Test for CallVisor ASAI
14-1. ASAI Feature Options Administration for AT&T
Vendor Partners 14-4
Issue 4  September 1995 
xv 
						

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbb
Tables
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
ACall Scenarios and Applications
A-1. Incoming Call Routed to External Destination
Example A-66
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
BASAI and Generic 3 Switch Requirements
B-1. System-Wide ASAI Limits B-1
B-2. ASAI Limits per Station B-2
B-3. ASAI Limits per ACD Split Domain B-3
B-4. ASAI Limits per VDN Domain B-3
B-5. ASAI Limits per Call B-3
B-6. ASAI Limits per Link B-4
xvi  Issue 4  September 1995 
						

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbb
About This Document
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
This reference manual provides detailed information regarding the CallVisor
Adjunct/Switch Application Interface1 for the Generic 3 switch.
ASAI is a communications interface that allows application processors (called
adjuncts in this document) to access switch features and control switch calls.
The ASAI is implemented using either an Integrated Services Digital Network
(ISDN) Basic Rate Interface (ASAI-BRI) or an Ethernet interface
(ASAI-Ethernet).
Intended Audiencebbbbbbbb
This document is written for the application designer responsible for
building/programming custom applications and features. This document is also
helpful to any individual who needs a functional description of ASAI.
ASAI provides users with the capability to drive a variety of switch features.  It is
essential, therefore, that readers of this document possess extensive knowledge
regarding not only these switch features themselves, but also their interactions.
NOTE:
See the ``Related Documents section for a list of manuals that provide
switch feature and ASAI protocol information.
aaaaaaaaaaaaaaaaaaa
1.  In the interest of brevity, CallVisor ASAI is referred to as ASAI throughout the remainder of this manual.
Issue 4  September 1995  xvii 
						

							About This Documentbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Terminologybbbbbbbb
Definitions of terms relating to ASAI can be found in the glossary at the end of
this document.
Conventions Used in This Documentbbbbbbbb
The majority of conventions in this document are self-explanatory and need not
be discussed here.  There are, however, some conventions whose meaning may
not be obvious to the reader.  An explanation of these conventions follows.
Chapters 3 through 11 detail the function of each feature or capability in this
version of ASAI.  A capability is a request for or an indication of an operation.
For example, dropping a party from a call is a capability of ASAI.  Related
capabilities are grouped into functional sets called capability groups.
2
Each capability within the group is divided into the following subsections:
Capability Name
Provides a short overview of the capability and its functions.
Information Flow
This heading provides information regarding the flow of data from the
adjunct to the switch or vice versa.  For example, the switch may generate
reports to the adjunct (application processor), but the adjunct does not
need to respond to these reports.  This situation is different when dealing
with many of the call control capabilities that require a give and take of
data between the switch and the adjunct.
 Parameter(s)
This heading documents the type of information (such as the caller_id)
that passes between the switch and the adjunct (usually in the form of a
request to the switch).  The actual name is based on the capability being
discussed; for example, Call Control Parameters.
aaaaaaaaaaaaaaaaaaa
2. Capability groups are analogous to Application Service Elements (ASEs) described in the 
AT&T Adjunct/Switch
Application (ASAI) Interface Specification, 555-025-203.
xviii  Issue 4  September 1995 
						

							About This Documentbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
ACK (positive acknowledgement) Parameter(s)
There are many instances when the switch simply acknowledges the
request made by the adjunct and subsequently performs the operation.
There are other times when the switch replies with specific information
(such as the identity of the party making the call) to the adjunct within the
acknowledgement.
Denial (NAK) Cause(s)
This heading designates a negative acknowledgement (NAK) from the
switch.  This means that the information provided by the adjunct to the
switch was incorrect; for example, one of the parameters, such as the
call_id, was incorrect.  At this point the switch rejects the request and
terminates the communication channel between the switch and the
adjunct.  The switch also provides a reason why the operation was not
performed.  These reasons or causes fall under the Denial (NAK)
Cause(s).
Each ASAI capability contains a Denial (NAK) section with a list of cause |
calues most commonly occurring.  An attempt was made to have these |
lists complete.  However, because of the many unpredictable |
switch/feature interactions, it is possible that those lists are not complete. |
Therefore, application and ASAI library writers should be able to handle |
any other (valid) cause values not listed under the particular capability.
Protocol (NAK) Error Cause(s)
This heading designates a protocol processing error.
Considerations
This heading provides the user with any special information that should be
taken into account for this particular capability.
Related Documentsbbbbbbbb
AT&T Adjunct/Switch Application Interface Specification (ASAI),
555-025-203
The ASAI Specification document provides a detailed description of the ASAI
Reference Model and contains all the capabilities available from ASAI.  The
CallVisor ASAI Technical Reference, on the other hand, describes only those the
capabilities available with the Generic 3 switch.
AT&T DEFINITYÒCommunications System Generic 3 CallVisor ASAI Planning
Guide
, 555-230-222
This manual provides planning and implementation information for CallVisor
ASAI.
Issue 4  September 1995  
xix 
						

							About This Documentbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
AT&T DEFINITY Communications System Generic 3 CallVisor ASAI Protocol
Reference, 
555-230-221
The Protocol Reference provides detailed protocol information of CallVisor
Adjunct Switch Application Interface (ASAI) for the Generic 3 switch.
NOTE:
Distribution of this document is restricted to AT&T.
AT&T DEFINITY Communications System Generic 3 Installation, Administration,
and Maintenance of CallVisor ASAI Over DEFINITY LAN Gateway
, 555-230-223
This document describes the installation, administration, and maintenance of the
ASAI-Ethernet application, which provides ASAI functionality using 10Base-T
Ethernet rather than BRI as a transport media.
AT&T DEFINITY Communications System Generic 3 Feature Description,
555-230-204
The Feature Description serves as an overall reference for the planning,
operation, and administration stages of Generic 3 switch.
AT&T DEFINITY Communications System Generic 3 System Description,
555-230-206
This manual provides a technical description of hardware, environmental, and
space requirements and parameters.
AT&T DEFINITY Communications System Generic 3 V4 Implementation,
555-230-655
This manual documents the implementation of the Generic 3i switch.
AT&T DEFINITY Communications System Generic 3 Call Vectoring/EAS Guide,
555-230-520
This manual documents call vectoring for the Generic 3 switch.
GBCS Products Security Handbook, 555-025-600
This manual provides information on securing various AT&T products against toll
fraud.
NOTE:
With regard to CallVisor ASAI, the importance of security cannot be
overestimated.  It is just as important to secure the processor the
application resides on as it is to secure the PBX.
xx  Issue 4  September 1995 
						

							About This Documentbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Issue 4  September 1995  xxi 
						

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbb
ASAI and Capability Groups
1
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Introductionbbbbbbbb
The purpose of this chapter is to present an overview of ASAI and the services it
provides.
ASAI services are divided into functional sets called capability groups.
1 Capability
groups enable the adjunct2 to communicate with and control the switch.3
aaaaaaaaaaaaaaaaaaa
1. Capability groups are analogous to Application Service Elements (ASEs) described in the 
AT&T Adjunct/Switch
Application Interface (ASAI) Specification, 555-025-203.
2.  For the purpose of this document, the term 
adjunct is defined as the application processor.
3. ASAI is not limited to a one-to-one correspondence between the switch and an adjunct. Multiple adjunct
configurations are available and are discussed in a subsequent section.  For the sake of this introduction,
however, the scope is limited to a single switch and a single adjunct.
Issue 4  September 1995  1-1 
						

							ASAI and Capability Groupsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Each capability group is defined by the set of functions within it.  ASAI defines
eight capability groups in all:
Call Control
4The capabilities in this group enable the adjunct to place,
monitor, and control any party on a single call as it moves
through the switch.
Domain
(Station/ACD
Split) Control
4
The station capabilities in this group enable the adjunct to
place, monitor, and control all calls at a specific station
domain.
This capability group also enables the adjunct to receive
reports as to the status of agents on an ACD split.  Currently
the switch provides the Logout Event, and, starting with
G3V4, the Login Event.
NotificationThis capability group lets the adjunct request and cancel
event reporting on certain calls.
RoutingThis capability group allows the switch to ask the adjunct for a
calls destination.  The adjunct supplies the destination based
on call-related information (for example, called number).
Request
FeatureThe single capability in this group lets the adjunct request
switch features, such as the agent login, logout, work mode
changes, Call Forwarding, and Send All Calls (SAC).
Value QueryThis capability group enables the adjunct to request
information regarding switch resources.  Using this capability
group would, for example, allow a user to query the switch for
the number of agents currently logged in to an ACD split.
Set ValueThis capability group enables the adjunct to set switch-
controlled services, such as the Message Waiting Indicator
(MWI), for any specified telephone set.
MaintenanceThis capability group enables the adjunct to suspend and
resume switch alarms on the ASAI link.  It also enables the
adjunct or the switch to request the status of the ASAI
software at the remote endpoint using the Heartbeat
capability.
aaaaaaaaaaaaaaaaaaa
4.  The Call Control Capability Group is the Single Call Control subset of the Third Party Call Control Capability
Group. The Domain Control Capability Group is also a subset of  the Third Party  Call Control Capability Group,
as specified in the 
AT&T Adjunct/Switch Interface (ASAI) Specification, 555-025-203.  For the sake of brevity,
these groups are referred to as the Call Control Capability Group and the  Domain Control Capability Group,
respectively. The specific capabilities within each group carry the Third Party prefix; for example, Third Party
Make Call and Third Party Domain (Station) Control Request.
1-2  Issue 4  September 1995 
						

							ASAI and Capability Groupsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Capabilitiesbbbbbbbb
While capabilities are grouped by the services they may provide, all groups
divide their particular capabilities into three categories or types.  These
categories are: initiating, controlling, and terminating capabilities.
InitiatingThese capabilities are used to open a channel of
communication between the adjunct and the switch
for messaging purposes.  An example of an initiating
capability is Third Party Make Call that allows the
adjunct to direct the switch to place a call.
ControllingThese capabilities are used to exchange information
once the channel of communication has been
established.  For example, Third Party Selective Hold
can be used to place a call on hold, or Third Party
Merge can be used to transfer a call.
TerminatingThese capabilities end or close the channel of
communication between the adjunct and the switch.
For example, Third Party Call Ended indicates that
the call has ended.
Capabilities and Associationsbbbbbbbbbbbbbbb
Central to this introduction of capability groups and ASAI in general is the
concept of an 
association.  An association is defined as a channel of
communication between the adjunct and the switch for messaging purposes.
It may be helpful to think of an association as a communications session; each
session could involve information pertaining to many calls.
The previous section regarding types of capabilities showed that all capabilities
act across a channel of communication which 
is an association.  Initiating
capabilities begin an association, controlling capabilities manipulate message
exchange during the association, and terminating capabilities end the
association.
Associations and Capability Groupsbbbbbbbbbbbbbbb
ASAI defines eight different types of associations, each of which corresponds to
a particular capability group:
Call Control Associations
Domain (Station/ACD Split) Control Associations
Notification Associations
Routing Associations
Issue 4  September 1995  
1-3