ATT DEFINITY Communications System Generic 3 Instructions Manual

							Call Waiting Termination
Issue  3   March 1996
3-467
Considerations
With Call Waiting Termination, the party who calls a busy single-line voice 
terminal does not have to hang up and try the call again later. Instead, the call 
waits at the called voice terminal until the called party hangs up on the current 
call.
Call Waiting Termination applies only to busy single-line voice terminals. Calls to 
multi-appearance voice terminals are route d to an idle call ap pearance and do 
not wait.
An analog voice terminal user must place the active call on ‘‘soft’’ hold (see Hold 
feature) and dial the Answer Hold-Unhold feature access code to answer the 
waiting call. The soft held call at that time becomes a ‘‘hard’’ held call.
If an analog single line set has the Call Wait feature enabled and has created a 
conference call, the Call Wait feature is denied. For example, when caller A on an 
analog set is talking to caller B, then flashes and is talking to caller C, and flashes 
to conference B and C, then, if caller D calls caller A, the Call Wait feature is 
denied.
Interactions
Call Waiting is denied when the following features are activated at the single-line 
voice terminal:
nAutomatic Callback (to or from the voice terminal)
nData Privacy
nData Restriction
nAnother Call Waiting Call
A Call Waiting call cannot be picked up by a Call Pickup group member.
Administration
Call Waiting Termination is assigned on a p er-voice terminal b asis b y the System 
Manager. The only administration required is the assignment of Call Waiting 
Termination to the desired voice terminals.
Hardware and Software Requirements
No a d ditional hardware or software is required. 
						

							Feature Descriptions
3-468Issue  3   March 1996 
Calling Line Identification (CLI) Prefix
Feature Availability
The Calling Line Identification (CLI) Prefix feature is available with G3V4 R elease 
3 and later releases.
Description
The Calling Line Identification (CLI) Prefix feature allows DEFINITY to modify 
calling party number (CPN) information for ISDN/PRI calls that come in to the 
switch on a given trunk group. These calls may terminate locally, or may be 
tandemed out to other private switches or central offices. This feature only 
a p plies to incoming calls, and is administered for and applied to
 all calls on a 
trunk group. It does not apply to calls originated locally.
Based on the values in the Calling Number - Delete, Insert and Numbering 
Format fields, DEFINITY will delete up to 15 of the most significant digits from the 
incoming CPN information. If there is a digit string in the Insert field, DEFI NI TY 
a p pends these numb ers to the CPN after deleting the sp ecified numb er of d igits. 
Only the first 15 digits are p assed on when the call is routed.
This feature is a requirement of the Unisource Network, but anyone may use the 
CLI Prefix  for  call  accounting or redirection purposes. By using this feature in 
conjunction with Call Vectoring, it is possible to accomplish call routing required 
by Unisource, as well as Unisource-sp ecific error handling. For examp le, if ANI 
information is required, a vector step can check whether it is present, and if the 
ANI is exa ctly the same as the inserted d i gits, this call may be rejected. 
Considerations
For switch- or adjunct-based features that require database lookup of CPN/ANI 
information, you will need to change the appropriate databases to reflect the CLI 
Prefix modifications. For example, if you use the CLI Prefix feature in conjunction 
with Call Vectoring, you may need to update the Vector Routing Table. 
Because Call Vectoring can determine whether an incoming call has Automatic  
Number Identification or not, if you use the CLI Prefix to a dd  d i gits to incoming 
CPNs, you may need to program ANI  detection differently.
If you administer the feature to delete incoming digits, this may lead to imp recise 
or amb iguous CPN/ANI lookups for features such as Malicious Call Trace. 
						

							Calling Line Identification (CLI) Prefix
Issue  3   March 1996
3-469
Interactions
Because this feature affects the calling party information for all c alls coming in on 
a given trunk group, other features that use the CPN will receive modified calling 
number information. However, the functionality of these features will not change. 
Terminal d isp lays for calls that have been mo dified with the CLI Prefix will reflect 
the modifications. 
The Message Sequence tracer continues to record  CPN information as it c ame in 
on the ISDN link, and does not record the modified number. 
The following features receive CPN information that may be changed as a result 
of the CLI prefix:
nAttendant Display
nAutomatic Incoming Call Disp lay
nCoverage Incoming Call Identification
nCall Detail Recording
nCalling Number Delivery to CMS (SID/ANI)
nCalling Number Display
nCall Pickup
nCall Vectoring:
— ANI/II Digits Routing
— Converse Command (VRU Inte gration) - if digits were added to the 
CPN, a slightly longer time may be required when the CPN is 
passed inband to a Voice Response  Unit.
— Error Trace Log (Vector Events)
nCommonwealth of Ind e pendent States - Outbound Call MFR ANI 
Transmission
nDS1 Interface
nDCS Alphanumeric Display for Terminals
nISDN/BRI
nISDN Call-by-Call Service Selection
nISDN QSIG Name and Number
nISDN QSIG Call Diversion 
nISDN QSIG Call Transfer
nISDN Gateway - 1-Way BRI Interface
nIntegrated R2-MFC  Signaling (DID/CO)
nInter-PBX Attendant Calls (IA Service) 
						

							Feature Descriptions
