ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							Installation and Test for CallVisor ASAIbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Facility Test Circuit Pack Ð Required for duplicated systems only;
optional for unduplicated
Expansion Interface Circuit Pack  Ð For new multiple-port network
systems or upgrades.  (If you have the older TN776 circuit pack, it must
be replaced with a TN570 circuit pack or later, which permits CallVisor
ASAI to terminate on an Expansion Port Network [EPN]).
MultiQuest trunk for Flexible Billing
Software Installationbbbbbbbb
In addition to the CallVisor ASAI and the DEFINITY Communications System
basic software, the following software might be needed for your specific CallVisor
ASAI installation.  Refer to the 
DEFINITY Communications System Generic 1
and Generic 3 Installation and Test
, 555-230-104, for more information.
Automatic Call Distribution (ACD) Software  Ð For ACD configurations
Automatic Route Selection (ARS) Software  Ð For ISDN-PRI call routing
ISDN-PRI Software  Ð For ISDN-PRI trunks
Vectoring Basic Software  Ð For call vectoring applications and ASAI
adjunct routing
Vectoring Prompting Software Ð For integrated call prompting
applications
Vectoring (ANI II Digits Routing)
Vectoring (G3V4 enhanced)
Vectoring (G3V4 advanced routing)
EAS Agent Skills
Answering Machine Detection for Predictive Outbound Call Management
(OCM)
AT&T Adjunct Links
VDN Return Destination
Optionable Switch-Classified Calling
AT&T MultiQuest Flexible Billing
ASAI-Accessed Internally Measured Data
VuStats
14-2  Issue 4  January 1996 
						

							Installation and Test for CallVisor ASAIbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
CallVisor ASAI Link Administrationbbbbbbbb
The CallVisor ASAI software must be installed in your system before an ASAI
link can be administered and activated. Up to eight ASAI links can be
administered at the same time to the same or different adjunct processors, and
using either BRI or Ethernet transport, or both.
To administer an ASAI link, use the add station command and set the link type
to 
ASAI. Fill out the remainder of the form as appropriate for your ASAI host.
CallVisor ASAI links do not support Management Information Messages (MIMs).
Screen 2-1 shows a sample completed Add Station form.
add station  Page 1 of 1
-----------------------------------------------------------------------------
STATION 
Extension: 5000  BCC: 0
Type: ASAI  COR: 1
Port: 1A0102  COS: 1
Name: asai link 
EVENT MINIMIZATION? n
XID? y  Fixed TEI? y  TEI: 3
MIM Support? n
CRV Length: 2
Screen 14-1.  Add Station
For more information on CallVisor ASAI link administration, see the 
DEFINITY
Communications System Generic 3 CallVisor ASAI Protocol Reference,
555-230-221, and the DEFINITY Communications System Generic 3 Feature
Description
, 555-230-204.
Issue 4  January 1996   
14-3 
						

							Installation and Test for CallVisor ASAIbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Table 14-1 shows how feature options are specified for different ASAI vendor
