ATT DEFINITY Communications System Generic 3 Instructions Manual

							Call-By-Call Service Selection
Issue  3   March 1996
3-477
Screen 3-33. Trunk Features
As shown above, a variety of specifications can be administered in the table for 
the treatment of incoming calls. The table allows for as many as 12 different 
combinations of call treatments. Seven columns are provided for seven different 
specifications. These specifications are as follows:
nSelection Criteria
—Service/Feature 
— Specifies the ISDN-PRI Services/Features to 
which the sp ecified  call treatment may ap ply. These 
services/features are those discussed in the ‘‘Services Used With 
Call-By-Call Service Selection’’ section of this feature description. 
The identifier ‘‘other’’ can be used for all Services/Features not 
explicitly specified.
—Called Len 
— Specifies the number of digits contained in the 
Called Party Numb er (the di gits received for the incoming call).  
The number of digits contained in the Information Element must 
exactly match the number of digits specified in this field. Allowable 
entries are 0 through 16 or blank. A blank entry indicates a wild 
card, meaning that a called number of any length matches.
—Called Number 
— Specifies the leading digits contained in the 
Called Party Number.  For this row to be chosen for a call, the data 
is this field must exactly match the leading digits in the IE.  A blank 
entry indicates that the incoming digits are not significant for this 
entry. Allowable entries are 1 through 16 digits or blank.
   
   TRUNK FEATURES                                                  Page 2 of x 
     Service/    Called     Called        Del       Insert      CPN/BN     Night 
     Feature      Len       Number                                           Serv 
   _____________  ___   _______________   ___   ______________ __________   _______ 
   _____________  ___   _______________   ___   ______________ __________   _______ 
   _____________  ___   _______________   ___   ______________ __________   _______ 
   _____________  ___   _______________   ___   ______________ __________   _______ 
   _____________  ___   _______________   ___   ______________ __________   _______ 
   _____________  ___   _______________   ___   ______________ __________   _______ 
   _____________  ___   _______________   ___   ______________ __________   _______ 
   _____________  ___   _______________   ___   ______________ __________   _______ 
   _____________  ___   _______________   ___   ______________ __________   _______ 
   _____________  ___   _______________   ___   ______________ __________   _______ 
   _____________  ___   _______________   ___   ______________ __________   _______ 
    
						

							Feature Descriptions
3-478Issue  3   March 1996 
nAction Taken Based on Selection Criteria
—Del 
— Specifies the numb er of leading digits to be deleted from 
the incoming Called Party Number.  Calls of a particular typ e may 
be administered to be routed to a single destination by deleting all 
incoming digits and then administering the “ Insert”  field with the 
desired extension.
—Insert 
— Specifies  the  digits  to  be  prepended to the front of the 
Called Party Numb er.  The new numb er is used to route the call.  
Allowable entries are up to 16 digits or blank.
—CPN/BN   
— Specifies your preference of a Calling Party Number 
(CPN) or Billing Numb er (BN) request for this type of  call.  A  blank 
or ‘‘none’’ indicates that the switch is not requested either CPN or 
BN for any incoming calls of this type.  Allowable entries are BN 
only, prefer BN but accept CPN, CPN only, and p refer CPN but 
accept BN.
—Night Serv 
— Specifies  a  night service extension per 
Service/Feature.  An entry other than blank overrides the night 
destination entry on Page 1 of the form.  Allowable entries are an 
assigned extension, attendant, or blank. 
NOTE:
Bellcore NI-2 Call-By-Call service does not support the 
delivery of CPNI B-N on a  per call basis.
The treatment for an incoming call is selected based on the “Service/Feature, 
Called Len” , and “ Called Number”  fields in the table.  When the attributes of an 
incoming call match these specifications, the call is treated according to the 
corresponding Del, Insert, CPN/BN, and Night Service specifications. If an 
incoming call matches more than one set of specifications, the most restrictive 
case is selected.  The following table lists the possible cases in order of most 
restrictive to least restrictive: 
						

							Call-By-Call Service Selection