3-470Issue  3   March 1996 
nMalicious Call Trace - If the incoming CPN is affected by this feature, 
accurate lookup of the numb er may not be p ossible.
nNetwork Access - Public 
nNetwork Access - Private Premises Bases
nNetwork Access - Private Public Net Based (SDN)
nPC/PBX Connection
nPC/ISDN Connection
nTransfer (single-line and multi-ap p earance)
nTrunk-to-Trunk Transfer
nVoice Terminal Display - Calling Number Display (SID/ANI/Extn ID)
Administration
This feature can be implemented for incoming calls on a per trunk group 
(incoming or two-way) basis. The administration required includes the 
assignment of digits to delete and/or a p pend to CPN information, and the 
numbering format to use. Send Calling Number must be set to “y. All of these 
fields are found on the ISDN/PRI Trunk Group form.
NOTE:
If you have an ISDN trunk group with incoming calls that are mixed 
between those that need this feature and those that d on’t, partition the calls 
into different trunk groups so that the CLI Prefix feature can be 
administered only for those calls that need it.
Existing G3MA Bulkload scripts may need to be modified to accommodate the 
CLI Prefix  Administration  fields.
Hardware Requirements
None. 
						

							Call-By-Call Service Selection
Issue  3   March 1996
3-471
Call-By-Call Service Selection
Feature Availability
This o ptional feature is available with  G3vs/G3s PBP, Generic 3i, and Generic 3r, 
and is not available with G3vs/G3s ABP.
Description
Call-By-Call Service Selection allows a single ISDN-PRI trunk group to c arry calls 
to many services or facilities (such as a SDN, MEGACOM telecommunications 
service, MEGACOM 800 service, and so on) and/or to carry calls using different 
Inter-exchange Carriers.
NOTE:
The Call-by-Call Service is only applicable for Country Protocol option 1 
(U.S.).
Call-By-Call Service Selection uses the same routing tables and routing 
preferences that are used b y AAR, ARS, and GRS. The service or facility used on 
an outgoing Call-By-Call Service Selection call is determined by information 
assigned in the AAR/ARS/GRS routing patterns.
As an example of how Call-By-Call Service Selection works, see the following 
figure. Without Call-By-Call Service Selection, each trunk group must be 
dedicated to a specific service or facility.  Call-By-Call Service Selection 
eliminates this requirement by allowing a variety of services to use a single trunk 
group.  These services are specified on a call-by-call basis. Trunking efficiency 
is imme diately obtained with Call-By-Call Service  Selection by distributing traffic 
over the total numb er of available trunks.
Services Used With Call-By-Call Service 
Selection
The services used on incoming and outgoing Call-By-Call Service Selection calls 
are assigned after an ISDN-PRI trunk group is assigned a service type of 
Call-By-Call Service Selection. A Call-By-Call Service Selection trunk g roup can 
be administered to carry calls to many services.  The available services in the US 
are as follows:
nACCUNET Digital Service — AT&T’s digital network services for various 
high-volume, high-speed data transmission requirements.
nINW ATS  — Provides OUTWATS-like pricing and service for incoming 
calls.
nAT&T Long Distance Service — A shared use, two-way, 
premises-to-p remises service that uses the public-switched network to 
transmit and receive voice, data, and graphics communications. 
						

							Feature Descriptions