partners equipment. 
MIM Support? must always be set to no.
Table 14-1.  ASAI Feature Options Administration for AT&T Vendor Partners (ISDN
Links Only
bbbbbbbbbbbbbbbbbbbbbbbb
MIM Fixed CRV Event
Vendor Partner XID Support TEI Length Min.
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
AT&T CONVERSANTÒVIS 4000 Yes No Yes,TEI=3 1 byte n
AT&T CONVERSANT VIS 5000 Yes No Yes,TEI=3 2 bytes n
Dialogic CT-Connect ÔNo No Yes, TEI=55 2 bytes n
International Business Machines
(IBMÒ)No No No 2 bytes y
Stratus Computers No No Yes,TEI=1 2 bytes n
Aristacom No No No 2 bytes n
Hewlett-Packard Yes No No 2 bytes n
CallVisor PC Yes No Yes,TEI=3 2 bytes n
(including EIS)
CallVisor 3000 No No No 2 bytes n
Novell Yes No Yes,TEI=3 2 bytes n
IBM ASAI-
Ethernet clientsNo No Yes,TEI=3 2 bytes y
All other ASAI-
Ethernet clientsNo No Yes,TEI=3 2 bytes n
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
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
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
See ``AT&T Vendor Partners that follows in this chapter for more information.
In addition to the CallVisor ASAI link administration, the DEFINITY
Communications System features that follow may need to be administered for
your specific ASAI application.  The required forms are listed as well.
Adjunct-Controlled Splits Ð Add/Change Hunt Group Form (For the
majority of applications, this field does not apply and should be left at the
default value of NONE.)
ASAI Adjunct Alarm Administration  Ð The system default for CallVisor
ASAI alarms is to provide warnings when an ASAI link fails or the adjunct
does not respond to switch messages. The customer can tune the level of
on-board and off-board alarms to warnings, or minor or major alarms.
Alarm severities are set by means of the set options maintenance
command, explained in 
DEFINITY Communications System Generic 3r
Maintenance
, 555-230-105.  Once the ASAI adjunct alarms are
14-4  Issue 4  January 1996 
						

							Installation and Test for CallVisor ASAIbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
administered to an alarm level, the switch alarms all CallVisor ASAI links
at that level.
Automatic Call Distribution (ACD) Ð Add/Change Hunt Group, Trunk
Group, Station, Feature-Related System Parameters, and Attendant
Console Forms
EAS Skills and Logical Agents Ð Agent Login ID form, Add/Change Hunt
Group form, and Add/Change VDN form
Automatic Route Selection (ARS)  Ð Change ARS Digit Analysis Form
Call Vectoring Ð Add/Change VDN and Call Vector Forms
ISDN-PRI Trunks and Options Ð Add/Change Trunk Group Form
Outbound Call Management (OCM) Special Information Tones
(SITs) Ð Remote Access Form
Answering Machine Detection Ð System-Parameters Customer-Options
Form
Option for Switch-Classified Calls Ð System-Parameters Customer-
Options Form
Flexible Billing Ð System-Parameters Customer-Options Form. In
addition, the following optional system features must be activated to
support the MultiQuest Flexible Billing feature:
Ð ASAI
Ð ISDN Ð Primary Rate Interface (ISDN-PRI)
Ð MultiQuest Flexible Billing
Finally, the following optional system features will probably be used when
Flexible Billing is active:
Ð Automatic Call Distribution (ACD) Ð Required if call routing uses
ACD
Ð Call Vectoring Ð Required if inbound calls use Call Vectoring for
routing
ASAI-Accessed Internally Measured Data  Ð System-Parameters
Customer Options Form.  In addition, the following system features must
be activated to support the ASAI-Accessed Internally Measured Data
feature:
Ð Internally Measured Data option
Ð VuStats
Issue 4  January 1996   
14-5 
						

							Installation and Test for CallVisor ASAIbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
For detailed instructions regarding the administration of the above features, see
the appropriate (G3i or G3r) 
DEFINITY Communications System Generic 3
Implementation 
document, 555-230-650 or 555-230-651, respectively.
CallVisor ASAI Link Testingbbbbbbbb
After the CallVisor ASAI link is administered and installed, perform the following
tests as described in the 
DEFINITY Communications System Generic 3
Installation and Test
, 555-230-104.
Status Station
Status bri-port
Test port
In addition, check that the switch does not report any alarms or errors associated
with the CallVisor ASAI port.
NOTE:
AT&T tests that the CallVisor ASAI link is functional as part of the basic
installation procedures. Coordination of additional testing can be done by
AT&T if the Single Point of Contact Enhanced Installation Offering is
purchased by the customer. Actual testing of other vendors equipment and
applications is performed by the customer or appropriate representative.
Additional testing of the adjunct application must be performed by the customer
to ensure that the application performs as desired.
AT&T Vendor Partnersbbbbbbbb
The following AT&T vendor partners have signed development agreements with
AT&T to share information about each others products and to establish working
relationships among companies.
NOTE:
This list of vendor partners is up-to-date at the time of this documents
publication.  However, the number of vendor partners may expand in the
future.  For a current list and more detailed information, contact your AT&T
representative.
Dialogic CT-Connect
International Business Corp. (IBM)
Hewlett-Packard (HP)
Aristacom
Stratus
14-6  Issue 4  January 1996 
						

							Installation and Test for CallVisor ASAIbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Tandem
Novell (PassageWayÔTelephony Services)
NOTE:
This product is known as NetWareÒTelephony Services if sold by
Novell instead of AT&T.
Electronic Information Systems (EIS)
See Appendix E in the 
AT&T DEFINITY Communications System Generic 3
CallVisor ASAI Planning Guide
, 555-230-222, for CallVisor ASAI functionality
supported by AT&T vendor partners.
Issue 4  January 1996   
14-7 
						

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
   
						

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbb
Call Scenarios and Applications
A
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
This Appendix has the following sections:
1. Basic Application Call Scenarios
2. Calls Across Multiple Switches
3. Expert Agent Selection Interactions
4. Converse Vector Command Interactions
5. Redirection on No Answer (RONA) Interactions
6. VDN in Coverage Path Interactions
7. User Scenarios Ð User to User (UUI) Information
8. User Scenarios Ð Connected IE for Non-ISDN Trunks
9. User Scenarios Ð ASAI-Provided Dial-Ahead Digits
10. User Scenarios Ð ASAI-Requested Digit Collection
11. User Scenarios Ð VDN Return Destination
12. ASAI Messaging Scenarios Ð VDN Return Destination
13. User Scenarios Ð Flexible Billing
Issue 4  September 1995  
A-1 
						

							Call Scenarios and Applicationsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
1. Basic Application Call Scenariosbbbbbbbb
The following call scenarios show how ASAI capabilities can be used to
implement several ASAI applications. Only sample parameters are given with the
ASAI messages; not all parameters are provided.  For example, the messages
do not show call identifiers or party identifiers for each message.  Duplicate event
reports and the associations that correspond to each message are not shown
either.
The application is assumed to know the telephone or extension number
associated with each VDN, ACD split, and agent or user shown. Additional
assumptions are provided with each sample scenario.
A-2  Issue 4  September 1995 
						

							Call Scenarios and Applicationsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Outbound Call Management Ð Preview
Dialing (Non-ISDN Facilities)
bbbbbbbbbbbbbbb
Call Initiated Event Report (A)
3rd Party Auto Dial
(dest=B, orig=A)
3rd Party Domain Control
(domain=A)
3rd Party Domain Control-ACK
Agent drops call
Dropped Event Report (A)
Adjunct Processor
Customer drops
Switch
Application displays
call list on the
agents data terminalAgent uses data
terminal to login
into application
Agent saves
customer recordAgent selects
customer to call
Agent
Terminal
A Agent
Phone
A Customer
Phone
B
Call uses non-ISDN
facilitiesTrunk Seized Event Report (B)
Connected Event Report (B)
Agent off-hook or
forced off-hook
Agent and customer
talk
The application in the adjunct processor provides the agent and/or user with a
call list. The agent uses the data terminal to select the destination to call. The
application then requests a call on behalf of the agent. The call uses non-ISDN
facilities.
Issue 4  September 1995  
A-3