Issue  3   March 1996
3-479
Table 3-47 lists the most/least restrictive specifications.
Considerations
Call-By-Call Service Selection provides the following benefits:
nCost Reduction — Since many services share the same trunks, the total 
number of trunks can be reduced.
nImproved Service — Call-By-Call Service Selection trunks can reduce the 
probability of features and services being blocked.
nSimp lified Networking — Network engineering is simplified because 
analysis of trunking needs can be done based on total traffic instead of on 
a per-service basis.
nThe ability to respond to changes in a more timely fashion. The network 
does not have to be consulted because of the flexibility provided by the 
usage allocation plans.
nMeasurement of Call-By-Call Service Selection calls. Table 3-47. Call-by-Call Service Selection Most/Least 
Restrictive Specifications
Service/ Feature Called Len Called Number
Most Restrictive Specified Specified X Number Of 
Leading Digits 
Specified
Specified Specified Y Number Of 
Leading Digits 
Specified, Where 
Y < X 
Specified Specified Not Specified
Specified Not Specified Not Specified
Specified as ‘‘other’’ Specified X Number Of 
Leading Digits 
Specified
Specified as ‘‘other’’ Specified Y Number Of 
Leading Digits 
Specified, Where 
Y <  X
Specified as ‘‘other’’ Specified Not Specified
Least Restrictive Specified as ‘‘other’’ Not Sp ecified Not Specified 
						

							Feature Descriptions
3-480Issue  3   March 1996 
Interactions
The following features interact with the Call-By-Call Service Selection feature.
nAAR 
Call-By-Call Service Selection uses the same routing tables and routing 
preferences that are used by AAR.
nARS 
Call-By-Call Service Selection uses the same routing tables and routing 
preferences that are used by ARS.
nGR S 
Call-By-Call Service Selection uses the same routing tables and routing 
preferences that are used by GRS.
nCDR 
On successful incoming and outgoing Call-By-Call Service Selection calls, 
the Network Specific Facility sp ecified by the call’s Network Specific 
Facility Information Element is recorded by CDR. CDR refers to this 
information as the INS (ISDN Network Service).
If an outgoing Call-By-Call Service Selection call uses an Inter-exchange 
Carrier (IXC) other than the presubscribed common carrier, CDR records 
the 3- or 4-digit IXC code. CDR may not record the IXC code properly if 
the dialed code format differs from the US IXC c o de formats.
When a Call-By-Call Service Selection call is rejected because of a trunk 
group usage allocation plan, CDR records the c ause as an ineffective call 
attemp t.
nTime of Day Routing
Any Time of Day Routing a dministration that affects routing preference 
also affects Call-By-Call Service Selection.
The Time of Day Routing feature can be used to vary the IXC based on the 
time of day and day of the week.
nTraffic Measurements
The system provides traffic measurements for each individual service 
administered as part of the ISDN Call-By-Call Service  Selection trunk 
group.
Administration
Call-By-Call Service Selection is administered by the System Manager on a per 
trunk group basis.  The following items require administration:
nISDN-PRI Trunk Group — Must be a dministered with a Service Type of 
Call-By-Call Service Selection.  The trunk group administration also 
includes the following: 
						

							Call-By-Call Service Selection
Issue  3   March 1996
3-481
— Incoming Call Handling Treatment
— Whether or not UAPs are required
—UAPs
— UAP Assignment Schedule
— Group Member Assignments
nAAR/ARS Routing Patterns — Routing Patterns can be administered to 
include a Network Specific Facility and/or IXC.
nNetwork Specific Facilities Encoding — New Network Specific Facilities 
can be added as needed by the system technician.
Hardware and Software Requirements
A TN767 24-port DS1  circuit  pack or TN464B/C/D DS1 interface (24-port 
T1/32-port E1)  circuit  pack  is  required for  assignment  of  a  signaling link and up 
to 23 or 30 ISDN-PRI Trunk Group members. For G3vs, a TN765 Processor 
Interface circuit pack is required in conjunction with the DS1 circuit pack, for 
ISDN D-Channel Links. For G3s and G3i, a TN675 Processor Interface or a 
TN778 Packet Control circuit pack are required for ISDN D-Channel Links.
NOTE:
The TN767 and the TN464C and later revisions of the DS1 circ uit packs 
provide a DSX1 interface. 
						

							Feature Descriptions