3-472Issue  3   March 1996 
nOUTW A TS  B a n d  — WATS is a voice-grade service providing both voice 
and low-speed data transmission capabilities from the user’s location to 
defined service areas commonly referred to as bands.  Currently, the 
widest band is five.
nMEGACOM Service — Provides an AT&T service that provides unbanded 
long distance services using sp ecial access (PBX to 4ESS switch) from an 
AT&T node.
nMEGACOM 800 Service — Provides an AT&T service that provides 
unbanded 800 service using special egress (4ESS switch to PBX) from an 
AT&T node.
nNetwork O perator — Provides access to the network operator.
nSDN — An AT&T offering that provides a virtual private network using the 
public-switched network. SDN can carry voice and data between 
customer locations as well as off-net locations.
nPresubsc rib e d Common Carrier Operator — Provides access to the 
presubsc ribed common carrier operator.
nMaximum Banded WATS — A WATS-like offering for which a user’s calls 
are billed at the highest WATS band subscribed to by the user.
nInternational 800 — Allows a subscriber to receive international calls 
without a charge to the call originating party.  The subscriber of the 
service is charged for the calls.
nMULTIQUEST. Telecommunications Service — Service b etween callers at 
switched-access locations and service p roviders d irectly connected to the 
AT&T switched network.  Callers a ccess the service p roviders by dialing a 
700 number.
nOther User-Defined Services — New service typ es can be assigned as 
they are developed and defined.
nCall-By-Call services by Bellcore NI-2 PRI are Foreign Exchanges (FX), 
Tie, OUTWATS, and INWATS. The DEFINITY switch does not supp ort the 
NI-2 FX, Tie, and Bonded OUTWATS services. 
NOTE:
When the DEFINITY  swi t c h  is connected to 5ESS, all of the services 
supported under the AT&T and NI-2 country options are available.
A call-by-call service selection examp le is shown in Figure 3-2. 
						

							Call-By-Call Service Selection
Issue  3   March 1996
3-473
Figure 3-2. Call-By-Call Service Selection Example
ISDN-PRI Messages and Information Elements 
Used for Call-By-Call Service Selection
Although the technical details of ISDN-PRI messages and information elements 
are not critical to implementing the ISDN-PRI application, the following details 
may aid in the understanding of some readers and are therefore included in this 
description.
Call-By-Call Service Selection allows the system to specify one of the preceding 
service types on a call-by-call basis.  This is done via a SETUP message that 
indicates the intent of the originating system to initiate a call using the specified 
service or facility.  The SETUP message contains units called information 
elements which specify call-related information. The information elements used 
with Call-By-Call Service Selection are as follows:
nNetwork Specific Facility — Indicates which facilities or services are to be 
used to complete the call.
MEGACOM TRUNK GROUP
MEGACOM 800 TRUNK GROUP
SDN TRUNK GROUP
OUTWATS TRUNK GROUP
WITH CALL BY CALL SERVICE SELECTION:
A SINGLE TRUNK GROUP CARRIES CALLS FOR A VARIETY OF
SERVICES ON A CALL-BY-CALL BASIS
CALL BY CALL SERVICE SELECTION
TRUNK GROUP DEFINITY
COMMUNICATIONS
SYSTEM
GENERIC 3
DEFINITY
COMMUNICATIONS
SYSTEM
GENERIC 3
WITHOUT CALL BY CALL SERVICE SELECTION:
EACH TRUNK GROUP IS DEDICATED TO A SPECIFIC SERVICE
PUBLIC
SWITCHED
NETWORK
PUBLIC
SWITCHED
NETWORK 
						

							Feature Descriptions
3-474Issue  3   March 1996 
The system also checks all incoming ISDN-PRI calls for the presence of a 
Network Specific Facility information element.  If this information element is 
present, the system makes sure that the requested service is comp atible 
with the administration of the trunk.  If the requested service is not 
compatible with administration, the switch rejects the call.
For an outgoing call on a Call-By-Call trunk group, the Network Specific 
Facility information element is constructed using the Service/Feature 
specified on the routing p attern preference selected for the call.
nTransit Network Selection — Indicates which Inter-exc hange Carrier is to 
be used on an inter-LATA call.
If a call requires both the Service/Feature and the Inter-exchange Carrier 
to be specified, the Inter-exchange Carrier information is sent in the 
Network Specific Facility information element rather than the Transit 
Network Selection information element.
Usage Allocation Plan
O ptional Usage Allocation Plans (UAPs) may be assigned to provide more 
control over a Call-By-Call Service Selection trunk group. Up to three Usage 
Allocation Plans can be assigned for each Call-By-Call Service  Selection trunk 
group.  A Usage Allocation Plan allows the customer to set the following:
nA maximum numb er of trunk group members that each specific service 
can use at any given time.
nA minimum number of trunk group members that always is available for 
each specific service.
The sum of the allocation plan maximums may exceed the total number of trunk 
group members.  For example, if a trunk group has 15 members and provides 
access to MEGACOM service, MEGACOM 800 service, and SDN, the maximum 
number of trunks to be used for each of these services could possibly add up to 
more than 15. In this case, for example, you could administer a maximum of 
seven MEGACOM service calls, six MEGACOM 800 service calls, and eight SDN 
calls. This ensures that all trunk group members are not dominated by a specific 
service, yet allows for periodic fluctuations in demand.
The sum of the allocation plan minimums may not exceed the total number of 
trunk group members.  For example, if a trunk group has 10 members and 
provides access to MEGACOM service, MEGACOM 800 service, and SDN, the 
minimum numb er of trunks to be used for each of these services cannot add up 
to more than 10.
If a UAP has been defined for a Call-By-Call Service  Selection trunk group, and 
the type of the incoming call exceeds one of the p lan’s limits, the system rejects 
the call, even if a trunk is available. If a UAP has been defined for a Call-By-Call 
Service Selection trunk group, and a system user makes an outgoing call of a 
type that exceeds one of the plan’s limits, the user receives reorder tone unless 
other preferences are available. 
						

							Call-By-Call Service Selection