3-482Issue  3   March 1996 
CallVisor Adjunct/Switch 
Applications Interface (ASAI)
Feature Availability
This optional feature may be p urchased with any Generic 3 release except 
G3vs/G3s ABP and G3i-Global.
Description
Provides one or more links between the DEFINITY switch and one or more 
adjuncts. CallVisor ASAI improves the call handling efficiency of ACD agents and 
other system users b y allowing an adjunct to monitor, initiate, control, and 
terminate calls on the switch. The CallVisor ASAI interface may be used for 
Inbound Call Management (ICM), Outbound Call Management (OCM), and office 
automation/messaging applications.
CallVisor ASAI services are provided using either Integrated Services Digital 
Network (ISDN) Basic Rate Interface (BRI) transport (CallVisor ASAI-BRI), or LAN 
Gateway Transmission Control Protocol/Internet Protocol transp ort (CallVisor 
ASAI-LAN Gateway).
Regardless of transport type, CallVisor ASAI messa ges and procedures are 
based on the ITU-T Q.932 international standard for supplementary services. A 
special information element, the Q.932 Facilities Information Element (FIE), 
carries the CallVisor ASAI requests and responses across the interface. An 
application program can access CallVisor ASAI services or features by 
supporting the ASAI protocol, by using a computer vendor, or by a third-party 
provider application programming interface.
The system can have up to eight (four for G3s PBP) CallVisor ASAI links.
G3V4 ASAI Enhancements
nASAI Accessed Internally Measured Data
This feature allows an ASAI adjunct application to access and retrieve 
Internally Measured Data used to provide VuStats information to 
display-equipped digital voice stations. The a p plication accesses this 
data via a new Value Query messa ge that specifies whether agent, 
split/skill, trunk group, or VDN information is b eing requested. The new 
message also specifies a particular observed object of the type (for 
example, agent or split) specified in the request.
By providing Internally Measured Data via ASAI, applications can offer 
enhanced VuStats-like presentations (for example, using g raphics, color, 
or multime dia) on a PC or can further process this data to provide  
						

							CallVisor Adjunct/Switch Ap plications Interface (ASAI)
Issue  3   March 1996
3-483
enhanced statistics for better call center management. Also, VuStats-like 
service can be provided without requiring a digital display-eq uipped 
station.
nSend DTMF Signals
This feature is an ASAI-accessed service that, when invoked by a client 
application, causes the DEFINITY system to send a DTMF sequence on 
behalf of one p arty on an active call. The di git sequence to be transmitted 
is contained  in the ASAI service message.
The DTMF tones can be heard by any endpoint connected to the sending 
talk path. Through such a tone sequence, an adjunct can interact with 
far-end applications such as automated bank tellers, automated 
attendants, voice mail systems, various databases, and paging services. 
An application could provide certain convenience features such as 
automated entry of passwords or service-access sequences.
nFlexible Billing
This feature allows an ASAI adjunct to change the rate at which an 
incoming 900-type call is billed. 
nRedirect Call
This feature allows an ASAI a djunct to d irect the switch to move an already 
alerting call away from an extension (at which it is alerting) to another 
en d point. Prior to G3V4. such routing was possible only if switch features, 
rather than an ASAI-provided service, were used (for example, call 
forward ing or Send All Calls). With this service, an application could, for 
example, d etermine, based on call-related information or time of d ay, etc., 
whether to answer the call or re-route it to some other numb er.
This servic e does not support removing a call from a queue. Only calls 
alerting at extensions can be manipulated by this service.
nASAI-Accessed Integrated Directory Database Service
This feature allows an ASAI adjunct to access and retrieve administered 
name-extension associations stored in the switch (all administered names 
associated with station extension numb ers, trunk groups, and VDNs). The 
application ac cesses this data via a new Value Query message containing 
the target extension. If a valid Query Message is submitted, the switch 
responds with a message containing the administered name.
nEvent Report Capabilities
Enhan cements to Event Re ports allow ASAI adjuncts to receive Event 
Reports when specified events occur at monitored objects. In addition, in 
the Alerting Event Report, new cause values are provided to specify a 
reason for redirection.
The following are descriptions of new/changed Event Re port  for  G3V4. 
These reports are provided only if Link Version 2 is active. 
						

							Feature Descriptions
3-484Issue  3   March 1996 
nAgent Login Event Report — This is a new Event Re port provided 
when an agent logs into a domain controlled ACD group or EAS 
skill. Notification of manual login events allows adjunct applications 
to maintain accurate views of current agent login/logout status.
nCall-Originated Event Report — This is a new Event Report 
provided when a call is manually or otherwise originated from a 
domain-monitored station. It also provides the d ialed digits to an 
application.
nAlerting Event Report — This existing Alerting Report has been 
enhanc ed to provide a new set of cause code values that ma p 
one-to-one to each existing G3V4 reason for redirection that 
a p pears on display-equipped stations when a redirected call is 
offered .
The new cause codes are provided in an existing Information 
Element of the Report. An adjunct application can use this 
information to provide an enhanced information disp lay (for 
example, on a comp uter monitor) to called parties or to otherwise 
determine how to b est handle an incoming call.
In a ddition to these GV4 enhancements, a new transport option, ASAI-LAN 
Gateway, is available. Also, CPN/BN on BX.25 links has been removed in G3V4.
See the 
DEFI NIT Y Comm uni c a tions System Generic 3 CallVisor ASAI Technical 
Referenc e,
 555-230-220, for more d etail on these enhancements.
CallVisor ASAI Capabilities
The following capability groups are provided by CallVisor ASAI: 
nThird Party Call Control Group
nThird Party Domain (Station/ACD Split) Control Group
nNotification Group
nSet Value  Grou p
nValue Query Group
nRequest Feature Grou p
nRouting Group
nMaintenance Group
The following paragraphs provide an overview of these c a pability groups.
NOTE:
The Third Party Domain (Station/ACD Split) Control Capability Group is a 
actually a subsection of the Call Control Capability Group. For  the  purpose 
of this document, the Third Party Domain (Station/ACD Split) Group is 
treated as a separate capability group. This section represents the 
DEFINITY Communications System imp lementation of ASAI, as described  
						

							CallVisor Adjunct/Switch Ap plications Interface (ASAI)
Issue  3   March 1996
3-485
in the DEFINITY Communications System Generic 3 CallVisor ASAI Protocol 
Reference
, 555-230-221, and the DE FI NITY  Co mm unications System 
Generic 3 CallVisor ASAI Technical Reference
, 555-230-220.
Computer vendors may not imp lement all of the ASAI cap a bilities with their 
respective Application Programming Interface (API). Specific comp uter vendors 
determine which aspects of these capabilities are supported within their APIs.
Third Party Call Control Capabilities Group
Third Party  Call control c a pabilities are used by the adjunct to initiate, control, 
and terminate calls to which it is not a party. The  following capabilities make up 
the Third Party Call Control capa bilities:
nInitiating Capabilities:
—Third Party Make Call 
— Used by the adjunct to set up a call. This 
capability supports the following typ es of adjunct-c ontrolled calls:
— Switch-Classified
— User-Classifie d
— Direct-Agent
— Supervisor-Assist
These call types are described in the next section of this feature 
description, CallVisor Adjunct/Switch Ap plications Interface 
(AS A I ) .
— User-to-User Information (UUI) Transport can be included in 
Third Party Make Call.
— Third Party Take Control 
— Used to take control of a call that 
is already in progress if other third party call control 
functions (such as hold, drop, and so on) are desired.
nControl Capabilities:
—Third Party Selective Drop 
— Used b y the adjunct to request that 
a party b e drop p ed from the specified adjunct-controlled call.
—Third Party Selective Hold 
— Used by the adjunct to request that 
a party on a sp ecified adjunct-controlled call be placed on hold.
—Third Party Reconnect 
— Used by the adjunct to request that a 
party be reconnected to a specified adjunct-controlled call.
—Third Party Merge 
— Used by the adjunct to request that two 
adjunct-c ontrolled calls be merged. Merging two calls means 
conferencing the calls or transferring a held call to an active call. 
The adjunct specifies the d esired type of merge.
—Redirect Alerting Call — Used by the adjunct to reroute a call that 
is alerting at a station. 
						

							Feature Descriptions
3-486Issue  3   March 1996 
nTerminating Capabilities:
—Third Party Relinquish Control 
— Used by the adjunct to request 
that a sp ecified adjunct-controlled call no longer send call events. 
The call must have been previously controlled by the same adjunct.
—Third Party Clear Call 
— Used by the adjunct to request that a 
specified adjunct-controlled c all b e d rop ped (all p arties on that call 
are dropped and all resources are released from the call).
—Third Party Call Ended 
— Invoked by the switch as a result of an 
adjunct-c ontrolled call being dropped. This capability lets the 
switch terminate the exchange between the switch and the adjunct 
of messages related to CallVisor ASAI.
nEvent Reporting Capability:
—Event Report 
— Used by the switch to convey call feedback and 
event information in the form of event reports to the a djunct. Call 
events are sent to the adjunct for monitored and controlled calls.
CallVisor ASAI Call Types
Table 3-48 shows the CallVisor ASAI c all types that the Third  Party Make Call, the 
Third Party Auto Dial, and the Route Select capabilities may request.
These call types are described next.
Switch-Classified Calls
A ‘‘Switch-Classified Call’’ is primarily used in Outbound Call Management 
(OCM) applications with AutoPace or Predictive Dialing.
An adjunct initiates Switch-Classified calls on behalf of the originator (extension 
number associated with a split, hunt group, or announcement) with only the 
answered calls are transferred to the originator; other calls are dropped by the 
switch.
Table 3-48. CallVisor ASAI Call Types Supported
Supported by...
Call TypeThird Party 
Make CallThird Party 
Auto DialAdjunct Route or 
Route Request
Switch Classified Calls X
User Classified Calls X X X
Direct Agent Calls X X
Supervisor Assist Calls X