Issue  3   March 1996
3-475
As previously mentioned, each Call-By-Call Service Selection trunk group can 
have as many as three UAPs.  The customer can assign either fixed or scheduled 
allocation plans for each Call-By-Call Service Selection trunk group, (see Screen 
3-30, Screen 3-31, and Screen 3-32) which are used to administer the Usage 
Allocation Schedule and plans).
nFixed
One plan a p plies at all times.  The minimum and maximum usages 
specified in this plan are in effect for the trunk group at all times.
nScheduled
Two or three plans can be administered to apply at different times based 
on the time of day and day of the week. As many as six activation times 
and associated plans can be assigned for each day of the week.  At the 
specified activation time, the associated plan goes into effect for the 
Call-By-Call Service Selection trunk group.
Screen 3-31. CBC Service Type Usage Allocation Plan 
Assignment Schedule
   
              CBC SERVICE TYPE USAGE ALLOCATION PLAN ASSIGNMENT SCHEDULE 
                                                                   Page x of x 
   Usage Method: 
           Fixed? _y       Allocation Plan Number: _1 
       Scheduled? _n 
          Time   #    Time   #    Time   #    Time   #    Time   #     Time   # 
   Sun    00:00  1    __:__  _    __:__  _    __:__  _    __:__  _     __:__  _ 
   Mon    00:00  1    __:__  _    __:__  _    __:__  _    __:__  _     __:__  _ 
   Tue    00:00  1    __:__  _    __:__  _    __:__  _    __:__  _     __:__  _ 
   Wed    00:00  1    __:__  _    __:__  _    __:__  _    __:__  _     __:__  _ 
   Thu    00:00  1    __:__  _    __:__  _    __:__  _    __:__  _     __:__  _ 
   Fri    00:00  1    __:__  _    __:__  _    __:__  _    __:__  _     __:__  _ 
   Sat    00:00  1    __:__  _    __:__  _    __:__  _    __:__  _     __:__  _ 
    
						

							Feature Descriptions
3-476Issue  3   March 1996 
Screen 3-32. CBC Service Type Usage Allocation
System administration allows the customer to have anything from a simple fixed 
usage allocation plan to a very flexible plan with many scheduling options. The 
customer can even start out with no allocation plan and b uild the plan as the 
need arises. This  allows  the customer to resp ond to periodic fluctuations in the 
environment in a more timely manner. The customer does not have to involve the 
network to fine-tune the trunk group administration. To ensure that administration 
complexity is kept to a minimum, the following steps should be followed when 
assigning UAPs.
1. Assign a Usage Allocation Plan for a Call-By-Call Service Selection trunk 
group.
2. If scheduling is desired, add one or two more Usage Allocation Plans for 
that trunk group.
3. Administer the scheduling information for the trunk group’s UAPs.
Incoming Call Handling Treatment
Call-By-Call Service Selection provides special Incoming Call Handling 
Treatment for ISDN-PRI trunk groups. An incoming call on an ISDN-PRI trunk 
group is handled according to a treatment table that is a dministered for that trunk 
group. An example of the screen that  contains this table follows.
   
                       CBC SERVICE TYPE USAGE ALLOCATION 
                                                                   Page 3 of 8 
   Trunk Allocation Plan 1      Trunk Allocation Plan 2    Trunk Allocation Plan 3 
     Service/    Min#  Max#      Service/    Min#  Max#     Service/     Min#  Max# 
     Feature     Chan  Chan      Feature     Chan  Chan     Feature      Chan  Chan 
   ____________   __    __     ____________   __    __     ____________   __   __ 
   ____________   __    __     ____________   __    __     ____________   __   __ 
   ____________   __    __     ____________   __    __     ____________   __   __ 
   ____________   __    __     ____________   __    __     ____________   __   __ 
   ____________   __    __     ____________   __    __     ____________   __   __ 
   ____________   __    __     ____________   __    __     ____________   __   __ 
   ____________   __    __     ____________   __    __     ____________   __   __ 
   ____________   __    __     ____________   __    __     ____________   __   __ 
   ____________   __    __     ____________   __    __     ____________   __   __ 
   ____________   __    __     ____________   __    __     ____________   __   __