PDF DEFINITY G3 Feature Description
Definity G3 Feature Description Definity G3 Feature Description
User Manual: PDF T E X T F I L E S
Open the PDF directly: View PDF 
.
Page Count: 1584
555-230-204
Issue 3
March, 1996
Table of
Contents
DEFINITY Communications
System Generic 3
Feature Description
Graphics © AT&T 1988
Contents
Table of Contents
i
About This Document
1
lxxiii
■
Purpose
lxxiii
■
Intended Audiences
lxxiv
■
Reason For Reissue
lxxiv
■
How to Use This Document
lxxiv
■
Organization
lxxiv
■
Security Requirements
lxxv
■
Conventions Used in This Document
lxxv
■
Trademarks and Service Marks
lxxv
■
How to Make Comments About This Document
lxxvi
Introduction
1-1
■
Overview
1-1
■
Generic 3 Version 1
1-3
G3i Version 1
1-3
G3i-Global Version 1
1-4
G3r Version 1
1-4
G3s Version 1
1-6
G3vs Version 1
1-6
■
Generic 3 Version 2
New Features for Version 2
■
Generic 3 Version 3
New Features for Version 3
■
Generic 3 Version 4
New Features for Version 4
1-7
1-7
1-7
1-8
1-8
1-9
■
Generic 3 Notation
1-10
■
Security Measures
1-13
Issue 3 March 1996
iii
Contents
Logoff Notification
1-14
Passwords
1-14
Physical Security
1-14
Remote Administration Port
1-15
Trunks
1-15
AUDIX
1-15
Automated Attendant
1-16
Call Forwarding
1-16
Call Vectoring
1-16
Action
Enhanced Call Transfer
Action
■
1-18
1-18
Other Features Requiring Security Precautions
1-19
Organization of Features
Functional Description
1-20
1-20
2-1
■
Overview
2-1
■
Voice Management Overview
2-2
Voice Management Features
■
Data Management
2-7
2-10
Data Communications Protocols and Interfaces
2-13
ISDN Protocols
2-14
Electronic Industries Association (EIA)
2-14
Digital Communications Protocol (DCP) Interface
■
2-2
Data Networking
EIA RS-232D
RS-449
RS-366
iv
1-17
Remote Ac cess
Organization of Each Feature Section
2
1-17
2-14
2-15
2-15
2-15
BX.25 Packet Switching Protocol
2-16
International Telecommunications
Union - Telecommunications,
Specifications Sector (ITU-T) Interface
2-20
Issue 3 March 1996
Contents
X.25 Packet-Switching Protocol
Wideband Switching
■
Data Management Features
2-22
■
Network Services
2-23
■
■
Network Services Features
2-23
Private Network Configurations
2-24
Electronic Tandem Network (ETN)
2-25
Distributed Communications System (DCS)
2-25
Main/Satellite/Tributary
2-29
Trunking
2-30
System Management
■
2-34
System Management Features
2-34
System Administration
2-35
Remote Administration
2-36
Technical Service Center (TSC)
2-36
Hospitality Services
Hospitality Services Features
Call Center Services
Call Center Services Features
3
2-20
2-21
Feature Descriptions
2-37
2-37
2-38
2-38
3-1
■
Overview
3-1
■
AAR/ARS Partitioning
3-2
■
Feature Availability
3-2
Description
3-2
Considerations
3-3
Interactions
3-3
Administration
3-4
Hardware and Software Requirements
3-4
Abandoned Call Search
3-5
Feature Availability
3-5
Description
3-5
Considerations
3-5
Issue 3 March 1996
v
Contents
■
Interactions
3-6
Administration
3-6
Hardware and Software Requirements
3-6
Ab breviated Dialing (AD)
3-7
Feature Availability
3-7
Description
3-7
List Types
List Entries
Personal Number List Entries
3-8
Group Number and System Number
List Entries
3-9
Enhanced Number List
3-9
List Assignments and Designations
Privileged Lists
Special Characters
Access Options
Programming Personal Lists, Abbreviated
Dialing Buttons and Automatic Dialing Buttons
Programming Group Lists
■
■
3-7
3-8
3-9
3-10
3-10
3-11
3-13
3-13
Considerations
3-14
Security Measures
3-15
Interactions
3-15
Administration
3-16
Hardware and Software Requirements
3-17
Ad d/Remove Skills
3-18
Feature Availability
3-18
Description
3-18
Feature History
3-19
Considerations
3-19
Interactions
3-19
Administration
3-19
Hardware and Software Requirements
3-20
Administered Connections
3-21
Feature Availability
3-21
Description
3-21
Access Endpoints
3-21
Typical Administered Connection Configurations 3-22
vi
Issue 3 March 1996
Contents
Establishment of Administered Connections
Administered Connection Establishment Retries
Dropping an Administered Connection
Administered Connection Failure:
Auto Restoration and Fast Retry
■
3-22
3-23
3-23
3-24
Interactions
3-25
Administration
3-27
Hardware and Software Requirements
3-30
Administrable Language Displays
3-31
Feature Availability
3-31
Description
3-31
Feature Displays
3-31
Automatic Wakeup
ASAI
Busy Verification of Stations and Trunks
Call Ap pearance Designation
Call Detail Record
Call Progress Feed back
Class of Restriction
Date/Time Mode and Formats
Do Not Disturb (Hotel/Motel feature)
Expert Agent Selection
Field Separator
Integrated Directory Display Mode
ISDN
Leave Word Calling
Malicious Call Trace
Miscellaneous Attendant Features
3-31
3-33
3-33
3-33
3-34
3-34
3-35
3-35
3-37
3-38
3-39
3-39
3-39
3-40
3-44
3-45
Caller Information
3-45
Emergency Access to Attendant
3-45
Queue Status
3-46
Queue Status Indication
3-46
Miscellaneous Call Identifier
3-46
Party Identifiers
Property Management System Interface
Security Violation Notification
Stored Number
Time of Day Routing
3-51
3-51
3-53
3-53
3-54
Considerations
3-55
Interactions
3-56
Administration
3-56
Issue 3 March 1996
vii
Contents
■
Hardware and Software Requirements
3-56
Administration Without Hardware (AWOH)
3-57
Feature Availability
3-57
Description
3-57
Considerations
3-58
Interactions
3-58
Voice Terminal Interactions
Attendant Interactions
Data Terminal Interactions
Association/Disassociation of Terminal Feature
Interactions
World Class Attendant
Data Modules
■
3-68
Hardware and Software Requirements
3-68
Advice of Charge
3-69
Feature Availability
3-69
Description
3-69
3-70
During and End
3-70
End Only
3-70
AOC in CDR Reports
3-70
Reported Units
3-71
Considerations
3-71
Interactions
3-71
Administration
3-72
Hardware and Software Requirements
3-72
Agent Call Handling
3-73
Feature Availability
3-73
Description
3-73
Agent Log-in and Log-out
Agent Answering Options
3-73
3-75
Automatic Answer
3-75
Manual Answer
3-76
ACD Work Modes
Agent Request for Supervisor Assistance
ACD Call Disconnecting
viii
3-63
3-66
3-67
Administration
When Information Is Received
■
3-58
3-61
3-63
Issue 3 March 1996
3-76
3-78
3-79
Contents
Stroke Counts
Call Work Codes
Forced Entry of Stroke Counts and
Call Work Codes
Agent Sizing (G3V3 and later releases)
■
■
3-82
3-82
Considerations
3-84
Interactions
3-86
Administration
3-87
Hardware and Software Requirements
3-88
Alphanumeric Dialing
3-89
Feature Availability
3-89
Description
3-89
Considerations
3-89
Interactions
3-90
Administration
3-90
Hardware and Software Requirements
3-90
Alternate Facility Restriction Levels (AFRL)
3-91
Feature Availability
3-91
Description
3-91
Terminal User Perspective
Attendant Perspective
Line Originator Case
Trunk Originator Case
Authorization Code Case
3-92
3-92
3-92
3-93
3-93
Considerations
3-94
Interactions
3-94
Administration
3-94
Field Description
Error Messages
Help Messages
Initial Values
Administration of AFRL Feature Button
Attendant Class of Operations
Hardware/Software Requirements
■
3-80
3-81
Answer Detection
3-94
3-94
3-95
3-95
3-95
3-95
3-96
3-97
Feature Availability
3-97
Description
3-97
Considerations
3-98
Issue 3 March 1996
ix
Contents
■
■
■
■
Administration
3-98
Interactions
3-98
Hardware and Software Requirements
3-98
Attendant Auto-Manual Splitting
Feature Availability
3-99
Description
3-99
Considerations
3-99
Administration
3-99
Hardware and Software Requirements
3-99
Attendant Call Waiting
3-100
Feature Availability
3-100
Description
3-100
Considerations
3-101
Interactions
3-101
Administration
3-102
Hardware and Software Requirements
3-102
Attendant Control of Trunk Group Access
3-103
Feature Availability
3-103
Description
3-103
Considerations
3-104
Interactions
3-104
Administration
3-105
Hardware and Software Requirements
3-105
Attendant Direct Extension Selection
With Busy Lamp Field
3-106
Description
3-106
The Group Display Button
x
3-106
Feature Availability
Standard DXS Tracking with Hundreds
Select Buttons
Enhanced DXS Tracking
■
3-99
3-107
3-108
3-108
Considerations
3-109
Interactions
3-109
Administration
3-110
Hardware and Software Requirements
3-110
Attendant Direct Trunk Group Selection
Issue 3 March 1996
3-111
Contents
■
Feature Availability
3-111
Description
3-111
Considerations
3-111
Interactions
3-112
Administration
3-112
Hardware and Software Requirements
3-112
Attendant Display
Feature Availability
3-113
Description
3-113
Call-Related Information
■
3-115
Call Appearance Identification
3-115
Calling Party Identification
3-115
Called Party Identification
3-115
Internal COR
3-115
Call Progress Feedback
3-116
Call Purpose
3-116
Sample Displays
■
3-113
3-118
Considerations
3-119
Interactions
3-120
Hospitality
3-120
Administration
3-120
Hardware and Software Requirements
3-121
Attendant Intrusion (Call Offer)
3-122
Feature Availability
3-122
Description
3-122
Considerations
3-122
Interactions
3-122
Administration
3-123
Hardware/Software Requirements
3-123
Attendant Override of Diversion Features
3-124
Feature Availability
3-124
Description
3-124
Considerations
3-124
Interactions
3-124
Administration
3-124
Issue 3 March 1996
xi
Contents
Hardware/Software Requirements
■
3-125
Attendant Priority Queue
3-126
Feature Availability
3-126
Description
3-126
Priority by Call Type
3-128
Considerations
3-128
Interactions
3-128
Interactions for Priority by Call Type (G3V4 and later
releases)
3-129
■
■
■
Administration
3-129
Hardware/Software Requirements
3-130
Attendant Recall
Feature Availability
3-131
Description
3-131
Considerations
3-131
Interactions
3-131
Administration
3-131
Hardware and Software Requirements
3-131
Attendant Release Loop Operation
3-132
Feature Availability
3-132
Description
3-132
Considerations
3-132
Interactions
3-132
Administration
3-133
Hardware and Software Requirements
3-133
Attendant Room Status
3-134
Feature Availability
3-134
Description
3-134
Feature History and Description
3-134
Check-In/Check-Out Status
3-135
Maid Status
3-135
Interactions
3-136
Considerations
3-136
Administration
3-137
Attendant Console Form
xii
3-131
Issue 3 March 1996
3-137
Contents
System-Parameters Customer-Options Form
System-Parameters Hospitality Form
Hardware and Software Requirements
■
■
■
3-137
Attendant Serial Calling
3-138
Feature Availability
3-138
Description
3-138
Considerations
3-138
Interactions
3-138
Administration
3-139
Hardware/Software Requirements
3-139
Audible Message Waiting
3-140
Feature Availability
3-140
Description
3-140
Considerations
3-140
Interactions
3-140
Administration
3-140
Hardware and Software Requirements
3-140
Audio Information Exchange (AUDIX) Interface
Description
3-141
3-141
DEFINITY AUDIX
AUDIX (external to the DEFINITY Switch)
■
3-137
3-137
3-142
3-143
Security Measures
3-144
Considerations
3-145
Interactions
3-146
Administration
3-150
Hardware and Software Requirements
3-150
Authorization Codes
3-151
Feature Availability
3-151
Description
3-151
AAR and ARS Calls
3-152
Remote Ac cess Calls
3-153
Considerations
3-153
Interactions
3-154
Administration
3-155
Hardware and Software Requirements
3-155
Issue 3 March 1996
xiii
Contents
■
■
Auto Start and Don’t Split
3-156
Feature Availability
3-156
Description
3-156
Considerations
3-156
Interactions
3-156
Administration
3-157
Hardware and Software Requirements
3-157
Auto-Available Split (AAS)
3-158
Feature Availability
3-158
Description
3-158
Considerations
3-158
Interactions
3-158
ACD Splits
Auto-Answer
Agent Logout
Group Administration
CMS Notifications
Adjunct CMS Move Agent
Administration
■
3-160
Hardware/Software Requirements
3-160
Automatic Alternate Routing (AAR)
3-161
Feature Availability
3-161
Description
3-161
Inter-Digit Time-out
Digit Conversion
Time of Day Routing
AAR Analysis
Routing Patterns
xiv
3-160
Hunt Group Administration
AAR Dialing
■
3-158
3-159
3-159
3-160
3-160
3-160
3-163
3-163
3-163
3-164
3-164
3-166
Considerations
3-167
Interactions
3-167
Administration
3-169
Hardware and Software Requirements
3-169
Automatic Call Distribution (ACD)
3-170
Feature Availability
3-170
Description
3-170
Issue 3 March 1996
Contents
Call Distribution
Direct Department Calling
3-170
Uniform Call Distribution
3-171
Expert Agent Distribution
3-171
Split Queuing and Announcements
3-171
Forced First Announcement
3-172
Entering the Queue
3-173
First Announcement
3-173
Second Announcement
3-174
Forced Disconnect
3-175
Announcement Rules
3-175
Intraflow and Interflow
3-175
Queue Status Indications
3-176
Priority Queuing
3-176
Agent Call Handling
CMS
BCMS
Abandoned Call Search
Service Observing
Direct Agent Calling
3-176
3-180
3-180
3-180
3-180
3-181
Delivery of Direct Agent Calls
3-181
Answering a Direct Agent Call
3-181
Vector-Controlled Splits
Agent Sizing
Stroke Counts
Call Work Codes
Forced Entry of Stroke Counts and
Call Work Codes
■
3-170
3-182
3-182
3-182
3-182
3-182
Considerations
3-183
Interactions
3-185
Administration
3-189
Hardware and Software Requirements
3-191
Automatic Callback
3-192
Feature Availability
3-192
Description
3-192
Considerations
3-192
Interactions
3-193
Issue 3 March 1996
xv
Contents
■
■
■
Administration
3-194
Hardware and Software Requirements
3-195
Automatic Circuit Assurance (ACA)
Feature Availability
3-196
Description
3-196
Considerations
3-198
Interactions
3-198
Administration
3-199
Hardware and Software Requirements
3-200
Automatic Incoming Call Display
3-201
Description
3-201
Considerations
3-201
Interactions
3-202
Administration
3-202
Hardware and Software Requirements
3-202
Automatic Route Selection (ARS)
3-203
Feature Availability
3-203
Description
3-203
3-204
Inter-Digit Timeout
3-204
Special Dialing Patterns
3-204
Digit Conversion
Time of Day Routing
ARS Digit Analysis
Routing Patterns
Digit 1 Outpulsing
NPA Deletion and Insertion
IDDD and Service Code Dialing
Operator and Operator-Assisted Calls
3-207
3-210
3-210
3-211
3-212
3-213
3-213
3-214
Considerations
3-214
Interactions
3-214
Administration
3-216
Hardware and Software Requirements
3-217
Automatic Transmission Measurement System (ATMS) 3-218
Feature Availability
xvi
3-201
Feature Availability
ARS Dialing
■
3-196
Issue 3 March 1996
3-218
Contents
Description
3-218
Considerations
3-219
Terminating Test Lines
■
3
■
3-219
Interactions
3-220
Administration
3-220
Hardware/Software Requirements
3-220
Automatic Wakeup
3-221
Feature Availability
3-221
Description
3-221
Considerations
3-225
Interactions
3-227
Administration
3-227
Hardware and Software Requirements
3-228
Basic Call Management System (BCMS)
3-229
Feature Availability
3-229
Description
3-229
Acceptable Service Level
3-230
Percent Within Service Level
3-230
BCMS Real-Time Reports
3-231
BCMS Split Status Report
3-232
Report Headers, Abbreviations, and
Their Definitions
BCMS System Status Report
3-236
Report Headers, Abbreviations, and
Their Definitions
BCMS VDN Status Report
3-237
3-239
Report Headers, Abbreviations, and
Their Definitions
BCMS Historical Reports
3-240
3-243
BCMS Agent Report
3-244
Report Headers, Abbreviations, and
Their Definitions
BCMS Agent Summary Report
3-233
3-246
3-248
Issue 3 March 1996
xvii
Contents
Report Headers, Abbreviations, and
Their Definitions
BCMS Split Report
Report Headers, Abbreviations, and
Their Definitions
BCMS Split Summary Report
Report Headers, Abbreviations, and
Their Definitions
BCMS Trunk Group Report
Report Headers, Abbreviations, and
Their Definitions
BCMS Trunk Group Summary Report
Report Headers, Abbreviations, and
Their Definitions
BCMS VDN Report
Report Headers, Abbreviations, and
Their Definitions
BCMS VDN Summary Report
Report Headers, Abbreviations, and
Their Definitions
xviii
3-253
3-257
3-259
3-264
3-266
3-268
3-270
3-272
3-273
3-276
3-277
3-280
Interactions
3-280
Administration
3-282
Bridged Call Appearance—
Multi-Ap pearance Voice Terminal
3-283
3-284
Feature Availability
3-284
Description
3-284
Extension Administrable Buttons and Lamps
Sample Applications
■
3-251
Considerations
Hardware and Software Requirements
■
3-249
3-285
3-285
Security
3-286
Considerations
3-286
Interactions
3-287
Administration
3-295
Hardware and Software Requirements
3-295
Bridged Call Appearance—
Single-Line Voice Terminal
Issue 3 March 1996
3-296
Contents
Feature Availability
3-296
Description
3-296
Sample Applications
■
3
■
3-297
Considerations
3-298
Interactions
3-299
Administration
3-306
Hardware and Software Requirements
3-306
Busy Verification of Terminals and Trunks
3-307
Feature Availability
3-307
Description
3-307
Considerations
3-309
Interactions
3-310
Administration
3-311
Hardware and Software Requirements
3-311
Call Coverage
3-312
Feature Availability
3-312
Description
3-312
Call Coverage Path
Multiple Coverage Paths
Redirection Criteria
Covering User Options
What Happens When a Call Goes to Coverage
VDN in a Call Coverage Path
Typical Call Coverage Arrangements
■
3-312
3-313
3-313
3-316
3-317
3-318
3-318
Considerations
3-320
Interactions
3-320
Administration
3-324
Hardware and Software Requirements
3-325
Call Detail Recording (CDR)
3-326
Feature Availability
3-326
Description
3-326
Splitting of CDR Records
CDR Privacy
3-327
3-328
Issue 3 March 1996
xix
Contents
Resource Limitation Call Record Handling
Options
Set Time and Date
CDR Data Formats
Date Record Format
3-329
Call Detail Record Format
3-331
Call Detail Record Fields
3-361
CDR Output Devices
Remove # from CDR Records
Considerations
Capacities
Account Code Recording
CDR Device Baud Rate Limits
3-381
3-381
3-381
Administration
3-392
3-392
3-393
3-393
3-393
3-393
3-394
3-394
3-395
Call Forwarding All Calls
3-396
Feature Availability
3-396
Description
3-396
Call Forwarding Override
3-397
Security Measures
3-397
Considerations
3-397
Interactions
3-398
Administration
3-400
Hardware and Software Requirements
3-400
Call Forward Busy/Don’t Answer
3-401
Feature Availability
3-401
Description
3-401
Call Forwarding Override
End User Operation
xx
3-381
3-382
Security
■
3-379
3-381
Interactions
System Parameters
Date and Time
Trunks, Loudspeaker Paging, and
Code Calling Access
COR
Feature Access Codes
IXC Codes
Data Modules and Modems
■
3-328
3-329
3-329
Issue 3 March 1996
3-401
3-402
Contents
■
■
■
■
Security Measures
3-402
Considerations
3-402
Interactions
3-403
Administration
3-405
Hardware and Software Requirements
3-405
Call Management System (CMS)
3-406
Feature Availability
3-406
Description
3-406
Call Park
3-407
Feature Availability
3-407
Description
3-407
Considerations
3-408
Interactions
3-408
Administration
3-409
Hardware and Software Requirements
3-410
Call Pickup
3-411
Feature Availability
3-411
Description
3-411
Considerations
3-412
Interactions
3-413
Administration
3-414
Hardware and Software Requirements
3-415
Call Prompting
3-416
Feature Availability
3-416
Description
3-416
Call Prompting Vector Commands
3-416
Collect <# of digits> digits after announcement
3-417
Goto step if digits or
if unconditionally
3-420
Goto vector if digits
3-421
< digits> or if unconditionally
Route-to number <#> with cov
if digit
3-421
Route-to digits with coverage
3-422
Stop
3-422
Issue 3 March 1996
xxi
Contents
Vector Processing and Calling Party Feedback
Agent Set Caller Display Information
Call Prompting Applications
■
Automated Attendant
3-424
Data In/Voice Answer (DIVA)
3-424
Data Collection
3-425
Message Collection
3-426
Considerations
3-427
Interactions
3-427
Administration
3-433
Hardware and Software Requirements
3-433
Call Vectoring
3-434
Feature Availability
3-434
Description
3-434
Vector Directory Numbers and Vectors
Applications
What Happens When a Call is Processed
by a Vector
xxii
3-423
3-423
3-424
3-434
3-435
3-436
General
3-436
Calling Party Feedback
3-437
Ad ditional Information
3-438
Vector Commands
3-439
Adjunct Routing
3-439
Announcement
3-440
Busy
3-440
Check-Backup Split/Skill
3-440
Collect Digits
3-441
Converse-On Command
3-441
Disconnect
3-442
Goto Step
3-443
Goto Vector
3-444
Messaging Split/Skill
3-444
Queue-To Main Split/Skill
3-445
Route-to Number
3-446
Route-To Digits
3-447
Stop
3-447
Issue 3 March 1996
Contents
Wait-Time
3-447
ACD Split/Hunt Group Operation with
Call Vectoring
3-448
Overview
3-448
Vector Controlled Splits/Skills
3-448
Split/Skill Queue Priority Levels
3-449
Split/Skill Thresholds
3-449
Call Vectoring and PBX Toll Fraud
3-449
Front Ending Remote Access
3-450
Replacing Remote Access
3-451
Call Vectoring and the Call Management System
(CMS)
3-451
DNIS
3-451
Vector Routing Tables (G3V4 and later releases) 3-452
■
■
■
Considerations
3-452
Interactions
3-453
Administration
3-462
Hardware and Software Requirements
3-465
Call Waiting Termination
3-466
Feature Availability
3-466
Description
3-466
Considerations
3-467
Interactions
3-467
Administration
3-467
Hardware and Software Requirements
3-467
Calling Line Identification (CLI) Prefix
3-468
Feature Availability
3-468
Description
3-468
Considerations
3-468
Interactions
3-469
Administration
3-470
Hardware Requirements
3-470
Call-By-Call Service Selection
3-471
Feature Availability
3-471
Description
3-471
Services Used With Call-By-Call Service Selection3-471
Issue 3 March 1996
xxiii
Contents
ISDN-PRI Messages and Information Elements
Used for Call-By-Call Service Selection
3-473
Usage Allocation Plan
Incoming Call Handling Treatment
■
Considerations
3-479
Interactions
3-480
Administration
3-480
Hardware and Software Requirements
3-481
CallVisor Adjunct/Switch Ap plications Interface (ASAI) 3-482
Feature Availability
3-482
Description
3-482
G3V4 ASAI Enhancements
CallVisor ASAI Capabilities
Third Party Call Control Capabilities Group
xxiv
3-482
3-484
3-485
CallVisor ASAI Call Types
3-486
Switch-Classified Calls
3-486
Answering Machine Detection (AMD)
3-487
User-Classified Calls
3-487
Direct-Agent Calls
3-488
Supervisor Assist Calls
3-489
Third Party Domain (Station/ACD Split) Control
Capabilities Group
Notification Capabilities Group
Set Value Capabilities Group
Value Query Capabilities Group
Request Feature Capabilities Group
■
3-474
3-476
3-490
3-491
3-493
3-493
3-494
Adjunct-Controlled Splits
3-495
Routing Capabilities Group
Maintenance Capabilities Group
CallVisor ASAI Applications
3-497
3-498
3-498
Considerations
3-500
Feature Initialization and Recovery
3-501
Interactions
3-501
Administration
3-517
Hardware and Software Requirements
3-521
CDR Account Code Dialing Forced
Entry of Account Codes
Issue 3 March 1996
3-522
Contents
■
■
Feature Availability
3-522
Description
3-522
Considerations
3-523
Interactions
3-523
Administration
3-524
Hardware and Software Requirements
3-524
Centralized Attendant Service (CAS)
3-525
Feature Availability
3-525
Description
3-525
Considerations
3-527
Interactions
3-528
Administration
3-531
Hardware and Software Requirements
3-531
Class of Restriction (COR)
3-532
Feature Availability
3-532
Description
3-532
Use of CORs
3-533
Calling Party and Called Party Restrictions
3-533
Forced Entry of Account Codes
3-535
Partitioned Group Number (PGN)
3-536
Service Observing
3-536
VDN of Origin Announcement
3-536
Priority Queuing
3-536
DAC
3-537
Facility Access Trunk Test
3-537
Fully Restricted Service (G3i-Global, G3rV1,
and G3V2 and later)
3-537
Restriction Override (3-way COR calling)
3-537
Restricted Call List
3-537
Unrestricted Call List
3-538
Selective Denial of Public Network Calling Through a
CCSA or EPSCS Network (APLT)
3-538
ARS/AAR FRL for Control of Call Routing
3-538
Miscellaneous Restriction Groups
3-539
COR Examples
3-540
Issue 3 March 1996
xxv
Contents
Example Using Miscellaneous Restrictions
3-540
Example Using Calling Party Restrictions, Called Party
Restrictions, and Miscellaneous Restrictions 3-542
Considerations
3-545
Interactions
3-546
Administration
3-548
Assignment of Restrictions
3-549
Voice Terminals
3-549
Trunk Groups
3-549
Attendant Consoles (as a group) and Individual
Attendant Extensions
3-549
Data Module, Loudspeaker Paging Access Zone,
Code Calling Access Zone, and Remote Access
Barrier Code
3-550
Terminating Extension Group, Automatic Call Distribution
Split, Uniform Call Distribution Group, and Direct
Department Calling Group
3-550
Hardware and Software Requirements
■
■
■
xxvi
Class of Service (COS)
3-550
3-551
Feature Availability
3-551
Description
3-551
Considerations
3-552
Interactions
3-552
Administration
3-552
Hardware and Software Requirements
3-553
Code Calling Access
3-554
Feature Availability
3-554
Description
3-554
Considerations
3-554
Interactions
3-554
Administration
3-555
Hardware and Software Requirements
3-556
Conference — Attendant
3-557
Feature Availability
3-557
Description
3-557
Considerations
3-557
Interactions
3-557
Issue 3 March 1996
Contents
■
■
■
■
■
Administration
3-558
Hardware and Software Requirements
3-558
Conference — Terminal
3-559
Feature Availability
3-559
Description
3-559
Considerations
3-559
Interactions
3-559
Administration
3-560
Hardware and Software Requirements
3-560
Constellation Voice/Data Terminal Support
3-561
Feature Availability
3-561
Description
3-561
Feature History and Development
3-561
Applications and Benefits
3-561
Configuration
3-562
Considerations
3-563
Administration
3-563
Hardware/Software Requirements
3-563
Consult
3-564
Feature Availability
3-564
Description
3-564
Considerations
3-564
Interactions
3-564
Administration
3-564
Hardware and Software Requirements
3-565
Coverage Callback
3-566
Feature Availability
3-566
Description
3-566
Considerations
3-566
Interactions
3-566
Administration
3-566
Hardware and Software Requirements
3-566
Coverage Incoming Call Identification (ICI)
3-567
Feature Availability
3-567
Description
3-567
Issue 3 March 1996
xxvii
Contents
■
3
■
Considerations
3-567
Interactions
3-567
Administration
3-567
Hardware and Software Requirements
3-567
Customer-Provided Equipment (CPE) Alarm
3-568
Feature Availability
3-568
Description
3-568
Considerations
3-569
Interactions
3-569
Administration
3-569
Hardware and Software Requirements
3-569
Data Call Setup
3-572
Feature Availability
3-572
Description
3-572
Data Call Setup for DCP Modules
3-572
Voice Terminal Dialing for DCP Data Modules 3-572
Data Terminal (Keyboard) Dialing for DCP Data
Modules
3-573
Single-Line Dialing
3-574
Multiple-Line Dialing
3-575
Alphanumeric Dialing
3-575
Call Forwarding All Calls
3-575
Default Dialing
3-575
Administered Connections
3-575
Hotline Dialing
3-576
Data Call Setup for ISDN-BRI Modules
3-578
Voice Terminal Dialing for ISDN-BRI
Data Modules
3-578
Data Terminal (Keyboard) Dialing for ISDN-BRI Data
Modules
3-578
xxviii
Basic Digit Dialing
3-579
Alphanumeric Dialing
3-579
Default Dialing
3-579
Issue 3 March 1996
Contents
■
■
■
■
Call Forwarding All Calls
3-580
Data Hotline
3-580
Administered Connections
3-580
Call Request
3-580
Cause Value
3-580
Endpoint Initialization
3-581
Multipoint Configurations on BRI ports
3-581
Exchange of User Information
3-581
Considerations
3-583
Interactions
3-583
Administration
3-585
Hardware and Software Requirements
3-585
Data Hot Line
3-588
Feature Availability
3-588
Description
3-588
Considerations
3-588
Interactions
3-588
Administration
3-589
Hardware and Software Requirements
3-589
Data Privacy
3-590
Feature Availability
3-590
Description
3-590
Considerations
3-590
Interactions
3-590
Administration
3-591
Hardware and Software Requirements
3-591
Data Restriction
3-592
Feature Availability
3-592
Description
3-592
Considerations
3-592
Interactions
3-592
Administration
3-593
Hardware and Software Requirements
3-593
Data-Only Off-Premises Extensions
Feature Availability
3-594
3-594
Issue 3 March 1996
xxix
Contents
■
■
■
■
■
xxx
Description
3-594
Considerations
3-594
Interactions
3-594
Administration
3-595
Hardware and Software Requirements
3-595
DCS Alphanumeric Display for Terminals
3-596
Feature Availability
3-596
Description
3-596
Considerations
3-596
Interactions
3-597
Administration
3-598
Hardware and Software Requirements
3-598
DCS Attendant Control of Trunk Group Access
3-599
Feature Availability
3-599
Description
3-599
Considerations
3-600
Interactions
3-601
Administration
3-601
Hardware and Software Requirements
3-601
DCS Attendant Direct Trunk Group Selection
3-602
Feature Availability
3-602
Description
3-602
Considerations
3-602
Interactions
3-602
Administration
3-602
Hardware and Software Requirements
3-603
DCS Attendant Display
3-604
Feature Availability
3-604
Description
3-604
Considerations
3-604
Interactions
3-605
Administration
3-605
Hardware and Software Requirements
3-605
DCS Automatic Callback
3-606
Feature Availability
3-606
Issue 3 March 1996
Contents
■
■
■
Description
3-606
Considerations
3-607
Interactions
3-607
Administration
3-607
Hardware and Software Requirements
3-607
DCS Automatic Circuit Assurance (ACA)
Feature Availability
3-608
Description
3-608
Considerations
3-608
Interactions
3-608
Administration
3-608
Hardware and Software Requirements
3-609
DCS Busy Verification of Terminals and Trunks
3-610
Feature Availability
3-610
Description
3-610
Considerations
3-610
Interactions
3-610
Administration
3-611
Hardware and Software Requirements
3-611
DCS Call Coverage
3-612
Feature Availability
3-612
Description
3-612
Feature Applications
Previous Feature Operation
New Feature Operation
Detailed Operation
User Interface
■
3-608
3-613
3-613
3-615
3-616
3-618
Interactions
3-625
Interworking
3-626
Hardware and Software Requirements
3-628
DCS Call Forwarding All Calls
3-629
Feature Availability
3-629
Description
3-629
Considerations
3-629
Interactions
3-629
Administration
3-630
Issue 3 March 1996
xxxi
Contents
Hardware and Software Requirements
■
■
■
■
■
xxxii
DCS Call Waiting
3-630
3-631
Feature Availability
3-631
Description
3-631
Considerations
3-631
Interactions
3-631
Administration
3-632
Hardware and Software Requirements
3-632
DCS Distinctive Ringing
3-633
Feature Availability
3-633
Description
3-633
Considerations
3-633
Interactions
3-633
Administration
3-634
Hardware and Software Requirements
3-634
DCS Leave Word Calling
3-635
Feature Availability
3-635
Description
3-635
Considerations
3-635
Interactions
3-636
Administration
3-636
Hardware and Software Requirements
3-636
DCS Multi-Ap pearance Conference/Transfer
3-637
Feature Availability
3-637
Description
3-637
Considerations
3-637
Interactions
3-637
Administration
3-638
Hardware and Software Requirements
3-638
DCS Over ISDN-PRI D-Channel
3-639
Feature Availability
3-639
Description
3-639
Considerations
3-640
Interactions
3-640
Administration
3-641
Issue 3 March 1996
Contents
Hardware and Software Requirements
■
■
■
■
■
3-642
DCS Trunk Group Busy/Warning Indication
3-643
Feature Availability
3-643
Description
3-643
Considerations
3-643
Interactions
3-644
Administration
3-644
Hardware and Software Requirements
3-644
Default Dialing
3-645
Feature Availability
3-645
Description
3-645
Considerations
3-645
Interactions
3-645
Administration
3-646
Hardware and Software Requirements
3-646
Dial Access to Attendant
3-647
Feature Availability
3-647
Description
3-647
Considerations
3-647
Interactions
3-647
Administration
3-647
Hardware and Software Requirements
3-648
Dial Plan
3-649
Feature Availability
3-649
Description
3-649
Considerations
3-651
Interactions
3-651
Administration
3-651
Hardware and Software Requirements
3-652
Digital Multiplexed Interface
3-653
Feature Availability
3-653
Description
3-653
Considerations
3-654
Interactions
3-654
Administration
3-654
Issue 3 March 1996
xxxiii
Contents
Hardware and Software Requirements
■
■
■
■
Direct Department Calling (DDC) and
Uniform Call Distribution (UCD)
3-656
Feature Availability
3-656
Description
3-656
Considerations
3-659
Interactions
3-661
Administration
3-663
Hardware and Software Requirements
3-664
Direct Inward and Outward Dialing
(DIOD) — International
3-665
Feature Availability
3-665
Description
3-665
Considerations
3-665
Interactions
3-666
Administration
3-666
Hardware and Software Requirements
3-666
Distinctive Ringing
3-667
Feature Availability
3-667
Description
3-667
Considerations
3-669
Interactions
3-670
Administration
3-670
DS1 Trunk Service
3-671
Feature Availability
3-671
Description
3-671
Voice Grade DS1 Tie Trunks
AVD Tie Trunks
Tie Trunks
DMI Tie Trunks
CO, FX, and WATS Trunks
Remote Access Trunks
DID Trunks
Off-Premises Stations
Access Endpoints
xxxiv
3-655
3-671
3-672
3-672
3-673
3-673
3-673
3-674
3-674
3-674
Considerations
3-674
Interactions
3-674
Issue 3 March 1996
Contents
■
Administration
3-675
Hardware and Software Requirements
3-675
Do Not Disturb
3-676
Feature Availability
3-676
Description
3-676
Feature Activation by Voice Terminal Users
Feature Activation by Attendant
Activation of Do Not Disturb Through a PMS
Audit Trail Reports
3
■
■
■
■
3-676
3-677
3-677
3-677
Considerations
3-678
Interactions
3-678
Administration
3-679
Hardware and Software Requirements
3-679
E1 Trunk Service
3-680
Feature Availability
3-680
Description
3-680
EIA Interface
3-681
Feature Availability
3-681
Description
3-681
Considerations
3-681
Interactions
3-682
Administration
3-682
Hardware and Software Requirements
3-683
Emergency Access to the Attendant
3-684
Feature Availability
3-684
Description
3-684
Considerations
3-686
Interactions
3-686
Administration
3-688
Hardware and Software Requirements
3-688
End-to-End Signalling
3-689
Feature Availability
3-689
Description
3-689
Issue 3 March 1996
xxxv
Contents
■
Interactions
3-689
Considerations
3-689
Administration
3-689
Hardware and Software Requirements
3-689
Enhanced 84xx Display
Feature Availability
3-690
Description
3-690
End User Operation
3-690
Security Measures
3-690
Considerations
3-690
Interactions
3-691
Internal Feature interactions
External Feature Interfaces
■
■
xxxvi
3-691
3-691
Administration
3-692
Hardware and Software Requirements
3-694
Enhanced Abbreviated Dialing (EAD)
3-695
Feature Availability
3-695
Description
3-695
Considerations
3-695
Interactions
3-695
Administration
3-696
Hardware and Software Requirements
3-696
Enhanced ICSU
3-697
Feature Availability
3-697
Description
3-697
Testing
Performance Measurements
■
3-690
3-698
3-698
Considerations
3-699
Interactions
3-699
Administration
3-700
Hardware and Software Requirements
3-700
Enhanced DCS (EDCS)
3-701
Feature Availability
3-701
Description
3-701
Considerations
3-701
Issue 3 March 1996
Contents
■
Interactions
3-701
Administration
3-701
Hardware and Software Requirements
3-701
Expert Agent Selection (EAS)
3-702
Feature Availability
3-702
Purpose
3-702
Identifying Caller Needs
3-702
AT&T Network DNIS/ISDN Called Party
Call Prompting/VRU Digits
ASAI Host Database Lookup
Routing Digits
3-703
3-703
3-703
3-703
Agents Skills
3-703
EAS Application
3-703
Writing Vectors
3-704
EAS Agent Operations
3-705
Other Login ID Ap plications
3-706
Administration of Skills
3-707
Call Distribution
3-707
EAS Logical Agent
Direct Agent Calling
Expert Agent Selection
Publishing Login ID Extensions Instead of
Physical Extensions
Direct Agent Calling
Class of Restriction
Considerations
3-711
3-711
3-711
Calling an EAS Agent
3-711
Making a Direct Agent Call to the Agent
Single Set of Work Mode Buttons
Message Waiting Lamp
ASAI
3-709
3-710
3-710
3-710
Caller Interactions
Agent Login Procedure
Logout Procedure
Adjunct Interactions
3-708
3-708
3-709
3-712
3-712
3-712
3-713
3-713
Call Control
3-713
Feature Requests
3-714
Value Queries
3-714
Issue 3 March 1996
xxxvii
Contents
Event Notification
3-714
Adjunct-Controlled Splits
3-714
AUDIX
Speech Processing Adjuncts
Feature Interactions
3-715
Administration
3-719
System Parameters
Logical Agent
Station Administration
VDN Administration
Vector Administration
Hardware and Software Requirements
■
■
■
■
xxxviii
3-715
3-715
3-719
3-719
3-719
3-720
3-720
3-720
Extended Trunk Access
3-721
Feature Availability
3-721
Description
3-721
Considerations
3-721
Capacity Requirements and Constraints
3-721
Interactions
3-722
Administration
3-724
Hardware/Software Requirements
3-725
Extension Number Portability
3-726
Feature Availability
3-726
Description
3-726
Considerations
3-726
Interactions
3-726
Administration
3-726
Hardware/Software Requirements
3-727
Facility Busy Indication
3-728
Feature Availability
3-728
Description
3-728
Considerations
3-728
Interactions
3-729
Administration
3-729
Hardware and Software Requirements
3-729
Facility Restriction Levels (FRLs) and
Traveling Class Marks (TCMs)
Issue 3 March 1996
3-730
Contents
Feature Availability
3-730
Description
3-730
Call Originating Facilities
Call Terminating Facilities
3-731
3-732
Considerations
3-732
Interactions
3-733
Administration
3-733
Assignment Guidelines
3-733
Hardware and Software Requirements
■
■
Facility Test Calls (with Security Measures)
3-735
Feature Availability
3-735
Description
3-735
Security Measures
3-736
Considerations
3-736
Interactions
3-737
Administration
3-737
Hardware and Software Requirements
3-737
Facility and Non-Facility Associated Signaling
3-738
Feature Availability
3-738
Description
3-738
Facility Associated Signaling
Non-Facility Associated Signaling
D-Channel Backup
■
3-734
3-738
3-738
3-738
Considerations
3-740
Interactions
3-740
Administration
3-740
Hardware and Software Requirements
3-741
Flexible Billing
3-742
Feature Availability
3-742
Description
3-742
Applications
Detailed Operation
3-743
3-743
Considerations
3-744
Interactions
3-744
Administration
3-744
Hardware and Software Requirements
3-744
Issue 3 March 1996
xxxix
Contents
■
Generalized Route Selection (GRS)
3-745
Feature Availability
3-745
Description
3-745
Bearer Capability Classes (BCCs)
ISDN-PRI BCC Parameters
3-746
3-748
Information Transfer Capability
3-748
Low-Layer Compatibility
3-749
DCP/DMI Mode
3-749
Determination of BCC at Tandeming or Terminating
System
3-750
GRS Operation
3-750
BCC and ITC Determination on Calls from
Endpoints to ISDN-PRI Trunks
3-753
BCC and ITC Determination on Calls from
Trunks to ISDN-PRI
3-755
BCC and ITC Determination on Calls from ISDN-PRI
Trunks to Endpoints (GRS not Involved)
3-757
■
■
Considerations
3-757
Interactions
3-758
Administration
3-759
Hardware and Software Requirements
3-761
Go to Cover
Feature Availability
3-762
Description
3-762
Consideration
3-762
Interactions
3-762
Administration
3-762
Hardware and Software Requirements
3-762
Hold
3-763
Feature Availability
3-763
Description
3-763
Multi-appearance Voice Terminal Hold
Single-line Voice Terminal Hold
xl
3-762
3-763
3-763
Considerations
3-764
Interactions
3-764
Administration
3-765
Hardware and Software Requirements
3-765
Issue 3 March 1996
Contents
■
■
■
3
■
Hold - Automatic
3-766
Feature Availability
3-766
Description
3-766
Considerations
3-766
Interactions
3-767
Administration
3-767
Hardware/Software Requirements
3-767
Hot Line Service
3-768
Feature Availability
3-768
Description
3-768
Considerations
3-768
Interactions
3-769
Administration
3-769
Hardware and Software Requirements
3-769
Hunting
3-770
Feature Availability
3-770
Description
3-770
Considerations
3-770
Interactions
3-770
Administration
3-770
Hardware and Software Requirements
3-771
Inbound Call Management (ICM)
3-772
Feature Availability
3-772
Description
3-772
Data Screen Delivery
Integration With Speech Processing Adjuncts
Host/Adjunct Call Routing
Direct Agent Calling
3-773
3-774
3-775
3-776
Adjunct Activation of Direct Agent Calling
3-776
Delivery of DAC
3-776
Answering a Direct Agent Call
3-777
Considerations
3-777
Interactions
3-777
Issue 3 March 1996
xli
Contents
■
■
■
■
Administration
3-779
Hardware and Software Requirements
3-779
Individual Attendant Access (IAA)
Feature Availability
3-780
Description
3-780
Considerations
3-780
Interactions
3-781
Administration
3-783
Hardware and Software Requirements
3-783
Information System Network (ISN) Interface
3-784
Feature Availability
3-784
Description
3-784
Considerations
3-785
Interactions
3-785
Administration
3-786
Hardware and Software Requirements
3-787
Integrated Directory
3-788
Feature Availability
3-788
Description
3-788
Considerations
3-790
Interactions
3-791
Administration
3-791
Hardware and Software Requirements
3-791
Integrated Services Digital Network
(ISDN) — Basic Rate Interface (BRI)
3-792
Feature Availability
3-792
Description
3-792
ISDN-BRI Endpoint Configurations
3-794
Service Profile Identifier (SPID)
3-794
3-795
Endpoint Initialization
3-795
Multipoint Configurations on BRI Ports
3-796
Exchange of User Information
3-796
ISDN-BRI Data Service
Issue 3 March 1996
3-793
Terminal Equipment Identifier (TEI)
ISDN-BRI Voice/Data Terminal Equipment
xlii
3-780
3-796
Contents
Basic Digit Dialing
3-796
Default Dialing
3-796
Data Hotline
3-796
Administered Connections
3-797
Call Request
3-797
Cause Value
3-797
Considerations
3-797
Interactions
3-798
Administration
3-799
BRI Voice/Data
BRI Data
3-799
3-800
Hardware Requirements
■
3-801
Integrated Services Digital Network
(ISDN) — Primary Rate Interface
3-802
Feature Availability
3-802
Description
3-802
AT&T Switched Network Protocol
3-804
Access to AT&T Switched Network Services
3-805
Call Identification Display
3-805
CPN/BN to Host Call Identification
3-808
Private Network Services
3-809
Wideband Switching
3-810
Call-by-Call Service Selection
3-810
Access to Software Defined Data Network
(SDDN)
3-811
Access to Switched Digital International (SDI) 3-811
ISDN-PRI Interworking
National ISDN-2 Services
3-811
3-812
Calling Line Identification
3-812
Non-Facility Associated Signaling
3-813
D-Channel Backup
3-813
Wideband Switching
3-813
Call-by-Call Service Selection
3-813
Global ISDN-PRI
3-813
Considerations
3-813
Interactions
3-814
Issue 3 March 1996
xliii
Contents
■
■
■
■
■
Administration
3-815
Hardware and Software Requirements
3-817
Inter-PBX Attendant Calls
3-819
Feature Availability
3-819
Description
3-819
Considerations
3-819
Interactions
3-819
Administration
3-820
Hardware and Software Requirements
3-820
Intercept Treatment
Feature Availability
3-821
Description
3-821
Considerations
3-822
Interactions
3-822
Administration
3-823
Hardware and Software Requirements
3-823
Intercom — Automatic
3-824
Feature Availability
3-824
Description
3-824
Considerations
3-824
Interactions
3-824
Administration
3-825
Hardware and Software Requirements
3-825
Intercom—Dial
3-826
Feature Availability
3-826
Description
3-826
Considerations
3-826
Interactions
3-826
Administration
3-827
Hardware and Software Requirements
3-827
Internal Automatic Answer (IAA)
3-828
Feature Availability
3-828
Description
3-828
IAA Feature Operations
Considerations
xliv
3-821
Issue 3 March 1996
3-829
3-829
Contents
■
■
■
■
■
Interactions
3-830
Administration
3-832
Hardware and Software Requirements
3-832
Intraflow and Interflow
3-834
Feature Availability
3-834
Description
3-834
Considerations
3-836
Interactions
3-836
Administration
3-837
Hardware and Software Requirements
3-837
Last Number Dialed
3-838
Feature Availability
3-838
Description
3-838
Considerations
3-838
Interactions
3-839
Administration
3-839
Hardware and Software Requirements
3-839
Leave Word Calling
3-840
Feature Availability
3-840
Description
3-840
Considerations
3-842
Interactions
3-842
Administration
3-843
Hardware and Software Requirements
3-844
Line Lockout
3-845
Feature Availability
3-845
Description
3-845
Considerations
3-845
Interactions
3-845
Administration
3-845
Hardware and Software Requirements
3-845
Look Ahead Interflow
3-846
Feature Availability
3-846
Description
3-846
Look Ahead Interflow Basics
3-847
Issue 3 March 1996
xlv
Contents
Two-Switch Look Ahead Interflow Configuration
Sending Switch Operation
3-848
Receiving Switch Operation
3-849
Tandem Switch Configuration
3-853
Sending Switch Operation
3-853
Tandem Switch Operation
3-853
Example of Tandem Switch Vector
3-854
Far End Switch Operation
3-854
Display Information
■
3-854
Answering Agent’s Display
3-854
Originator’s Display
3-855
Audible Feedback
■
3-847
3-855
Considerations
3-855
Interactions
3-856
Administration
3-860
Hardware and Software Requirements
3-860
Loudspeaker Paging Ac cess
3-861
Feature Availability
3-861
Description
3-861
Considerations
3-862
Interactions
3-862
Administration
3-863
Hardware and Software Requirements
3-863
Loudspeaker Paging Ac cess — Deluxe
3-864
Feature Availability
3-864
Description
3-864
Paging Zones
PagePac Paging
Operations
Activation of Deluxe Paging by Single-Line
Voice Terminal Users
3-864
3-865
3-865
3-865
Activation of Deluxe Paging by Multi-Ap pearance
Voice Terminal Users
3-866
Activation of Deluxe Paging by an Attendant for
Another Party
3-867
xlvi
Issue 3 March 1996
Contents
Activation of Deluxe Paging Answer-Back by the
Paged Party
3-868
Unparking a Loudspeaker Paging Call
3
■
Considerations
3-868
Interactions
3-869
Administration
3-871
Hardware and Software Requirements
3-872
Malicious Call Trace (MCT)
3-873
Description
3-873
Considerations
Display Information
Switch Failure
■
3-873
Feature Availability
Feature Activation
Feature Control
Feature Deactivation
■
3-868
3-874
3-875
3-875
3-876
3-876
3-876
Interactions
3-876
Administration
3-880
Hardware/Software Requirements
3-881
Manual Message Waiting
3-882
Feature Availability
3-882
Description
3-882
Considerations
3-882
Interactions
3-882
Administration
3-882
Hardware and Software Requirements
3-882
Manual Originating Line Service
3-883
Feature Availability
3-883
Description
3-883
Considerations
3-883
Interactions
3-883
Administration
3-883
Hardware and Software Requirements
3-883
Issue 3 March 1996
xlvii
Contents
■
■
■
Manual Signaling
Feature Availability
3-884
Description
3-884
Considerations
3-884
Interactions
3-884
Administration
3-884
Hardware and Software Requirements
3-884
MERLIN®/System 25 Voice Terminal
Support — 731xH Series
3-885
Description
3-885
Considerations
3-888
Misoperation Handling
3-890
Feature Availability
3-890
Description
3-890
xlviii
3-890
Analog Operation
3-890
Digital Operation
3-891
G3V4 and Later Releases
■
3-885
Feature Availability
Standard Operation
■
3-884
3-891
Analog Operation
3-891
Digital Operation
3-892
Attendant Console
3-892
Interactions
3-893
Administration
3-893
Hardware and Software Requirements
3-893
Modem Pooling
3-894
Feature Availability
3-894
Description
3-894
Considerations
3-895
Interactions
3-896
Administration
3-897
Hardware and Software Requirements
3-897
Move Agents From CMS
3-898
Feature Availability
3-898
Description
3-898
Issue 3 March 1996
Contents
Move Agent While Staffed
■
■
Considerations
3-900
Interactions
3-901
Administration
3-901
Hardware and Software Requirements
3-901
Multi-Ap pearance Preselection and Preference
3-902
Description
3-902
Considerations
3-903
Interactions
3-903
Administration
3-904
Hardware and Software Requirements
3-904
Multiple Call Handling
3-905
Feature Availability
3-905
Description
3-905
Considerations
Work Modes
■
3-902
Feature Availability
None
On Request
One Forced
One Per Skill
Many Forced
MCH Example
■
3-899
3-906
3-906
3-906
3-907
3-908
3-908
3-909
3-909
Interactions
3-910
Administration
3-912
Hardware and Software Requirements
3-912
Multiple Listed Directory Numbers
3-913
Feature Availability
3-913
Description
3-913
Considerations
3-913
Interactions
3-913
Administration
3-914
Hardware and Software Requirements
3-914
Music-on-Hold Access
3-915
Feature Availability
3-915
Description
3-915
Issue 3 March 1996
xlix
Contents
■
Considerations
3-915
Interactions
3-915
Administration
3-916
Hardware and Software Requirements
3-916
Names Registration
Feature Availability
3-917
Description
3-917
Check-In and Check-Out
Guest Information Input/Change
Names Registration Information Format
Call Coverage
■
■
■
l
3-917
3-917
3-918
3-918
3-919
Considerations
3-919
Interactions
3-919
Administration
3-920
Hardware and Software Requirements
3-921
Network Access — Private
3-922
Feature Availability
3-922
Description
3-922
Considerations
3-922
Interactions
3-923
Administration
3-923
Hardware and Software Requirements
3-923
Network Access — Public
3-924
Feature Availability
3-924
Description
3-924
Considerations
3-924
Interactions
3-924
Administration
3-924
Hardware and Software Requirements
3-925
Night Service — Hunt Group
3-926
Feature Availability
3-926
Description
3-926
Considerations
3-926
Interactions
3-927
Administration
3-927
Hardware and Software Requirements
3-928
Issue 3 March 1996
Contents
■
■
■
■
■
Night Service — Night Console Service
3-929
Feature Availability
3-929
Description
3-929
Considerations
3-929
Interactions
3-929
Administration
3-930
Hardware and Software Requirements
3-930
Night Service — Night Station Service
3-931
Feature Availability
3-931
Description
3-931
Considerations
3-932
Interactions
3-932
Administration
3-933
Hardware and Software Requirements
3-934
Night Service — Trunk Answer From Any Station
3-935
Feature Availability
3-935
Description
3-935
Considerations
3-935
Interactions
3-935
Administration
3-936
Hardware and Software Requirements
3-936
Night Service — Trunk Group
3-937
Feature Availability
3-937
Description
3-937
Considerations
3-937
Interactions
3-938
Administration
3-939
Hardware and Software Requirements
3-939
Off-Premises Station
3-940
Feature Availability
3-940
Description
3-940
Considerations
3-940
Interactions
3-940
Administration
3-940
Hardware and Software Requirements
3-941
Issue 3 March 1996
li
Contents
3
■
PC Interface
Feature Availability
3-942
Description
3-942
Configurations
3-942
Configuration Group 2
3-943
Configuration Group 3
3-944
Applications and Benefits
3-944
Switch Features and Services
3-945
PC Features and Services
3-945
Feature History and Development
3-946
User Operations
3-947
Considerations
3-947
Interactions With Other Features
3-949
Restricting Feature Use
3-949
Hardware Requirements
3-950
lii
3-950
3-950
3-951
System Connections
3-952
Group 1
Group 2
Group 3
3-952
3-952
3-953
Feature Administration
■
3-942
Configuration Group 1
Group 1
Group 2
Group 3
■
3-942
PC/PBX Connection
3-953
3-955
Feature Availability
3-955
Description
3-955
Security Measures
3-955
Considerations
3-955
Interactions
3-956
Administration
3-956
Hardware and Software Requirements
3-956
Personal Central Office Line (PCOL)
3-957
Feature Availability
3-957
Description
3-957
Considerations
3-957
Issue 3 March 1996
Contents
■
■
■
■
■
Interactions
3-957
Administration
3-958
Hardware and Software Requirements
3-959
Personalized Ringing
3-960
Feature Availability
3-960
Description
3-960
Considerations
3-961
Interactions
3-961
Administration
3-961
Hardware and Software Requirement
3-961
Power Failure Transfer
3-962
Feature Availability
3-962
Description
3-962
Considerations
3-962
Interactions
3-962
Administration
3-962
Hardware and Software Requirements
3-963
Priority Calling
3-964
Feature Availability
3-964
Description
3-964
Considerations
3-964
Interactions
3-964
Administration
3-966
Hardware and Software Requirements
3-966
Privacy — Attendant Lockout
3-967
Feature Availability
3-967
Description
3-967
Considerations
3-967
Interactions
3-967
Administration
3-967
Hardware and Software Requirements
3-967
Privacy — Manual Exclusion
3-968
Feature Availability
3-968
Description
3-968
Considerations
3-968
Issue 3 March 1996
liii
Contents
■
Interactions
3-968
Administration
3-968
Hardware and Software Requirements
3-968
Property Management System (PMS) Interface
Feature Availability
3-969
Description
3-969
Message Waiting Notification
Controlled Restriction
Housekeeping Status
Check-In/Check-Out
Room Change/Room Swap
Names Registration
Guest Information Input/Change
■
■
3-972
3-972
3-973
3-973
3-974
3-974
3-974
Considerations
3-975
Interactions
3-975
Administration
3-976
Hardware and Software Requirements
3-978
Pull Transfer
3-979
Feature Availability
3-979
Description
3-979
Considerations
3-979
Interactions
3-980
Administration
3-980
Hardware and Software Requirements
3-980
QSIG Global Networking
3-981
Feature Availability
3-981
Description
3-981
QSIG Global Networking Basic Call
QSIG Global Networking Platform
Supplementary Services
Identification Services
Call Forwarding (Diversion)
Transfer
Interactions
Identification Services Interactions
Call Forwarding (Diversion) Interactions
Transfer Interactions
Administration
liv
3-969
Issue 3 March 1996
3-981
3-981
3-982
3-982
3-983
3-983
3-984
3-984
3-984
3-985
3-985
Contents
Hardware and Software Requirements
■
3
■
■
■
Queue Status Indications
3-986
Feature Availability
3-986
Description
3-986
Considerations
3-987
Interactions
3-987
Administration
3-988
Hardware and Software Requirements
3-988
R2-MFC Signaling
3-989
Feature Availability
3-989
Description
3-989
Considerations
3-989
Interactions
3-990
Administration
3-991
Hardware and Software Requirements
3-992
Recall Signaling
3-993
Feature Availability
3-993
Description
3-993
Considerations
3-993
Administration
3-993
Hardware and Software Requirements
3-993
Recent Change History
3-994
Feature Availability
3-994
Description
3-994
Commands
Data Commands
Transaction Log and History Report
■
3-985
3-994
3-994
3-996
Considerations
3-999
Interactions
3-999
Administration
3-999
Hardware and Software Requirements
3-999
Recorded Announcement
3-1000
Feature Availability
3-1000
Issue 3 March 1996
lv
Contents
Description
Integrated Announcements
■
■
3-1002
Single Integrated Announcement Boards
3-1002
Multiple Integrated Announcement Boards
3-1003
End User Operation
3-1003
Considerations
3-1004
Interactions
3-1004
Administration
3-1005
Hardware and Software Requirements
3-1005
Recorded Telephone Dictation Access
3-1006
Feature Availability
3-1006
Description
3-1006
Considerations
3-1006
Interactions
3-1006
Administration
3-1006
Hardware and Software Requirements
3-1007
Redirection On No Answer (RONA)
3-1008
Feature Availability
3-1008
Description
3-1008
Considerations
3-1009
Determining Which Agents Have Timed Out
Using BCMS/CMS Reports With RONA
3-1009
3-1010
BCMS
3-1010
R3 CMS
3-1010
Interactions With Other Ringing Call Timers
Miscellaneous Considerations
■
3-1000
3-1011
3-1012
Interactions
3-1012
Administration
3-1025
Hardware and Software Requirements
3-1026
Remote Access (with Security Measures)
3-1027
Feature Availability
3-1027
Description
3-1027
Setting up an Ab breviated Dialing List on
Remote Ac cess Trunks
3-1027
Remote Access Status (G3V4 and later releases) 3-1028
Security Measures
lvi
Issue 3 March 1996
3-1028
Contents
Barrier Codes
Authorization Codes
Alternate Facility Restriction Levels (AFRL)
Class of Restriction
Time of Day Routing
3-1030
Toll Restriction and Analysis
3-1030
Trunk Access Code
3-1030
Trunk Administration
3-1030
Logoff Notification
■
■
■
3-1030
Considerations
3-1031
Interactions
3-1032
Administration
3-1032
Remote Call Coverage
3-1033
Feature Availability
3-1033
Description
3-1033
Hardware Requirements
3-1033
Report Scheduler and System Printer
3-1034
Feature Availability
3-1034
Description
3-1034
Scheduling (Adding) Reports
Changing Scheduled Reports
Removing Scheduled Reports
Listing Scheduled Reports
Establishing the Printer Link
■
3-1029
3-1029
3-1030
3-1030
3-1034
3-1036
3-1037
3-1037
3-1038
Considerations
3-1038
Interactions
3-1039
Administration
3-1039
Hardware and Software Requirements
3-1039
Restriction — Controlled
3-1041
Feature Availability
3-1041
Description
3-1041
Considerations
3-1041
Interactions
3-1042
Administration
3-1042
Hardware and Software Requirements
3-1042
Restriction — Fully Restricted Service
Feature Availability
3-1043
3-1043
Issue 3 March 1996
lvii
Contents
■
■
■
■
lviii
Description
3-1043
Considerations
3-1043
Interactions
3-1043
Prohibitive
Accessible
3-1044
3-1045
Administration
3-1046
Hardware/Software Requirements
3-1046
Restriction — Miscellaneous Terminal
3-1047
Feature Availability
3-1047
Description
3-1047
Considerations
3-1047
Interactions
3-1047
Administration
3-1047
Hardware and Software Requirements
3-1047
Restriction — Miscellaneous Trunk
3-1048
Feature Availability
3-1048
Description
3-1048
Considerations
3-1048
Interactions
3-1048
Administration
3-1048
Hardware and Software Requirements
3-1049
Restriction — Toll
3-1050
Feature Availability
3-1050
Description
3-1050
Considerations
3-1051
Interactions
3-1051
Administration
3-1051
Hardware and Software Requirements
3-1052
Restriction — Voice Terminal — Inward
3-1053
Feature Availability
3-1053
Description
3-1053
Considerations
3-1053
Interactions
3-1053
Administration
3-1054
Hardware and Software Requirements
3-1054
Issue 3 March 1996
Contents
■
■
■
■
■
Restriction — Voice Terminal — Manual
Terminating Line
3-1055
Feature Availability
3-1055
Description
3-1055
Considerations
3-1055
Interactions
3-1055
Administration
3-1055
Hardware and Software Requirements
3-1055
Restriction — Voice Terminal — Origination
3-1056
Feature Availability
3-1056
Description
3-1056
Considerations
3-1056
Interactions
3-1056
Administration
3-1056
Hardware and Software Requirements
3-1056
Restriction — Voice Terminal — Outward
3-1057
Feature Availability
3-1057
Description
3-1057
Considerations
3-1057
Interactions
3-1057
Administration
3-1057
Hardware and Software Requirements
3-1057
Restriction — Voice Terminal — Public
3-1058
Feature Availability
3-1058
Description
3-1058
Considerations
3-1058
Interactions
3-1058
Administration
3-1059
Hardware and Software Requirements
3-1059
Restriction — Voice Terminal — Termination
3-1060
Feature Availability
3-1060
Description
3-1060
Considerations
3-1060
Interactions
3-1060
Administration
3-1060
Issue 3 March 1996
lix
Contents
Hardware and Software Requirements
■
■
■
Ringback Queuing
3-1061
Description
3-1061
Considerations
3-1061
Interactions
3-1062
Administration
3-1063
Hardware and Software Requirements
3-1063
Ringer Cutoff
3-1064
Feature Availability
3-1064
Description
3-1064
Considerations
3-1065
Interactions
3-1065
Administration
3-1066
Hardware and Software Requirements
3-1066
Ringing — Abbreviated and Delayed
3-1067
Feature Availability
3-1067
Description
3-1067
3-1067
3-1068
Ab breviated Ring
3-1068
Delayed Ring
3-1068
No Ring
3-1068
Ring
3-1068
Sample Operation
End-User Operation
Sample Application
lx
3-1061
Feature Availability
What Is Ringing — Abbreviated and Delayed?
What Ring Options Are Available?
■
3-1060
3-1068
3-1070
3-1070
Considerations
3-1070
Interactions
3-1071
Administration
3-1073
Hardware and Software Requirements
3-1073
Rotary Dialing
3-1074
Feature Availability
3-1074
Description
3-1074
Considerations
3-1074
Interactions
3-1074
Issue 3 March 1996
Contents
3
■
Administration
3-1074
Hardware and Software Requirements
3-1074
Security Violation Notification (SVN)
3-1075
Feature Availability
3-1075
Description
3-1075
SVN Enhancements
3-1075
Referral Call Activation/Deactivation
Login ID Kill After ‘‘N’’ Attempts
Remote Access Kill After ‘‘N’’ Attempts
Authorization Code Security Violation
SVN Referral Call With Announcement
Monitor Security Violations Report
3-1075
3-1076
3-1076
3-1076
3-1077
3-1077
Administering SVN System Parameters
3-1079
Administering the SVN Login Security Violation
Notification Feature
3-1079
Enable/Disable a Login ID
List the Status of a Login ID
3-1080
3-1081
Administering Remote Access Security Violation
Notification Parameters
Enable/Disable Remote Access Code
3-1081
3-1082
Administering Authorization Code Security Violation
Parameters
3-1083
■
■
Send All Calls
3-1087
Feature Availability
3-1087
Description
3-1087
Considerations
3-1087
Interactions
3-1087
Administration
3-1088
Hardware and Software Requirements
3-1088
Senderized Operation
3-1089
Feature Availability
3-1089
Description
3-1089
Considerations
3-1089
Interactions
3-1089
Issue 3 March 1996
lxi
Contents
■
Administration
3-1089
Hardware and Software Requirements
3-1089
Service Observing
Feature Availability
3-1090
Description
3-1090
Service Observing Logical Agent IDs
Service Observing VDNs
Service Observing Remotely/By FAC
3-1095
Security
3-1099
lxii
3-1099
3-1099
3-1099
3-1100
3-1100
Considerations
3-1100
Interactions
3-1102
Administration
3-1107
Hardware and Software Requirements
3-1107
Single-Digit Dialing and Mixed Station Numbering
3-1108
Feature Availability
3-1108
Description
3-1108
Single-Digit Dialing
Prefixed Extensions
Mixed Numbering
■
3-1091
3-1092
3-1093
Service Observing User Interface
General Service Observing Security
Vector Initiated Service Observing Security
Remote/FAC Observing
Remote Access Feature Access to Service
Observing
VDN Call Observing Security
■
3-1090
3-1108
3-1108
3-1110
Considerations
3-1112
Interactions
3-1112
Administration
3-1113
Hardware and Software Requirements
3-1113
Straightforward Outward Completion
3-1114
Feature Availability
3-1114
Description
3-1114
Considerations
3-1114
Interactions
3-1114
Administration
3-1114
Hardware and Software Requirements
3-1114
Issue 3 March 1996
Contents
■
■
Subnet Trunking
3-1115
Feature Availability
3-1115
Description
3-1115
Considerations
3-1117
Interactions
3-1118
Administration
3-1118
Hardware and Software Requirements
3-1118
Switch Based Bulletin Board
3-1119
Feature Availability
3-1119
Description
3-1119
Access to the Switch Based Bulletin Board
3-1119
Bulletin Board Commands
3-1120
System Commands Used to Access the Switch
Based Bulletin Board
Commands Used to Change Switch Based
Bulletin Board Messages
Entering Messages into the Switch Based
Bulletin Board
Displaying Messages on the Switch Based
Bulletin Board
■
■
3-1120
3-1120
3-1120
3-1121
Considerations
3-1121
Administration
3-1121
Feature Initialization and Recovery
3-1122
System Measurements
3-1123
Feature Availability
3-1123
Description
3-1123
Considerations
3-1124
Interactions
3-1124
Administration
3-1125
Hardware and Software Requirements
3-1125
System Status Report
3-1126
Feature Availability
3-1126
Description
3-1126
Considerations
3-1127
Interactions
3-1127
Administration
3-1127
Hardware and Software Requirements
3-1127
Issue 3 March 1996
lxiii
Contents
■
■
Temporary Bridged Ap pearance
Feature Availability
3-1128
Description
3-1128
Considerations
3-1128
Interactions
3-1129
Administration
3-1129
Hardware and Software Requirements
3-1129
Tenant Partitioning
3-1130
Description
3-1130
3-1130
Access Control
3-1131
Attendant Services
3-1132
Multiple Music on Hold
3-1132
Network Route Selection
3-1133
Sample Tenant Partitioning
3-1133
Considerations
Capacities
3-1135
3-1135
Interactions
3-1135
Administration
3-1138
Hardware and Software Requirements
3-1139
Terminal Translation (with Security Measures)
3-1140
Feature Availability
3-1140
Description
3-1140
Terminal Association from a Voice TTI Port
Terminal Disassociation from a Voice Station
Other Types of Terminals
Attendants
Analog Queue Warning Ports and External
Alert Ports
Data Modules
3-1140
3-1141
3-1141
3-1141
3-1141
3-1142
Tone differences
3-1142
Digit sequence differences
3-1142
Voice/Data terminals
ISDN BRI Terminals
lxiv
3-1130
Feature Availability
Partitioning Tenants
■
3-1128
3-1142
3-1143
Security Measures
3-1143
Considerations
3-1143
Issue 3 March 1996
Contents
Interactions
3-1144
Administration
3-1147
TTI Port Assignment
Terminal Moves and Site Data
Administration without Hardware
Enabling/Disabling TTI
3-1147
3-1147
3-1148
3-1148
System Parameters Customer Option Screen 3-1148
System Parameters Features Screen
System Parameter Operation
TTI Status Form
Save Translation Operation
Transaction Logging
TTI Security Code
Feature Access Codes
3-1148
3-1149
3-1150
3-1150
3-1150
3-1150
Hardware/Software Requirements
■
■
3-1150
Terminating Extension Group (TEG)
3-1151
Feature Availability
3-1151
Description
3-1151
Considerations
3-1151
Interactions
3-1152
Administration
3-1153
Hardware and Software Requirements
3-1154
Time of Day Routing
3-1155
Feature Availability
3-1155
Description
3-1155
Time of Day Routing Example
Overriding the Time of Day Routing Plan
■
3-1148
3-1156
3-1157
Immediate Manual Override
3-1158
Clocked Manual Override
3-1159
Considerations
3-1160
Interactions
3-1160
Administration
3-1162
Hardware and Software Requirements
3-1162
Timed Reminder and Attendant Timers
3-1163
Feature Availability
3-1163
Description
3-1163
Considerations
3-1164
Issue 3 March 1996
lxv
Contents
■
■
■
Interactions
3-1165
Administration
3-1166
Hardware and Software Requirements
3-1166
Touch-Tone Dialing
Feature Availability
3-1167
Description
3-1167
Considerations
3-1167
Interactions
3-1167
Administration
3-1167
Hardware and Software Requirements
3-1167
Transfer
lxvi
3-1168
Feature Availability
3-1168
Description
3-1168
Considerations
3-1168
Interactions
3-1168
Administration
3-1169
Hardware and Software Requirements
3-1169
Transfer — Outgoing Trunk to
Outgoing Trunk (with Security Measures)
3-1170
Feature Availability
3-1170
Description
3-1170
Considerations
3-1171
Security Measures
3-1171
Interactions
3-1171
DCS Trunk Turnaround
Incoming Disconnect Supervision
Release Link Trunks (RLT)
Restriction
Trunk-to-Trunk Transfer
PCOL Interactions
■
3-1167
3-1171
3-1172
3-1172
3-1172
3-1172
3-1173
Administration
3-1173
Hardware/Software Requirements
3-1174
Trunk Flash
3-1175
Feature Availability
3-1175
Description
3-1175
Considerations
3-1175
Issue 3 March 1996
Contents
■
■
■
3
■
■
Interactions
3-1177
Administration
3-1177
Hardware and Software Requirements
3-1177
Trunk Group Busy/Warning Indicators to Attendant
3-1178
Feature Availability
3-1178
Description
3-1178
Considerations
3-1178
Interactions
3-1178
Administration
3-1178
Hardware and Software Requirements
3-1179
Trunk Identification By Attendant
3-1180
Feature Availability
3-1180
Description
3-1180
Considerations
3-1180
Interactions
3-1181
Administration
3-1181
Hardware and Software Requirements
3-1181
Trunk-to-Trunk Transfer
3-1182
Feature Availability
3-1182
Description
3-1182
Considerations
3-1182
Interactions
3-1183
Administration
3-1183
Hardware and Software Requirements
3-1183
Uniform Dial Plan (UDP)
3-1184
Feature Availability
3-1184
Description
3-1184
Considerations
3-1187
Interactions
3-1188
Administration
3-1189
Hardware and Software Requirements
3-1189
VDN of Origin Announcement (VOA)
3-1190
Issue 3 March 1996
lxvii
Contents
■
■
■
■
lxviii
Feature Availability
3-1190
Feature History
3-1190
Description
3-1190
Considerations
3-1192
Interactions
3-1193
Administration
3-1197
Hardware and Software Requirements
3-1197
Visually Impaired Attendant Service (VIAS)
3-1198
Feature Availability
3-1198
Description
3-1198
Considerations
3-1199
Interactions
3-1199
Administration
3-1199
Hardware and Software Requirements
3-1199
Voice Message Retrieval
3-1200
Feature Availability
3-1200
Description
3-1200
Considerations
3-1203
Interactions
3-1203
Administration
3-1204
Hardware and Software Requirements
3-1204
Voice Response Integration (VRI)
3-1205
Feature Availability
3-1205
Description
3-1205
Security Measures
3-1209
Considerations
3-1209
Interactions
3-1209
Administration
3-1216
Hardware and Software Requirements
3-1216
Voice Terminal Alerting Options
3-1217
Feature Availability
3-1217
Description
3-1217
Considerations
3-1218
Interactions
3-1218
Administration
3-1219
Issue 3 March 1996
Contents
Hardware and Software Requirements
■
3-1219
Voice Terminal Display
3-1220
Feature Availability
3-1220
Description
3-1220
Considerations
3-1225
Interactions
3-1226
Administration
3-1226
Hardware and Software Requirements
3-1227
■
Voice Terminal Flash Timing
3-1228
■
VuStats
3-1229
Feature Availability
3-1229
What Is VuStats?
3-1229
VuStats Ap plications
3-1230
Self-Managed Teams
Information Distribution
Call Center Management
3-1230
3-1231
3-1231
Detailed Description
3-1231
What Information Ap pears on the Display
3-1231
Object Type
3-1231
Data Type
3-1232
Interval
3-1232
Thresholds
3-1233
Text
3-1233
Display Linking
3-1233
How the Information Looks
When the Information Updates, or Vanishes
End User Operation
3-1234
3-1235
3-1235
Agent Operation (Agent Object Type)
Supervisor Operation (Agent-extension, split,
VDN, or Trunk Group Object Type)
3-1235
3-1236
Administered ID
3-1236
ID Not Administered
3-1237
Error Messages
3-1238
Call Center Example
3-1239
Split 1
Splits 2 and 3
Split 4
3-1240
3-1242
3-1244
Issue 3 March 1996
lxix
Contents
Agent 12
Split Supervisors
Supervisor 1
Sample Administration
■
lxx
3-1247
3-1248
3-1248
Interactions
3-1248
Administration
3-1250
Hardware Requirements
3-1250
Wideband Switching
3-1251
Feature Availability
3-1251
Description
3-1251
Technical Description
3-1252
Channel Allocation
Typical Uses
3-1253
3-1253
Considerations
3-1254
Glare
Blocking
3-1254
3-1255
Interactions
3-1255
Administration
3-1257
Hardware and Software Requirements
■
3-1246
Considerations
Access Endpoint
PRI Endpoint
Trunk Groups
Routing Patterns
Customer Option Form
■
3-1245
World Class Basic Rate Interface (BRI)
3-1257
3-1258
3-1258
3-1258
3-1258
3-1259
3-1260
Feature Availability
3-1260
Description
3-1260
Considerations
3-1260
Interactions
3-1260
Administration
3-1261
Hardware and Software Requirements
3-1261
World Class Tone Detection
3-1262
Feature Availability
3-1262
Description
3-1262
Considerations
3-1262
Issue 3 March 1996
Contents
■
A
3-1262
Administration
3-1263
Hardware and Software Requirements
3-1263
World Class Tone Generation
3-1264
Feature Availability
3-1264
Description
3-1264
Considerations
3-1264
Interactions
3-1264
Administration
3-1264
Hardware and Software Requirements
3-1264
System Parameters
■
■
B
Interactions
A-1
Overview
A-1
Administration Not Required
A-1
Administration Required
A-2
Feature Access
A-7
Dial Access Only
A-7
Button Access Only
A-9
Dial and Button Access
A-11
Feature Status Button Indicators
A-12
■
Overview
A-12
■
System Hardware and Software Capacity Limits
A-12
References
B-1
■
Basic
B-1
■
Call Center
B-6
■
Networks
B-7
■
Ap plication Specific
B-7
Issue 3 March 1996
lxxi
Contents
C
Generic 3 V3 to Generic 3 V4
Transition Reference
C-1
ABB
Abbreviations
ABB-1
GL
Glossary
GL-1
IN
Index
IN-1
lxxii
Issue 3 March 1996
About This Document
This document describes DEFINITY® Communications System Generic 3
features. Differences between the various Generic 3 (G3) releases, are
specifically identified throughout this document.
Purpose
This document helps switch administrators and managers select communication
features to include in their initial system or to add after the system is in service. It
provides feature descriptions, administration and hardware information, and
other considerations applicable for each available feature.
Along with the DEFINITY Communications System Generic 3 System Description
and Specifications, 555-230-206, this document provides an overall reference for
the planning, operation, and administration of your DEFINITY switch. It is also a
tool for answering questions about the interactions between specific features.
Feature capacities and limitations are described in the System Capacity Limits
table in Ap pendix A.
This document is used in conjunction with the DEFINITY Communications System
Generic 3 Version 4 Implementation, 555-230-655, for software initialization and
subsequent changes in feature assignments for systems G3sV1, 555-230-650
and 555-230-650ADD; G3iV1, 555-230-650; G3rV1, 555-230-651; G3i-Global,
555-230-652; G3V2, 555-230-653; G3V3, 555-230-653ADD1; G3V4, 653ADD1.
Issue 3 March 1996
lxxxv
About This Document
Intended Audiences
This document is intended for the DEFINITY switch administrators and managers
in your company, end-users interested in information about specific features, and
AT&T support personnel responsible for planning, designing, configuring, and
selling the system.
Reason For Reissue
This document is updated to include Generic 3 Version 4 information.
How to Use This Document
This document is designed to be used as a reference document. If you are
interested in information about a particular feature, use the table of contents or
index to locate the page number where the feature is described.
Organization
This document is organized as follows:
■
Chapter 1, "Introduction" provides an introduction to this document and
provides a general description of the functions and services provided with
the system. Chapter 1 also recommends various security measures to
protect your system from unauthorized use.
■
Chapter 2, "Functional Description" provides descriptions of the
DEFINITY switch features, functions, and services. This chapter also
presents these capabilities classified into six categories: Voice
Management, Data Management, Network Services (including World
Class Routing), System Management, Hospitality Services, and Call
Center Services. Each group of functions and services, including a listing
of associated features, is described separately in a section of this chapter.
See Chapter 3, "Feature Descriptions" for detailed information on
individual features.
lxxxvi
■
Chapter 3, "Feature Descriptions" provides detailed information of the
system features. The features are arranged in alphabetical order,
regardless of the functional area to which they apply. The information for
each feature is presented under six headings: Feature Availability,
Description, Considerations, Interactions, Administration, and Hardware
and Requirements.
■
Appendix A, "System Parameters" provides information relating to
overall system characteristics and capacities. This chapter includes items
that must be considered when planning for system implementation.
Issue 3 March 1996
Security Requirements
■
Appendix B, "References" provides a list and brief descriptions of
reference documents.
■
Appendix C, "Generic 3 V3 to Generic 3 V4 Transition Reference"
provides a list indicating new and enhanced features for G3V4 and briefly
describes G3V4 feature enhancements.
■
Abbreviations provides a list of abbreviations for the entire document.
■
Glossary provides a glossary for the entire document.
■
Index provides an index for the entire document.
Security Requirements
Chapter 1, "Introduction" contains a section describing security practices you
should follow and list the features requiring special measures to secure them
from unauthorized use. (You can also consult the index under ‘‘Security
Measures.’’)
The feature descriptions for these features have an extra section, entitled
‘‘Security Measures,’’ describing the security steps you should perform.
Conventions Used in This Document
This document uses the following conventions:
■
Italic typeface is used to emphasize key words in text.
■
Command names, file names, and parameters are shown in Helvetica
Bold typeface.
■
Variables and information you type are shown in Helvetica Bold Italic.
■
System messages, screens, and responses are shown using Constant
Width typeface.
■
Variables are shown in Helvetica Light Oblique typeface.
■
Keyboard keys are shown inside an oval (for example,
■
Telephone dial-pad buttons are shown inside square boxes (for example,
2 or
) and may refer to either rotary or touch-tone telephones.
RETURN
).
*
Trademarks and Service Marks
The following are trademarks or registered trademarks of AT&T:
■
ACCUNET®
■
AUDIX®
■
CallVisor™
Issue 3 March 1996
lxxxvii
About This Document
■
CALLMASTER®
■
CentreVu™
■
CONVERSANT®
■
DATAPHONE®
■
DEFINITY®
■
DIMENSION®
■
4ESS™
■
MEGACOM®
■
MERLIN®
■
MULTIQUEST®
■
TELESEER®
■
VOICE POWER®
■
UNIX®
The following are trademarks or registered trademarks of other companies:
■
Ascend® (registered trademark of Ascend, Inc.)
■
Audichron® (registered trademark of the Audichron Company)
■
MS-DOS® (registered trademark of the Microsoft Corporation)
■
MicroChannel® (registered trademark of IBM Systems)
■
MULTIQUEST® (registered trademark of Telecommunications Service)
■
PagePac ® (trademark of the Dracon Division of the Harris Corporation)
How to Make Comments About This
Document
Reader comment cards are provided at the back of this document. While we
have tried to make this document fit your needs, we are interested in your
suggestions for improving it and urge you to complete and return a reader
comment card.
If the reader comment cards have been removed from this document, please
send your comments to:
AT&T
Product Documentation Development Group
Room 22-2C11
11900 North Pecos Street
Denver, CO 80234
lxxxviii
Issue 3 March 1996
Introduction
1
Overview
This document describes the DEFINITY Generic 3 family of cost-effective digital
communication systems. These systems:
■
Route voice and data information between various endpoints (telephones,
terminals, computers, etc.)
■
Provide highly robust networking capabilities
■
Include an extensive set of standard features (for example, Attendant
Consoles, Voice Processing Interface, Call Coverage, DS1/E1
Connectivity, Hospitality Support, Recorded Announcement, and
Trunk-to-Trunk Transfer)
■
Provide flexibility and allow for the addition of optional features and/or
upgrades to the system as business needs change
The term ‘‘DEFINITY Generic 3’’ refers to four distinct hardware platforms:
■
DEFINITY Generic 3vs [A wall mounted unit] (G3vs)
■
DEFINITY Generic 3s [A small floor or table unit] (G3s)
■
DEFINITY Generic 3i [A medium size i386-based switch available in
several configurations] (G3i)
■
DEFINITY Generic 3r [A large MIPS-based switch also available in multiple
configurations] (G3r)
These switches meet and exceed the needs of a wide variety of businesses. For
example, G3s is a cost-effective switch for businesses with less than 200 stations
and 100 trunks. G3i, on the other hand, meets the requirements of larger
businesses that require more than 200 stations and 100 trunks. G3r, the largest
switch, provides even greater capacities.
Issue 3 March 1996
1-1
Introduction
The current release of Generic 3 introduces Version 4 of the G3 switches. These
phone switches are now more powerful and full-featured than ever.
This document describes versions of Generic 3. This chapter briefly describes
the differences between the various Generic 3 switches and is organized into the
following sections:
■
Generic 3 Version 1
This section describes the Generic 3 Version 1 offering; it compares the
G3i, G3i-Global, and G3r Version 1 switches to the earlier G1 switch; and
it compares the G3s and G3vs Version 1 switch to the G3i Version 1
switch.
■
Generic 3 Version 2
This section describes the Generic 3 enhancements introduced in Version
2.
■
Generic 3 Version 3
This section describes the Generic 3 enhancements introduced in Version
3.
■
Generic 3 Version 4
This section describes the Generic 3 enhancements introduced in Version
4.
■
Generic 3 Notation
This section explains notation used throughout this document to
differentiate the various switches, and the different versions of the same
switch.
For a list of the features available with each switch, see Table 1-6 in this chapter;
for a summary of the system capacities for each switch, see Appendix A,
"System Parameters".
1-2
Issue 3 March 1996
Generic 3 Version 1
Generic 3 Version 1
Generic 3 Version 1 includes the following switches:
■
Generic 3i Version 1
■
Generic 3i-Global (Contains features for international requirements)
■
Generic 3r Version 1
■
Generic 3s Version 1
■
Generic 3vs Version 1
Each switch is described next.
G3i Version 1
G3i Version 1 is an enhanced version of earlier DEFINITY switches and combines
many of the features of Generic 1 and Generic 2. G3i Version 1 addresses the
needs of businesses in the United States and supports up to 1600 stations and
400 trunks.
G3i Version 1 introduced the following features and functions that are not part of
G1 or G2:
■
Access Endpoints (See the Administered Connections Feature)
■
Administered Connections
■
Administration Without Hardware
■
Alphanumeric Dialing
■
Attendant Serial Calling
■
Attendant Intrusion (Call Offer)
■
Attendant Override of Diversion Features
■
Attendant Priority Queue
■
Call Pickup Alerting
■
Call Prompting
■
Call Vectoring
■
CallVisorTM ASAI (Adjunct/Switch Application Interface)
■
DCS Over ISDN-PRI D-Channel
■
Default Dialing
■
Non-Facility Associated Signaling and D-Channel Backup
■
Inbound Call Management
■
Integrated Services Digital Network — Basic Rate Interface (ISDN-BRI)
Issue 3 March 1996
1-3
Introduction
■
Look Ahead Interflow
■
Security Violation Notification
Additional G1 features are significantly enhanced for G3i Version 1. These
features include:
■
ARS and AAR also known as ‘‘Ten-to-Seven Digit Conversion’’ are
enhanced to support Multi-National Call Routing and Multi-National Toll
Analysis
■
Forced Entry of Account Codes, now known as CDR Ac count Code
Dialing
■
Agent Call Handling — Stroke Counts, Call Work Codes, and Forced Entry
of Stroke Counts and Call Work Codes are added
■
Automatic Call Distribution — Direct Agent Calling is added
■
Call Detail Recording — New CDR record formats are added
■
Class of Restriction — New restrictions are added
■
Integrated Services Digital Network — Primary Rate Interface (ISDN-PRI)
— Software Defined Data Network (SDDN) was added
■
Toll Restriction
G3i-Global Version 1
G3i Version 1 is an enhanced version of earlier DEFINITY switches and combines
many of the features of Generic 1 and Generic 2. G3i-Global Version 1
addresses business needs in the global market and supports up to 2400 stations
and 400 trunks.
The number of differences between G1 and G3i-Global is predicated on whether
you had an international version of G1 or the United States (US) version. Some
international features were built into the G1 switches produced for locations
outside this country.
G3r Version 1
G3r Version 1 is an enhanced version of earlier DEFINITY switches and
combines many of the features of Generic 1 and Generic 2. It is the DEFINITY
switch required for large applications or large offices. G3r Version 1 addresses
the needs of businesses in the United States and supports up to 10,000 stations
and 4,000 trunks.
G3r Version 1 introduced the following features and functions that are not part of
G1. It also contains most of the G3iV1 features. New features are shown below:
1-4
■
Alternate Facilities Restriction Levels
■
Attendant Serial Calling
Issue 3 March 1996
Generic 3 Version 1
■
Attendant Intrusion (Call Offer)
■
Attendant Override of Diversion Features
■
Attendant Priority Queue
■
ACD — Auto-Available Split
■
Audible Message Waiting
■
Auto-Start/Don’t Split
■
Automatic Transmission Measurement System
■
DCS Over ISDN-PRI D-Channel
■
Extension Number Portability
■
Extended Trunk Access
■
Hold — Automatic
■
Malicious Call Trace
■
Multiple User Access — Maintenance and Administration
■
Restriction — Fully Restricted Service
■
Terminal Translation Initialization
■
Transfer — Outgoing Trunk to Outgoing Trunk
Other G1 features are significantly enhanced for G3r Version 1. These features
include:
■
Administration Without Hardware
■
Attendant Dial Access
■
Attendant Timers and Timed Reminders
■
Automatic Alternate Routing (AAR)
■
Automatic Route Selection (ARS)
■
AUDIX
■
Call Detail Recording (CDR) [Formerly called SMDR]
■
CallVisor ASAI (Adjunct/Switch Application Interface)
■
Class of Restrictions (COR)
■
Conference — Attendant
■
Conference — Voice Terminal
■
Dial Plan
■
Direct Inward Dialing (DID)
■
Distinctive Ringing
■
DS1 Tie Trunk Service
Issue 3 March 1996
1-5
Introduction
■
Emergency Access to Attendant
■
Facilities Test Calls
■
Leave Word Calling
■
Line Lockout
■
Trunk Group Hunting
G3s Version 1
DEFINITY Generic 3s Version 1 is designed to provide businesses with up to 200
stations with greater flexibility in choosing their telecommunication systems. Not
only does G3s carry the same strength of architecture, price performance, and
investment protection provided by Generic 3i and Generic 3r, DEFINITY Generic
3s also includes many of the Generic 3i features and applications in packages
that serve a variety of business needs.
DEFINITY Generic 3s offers two distinct packages: the Premier Business
Package (PBP) and the Advantage Business Package (ABP). Each package
contains a subset of the DEFINITY Generic 3i features and options that meet
specific business needs and provide flexible communication solutions.
The Premier Business Package is designed for customers with up to 200 stations
and 100 trunks, while the Advantage Business Package is designed for
customers with up to 200 stations and 50 trunks. The optional features for PBP
are the same as for G3i; the optional features for ABP includes a subset of the
G3i optional features and are available through various option packages. See
Table 1-6 for further details.
G3vs Version 1
DEFINITY Generic 3vs is a new member of the Generic 3 family of cost-effective
digital communications systems designed to: provide businesses with 80 or
fewer stations greater flexibility in choosing their telecommunication systems. It
also provides satellite affiliates of multi-location businesses with the same
telecommunication services available at larger locations using the G3s, G3i, and
G3r switches.
G3vs is a convenient compact single-carrier cabinet switch that is wall-mounted.
It has a FLASH memory cartridge that supports all G3s features and options
except, Integrated Services Digital Network — Basic Rate Interface (ISDN-BRI)
and CallVisor Adjunct/Switch Ap plication Interface (ASAI).
As stated for G3s, the Advantage Business Package and the Premier Business
Package are available.
1-6
Issue 3 March 1996
Generic 3 Version 2
Generic 3 Version 2
Version 2 combines almost all features available in Version 1 software across all
hardware platforms into one software base. This base is available on all
platforms. For example, the international features that were only available for
DEFINITY G3i-Global are now available for G3r, G3i, and G3s/G3vs. Generic 3
Version 2 includes the following switches:
■
Generic 3i Version 2 (G3iV2)
G3i Version 2 also runs on two distinct processor platforms: an i286 and
i386. To distinguish between these products this document will sometimes
specify G3iV1-286 and G3iV1-386 or G3iV2-286 and G3iV2-386. The
major differences between these packages are that G3i-386 has larger
capacity limits than the G3i-286 (see Ap pendix A, "System Parameters" for
details).
■
Generic 3r Version 2 (G3rV2)
■
Generic 3s Version 2 (G3sV2)
G3s Version 2 has two packages: the Premier Business Package (PBP)
and the Advantage Business Package (ABP).
■
Generic 3vs Version 2 (G3vsV2)
G3vs Version 2 has two packages: the Premier Business Package (PBP)
and the Advantage Business Package (ABP).
New Features for Version 2
The following new features are supported in Generic 3 Version 2:
■
EAS (Expert Agent Selection)
■
ECMA (European Computer Manufactures Association) ISDN-PRI Basic
Call
■
Japan NTT ISDN-PRI Basic Call
■
Redirection on No Answer (RONA)
■
Spain Telephone System Compatibility
■
Voice Response Integration (VRI)
■
Wideband Switching
Generic 3 Version 3
Generic 3 Version 3 includes the following switches:
■
Generic 3i Version 3 (G3iV3)
G3i Version 3 runs on the i386 processor platform.
Issue 3 March 1996
1-7
Introduction
■
Generic 3r Version 3 (G3rV3)
■
Generic 3s Version 3 (G3sV3)
G3s Version 3 has two packages: the Premier Business Package (PBP)
and the Advantage Business Package (ABP).
■
Generic 3vs Version 3 (G3vsV3)
G3vs Version 3 has two packages: the Premier Business Package (PBP)
and the Advantage Business Package (ABP).
New Features for Version 3
The following new features are supported in Generic 3 Version 3:
■
Add/Remove Skills
■
Administrable Logins
■
Agent Sizing
■
Attendant Room Status
■
Constellation Voice/Data Terminal Support
■
Forced Password Aging
■
Multiple Call Handling
■
Switch Based Bulletin Board
■
VDN of Origin Announcements
■
VuStats
Many Generic 3 features were also enhanced for G3V3. See DEFINITY
Communications System Generic 3V2 to Generic 3V3 Transition Reference,
555-230-621, for a complete description of all V2 to V3 additions and
enhancements.
Generic 3 Version 4
Generic 3 Version 4 includes the following switches:
■
Generic 3i Version 4 (G3iV4)
G3i Version 4 runs on the i386 processor platform.
■
Generic 3r Version 4 (G3rV4)
■
Generic 3s Version 4 (G3sV4)
G3s Version 4 has two packages: the Premier Business Package (PBP)
and the Advantage Business Package (ABP).
■
1-8
Generic 3vs Version 4 (G3vsV4)
Issue 3 March 1996
Generic 3 Version 4
G3vs Version 4 has two packages: the Premier Business Package (PBP)
and the Advantage Business Package (ABP).
New Features for Version 4
The following new features are supported in Generic 3 Version 4:
■
Advice of Charge (ISDN-PRI)
■
Call Forward Busy/Don’t Answer
■
DCS Call Coverage
■
Flexible Billing
■
Misoperation Handling (modified)
■
PC Application Software Translation Exchange (PASTE)
■
Ringing — Ab breviated and Delayed
■
Tenant Partitioning
■
World Class Core BRI
Many Generic 3 features were also enhanced for G3V4. See Appendix C,
"Generic 3 V3 to Generic 3 V4 Transition Reference" for a complete description of
all V3 to V4 additions and enhancements.
Issue 3 March 1996
1-9
Introduction
Generic 3 Notation
The Generic 3 notation refers to ALL G3 releases. To differentiate between the
Generic 3 (G3) switches as a group, and the different implementations of the
Generic 3 switches, the notations listed below are used in this document
Table 1-1.
Generic 3 Version 1 Switches
Abbreviation
Refers to...
G3sV1
Generic 3s Version 1
G3sV1 ABP
Generic 3s Version 1 Advantage Business Package
G3sV1 PBP
Generic 3s Version 1 Premier Business Package
G3vsV1
Generic 3vs Version 1
G3vsV1 ABP
Generic 3vs Version 1 Advantage Business Package
G3vsV1 PBP
Generic 3vs Version 1 Premier Business Package
G3iV1
Generic 3i Version 1
G3i-Global
International Generic 3i Version 1
G3rV1
Generic 3r Version 1
G3V1
G3sV1, G3vsV1, G3iV1, G3i-Global, and G3rV1
.
Table 1-2.
1-10
Generic 3 Version 2 Switches
Abbreviation
Refers to...
G3sV2
Generic 3s Version 2
G3sV2 ABP
Generic 3s Version 2 Advantage Business Package
G3sV2 PBP
Generic 3s Version 2 Premier Business Package
G3vsV2
Generic 3vs Version 2
G3vsV2 ABP
Generic 3vs Version 2 Advantage Business Package
G3vsV2 PBP
Generic 3vs Version 2 Premier Business Package
G3iV2
Generic 3i Version 2
G3iV2-286
Generic 3i Version 2 on 286 processor
G3iV2-386
Generic 3i Version 2 on 386 processor
G3rV2
Generic 3r Version 2
G3V2
G3sV2, G3vsV2, G3iV2, and G3rV2
Issue 3 March 1996
Generic 3 Notation
Table 1-3.
Generic 3 Version 3 Switches
Abbreviation
Refers to...
G3sV3
Generic 3s Version 3
G3sV3 ABP
Generic 3s Version 3 Advantage Business Package
G3sV3 PBP
Generic 3s Version 3 Premier Business Package
G3vsV3
Generic 3vs Version 3
G3vsV3 ABP
Generic 3vs Version 3 Advantage Business Package
G3vsV3 PBP
Generic 3vs Version 3 Premier Business Package
G3iV3
Generic 3i Version 3
G3rV3
Generic 3r Version 3
G3V3
G3sV3, G3vsV3, G3iV3 and G3rV3
Table 1-4.
Generic 3 Version 4 Switches
Abbreviation
Refers to...
G3sV4
Generic 3s Version 4
G3sV4 ABP
Generic 3s Version 4 Advantage Business Package
G3sV4 PBP
Generic 3s Version 4 Premier Business Package
G3vsV4
Generic 3vs Version 4
G3vsV4 ABP
Generic 3vs Version 4 Advantage Business Package
G3vsV4 PBP
Generic 3vs Version 4 Premier Business Package
G3iV4
Generic 3i Version 4
G3rV4
Generic 3r Version 4
G3V4
G3sV4, G3vsV4, G3iV4 and G3rV4
Issue 3 March 1996
1-11
Introduction
The following table identifies switches independent of their versions.
Table 1-5.
1-12
Generic 3 Switches
Abbreviation
Refers to...
G3s
G3sV1, G3sV2, G3sV3, G3sV4
G3vs
G3vsV1, G3vsV2, G3vsV3, G3vsV4
G3i
G3iV1, G3iV2, G3iV3, G3iV4
G3i-Global
G3V1-Global
G3r
G3rV1, G3rV2, G3rV3, G3rV4
G3
G3V1, G3V2, G3V3, G3V4
Issue 3 March 1996
Security Measures
Security Measures
Security on the Remote Administration port cannot be overemphasized. If it is not
secure, an unauthorized user can compromise the system in many ways, such
as viewing Barrier and Authorization codes or viewing Feature Access Codes.
!
WARNING:
If you suspect that unauthorized access has occurred, the system
administrator should change the barrier codes, authorization codes,
passwords, and any other sensitive codes.
To help secure the system, the system administrator should follow the steps
below:
■
Change the factory default passwords after the system is powered up if
you have a DEFINITY release prior to G3V3. With G3V3 and higher, the
switch is equipped with init, inads, and craft passwords. These are the
only default logins and are AT&T services logins. The first superuser
customer login must be created during the installation process.
■
If you are upgrading to V3 or V4, your logins and passwords will be
preserved as part of the upgrade process. In this case, change logins and
passwords following the upgrade.
■
Change passwords quarterly.
■
Administer the Security Violation Notification feature to report
unsuccessful attempts to access the system. With G3V3 and later
releases, the Security Violation Notification Feature has the added
capability of disabling a valid login ID following a security violation
involving that login ID and disabling remote access following a security
violation involving a barrier code or authorization code.
■
Use the Recent Change History feature to determine if unauthorized
changes have been made to the system. To assist in identifying
unauthorized use of the system, in G3V4, the Recent Change History
Report lists each time a user logs in or off the system.
NOTE:
With the exception of log ins and log offs with G3V4 and later
releases, the Recent Change History feature does not record and
display administration commands that only display information.
Please pay special attention to the features and security measures discussed in
the following sub-sections.
For assistance with toll fraud prevention, call either AT&T Corporate Security at
800 821-8235 or the DEFINITY Helpline at 800 225-7585.
If you have identified fraudulent calling in progress, and require assistance in
stopping the fraud, call the AT&T Technical Service Center at 800 242-2121.
Issue 3 March 1996
1-13
Introduction
When you have dialed the service center number from a touch-tone phone, you
will make selections on several menus to access toll fraud help. Follow the verbal
instructions provided by the menu topics.
Logoff Notification
G3V4 and later releases provide for notification at logoff when the Remote
Access or Facility Test Calls features remain active. Logoff Notification is
administered on the Login Administration form and can be assigned to any login
ID. The notification can be administered to force acknowledgment from the user.
Logoff Notification is primarily used to notify the system administrator when one
of these security risk features is still active at logoff. Notification guards against
inadvertently leaving a security risk feature active. It can also alert the system
administrator to unauthorized feature activation. See the GBCS Products Security
Handbook, 555-025-600, for more information.
Passwords
1. Change all default passwords in both the switch and adjuncts (CMS,
CSM, AUDIX, Trouble Tracker, VMAAP, Manager II/III, Conversant, Intuity,
and others)
2. The following customer logins are included in the G1 and G3 (pre-V3)
product: cust, rcust, browse, b cms, and nms. The “cust” login is for
superuser access. The remaining logins are non-superuser access.
G3V3 and later releases have administrable logins.
3. AT&T will change the password quarterly on its login IDs.
4. Use the maximum number of digits, mixing both alpha and numeric
5. Change passwords at least quarterly
G3V3 and later releases enhanced switch security by adding Forced Password
Aging and Administrable Logins. This security feature enables the user to define
their own login IDs and specify a set of commands that each login has access
to. In addition, the user is required to change the password for each login at
specified time intervals when Forced Password Aging is administered.
Physical Security
1. Keep wiring closets and switch rooms secure
2. Keep any documentation pertaining to switch operation secure
3. Keep any reports that may reveal trunk access code, remote access
barrier codes, authorization codes, or password information secure
1-14
Issue 3 March 1996
Security Measures
Remote Administration Port
Security on the Initialization and Administration System (INADS) Remote
Administration Port is critical. The optional Remote Port Security Device (RPSD)
is a password encryption device that can be attached to the Remote
Administration Port for increased security. It is virtually impenetrable and
provides maximum protection.
To increase system security, G3V4 by default disables customer access to the
INADS Remote Administration Port. For a customer to have access, AT&T must
enable customer super-user login access. Once access is enabled, the
customer must enable port access as needed per user login.
Trunks
1. If ARS is provided, do not allow Dial Access by Trunk Access Codes
2. Remove the Facility Test Call feature code (Feature Access Codes)
3. On the COR form disable the Facility Access Trunk Test (N)
4. If provided, administer a trk-ac-alm on the console to alert whenever the
Facility Test Call feature is enabled
5. Disallow Trunk-To-Trunk Transfer if not needed
6. Disallow or limit outgoing calls from tie lines by assigning appropriate
FRL’s
7. Require Forced Entry of Account Codes or Authorization Codes on toll
calls
8. Block International calls if no business is conducted overseas or use the
ARS tables to limit calling to specific country codes or North American
area codes.
9. Block area codes if calls to certain states are not permitted
AUDIX
1. Limit voice mail to internal calling only by Outward Restricting the COR of
the voice ports and assigning the lowest possible FRL to the COR
2. Allow outbound calls to only certain numbers as defined by the
Unrestricted Call List
3. Activate Enhanced Call Transfer if available in the AUDIX, DEFINITY
AUDIX, or Intuity and if supported by the switch
4. Restrict the transfer capability of AUDIX from accessing trunks by
assigning a COR that prohibits access.
For details on how to administer a DEFINITY AUDIX installation, refer to Switch
Administration for DEFINITY AUDIX System R1.0, 555-300-509.
Issue 3 March 1996
1-15
Introduction
Automated Attendant
1. Restrict menu options to internal extensions only, by Outward Restricting
the automated attendant ports
2. Restrict calls that transfer off-premises to specific numbers as defined in
the Restricted Call List
3. Force disconnect or route to an attendant any menu option that is not valid
NOTE:
The above values may differ in different switches. Always try to use the
maximum value for the feature as defined by the switch documentation.
This list is to provide ideas in preventing fraud and does not list all possible
ways fraud may occur. AT&T does not guarantee that the list above will stop
all fraud.
Call Forwarding
Use the list call-forwarding command, available with G3V4 and later releases,
to identify unauthorized Call Forwarding feature activation. The command can be
used to list: all stations with Call Forwarding Active; a subset of stations with Call
Forwarding active; or the Call Forwarding status of a specified station.
The list identifies stations with either Call Forwarding All Calls (on-net or off-net)
or Call Forwarding Busy/Don’t Answer active. It shows the station extension, the
station name and the forwarded-to destination.
Call Vectoring
Call vectoring allows processing of incoming and internal calls according to a
programmed set of commands. Vector commands can direct calls to
on-premises or off-premises destinations, to a hunt group or split, or to a specific
call treatment such as an announcement, forced disconnect or delay treatment.
It is possible for the system to collect digits from the user and route calls to a
destination specified by those digits, and/or do conditional processing
according to the digits dialed (Call Prompting feature).
Calls access vectors using Vector Directory Numbers (VDNs). A VDN is a ‘‘soft’’
switch extension not assigned to a physical equipment location but having many
of the properties of a normal extension number, including a Class Of Restriction
(COR). The VDN, when dialed (or inferred), routes calls to the vector. Calls
processed by the vector carry the permissions and restrictions associated with
the COR of the Vector Directory Number.
Putting this all together, if a vector in the switch is written to collect digits, and
then to route to the digits dialed, the restrictions on what calls can be placed are
determined by the COR of the VDN. An incoming caller can access Trunk
Access Codes, some Feature Access Codes, or most other sets of dialed digits.
1-16
Issue 3 March 1996
Security Measures
In order to deny incoming callers access to outgoing facility paths, the COR of
the Vector Directory Number must be configured to disallow outgoing access.
This should include; lowering the Facility Restriction Level in the COR to the
lowest acceptable value (FRL=0 provides the most restricted access to network
routing preferences), assigning a Calling Party Restriction of ‘‘Toll’’ or ‘‘Outward’’,
denying Facility Test Call capability, and blocking access to specific COR’s
assigned to outgoing Trunk Groups using the Calling Permissions section of the
Class Of Restriction Screen.
Action
Review the Classes of Restriction assigned to your VDNs. If they are not
restricted, consider assigning restrictions on the VDN to prevent callers exiting
the system via the vector. For assistance, please contact the DEFINITY Helpline
at 800 225-7585.
Enhanced Call Transfer
When using AUDIX, DEFINITY AUDIX, or Intuity, remember to activate the
Enhanced Call Transfer (ECT) feature as part of your security plan. While this
powerful feature limits transfers to valid extensions, there are some extension
numbers that should NOT be made available to AUDIX transfers.
ECT allows callers to transfer out of AUDIX to valid extension numbers (as
determined by the switch’s Dial Plan.) However, there are certain extension
numbers, within the Dial Plan, that provide capabilities AUDIX transfers should
be denied access to. Examples would include extension numbers used to
dial-access system administration capabilities within the switch or extension
numbers that are associated with features that provide second dial tone (Remote
Access Extension).
To block AUDIX access to these extension numbers, they should be placed in
special Class(es) of Restriction (COR). Using COR-To-COR calling permissions,
the COR of the AUDIX analog ports should be denied access to the CORs
containing these special extension numbers. To do this, access the Change Class Of Restriction screen for the COR assigned to the analog ports that
connect to AUDIX.
NOTE:
AUDIX ports should always reside in a separate COR designed specifically
for them. In the COR-To-COR permissions area at the bottom of the screen,
enter ‘‘no’’ in each COR field corresponding to the CORs assigned to the
extensions you want protected.
Issue 3 March 1996
1-17
Introduction
Action
Review the Classes of Restriction assigned to your AUDIX analog ports and your
Remote Access/Netcon (G3vs, G3s, G3i) or system port (G3r) data extensions. If
they are not restricted, consider assigning restrictions that would prevent callers
in AUDIX from being transferred to these extensions. For assistance, please
contact the DEFINITY Helpline at 800 225-7585.
Remote Access
1. Use maximum Barrier Code Length (7)
G3V3 and later releases provide a 7-digit barrier code with Remote
Access Barrier Code Aging. Remote Access Barrier Code Aging limits the
length of time a barrier code remains valid, and/or the number of times a
barrier code can be used. The ability to define the life span and number of
times a barrier code can be used reduces the opportunity for
unauthorized use of the Remote Access feature.
2. Activate Authorization Code Required (Y)
3. Assign each barrier code a COR and COS that allow only necessary calls
4. Assign an ap propriate Facility Restriction Level (FRL) and other
restrictions for each COR (outward, toll, etc.)
5. Use maximum Authorization Code Length (7)
6. If providing attendant coverage, activate Timeout To Attendant (Y)
7. Change or remove authorization codes when authorized users leave the
company
8. If Time of Day Routing is provided, raise the FRLs on route patterns during
hours that remote access should not be used.
9. Suppress dial tone in the Remote Access Dial Tone field (Y)
10. If Remote Access is not going to be used, permanently disable the
Remote Access feature. This feature is available on RV3, G1, and G3 V1.1
and higher.
Use the status remote-access command in G3V4 to check the status of the
remote access feature and barrier codes. The command displays information
that can help in determining why and when use of the remote access feature or a
particular barrier code was denied.
If Remote Access is not permanently disabled, but is not administered, set Logoff
Notification, available with G3V4 and later releases, to notify the system
administrator at logoff when the Remote Access feature is enabled. Logoff
Notification is administrable on a login ID basis.
For a detailed description of the status remote-access command and Logoff
Notification, see the GBCS Products Security Handbook, 555-025-600.
1-18
Issue 3 March 1996
Security Measures
Other Features Requiring Security Precautions
Follow the specific security measures recommended in this chapter when
administering the following features:
— AUDIX Interface
— Call Vectoring
— Facility Test Calls
— Remote Access
— Remote Administration
— Transfer - Trunk to Trunk
— Terminal Translation Initialization
(See the index under ‘‘Security Measures’’ for the specific page numbers where
the security measures are described for each of these features.)
Consult the GBCS Products Security Handbook, 555-025-600, for additional
steps to secure your system and to find out how to regularly obtain information
concerning security developments.
Issue 3 March 1996
1-19
Introduction
Organization of Features
The next few chapters describe the DEFINITY switch features, functions, and
services. Chapter 2 presents these capabilities classified into six categories:
■
Voice Management Overview
■
Data Management
■
Network Services (including World Class Routing)
■
System Management
■
Hospitality Services
■
Call Center Services
NOTE:
It is useful to consider the features and functions from the perspective of
the following functional views: System View, Call Center View, PBX-to-Host
View, Voice Processing View, Network View (including World Class
Routing), System Management View, Desktop View, Hospitality View, and
Support View. Some features and functions support several of these views,
so the views should not be seen as discrete categories for listing features
and functions. For a description of the system organized from a functional
perspective, see An Introduction to DEFINITY Communications System
Generic 3, 555-230-020.
Organization of Each Feature Section
In Chapter 3 the features are arranged in alphabetical order. The information for
each feature is generally presented under six headings with some differences
among the sections:
■
Feature Availability
Defines in which release(s) the feature is available. (Also see the table
later in this chapter for a listing of the G3 feature set.)
■
Description
Defines the feature, tells what it does for the user, or how it serves the
system, and briefly describes how it is used.
■
Considerations
Discusses the applications and benefits of the feature, followed by the
feature parameters and any other factors to be considered when the
feature is used.
■
Interactions
Lists and briefly discusses other features that may significantly affect the
feature being described. Interacting features are those that:
1-20
Issue 3 March 1996
Organization of Features
— Depend on each other — one of the features must be provided if
the other one is.
— Cannot coexist — one of the features cannot be provided if the
other one is.
— Affect each other — the normal operation of one feature modifies,
or is modified by, the normal operation of the other feature.
— Enhance each other — the features, in combination, provide
improved service to the user.
■
Administration
States whether or not administration is required, how the feature is
administered, who administers the feature, and lists items requiring
administration. See the DEFINITY Communications System Generic 3
Version 4 Implementation, 555-230-655, for details.
■
Hardware and Software Requirements
Lists any additional hardware and/or software requirements needed for
the feature.
Table 1-6 provides a complete list of the Generic G3 features and, for each
feature, indicates whether the feature is standard (always part of the offering) or
optional (can be purchased separately) with the Advantage Business Package,
the Premier Business Package, Generic G3i, and Generic G3r.
The following notations indicate feature availability:
LEGEND:
S
Standard
O
Optional
N/A
Not Available
V2
Only available with G3V1.1, G3V2 and later releases. Not
available with G3V1. Please note that feature availability
between G3V1.1 is somewhat different. Any feature identified
as V2 is NOT available with G3V1.1 except as an upgrade.
GD
Available with G3i-Global and G3iV2 (and later releases). Not
available with G3iV1.
V3
Only available with G3V3 and later releases.
V4
Only available with G3V4 and later releases.
NOTE:
Customers outside of North America should refer to the column marked
G3vs PBP for feature availability.
Standard features may require ad ditional hardware.
Issue 3 March 1996
1-21
Introduction
Table 1-6.
Feature Availability
Feature
G3vs ABP
G3vs PBP
G3s ABP
G3s PBP
G3i
G3r
AAR/ARS Partitioning
S
S
S
S
S
S
AAR/ARS Digit Conversion
O
O
O
O
S
S
Abandoned Call Search
S
S
S
S
S
S
Abbreviated Dialing
S1
S2
S2
S2
S2
S2
Abbreviated Dialing (Enhanced)
N/A
O
N/A
O
O
O
Add/Remove Skills
V3
V3
V3
V3
V3
V3
Administrable Language Displays
V2
V2
V2
V2
GD
V2
Administrable Logins
V3
V3
V3
V3
V3
V3
Administered Connections
N/A
S
N/A
S
S
S
Administration Without Hardware
S
S
S
S
S
S
Advice of Charge
V4
V4
V4
V4
V4
V4
Agent Call Handling
O3
O4
O3
O4
O4
O4
Agent Sizing
V3
V3
V3
V3
V3
V3
Alphanumeric Dialing
S
S
S
S
S
S
Alternate Facility Restriction Levels
V2
V2
V2
V2
V2
O
Answer Detection by Call Classifier
N/A
O
N/A
O
O
S
Attendant Auto-Manual Splitting
S
S
S
S
S
S
Attendant Call Waiting
S
S
S
S
S
S
Attendant Control of Trunk Group Access
S
S
S
S
S
S
Attendant Direct Extension Selection With
Busy Lamp Field
S
S
S
S
S
S
Attendant Direct Trunk Group Selection
S
S
S
S
S
S
Attendant Display
S
S
S
S
S
S
Attendant Intrusion (Call Offer)
V2
V2
V2
V2
GD
S
Attendant Override of Diversion Features
V2
V2
V2
V2
GD
S
Attendant Priority Queue
V2
V2
V2
V2
GD
S
Attendant Recall
S
S
S
S
S
S
Attendant Release Loop Operation
S
S
S
S
S
S
1.
2.
3.
4.
Abbreviated Dialing is a standard feature; however, Enhanced Abbreviated Dialing is not available
with the Advantage Business Package.
Abbreviated Dialing is a standard feature; however, Enhanced Abbreviated Dialing is a Premier
Business Package, G3i, and G3r option.
Available when the Basic Call Center Option is active.
Available when ACD software is active.
1-22
Issue 3 March 1996
Organization of Features
Table 1-6.
Feature Availability — Continued
Feature
G3vs ABP
G3vs PBP
G3s ABP
G3s PBP
G3i
G3r
Attendant Room Status
V3
V3
V3
V3
V3
V3
Attendant Serial Calling
V2
V2
V2
V2
GD
V2
Audible Message Waiting
V2
V2
V2
V2
V2
S
Audio Information Exchange
(AUDIX) Interface
S
S
S
S
S
S
Authorization Codes
O
O
O
O
O
O
Automatic Alternate Routing (AAR)
N/A
O1
N/A
O1
O1
O1
Automatic Callback
S
S
S
S
S
S
Automatic Call Distribution (ACD)
O2
O
O2
O
O
O
ACD Auto-Available Split (AAS)
V2
V2
V2
V2
V2
S
Automatic Circuit Assurance
S
S
S
S
S
S
Automatic Hold
V2
V2
V2
V2
GD
S
Automatic Incoming Call Display
S
S
S
S
S
S
Automatic Route Selection (ARS)
O
O
O
O
O
O
Automatic Transmission
Measurement System
V21
V21
V21
V21
V21
S
Automatic Wakeup
S
S
S
S
S
S
Auto-Start/Don’t Split
V2
V2
V2
V2
GD
V2
Basic Call Management System
(BCMS)
O2
O
O2
O
O
O
Bridged Call Appearance —
Multi-Appearance Voice Terminal
S
S
S
S
S
S
Bridged Call Appearance —
Single-Line Voice Terminal
S
S
S
S
S
S
Busy Verification of Terminals and
Trunks
S
S
S
S
S
S
1.
2.
Available with Private Network Access (PNA) software.
Available with the Basic Call Center Option.
Issue 3 March 1996
1-23
Introduction
.
Table 1-6.
Feature Availability — Continued
Feature
G3vs ABP
G3vs PBP
G3s ABP
G3s PBP
G3i
G3r
Call-By-Call Service Selection
N/A
O1
N/A
O1
01
01
Call Coverage
S2
S
S2
S
S
S
Call Detail Recording (CDR)
S
S
S
S
S
S
Call Forwarding All Calls
S
S
S
S
S
S
Call Forward Busy/Don’t Answer
V4
V4
V4
V4
V4
V4
Call Management System (CMS)
O3
O3
O3
O3
O3
O3
Call Park
S
S
S
S
S
S
Call Pickup
S
S
S
S
S
S
Call Prompting
N/A
O
N/A
O
O
O
Call Vectoring
N/A
O
N/A
O
O
O
CallVisor Adjunct/Switch Application
Interface (ASAI)
N/A
N/A
N/A
O
O
O
Call Waiting Termination
S
S
S
S
S
S
Centralized Attendant Service (CAS)
N/A
O
N/A
O
O
O
Class of Restriction (COR)
S
S
S
S
S
S
Class of Service (COS)
S
S
S
S
S
S
CDR Account Code Dialing
S
S
S
S
S
S
Code Calling Access
S
S
S
S
S
S
Conference — Attendant
S
S
S
S
S
S
Conference — Terminal
S
S
S
S
S
S
Constellation Voice/Data Terminal
Support
V3
V3
V3
V3
V3
V3
Consult
S
S
S
S
S
S
Coverage Callback
S
S
S
S
S
S
Coverage Incoming Call Identification
(ICI)
S
S
S
S
S
S
Customer-Provided Equipment (CPE)
Alarm
S
S
S
S
S
S
1.
2.
3.
Available as an option when ISDN-PRI software is purchased for public and private networking.
Linked Call Coverage Paths are not standard. However, Linked Call Coverage Paths are available
as part of the Voice Mail Application Support Option package.
CMS is optionally available as an adjunct.
1-24
Issue 3 March 1996
Organization of Features
Table 1-6.
Feature Availability — Continued
Feature
G3vs ABP
G3vs PBP
G3s ABP
G3s PBP
G3i
G3r
Data Call Setup
S
S
S
S
S
S
Data Hot Line
S
S
S
S
S
S
Data-Only Off-Premises Extensions
S
S
S
S
S
S
Data Privacy
S
S
S
S
S
S
Data Restriction
S
S
S
S
S
S
DCS Alphanumeric Display for
Terminals
N/A
O1
N/A
O1
O1
O1
DCS Attendant Control of Trunk
Group Access
N/A
O2
N/A
O2
O2
O2
DCS Attendant Direct Trunk Group
Selection
N/A
O2
N/A
O2
O2
O2
DCS Attendant Display
N/A
O2
N/A
O1
N/A
O1
DCS Automatic Callback
N/A
O2
N/A
O1
O1
O1
DCS Automatic Circuit Assurance
(ACA)
N/A
O1
N/A
O1
O1
O1
DCS Busy Verification of Terminals
and Trunks
N/A
O2
N/A
O2
O2
O2
DCS Call Coverage
N/A
V4/O3
N/A
V4/O3
V4/O3
V4/O3
DCS Call Forwarding All Calls
N/A
O1
N/A
O1
O1
O1
DCS Call Waiting
N/A
O1
N/A
O1
O1
O1
DCS Distinctive Ringing
N/A
O1
N/A
O1
O1
O1
DCS Leave Word Calling
N/A
O1
N/A
O1
O1
O1
DCS Multi-Appearance
Conference/Transfer
N/A
O1
N/A
O1
O1
O1
1.
2.
3.
Available when DCS software is purchased.
Available when DCS is purchased, but not available with DCS over PRI D-Channel when the PRI
D-Channel is connected to the public network.
Optional feature with DCS.
Issue 3 March 1996
1-25
Introduction
Table 1-6.
Feature Availability — Continued
Feature
G3vs ABP
G3vs PBP
G3s ABP
G3s PBP
G3i
G3r
DCS Over ISDN-PRI D-Channel
N/A
O1
N/A
O1
O1
O1
DCS Trunk Group Busy/Warning
Indication
N/A
O1
N/A
O1
O1
O1
Default Dialing
S
S
S
S
S
S
Dial Access to Attendant
S
S
S
S
S
S
Dial Plan
S
S
S
S
S
S
Digital Multiplexed Interface
S
S
S
S
S
S
Direct Department Calling (DDC) and
Uniform Call Distribution (UCD)
S
S
S
S
S
S
Direct Inward Dialing (DID)
S
S
S
S
S
S
Direct Inward and Outward Dialing
(DIOD) — International
S
S
S
S
S
S
Direct Outward Dialing (DOD)
S
S
S
S
S
S
Distinctive Ringing
S
S
S
S
S
S
Do Not Disturb
S
S
S
S
S
S
DS1 Trunk Service
S
S
S
S
S
S
E1 Trunk Service
V2
V2
V2
V2
GD
V2
EIA Interface
S
S
S
S
S
S
Emergency Access to the Attendant
S
S
S
S
S
S
Enhanced DCS (EDCS)
V2
V2
V2
V2
GD
V2
End-to-End Signaling
V2
V2
V2
V2
GD
V2
Expert Agent Selection
N/A
V2†
N/A
V2†
V2†
V2†
Extension Number Portability
V2
V2
V2
V2
V2
S
Extended Trunk Access
V2
V2
V2
V2
V2
S
1.
Available when DCS software is purchased.
1-26
Issue 3 March 1996
Organization of Features
Table 1-6.
Feature Availability — Continued
Feature
G3vs ABP
G3vs
PBP
Facility and Non-Facility Associated
Signaling
N/A
O
Facility Busy Indication
S
Facility Restriction Levels (FRLs)
1
G3s ABP
G3s PBP
1
G3i
G3r
O1
N/A
O
S
S
S
S
S
S
S
S
S
S
S
Facility Test Calls
S
S
S
S
S
S
Flexible Billing
V4/O
V4/O
V4/O
V4/O
V4/O
V4/O
Forced Entry of Account Codes
N/A
O
N/A
O
O
O
Forced Password Aging
V3
V3
V3
V3
V3
V3
Generalized Route Selection
N/A
O1
N/A
O1
O1
O1
Go to Cover
S
S
S
S
S
S
Hold
S
S
S
S
S
S
Hold—Automatic
V2
V2
V2
V2
GD
S
Hot Line Service
S
S
S
S
S
S
Hunting
S
S
S
S
S
S
Inbound Call Management
N/A
O
N/A
O
O
O
Individual Attendant Access
S
S
S
S
S
S
Information System Network (ISN)
Interface
S
S
S
S
S
S
Integrated Directory
S
S
S
S
S
S
Integrated Services Digital Network
— Basic Rate Interface
N/A
N/A
S
S
S
S
Integrated Services Digital Network
— Primary Rate Interface
N/A
O
N/A
O
O
O
Intercept Treatment
S
S
S
S
S
S
Intercom — Automatic
S
S
S
S
S
S
Intercom — Dial
S
S
S
S
S
S
Internal Automatic Answer
S
S
S
S
S
V2
Inter-PBX Attendant Calls
S
S
Intraflow and Interflow
O2
O
Last Number Dialed
S
S
1.
2.
3.
S
3
O
S
S
2
O
S
O
1
S
3
O
S
3
S
O3
S
Available when ISDN-PRI software is purchased for public and private networking.
Available when the Basic Call Center Option is purchased.
Available when ACD software is purchased.
Issue 3 March 1996
1-27
Introduction
Table 1-6.
Feature Availability — Continued
Feature
G3vs ABP
Leave Word Calling
O
Line Lockout
1
G3vs PBP
G3s ABP
1
G3s PBP
G3i
G3r
S
S
S
S
O
S
S
S
S
S
S
Look Ahead Interflow
N/A
O
N/A
O
O
O
Loudspeaker Paging Access
S
S
S
S
S
S
Loudspeaker Paging Access — Deluxe
S
S
S
S
S
S
Malicious Call Trace
V2
V2
V2
V2
V2
S
Manual Message Waiting
S
S
S
S
S
S
Manual Originating Line Service
S
S
S
S
S
S
Manual Signaling
S
S
S
S
S:S
MERLIN./System 25 — Voice Terminal
Support (731xH Series)
S
S
S
S
S
V2
Modem Pooling
S
S
S
S
S
S
Move Agents from CMS
O2
O2
O2
O2
O2
O2
Multi-Appearance Preselection and
Preference
S
S
S
S
S
S
Multiple Call Handling
V3/O
V3/O
V3/O
V3/O
V3/O
V3/O
Multiple Listed Directory Numbers
S
S
S
S
S
S
Music-on-Hold Access
S
S
S
S
S
S
Names Registration
S
S
S
S
S
S
Network Access — Private
S
S
S
S
S
S
Network Access — Public
S
S
S
S
S
S
Night Service — Hunt Group
S
S
S
S
S
S
Night Service — Night Console Service
S
S
S
S
S
S
Night Service — Night Station Service
S
S
S
S
S
S
Night Service — Trunk Answer from Any
Station
S
S
S
S
S
S
1.
2.
Available when the Voice Mail Application Support Option is purchased.
CMS is optionally available as an adjunct. Move Agents from CMS is only available if CMS is
selected.
1-28
Issue 3 March 1996
Organization of Features
Table 1-6.
Feature Availability — Continued
Feature
G3vs ABP
G3vs PBP
G3s ABP
G3s PBP
G3i
G3r
Night Service — Trunk Group
S
S
S
S
S
S
Off-Premises Station
S
S
S
S
S
S
PC Application Software Translation
Exchange (PASTE)
V4
V4
V4
V4
V4
V4
PC Interface
S
S
S
S
S
S
PC/PBX Connection
S
S
S
S
S
S
Personal Central Office Line (PCOL)
S
S
S
S
S
S
Personalized Ringing
S
S
S
S
S
S
Power Failure Transfer
S
S
S
S
S
S
Priority Calling
S
S
S
S
S
S
Privacy — Attendant Lockout
S
S
S
S
S
S
Privacy — Manual Exclusion
S
S
S
S
S
S
Property Management System Interface
S
S
S
S
S
S
Pull Transfer
V2
V2
V2
V2
GD
V2
QSIG Global Networking
V2
V2
V2
V2
V2
V2
Queue Status Indications
S
S
S
S
S
S
Recall Signaling
S
S
S
S
S
S
Recent Change History
S
S
S
S
S
S
Recorded Announcement
S
S
S
S
S
S
Recorded Telephone Dictation Access
S
S
S
S
S
S
Redirection On No Answer (RONA)
V2
V2
V2
V2
V2
V2
Remote Access
S
S
S
S
S
S
Report Scheduler and System Printer
S
S
S
S
S
S
Restriction — Controlled
S
S
S
S
S
S
Restriction — Fully Restricted Service
V2
V2
V2
V2
GD
S
Restriction — Miscellaneous Terminal
S
S
S
S
S
S
Restriction — Miscellaneous Trunk
S
S
S
S
S
S
Issue 3 March 1996
1-29
Introduction
Table 1-6.
Feature Availability — Continued
Feature
G3vs ABP
G3vs PBP
G3s ABP
G3s PBP
G3i
G3r
Restriction — Toll
S
S
S
S
S
S
Restriction — Voice Terminal — Inward
S
S
S
S
S
S
Restriction — Voice Terminal — Manual
Terminating Line
S
S
S
S
S
S
Restriction — Voice Terminal —
Origination
S
S
S
S
S
S
Restriction — Voice Terminal —
Outward
S
S
S
S
S
S
Restriction — Voice Terminal — Public
V2
V2
V2
V2
GD
V2
Restriction — Voice Terminal —
Termination
S
S
S
S
S
S
Ringback Queuing
S
S
S
S
S
S
Ringer Cutoff
S
S
S
S
S
S
Ringing — Abbreviated and Delayed
V4
V4
V4
V4
V4
V4
Rotary Dialing
S
S
S
S
S
S
R2-MFC
V2
V2
V2
V2
GD
V2
Security Violation Notification (SVN)
S
S
S
S
S
S
Send All Calls
S
S
S
S
S
S
Senderized Operation
S
S
S
S
S
S
Service Observing
S
S
S
S
S
S
Single-Digit Dialing and Mixed Station
Numbering
S
S
S
S
S
S
Straightforward Outward Completion
S
S
S
S
S
S
Subnet Trunking
S
S
S
S
S
S
Switch Based Bulletin Board
V3
V3
V3
V3
V3
V3
S
S
S
System Measurements
O
System Status Report
1
1
S
O
S
S
S
S
S
S
Temporary Bridged Appearance
S
S
S
S
S
S
Tenant Partitioning
V4/O
V4/O
V4/O
V4/O
V4/O
V4/O
Terminal Translation Initiation
V2
V2
V2
V2
V2
S
Terminating Extension Group
S
S
S
S
S
S
1.
Available when the System Measurements Option package or the Basic Call Center Option
package is purchased.
1-30
Issue 3 March 1996
Organization of Features
Table 1-6.
Feature Availability — Continued
Feature
G3vs ABP
G3vs PBP
G3s ABP
G3s PBP
G3i
G3r
Through Dialing
S
S
S
S
S
S
Time of Day Routing
O1
O1
O1
O1
O1
O1
Timed Reminder and Attendant
Timers
S2
S2
S2
S2
S2
S2
Touch-Tone Dialing
S
S
S
S
S
S
Transfer
S
S
S
S
S
S
Transfer Outgoing Trunk to Outgoing
Trunk
V23
V2
V23
V2
V2
S
Traveling Class Marks (TCMs)
N/A
O
N/A
O
0
0
Trunk Flash
S
S
S
S
S
S
Trunk Group Busy/Warning Indicators
to Attendant
S
S
S
S
S
S
Trunk Identification By Attendant
S
S
S
S
S
S
Trunk-to-Trunk Transfer
S
S
S
S
S
S
Uniform Dial Plan (UDP)
N/A
O
N/A
O
O
O
Unrestricted Uniform Dial Plan (UDP)
NA
V2
NA
V2
V2
VDN of Origin Announcements
V3
V3
V3
V3
V3
V3
Visually Impaired Attendant Services
(VIAS)
V2
V2
V2
V2
GD
V2
Voice Message Retrieval
S
S
S
S
S
S
Voice Response Integration
V2†
V2†
V2†
V2†
V2†
V2†
Voice Terminal Alerting Options
V2
V2
V2
V2
V2
V2
Voice Terminal Display
S
S
S
S
S
S
VuStats
V3
V3
V3
V3
V3
V3
Wideband Switching
V2†
V2†
V2†
V2†
V2†
V2†
World Class Core BRI
V4
V4
V4
V4
V4
V4
World Class Tone Detection
V2
V2
V2
V2
GD
V2
World Class Tone Generation
V2
V2
V2
V2
GD
V2
1.
2.
3.
Available with ARS or Private Network Access (PNA) software.
Timed Reminder and Attendant Timers held call timer transfer to ‘‘aatd.’’ Standard in
G3vs/G3sABP, G3vs/G3sPBP, G3i, and G3r.
Transfer Outgoing Trunk to Outgoing Trunk is not available with G3vs/G3s ABP.
Issue 3 March 1996
1-31
Functional Description
2
Overview
This chapter describes the DEFINITY switch features, functions, and services,
and presents these capabilities classified into six categories: Voice
Management, Data Management, Network Services (including World Class
Routing), System Management, Hospitality Services, and Call Center Services.
Each group of functions and services, including a listing of associated features,
is described separately in a section of this chapter.
See Chapter 3 for detailed information on individual features. (The feature
descriptions in Chapter 3 are arranged in alphabetical order.)
NOTE:
It is useful to consider the features and functions from the perspective of
the following functional views: System View, Call Center View, PBX-to-Host
View, Voice Processing View, Network View (including World Class
Routing), System Management View, Desktop View, Hospitality View, and
Support View. Some features and functions support several of these views,
so the views should not be seen as discrete categories for listing features
and functions. For a description of the system organized from a functional
perspective, see An Introduction to DEFINITY. Communications System
Generic 3, 555-230-020.
Issue 3 March 1996
2-1
Functional Description
Voice Management Overview
The Voice Management features try to meet the individual communications
needs of everyone in the system. As the individual needs change, the assigned
features can also be changed. The Voice Management features provide many
important services with benefits such as saving time and making calling more
convenient.
Voice Management Features
The following features are associated with Voice Management:
2-2
■
Abbreviated Dialing
■
Alternate Facilities Restriction Levels
■
Attendant Auto-Manual Splitting
■
Attendant Call Waiting
■
Attendant Control of Trunk Group Access
■
Attendant Direct Extension Selection With Busy Lamp Field
■
Attendant Direct Trunk Group Selection
■
Attendant Display
■
Attendant Intrusion (Call Offer)
■
Attendant Override
■
Attendant Priority Queue
■
Attendant Recall
■
Attendant Release Loop Operation
■
Attendant Serial Calling
■
Audio Information Exchange (AUDIX) Interface
■
Audible Message Waiting
■
ACD - Auto-Available Split
■
Auto-Start/Don’t Split
■
Automatic Callback
■
Automatic Incoming Call Display
■
Automatic Transmission Measurement System (ATMS)
■
Authorization Codes
■
Automatic Callback
■
Automatic Incoming Call Display
■
Brid ged Call Ap pearance — Multi-Ap pearance Voice Terminal
Issue 3 March 1996
Voice Management Overview
■
Brid ged Call Ap pearance — Single-Line Voice Terminal
■
Busy Verification of Terminals and Trunks
■
Call By Call Service Selection
■
Call Coverage
■
Call Forwarding All Calls
■
Call Forward Busy/Don’t Answer
■
Call Park
■
Call Pickup
■
Call Waiting Termination
■
CDR Account Code Dialing
■
Centralized Attendant Service
■
Class of Restriction
■
Class of Service
■
Code Calling Access
■
Conference — Attendant
■
Conference — Terminal
■
Consult
■
Coverage Callback
■
Coverage Incoming Call Identification
■
Dial Access to Attendant
■
Dial Plan
■
Direct Department Calling and Uniform Call Distribution
■
Direct Inward Dialing
■
Direct Outward Dialing
■
Distinctive Ringing
■
Emergency Access to the Attendant
■
Facility Busy Indication
■
Go To Cover
■
Hold
■
Hold - Automatic
■
Hot Line Service
■
Hunting
■
Individual Attendant Access
Issue 3 March 1996
2-3
Functional Description
2-4
■
Integrated Directory
■
Integrated Services Digital Network — Basic Rate Interface (ISDN-BRI)
■
Intercept Treatment
■
Intercom — Automatic
■
Intercom — Dial
■
Internal Automatic Answer (G3i)
■
Inter-PBX Attendant Calls
■
Last Number Dialed
■
Leave Word Calling
■
Line Lockout
■
Loudspeaker Paging Access
■
Loudspeaker Paging Access — Deluxe
■
Manual Message Waiting
■
Manual Originating Line Service
■
Manual Signaling
■
MERLIN/System 25 Voice Terminal Support — 731xH Series
■
Misoperation Handling
■
Multi-Appearance Preselection and Preference
■
Multiple Listed Directory Numbers
■
Multiple Music-on-Hold
■
Music-on-Hold Access
■
Night Service — Hunt Group
■
Night Service — Night Console Service
■
Night Service — Night Station Service
■
Night Service — Trunk Answer From Any Station
■
Night Service — Trunk Group
■
Personal Central Office Line
■
Personalized Ringing
■
Power Failure Transfer
■
Priority Calling
■
Privacy — Attendant Lockout
■
Privacy — Manual Exclusion
■
Recall Signaling
Issue 3 March 1996
Voice Management Overview
■
Recorded Announcement
■
Recorded Telephone Dictation Access
■
Remote Access
■
Restriction — Controlled
■
Restriction — Fully Restricted Service
■
Restriction — Miscellaneous Terminal
■
Restriction — Miscellaneous Trunk
■
Restriction — Toll
■
Restriction — Toll/Code
■
Restriction — Voice Terminal — Inward
■
Restriction — Voice Terminal — Manual Terminating Line
■
Restriction — Voice Terminal — Origination
■
Restriction — Voice Terminal — Outward
■
Restriction — Voice Terminal — Termination
■
Ringback Queuing
■
Ringer Cutoff
■
Ringing Abbreviated and Delayed
■
Rotary Dialing
■
Send All Calls
■
Senderized Operation
■
Single-Digit Dialing and Mixed Station Numbering
■
Straightforward Outward Completion
■
Temporary Bridged Appearance
■
Tenant Partitioning
■
Terminal Translation Initialization
■
Terminating Extension Group
■
Through Dialing
■
Timed Reminder
■
Touch-Tone Dialing
■
Transfer
■
Transfer - Outgoing Trunk to Outgoing Trunk Trunk Flash
■
Trunk Group Busy/Warning Indicators to Attendant
■
Trunk Identification by Attendant
Issue 3 March 1996
2-5
Functional Description
■
Trunk-to-Trunk Transfer
■
Voice Message Retrieval
■
Voice Terminal Display
■
Voice Terminal Alerting Options
Specific Attendant Features are listed below.
2-6
■
DCS Attendant Control of Trunk Group Ac cess
■
DCS Attendant Display
■
DCS Attendant Direct Trunk Group Selection
■
Attendant Auto-Manual Splitting
■
Attendant Control of Trunk Group Access
■
Attendant Call Waiting
■
Attendant Direct Extension Selection With Busy Lamp Field
■
Attendant Direct Trunk Group Selection
■
Attendant Intrusion (Call Offer)
■
Attendant Override of Diversion Features
■
Attendant Priority Queue
■
Attendant Recall
■
Attendant Release Loop Operation
■
Attendant Serial Calling
■
Attendant Display
■
Conference — Attendant
■
Centralized Attendant Service (CAS)
■
Dial Access to Attendant
■
Emergency Access to the Attendant
■
Individual Attendant Access
■
Inter-PBX Attendant Calls
■
Privacy — Attendant Lockout
■
Trunk Group Busy/Warning Indicators to Attendant
■
Trunk Identification By Attendant
■
Timed Reminder and Attendant Timers
■
Visually Impaired Attendant Service (VIAS)
Issue 3 March 1996
Data Management
Data Management
The DEFINITY switch is a private digital switching system that permits
connections with a variety of data equipment. Data terminals, printers, graphics,
facsimile equipment, and computers can be connected to the switch through
various protocols or interfaces. The physical connection can be through a digital
data module, analog modem, or access endpoint.
For use outside the United States, modems that comply with the ITU-T 108.1
signaling procedures are supported. Administration forms are available to
support combined (external) modem pools.
The system provides the ability to option data modules [or data-like devices such
as a Data Line Circuit (DLC)] for Terminal Dialing. Also, data modules can be
used without Terminal Dialing with host computers, printers, or other such
applications. Computer file transfer at a rate of 64 kbps is possible with the
Modular Processor Data Module (MPDM) and the Modular Trunk Data Module
(MTDM).
The family of data modules includes a Wideband Data Module (WDM), Processor
Data Module (PDM), a Digital Terminal Data Module (DTDM), a Trunk Data
Module (TDM), a Z702AL1-DSU Data Module Base, a 7400A Data Module, a
7500B Data Module, an ISDN Asynchronous Data Module (ADM), and a 3270
Data Module. The data modules are generally more versatile than modems,
operate at faster data rates, and provide additional features.
The WDM provides Wideband (128 kbps plus any multiple of 64 kbps, up to a
total of 1984 kbps) communications between a Wideband data and dialing
interfaces and an ISDN PRI interface. WDM provides for extremely high-speed
data transmission and is used by applications ranging from video conferencing
to data backup.
The DTDM provides synchronous or asynchronous data communications to
7403D and 7405D digital voice terminal users who have a terminal or personal
computer. The DTDM and voice terminal integrate data and voice into the Digital
Communications Protocol (DCP) to the digital switch.
The Z702AL1-DSU Data Module Base provides the Data Communications
Equipment (DCE) interface connection for a 7407D voice terminal to data
terminals. The module provides full-duplex asynchronous operation only. The
module and 7407D voice terminal integrate data and voice into the DCP to the
digital switch.
The MTDM provides an EIA RS-232D Data Terminal Equipment (DTE) interface
for connection to off-premises (out of building) private-line trunk facilities, or a
switched telecommunications network, and a DCP interface for connection to the
digital switch. The MTDM may also serve as part of a conversion resource for
modem pooling. The MTDM is also used to interface with DCE-type multiplexers.
Issue 3 March 1996
2-7
Functional Description
The MPDM provides a DCE asynchronous or synchronous interface for
connection to data terminals, Call Detail Recording (CDR) output devices,
DEFINITY Communications System Generic 3 Management Terminals (G3-MT),
Generic 3 Management Application Systems (G3-MA), on-premises (in building)
administration terminals, and host computers. The MPDM can be preset in the
factory to provide the following interfaces: EIA RS-232C, RS-449, V.35, and
RS-366 to support Automatic Calling Unit (ACU) type dialing. The MPDM can be
configured to support the Data Call Setup or Off-Premises Data-Only Extension
feature. The MPDM also supports data rates of 56 and 64 kbps for downloading
and other high-speed data transfer requirements.
The 7400A Data Module may be used instead of an MTDM when supporting the
combined Modem Pooling feature. The 7400A Data Module sup ports
asynchronous operation and provides a DCP interface to the switch and an EIA
RS-232C interface to the associated modem. The 7400A Data Module also can
be used with a data terminal and supports keyboard dialing in the same manner
as the MPDM.
The 7500B Data Module is a stand-alone unit that supports asynchronous or
synchronous DCE and asynchronous DTE on the ISDN Basic Rate Interface
(BRI) switch interface (G3, DEFINITY Generic 2 (G2) and the 5ESS switch). In
asynchronous mode, the 7500B supports packet or circuit-switched data
communications, and can be controlled via the front panel or the keyboard of a
connected terminal. In synchronous mode, the 7500B supports circuit-switched
or nailed-up data communications, requires either the Multipurpose
Enhancement Board or the High-Speed Synchronous Enhancement Board, and
only can be controlled via the front panel.
When configured as an asynchronous DCE, the 7500B provides an EIA RS-232D
interface and sup ports full-duplex data transmission at rates of 300, 1200, 2400,
4800, 9600, and 19200 b ps. The following optional enhancements are available
for the 7500B in an asynchronous DCE configuration: an RS-366 ACU interface
and a second asynchronous EIA RS-232D interface. With an additional
asynchronous EIA RS-232D interface, the 7500B can simultaneously support
either two D-channel packet data calls or one D-channel packet call and one
B-channel circuit call. However, the 7500B cannot simultaneously support two
B-channel circuit-switched calls.
When configured as an asynchronous DTE, the 7500B provides an EIA RS-232D
interface and supports full-duplex data transmission at rates of up to 19200 bps.
This configuration is most commonly used for modem pooling applications.
In order to be configured as a synchronous DCE, the 7500B must have either the
Multipurpose Enhancement Board or the High-Speed Synchronous
Enhancement Board. With the Multipurpose Board, the 7500B provides an EIA
RS-232D interface and an RS-366 ACU interface, and supports full-duplex data
transmission at rates of 1200, 2400, 4800, 9600, 19200, 56000, and 64000 bps.
The 7500B also supports half-duplex emulation at rates of 1200, 2400, 4800,
9600, 19200, and 56000 bps. With the High-Speed Synchronous Enhancement
Board, the 7500B provides a V.35 interface and supports full-duplex data
2-8
Issue 3 March 1996
Data Management
transmission at rates of 48000, 56000, and 64000 bps. The 7500B only provides
half-duplex emulation at a rate of 56000 bps. Regardless of the configuration, the
7500B provides no voice functions and is not used with voice terminals.
The ISDN ADM may be used with asynchronous DTE as a data stand for
7500-series BRI voice terminals. Consisting of a board located inside the BRI
voice terminal, the ISDN ADM allows simultaneous voice and data transmissions
through one terminal. The ISDN ADM supports the standard Hayes command set
for compatibility with existing PC communications packages and provides AT&T
extensions to the standard Hayes command set to allow even greater flexibility in
future applications. PC applications that use the ISDN ADM Ap plications
Programming Interface (API) can simultaneously control, monitor, and process
both voice and data calls.
The DLC, which provides eight ports to connect user’s asynchronous EIA
RS-232D interface to DTE, can be used as an alternative to DTDM or PDM.
Data modules support the following interfaces:
■
All data modules (except the WDM, MPDM, and 3270) provide a modified
EIA RS-232D interface.
■
The WDM provides a ITU-T interface for Wideband transmissions.
■
The MPDM provides either EIA RS-232D V.35 or RS-449 interface. The
MPDM can also emulate an Automatic Call Unit (ACU) and supports the
RS-366 interface. The ACU emulation and RS-366 interface are required
for Keyboard Dialing and are discussed in the Data Call Setup feature
description.
■
The 3270 Data Module provides a Category A coaxial DCE interface for
connection to 3270-type data terminals or a cluster controller. It also
provides a DCP interface for connection to the digital switch.
The 3270 Data Module is available in the following three models:
■
3270T (Terminal) — connects to a Category A 3270-type terminal, such as
the IBM. 3278 Information Delivery System. The 3270T Data Module must
connect through the switch to a 3270C (Controller) Data Module.
■
3270A (Asynchronous) — provides the same function as the 3270T Data
Module. It also allows the 3270-type terminal to emulate a Digital
Equipment Corporation VT100 or an AT&T asynchronous terminal.
■
3270C (Controller) — connects an IBM 3274 or 3276 cluster controller to
the switch. A 3270C Data Module can contain as many as eight ports.
Trunks or channels of a DS1/E1 can also be used as non-signaling data
endpoints with the Access End points function. An access endpoint is either a
non-signaling channel on a DS1/E1 interface or a non-signaling port on an
Analog Tie Trunk circuit pack that is assigned a unique extension. Since an
access endpoint is non-signaling, it neither generates nor responds to signaling.
As a result, an access endpoint cannot be used as a trunking facility (it cannot
Issue 3 March 1996
2-9
Functional Description
receive incoming calls or route outgoing calls). An access endpoint is used
primarily to support devices, switches, or services that have a trunk interface but
do not support signaling for the trunk. An access endpoint may be designated as
the originating (local) endpoint or destination endpoint in an Administered
Connection. The status of an access endpoint can be displayed by entering the
status access-endpoint command from the G3-MT/G3-MA or a PC with a
terminal emulator.
The system supports digital-to-digital, digital-to-analog, analog-to-digital, and
analog-to-analog data calls. For data calls, the user can access the system
through these digital or analog data endpoints. Digital data endpoints are data
modules and associated data equipment, PCs, and data channels [used for
remote G3-MT terminals, and CDR]. Analog data endpoints are modems (or
acoustic coupled modems) and associated data equipment connected to the
system through analog lines or trunks. Voice-band data calls using modems can
be connected to the system through digital trunks.
The system supports DCP. This protocol provides framing, control, and signaling
for each of two information channels. Only one channel is used for voice-only or
data-only applications. Both channels are used for simultaneous voice and data
transmission. Simultaneous voice and data information can be transmitted on
calls to or from a 7403D or 7405D voice terminal with a DTDM, a 7404D with its
built-in data module, any 7400-series with an optional data module base, and
any 8400 series voice terminal with listed 7400 data module. Calls to or from
other equipment are either voice-only or data-only.
ISDN-BRI provides one 16 kbps signaling channel (D-channel) and two 64 kbps
information channels (B-channels), with a total information rate of 144 kbps. The
primary purpose of the signaling channel is to convey Q.931 message-oriented
signaling for the setup and tear down of calls carried by the B-Channels on the
BRI. Since all the signaling is done on the D-channel, both B-channels are
‘‘clear.’’ As a result, the entire widths of the B-channels are used for
simultaneously carrying voice and circuit-switched data. Voice and data
information can be simultaneously transmitted on calls to or from a 7505, 7506, or
7507 voice terminal equip ped with an optional ADM. Without the optional ADM,
the 7505, 7506, and 7507 voice terminals can handle voice-only calls.
Data Networking
Data networking connects two or more data endpoints. The system is a highly
reliable, centralized switch that provides switched access between endpoints.
Typical data communications configurations for the system are shown in Figure
2-1.
Switched access allows one terminal to connect to one of any number of
devices. Therefore, more effective use of data equipment is obtained than with
dedicated (hard-wired) links. Switched access also reduces the need for
duplicated (dedicated) equipment. Switched Ac cess systems can emulate
hardwired networks through use of the Administered Connections feature.
2-10
Issue 3 March 1996
Data Management
The system uses twisted-pair standard building wiring and eight-pin modular wall
jacks. Each wall jack is a single outlet that can handle simultaneous voice and
data information.
The digital switch, data modules, DCP, twisted-pair wiring, modular wall jacks,
and switched data features give the system its unique capabilities. These
capabilities merge the business office data processing and telecommunications
functions into a single system.
RS-232C
DATA
TERMINAL
DATA
TERMINAL
7404D WITH
BUTTON
DATA MODULE
RS-232C
DIGITAL VOICE
TERMINAL WITH
AN ATTACHED
DIGITAL
TERMINAL DATA
MODULE
513 BCT
TERMINAL
DCP
RS-232C
DCP
EIA PRINTER
PROCESSOR
DATA MODULE
RS-232C
DCP
DCP
PROCESSOR
DATA MODULE
DEFINITY
GENERIC 3
ANALOG
VOICE
TERMINAL
DCP
ANALOG
DATA MODEM
DATA
TERMINAL
RS-232C
DCP
515 BCT
TERMINAL
DCP*
HOST
COMPUTER
‡
DLC
3270-TYPE
DATA MODULE
†
ADU
COAX A
RS-232C
PROCESSOR
DATA MODULE
DATA
TERMINAL
3270-TYPE
DATA
TERMINAL
LEGEND
* DCP - DIGITAL COMMUNICATIONS PROTOCOL
‡ DLC - DATA LINE CIRCUIT
† ADU - ASYNCHRONOUS DATA UNIT
Figure 2-1.
System Data Communications Configuration
Generally, data networks are either local area networks, extended networks, or
combinations of both. The two networks and their implementation within the
system are defined as follows:
Issue 3 March 1996
2-11
Functional Description
■
Local Area Networks (LANs)
The system provides this capability by connecting communication
devices physically located within a local-area or campus-like environment.
These include conventional, semi-intelligent, and intelligent data
terminals, personal computers, host computers, and virtually any device
with the proper communications interface.
The centralized network provides circuit-switched paths using twisted-pair
building cable that extends to the endpoints. Since the business office
equipment can access multiple data systems, the data equipment and
applications can be used more productively. The system also provides
several data-related features that are easy to use and contribute to
expedient use of the system and its networking capabilities.
■
Extended Networks
Extended networks mainly provide connections between the system and
other distant switches, including remote access facilities. With remote
access facilities, a local terminal can access remote host computers. Also,
remote terminals can access either local computer facilities or other
remote computer facilities. Extended networks are constructed of analog
or digital facilities and can be either public or private. Typical networking
configurations are shown in Figure 2-2. Public networks available in the
US include the following:
— Local Central Office (CO) switching extended through direct
distance dialing
— Foreign exchange (FX) central office trunking
— Wide Area Telecommunications Service (WATS)
— MEGACOM Telecommunications Service
— MEGACOM 800 Telecommunications Service
— Software Defined Network (SDN)
— Software Defined Data Network (SDDN) (G3i)
— ACCUNET. Digital Service
■
Private networks include:
— AT&T DATAPHONE. Data Communications Service
— Distributed Communications System (DCS)
— Electronic Tandem Network (ETN)
— Enhanced Private Switched Communications Service (EPSCS)
— Private line (PL)
— Software Defined Network (SDN)
— Software Defined Data Network (SDDN)
— Tandem tie trunk
2-12
Issue 3 March 1996
Data Management
DIGITAL - PUBLIC
NETWORK FACILITIES
DS1/CO
DS1/FX
DS1/WATS
ISDN-PRI
LOCAL AREA
DATA TERMINALS
PERSONAL COMPUTERS
PRINTERS
FACSIMILE EQUIPMENT
OTHERS
SYSTEM B
ANALOG - PRIVATE
NETWORK FACILITIES
EPSCS
ETN
PL
TANDEM TIE TRUNKS
HOST
COMPUTER
SYSTEM A
DIGITAL - PRIVATE
NETWORK FACILITIES
ETN
"DATAPHONE "
DIGITAL SERVICE
DS1
ANALOG - PUBLIC
NETWORK FACILITIES
WATS
FX TRUNKS
CO TRUNKS
APPLICATIONS
PROCESSOR
PRIVATE LINES
SYSTEM C
CENTRAL
OFFICE
HOST
COMPUTER
DATA
TERMINAL
REMOTE ACCESS FACILITIES
Figure 2-2.
System Networking Configurations
Data Communications Protocols and Interfaces
A protocol is a set of conventions or rules that governs how data is transmitted
and received. The rules generally cover the following:
■
Physical interface
■
Mechanical interface
■
Electrical interface
■
Framing
Issue 3 March 1996
2-13
Functional Description
■
Error detection and control
Communications protocols are designed to meet the transmission requirements
for specific data exchange and data communications equipment. These
communications protocols are sponsored by a national or international
organization or a major corporation. The system equipment and communications
processing software provide the following protocols:
■
ISDN Protocols
■
EIA RS-232C
■
RS-449
■
RS-366
■
Standard Serial Interface (SSI)
■
Teletypewriter (TTY) Modes
■
Digital Communications Protocol (DCP)
■
BX.25 Packet Switching
■
ITU-T V.35
■
Wideband Switching
■
Binary Synchronous Communications (Bisync)
ISDN Protocols
The ISDN Q.931 Protocol is used to support Layer 3 call control signaling for both
the network and user sides of an ISDN Primary Rate Interface (PRI). Both DS1
and E1 digital transmission standards are supported on a per-interface basis.
This implementation provides call state transition, proper message content, and
error recovery, as well as protocol support for other related features. For all
switches (except G3vs/G3s ABP), the ISDN Q.932 Protocol is used to support the
CallVisor Adjunct Switch Ap plications Interface (ASAI) required for the Inbound
Call Management feature.
Electronic Industries Association (EIA)
EIA RS-232D
This protocol is widely used for short distance and low-speed applications such
as data terminals and modems connecting data terminals. The data link consists
of a 25-conductor cable. The conductors are used for data-link control and
timing, as well as for transmitting and receiving signals. Data-link control is
accomplished by handshake signaling between the transmit and receive
devices. Data speeds are limited to 19.2 kbps or fewer.
2-14
Issue 3 March 1996
Data Management
The EIA RS-232D protocol provides two interface connectors. The female side
connector is known as data communications equipment (DCE). The male side
connector is known as data terminal equipment (DTE). Data equipment
manufacturers design either the DCE or DTE interface into their products.
Products such as modems, data service units (DSUs), Digital Terminal Data
Modules (DTDMs), and Processor Data Modules (PDMs) have a built-in DCE
interface. Products such as some types of multiplexers, data terminals, printers,
computer ports, and Trunk Data Modules (TDMs) have a built-in DTE interface.
Modular Data Modules (MDMs) can be configured as either DCE or DTE.
The maximum cable length recommended by EIA for the EIA RS-232D protocol is
25 feet (15 meters). However, practical applications have shown that the cable
length can be much greater. Factors limiting cable length include transmission
speed, cable capacitance, and nearness of noise sources such as fluorescent
lights or electric generators. Each application should be considered separately.
RS-449
This protocol allows longer cables than the EIA RS-232D. Maximum cable
lengths for various data speeds are as follows:
■
19.2 kbps — 200 feet (61 meters)
■
9.6 kbps — 400 feet (122 meters)
■
4.8 kbps — 800 feet (244 meters)
■
2.4 kbps — 1,600 feet (488 meters)
The RS-449 protocol is provided as a communications link interface on the
Applications Processor (AP). This standard uses a 37-conductor cable. The AP
RS-449 interface contains unbalanced driver/receivers that also permit
interconnection to the EIA RS-232D interface when used with a 37- to 25-pin
cable adapter. Since the AP RS-449 interface is compatible with the EIA
RS-232D protocol, it also is limited to the same maximum 19.2 kbps data rate.
RS-366
The RS-366 communications protocol specifies the standards for interfacing
computers to ACUs. This permits a computer to originate data calls over a
switched telephone network. The AP provides one RS-366 interface for each six
EIA RS-232D interface ports.
Digital Communications Protocol (DCP) Interface
The DCP is used by the system’s digital switch, digital voice terminals, data
modules, the 510D terminal, and the 515 BCT. This protocol permits
simultaneous voice and data over the same communications link to the switch.
The DCP consists of a 160 kbps, four-wire serial data link that operates
full-duplex over standard twisted-pair building cable. For data-only transmission,
Issue 3 March 1996
2-15
Functional Description
the maximum cable length is 5,000 feet (1,524 meters). When voice and data
transmission is carried over the same data link, as when a 510D terminal, 515
BCT, or a DTDM is used, the cable length is limited by the voice transmission
distance.
The DCP sends digitized voice and digital data in frames. Each frame consists of
four fields or channels (see Figure 2-3). The first field is a unique three-bit framing
pattern that defines the frame boundary. The second field is a one-bit control or
signaling channel between the digital switch and digital data endpoint. The third
and fourth fields are two independent information (I) channels. The information
channels are eight bits each and are used to send digitized voice or digital data.
FRAMING
FIELD
SIGNAL
INFORMATION
#1
INFORMATION
#2
FRAMING
FIELD
DCP FRAME
Figure 2-3.
Digital Communications Protocol Frame Structure
There are 8,000 frames per second. Therefore, the bit rate available is eight for
the signaling channel and 64 kbps for the information channel. The digital switch
routes each information channel independently so that simultaneous voice and
data can be completed to different destinations.
The full capacity of the information channels (64 kbps) is available for digitized
voice. Data terminals typically operate at speeds from below 300 bps up to 19.2
kbps, asynchronous or synchronous. The DCP uses data modules to map the
data terminal data into a 64 kbps information channel.
The framing rate of 8,000 per second and eight bits per information channel is
consistent with other telecommunication systems such as the DS1/E1 carrier.
This minimizes potential conversion problems when interfacing to different digital
facilities.
BX.25 Packet Switching Protocol
The BX.25 protocol implements the international standard for packet switching. It
is a multilayered protocol. [Layering is a structuring of specific protocol functions
(for example, error detection and correction) that are grouped together as a
unique layer or level.]
2-16
Issue 3 March 1996
Data Management
The BX.25 protocol is similar to the ITU-T X.25 protocol and, from a user
perspective, is compatible with the standard. The BX.25 protocol has three
layers that are not specified for the X.25 protocol. These layers are Application,
Presentation, and Session. The Application and Presentation layers are defined
in the Transaction-Oriented Protocol (TOP) of the BX.25.
The TOP is a high-level protocol, intended to standardize communications
between transaction-oriented systems. Transaction-oriented communications
involve communication of small messages or requests describing a single unit of
work that may result in a reply being sent back to the originating system. The
Session layer is intended to establish, manage, and terminate sessions for use
by higher-level protocols or, in some cases, by user applications directly. Other
differences between X.25 and BX.25 are as follows:
■
The X.25 protocol specifies network standards only; the BX.25 protocol
places requirements on the user interface as well.
■
The X.25 protocol provides for datagram services while the BX.25 protocol
does not. Datagram service has not been implemented within the
continental United States.
■
The X.25 protocol leaves the users in a point-to-point environment to
develop their own solutions to the following areas of potential conflict,
while the BX.25 protocol provides solutions:
— Link layer addressing
— Logical channel selection
— Call collision
Basic elements of the Application and Presentation layers must be user defined
under both protocols. The following figures shows the relationship and similarity
between the BX.25 and X.25 protocols.
The BX.25 protocol is used in the system to provide communications between
the switch and the switch-related features. The BX.25 protocol is also used in the
system to provide communications between the switch and the AUDIX and to
provide communication between DCS switches
Issue 3 March 1996
2-17
Functional Description
USER
USER
--APPLICATION
LAYER
T
O
P
PRESENTATION
LAYER
*
--SESSION
LAYER
SESSION
LAYER
--TRANSPORT
LAYER
PACKET
LAYER
NETWORK
LAYER
--LINK
LAYER
DATA LINK
LAYER
--PHYSICAL
LAYER
PHYSICAL
LAYER
BX.25 Protocol Layers
Figure 2-4.
2-18
BX.25 Packet-Switching Protocol
Issue 3 March 1996
Data Management
USER
USER
--APPLICATION
LAYER
PRESENTATION
LAYER
Not
Specified
--SESSION
LAYER
by
Protocol
--TRANSPORT
LAYER
PACKET
LAYER
NETWORK
LAYER
--LINK
LAYER
DATA LINK
LAYER
--PHYSICAL
LAYER
PHYSICAL
LAYER
X.25 Protocol Layers
Figure 2-5.
X.25 Packet-Switching Protocol
Issue 3 March 1996
2-19
Functional Description
International Telecommunications
Union - Telecommunications,
Specifications Sector (ITU-T) Interface
X.25 Packet-Switching Protocol
The ITU-T (formerly CCITT) is one of three divisions of the International
Telecommunications Union, an agency of the United Nations. The standards set
by the ITU-T generally deal with public networks. Two series of standards or
recommendations specifically deal with data transmission:
■
The V-series provides recommendations for data transmission over analog
or voice telephone networks.
■
The X-series provides recommendations for data transmission over digital
networks.
The V-series includes the V.10, V.11, V.24, V.28, and V.35. Also, V.26, V.27, and
V.28 are modem recommendations for 2400, 4800, and 9600 bps, respectively.
V.10 and V.11 are the equivalent to the EIA RS-423 and RS-422.
V.24 provides definitions for all interchange circuits crossing the DTE/DCE
interface.
V.28 defines a set of electrical characteristics compatible with EIA RS-232D.
V.35 provides the constant current interface for 48 kbps operation.
The X.25 protocol is the ITU-T recommendation for implementing International
Standards Organizations Reference Model of Open Systems Interconnection.
This is the international model for packet-switching networks and is a
bit-oriented, layered-type protocol. The transport, network, data link, and
physical layers (levels) are defined functionally by the ITU-T.
The X.25 protocol specifies network requirements and procedures to provide the
user interface for a packet-switching network. Typically, users generate
low-speed asynchronous data. The X.25 software segments this data into
packets, adds framing and routing information, and queues the packets into a
buffer memory. User data packets, along with the added framing bits, are then
transmitted over high-speed carriers. This permits efficient and dynamic sharing
of these high-speed data links.
The X.25 protocol provides the communications links between multiple APs.
2-20
Issue 3 March 1996
International Telecommunications Union Telecommunications, Specifications Sector (ITU-T)
Interface
Wideband Switching
Wideband Switching provides a range of data transmission speeds (from 128 to
1984 kbps for E1 services, 128 to 1536 kbps for T1 services). The higher
transmission rates are needed for applications such as video conferencing, data
backup, scheduled batch processing, and primary data connectivity.
Issue 3 March 1996
2-21
Functional Description
Data Management Features
The following features are associated with Data Management:
2-22
■
Administered Connections
■
Alphanumeric Dialing
■
Data Call Setup [including Default Dialing and Alphanumeric Dialing]
■
Data Hot Line
■
Data-Only Off-Premises Extensions
■
Data Privacy
■
Data Restriction
■
Default Dialing
■
Digital Multiplexed Interface
■
DS1/E1 Tie Trunk Service
■
EIA Interface
■
Information System Network (ISN) Interface
■
Modem Pooling
■
PC Interface
■
PC/PBX Connection
■
Uniform Call Distribution (See Direct Department Dialing [a VOICE
Management Feature])
■
Wideband Switching
■
World Class Core BRI
Issue 3 March 1996
Network Services
Network Services
Network Services allows a group of switches (consisting of DEFINITY Generic 1,
Generic 2, Generic 3, System 75 and System 85, and/or other systems) to be
configured to meet the communications needs of a medium- to large-size
corporation. Possible arrangements include an "Electronic Tandem Network
(ETN)", "Distributed Communications System (DCS)", and Main/Satellite/Tributary.
Each is briefly described in this chapter.
Do not assume that the system has any capabilities other than those explicitly
stated herein. Refer to the System 75/85 AT&T Network and Data Services
Reference manual, 555-025-201, for differences between this system and other
AT&T systems.
Network Services Features
The following features are associated with Network Services:
■
AAR/ARS Partitioning
■
ARS to AAR Conversion
■
Automatic Alternate Routing
■
Automatic Circuit Assurance
■
Automatic Route Selection
■
DCS Alphanumeric Display for Terminals
■
DCS Attendant Control of Trunk Group Ac cess
■
DCS Attendant Direct Trunk Group Selection
■
DCS Attendant Display
■
DCS Automatic Callback
■
DCS Automatic Circuit Assurance
■
DCS Busy Verification of Terminals and Trunks
■
DCS Call Coverage
■
DCS Call Forwarding All Calls
■
DCS Call Waiting
■
DCS Distinctive Ringing
■
DCS Leave Word Calling
■
DCS Multi-Appearance Conference/Transfer
■
DCS Trunk Group Busy/Warning Indication
■
Non-Facility Associated Signaling and D-channel Backup (G3i)
■
Facility Restriction Levels and Traveling Class Marks
Issue 3 March 1996
2-23
Functional Description
■
Forced Entry of CDR Ac count Codes
■
Generalized Route Selection
■
Integrated Services Digital Network — Primary Rate Interface
■
Network Access — Private
■
Network Access — Public
■
Off-Premises Station
■
QSIG Global Networking
■
Restriction — Toll
■
Subnet Trunking
■
Time of Day Routing
■
Uniform Dial Plan
Private Network Configurations
A private network is a configuration of trunk and switching facilities dedicated to
the use of a business or organization. It may have as few as two switches or it
may have hundreds of switches located throughout the world. Although they
normally serve moderate to heavy calling between locations, the following
configurations make it possible for organizations of all sizes to realize the
benefits of a private network.
■
"Electronic Tandem Network (ETN)" — Serves the needs of customers with
many locations in a large geographic area. This configuration provides for
calling between locations without accessing toll facilities.
■
"Distributed Communications System (DCS)" — Serves the needs of
customers with several locations in a small or large geographic area. A
Distributed Communications System (DCS) appears as a single switch
with respect to certain features.
■
"Main/Satellite/Tributary" — Serves the needs of customers with a few
locations in a small geographic area.
The system also can be used within a Tandem Tie Trunk Network (TTTN). A TTTN
is a nonhierarchical network of tie trunks interconnecting three or more switches.
User dialing into each switch in the call’s path is required. That is, the user at one
switch dials the trunk access code for a tie trunk group to another switch,
receives dial tone from that switch, and then dials another trunk access code to
reach another switch. When dial tone is received from the final (desired) switch,
the user dials the desired extension number.
2-24
Issue 3 March 1996
Network Services
Electronic Tandem Network (ETN)
An Electronic Tandem Network (ETN) is a hierarchical network of privately owned
trunk and switching facilities that can provide a cost-effective alternative to toll
calling between locations. An ETN consists of tandem switches, the intertandem
tie trunks that interconnect them, the access or bypass tie trunks from a tandem
switch to a main switch, and the capability to control call routing over these
facilities. A Main/Satellite/Tributary configuration can be served by an ETN or a
DCS can also be part of an ETN.
The system can serve as an ETN tandem switch.
Within an ETN each location is identified by a unique private network office code.
With G3i, this private network office code may be of the form RN, RNX, RX, XX,
RNX, RXX, XXX, and RNXX, depending on administration (R = digits 2 through 9,
N = digits 2 through 9, and X = digits 0 through 9). After accessing the ETN, the
user simply dials the private network office code plus the desired extension
number, for a total of ten digits or less.
Private network office codes are unique within an ETN. Private network office
codes are assigned when the ETN is established. When Direct Inward Dialing
(DID) is provided by the local central office, the extension numbers (last four
digits of the number) will match. Network Inward Dialing (NID) is the ETN
equivalent of DID and can be provided without DID.
The software program that controls call routing over an ETN is called Automatic
Alternate Routing (AAR). AAR not only determines the route for a call, but,
through the Facilities Restriction Level (FRL) function, defines up to eight levels of
calling privileges for users of the ETN. Another function of AAR, Subnet Trunking,
can convert an on-network number to a public network or international number.
This function is useful when all on-network routes are busy or are not provided.
The details of Automatic Alternate Routing, Facilities Restriction Level, and
Subnet Trunking are provided in this chapter.
AAR digit conversion can be used to convert private network numbers to other
private network numbers or public network numbers. This allows the system to
steer some AAR calls to other switches in the private network or, by changing
specific dialed digits to a public network number, eventually route some calls via
ARS. Also, unauthorized private network calls can be routed to an attendant or
receive intercept treatment. Details on AAR digit conversion can be found in the
Automatic Alternate Routing feature description.
Distributed Communications System (DCS)
A Distributed Communication System (DCS) is a cluster of private
communications switches (nodes) interconnected among several geographic
locations. These switches can be either a DEFINITY Generic 1, DEFINITY
Generic 2, DEFINITY Generic 3, System 75, System 85, or DIMENSION PBX.
Issue 3 March 1996
2-25
Functional Description
Refer to the System Parameters table In Appendix A for the node limitations of
each system type.
An attribute of a DCS configuration that distinguishes it from other networks is
that it appears as a single switch with respect to certain features. This provides
simplified dialing procedures between locations, as well as the convenience of
using some of the system’s features between locations. DCS is particularly useful
if there is frequent interlocation calling.
Each DCS node is connected with every other DCS node by tie trunks or
ISDN-PRI trunks (DEFINITY Generic 3) for voice communications and data links
that send and receive control and feature information. However, each DCS node
does not have to be directly connected to every other node. Communication may
be through a DCS tandem node. The data links and voice channels may be
directly between nodes or may pass through a tandem node. Nodes that cannot
serve as a tandem node (that is, those that cannot receive information from one
node and pass it on to another node) are called endpoints (or endpoint nodes).
Nodes that can pass information are simply referred to as nodes. DEFINITY
Generic 3i can serve as either an endpoint node or a regular (tandem) node.
Figure 2-6 shows a typical DCS configuration.
A DCS can consist of all end points. That is, each node in the DCS may be
directly connected by data links and voice channels with every other node in the
DCS.
Some of the applications of the DCS configuration are as follows:
■
In a ‘‘campus environment’’ that has two or more separate buildings and
the nodes are connected by local cable.
■
In a larger area such as a city, several states, or even the entire country,
where the nodes are separated by distances too great for local cable and
may be connected to different central offices.
A DCS has the property of ‘‘transparency’’ with respect to inside calling and
some features. Transparency is the ability of the system, from the user’s
standpoint, to operate across several nodes in the same way it does at the local
node. This allows users to dial from any terminal to any other terminal within the
DCS without regard for which nodes are involved. Likewise, transparency allows
certain voice features to be used across nodes.
2-26
Issue 3 March 1996
Network Services
CENTRALIZED
ATTENDANT SERVICE
SYSTEM B
CO
ENDPOINT NODE
OUTSIDE
CO
TRUNKS
OUTSIDE
TRUNKS
TIE TRUNKS
RELEASE LINK TRUNKS*
DATA LINK
TIE TRUNKS
DATA LINK
MAIN LOCATION
BRANCH
(SYSTEM A)
SYSTEM C
TIE TRUNKS
OUTSIDE
TRUNKS
DATA LINK
* REQUIRED ONLY IF THE NETWORK HAS OPTIONAL
CO
CENTRALIZED ATTENDANT SERVICE. RELEASE
LINK TRUNKS ARE NOT REQUIRED FOR DCS.
SYSTEM D
ENDPOINT NODE
WITH V2, SYSTEM 75 CAN ONLY BE AN ENDPOINT
IN DCS.
OUTSIDE
TRUNKS
CO
Figure 2-6.
Typical Distributed Communications System
Some voice features have transparency in a DCS configuration. The following
voice features have unique aspects in a DCS environment and are described in
detail in this book.
■
DCS Alphanumeric Display for Terminals
■
DCS Attendant Call Waiting (described under DCS Call Waiting)
■
DCS Attendant Control of Trunk Group Ac cess
■
DCS Attendant Direct Trunk Group Selection
■
DCS Attendant Display
■
DCS Automatic Callback
■
DCS Automatic Circuit Assurance
■
DCS Busy Verification of Terminals and Trunks
■
DCS Call Coverage
Issue 3 March 1996
2-27
Functional Description
■
DCS Call Forwarding All Calls
■
DCS Call Waiting — Termination (described under DCS Call Waiting)
■
DCS Distinctive Ringing
■
DCS Leave Word Calling
■
DCS Multi-Appearance Conference/Transfer
■
DCS Priority Calling (described under DCS Call Waiting)
■
DCS Trunk Group Busy/Warning Indication.
■
Enhanced DCS (described under Enhanced DCS).
Abbreviated Dialing and Last Number Dialed also have transparency in a DCS
configuration. These features operate the same in a DCS as they do at a single
switch.
A DCS cluster can consist of up to 64 nodes. Since AUDIX and the Call
Management System (CMS) and ISDN-PRI each require the same data link
facilities as a node, each of these included in the system reduces the number of
available data links, which, depending on the system configuration, may reduce
the maximum number of nodes.
Use of the DCS over the ISDN-PRI D-channel feature on the other hand, may
increase the maximum number of nodes. (Note that on G3r, ISDN-PRI does not
require the same data link facilities as a node.)
DCS Message Hopping lets a DCS message route through an intermediate node
without tandeming an associated trunk call. This is accomplished through the
use of hop channels. The system provides Message Hopping through up to two
hops.
DCS transparency is more restricted when the tandem node is an Enhanced
DIMENSION PBX or a System 85 Release 2 Version 1 than when it is a System 85
Release 2 Version 2, or later, or a DEFINITY Generic 2.1, or later. (See the DCS
Alphanumeric Display for Terminals and DCS Leave Word Calling features.)
Certain feature capabilities are unique to a particular type of node (for example,
a DEFINITY Generic 3 endpoint node). Therefore, a detailed feature description
should be consulted for each type of node.
The Centralized Attendant Service (CAS) feature can be used as an advantage in
DCS networks where all attendants are at one node. CAS reduces traffic volume
on interconnecting tie trunks caused by incoming attendant-seeking calls at the
endpoint nodes. DEFINITY Generic 3 can serve as the main location for CAS
attendants. Centralized Attendant Service capabilities are given in detail in this
manual.
With DCS Call Coverage (G3V4 and later releases), calls to an extension on one
system can be covered by extensions administered as coverage points on
2-28
Issue 3 March 1996
Network Services
remote systems. DCS Call Coverage provides transparency across systems for
the Call Coverage feature.
Main/Satellite/Tributary
Figure 2-7 shows a Main/Satellite/Tributary configuration. It can function
independently or serve as an ETN access arrangement. For a Main/Satellite
configuration, attendant positions and public network trunk facilities are
concentrated at the Main, and calls to or from satellite locations pass through the
Main. To a caller outside the Main/Satellite complex, the system appears to be a
single switch with one Listed Directory Number. This is accomplished with the
optional Uniform Dial Plan software.
Tributary and Satellite locations are similar except that a Tributary has one or
more attendant positions and its own Listed Directory Number.
DEFINITY Generic 3 can serve as a Main, Satellite, or Tributary.
A small business can start with a single Main/Satellite or Main/Tributary complex
and add trunk and switching facilities as the business grows. In this situation, tie
trunks connect the main locations within an urban area and intercity traffic is
routed via the public network. This arrangement favors a medium-size
organization or one that has small isolated locations where the intercity traffic is
too small to justify the cost of tie trunks.
MAIN
TIE TRUNKS
Figure 2-7.
SATELLITE
TRIBUTARY
SYSTEM
SYSTEM
Main/Satellite/Tributary Configuration
Issue 3 March 1996
2-29
Functional Description
Trunking
Trunking is the use of communications links to interconnect two switching
systems, such as connecting the switch to a local central office or to another
switch. These links, called trunks, can be grouped together in Trunk Groups
when all the trunks in the group perform the same function. This grouping
simplifies administration since the required service characteristics (parameters)
are assigned to the group rather than to each trunk. Grouping also simplifies call
processing. Calls requiring a trunk are routed to the appropriate trunk group and
an idle trunk, if available, is selected from the group.
There are analog trunks and digital type trunks. The type of signal is specified for
each trunk in the list below. The following types of trunk groups can be used with
the system:
2-30
■
Auxiliary — Provides internal trunk applications for features such as
Loudspeaker Paging and Music-on-Hold. This is an analog signal.
■
CO — Provides a link with the local Central Office (CO) for Direct Outward
Dialing (DOD) and manually completed incoming calls, not Direct Inward
Dialing (DID) calls. The signals may be analog or digital
■
Direct Inward Dialing (DID) — Provides a link with the local CO that is only
usable for incoming calls and allows the CO to send digits to the PBX so
the call can be routed to a particular station. The signal can be analog or
digital
■
Direct Inward/Outward Dialing (DIOD) — Provides a link with the local CO
that allows digits to be sent in either direction for incoming and outgoing
calls. The signal can be either analog or digital
■
DS1/E1 Tie Trunk — Provides for two types of digital tie trunk interfaces:
Voice-Grade DS1/E1 and Alternate Voice/Data (AVD) DS1/E1 tie trunks.
The Voice-Grade DS1 tie trunks are an alternative to four-wire analog E&M
tie trunks and may be used to interface with other properly-equipped
switching systems. AVD DS1/E1 tie trunks permit alternate voice and data
calling between a System 75, DEFINITY Generic 1, DEFINITY Generic 3
and a System 85 or DEFINITY Generic 2. DS1/E1 tie trunks also can be
used with Release Link trunks for Centralized Attendant Service, and can
be used with AT&T unbanded telecommunications service. (digital signal)
■
FX — Provides a link with a CO other than the local CO. (analog or digital
signal)
■
ISDN-PRI — Provides end-to-end digital connectivity and supports a wide
range of voice and non-voice services. Calls to a variety of switched nodal
services and calls destined for different inter-exchange carriers can be
processed. (digital signal)
■
Tie and Release Link — Provide a link with another private switching
system for calls between the systems. Release link trunks are used only
with Centralized Attendant Service. The signal can be analog or digital.
Tie trunks are used on calls to or from the following:
Issue 3 March 1996
Network Services
— a Private Branch Exchange (PBX)
— an ETN switch
— an EPSCS or Common Control Switching Arrangement (CCSA)
office
— MEGACOM Service (AT&T unbanded long distance service.)
■
WATS —Provides access to a portion of the DDD network via dedicated
trunks to a WATS serving office. Each WATS trunk terminates as a WATS
line in the WATS serving office. The trunks used are always one-way
outgoing. Outgoing WATS calls to various geographic areas are made on
an attendant-handled basis or a station direct-outward-dial basis. Signals
can be analog or digital.
Tie trunks used with the system are administered as either internal or external.
The internal or external designation controls the type of ringing (which is
administrable) received at a voice terminal when an incoming tie trunk call
arrives and controls the routing of the call if it is redirected through the Call
Coverage feature. The default ringing pattern is the following:
■
Incoming internal tie trunk calls cause internal-call ringing and will redirect
according to the redirection criteria administered for internal calls.
■
Incoming external tie trunk calls cause external-call ringing and redirect
according to the redirection criteria administered for external calls.
The number of bursts for internal/external/priority calls is administrable in
G3i-Global and G3V2 and later releases. The "Call Coverage" feature interaction
with Tie Trunks is described in detail in Chapter 3 of this manual.
Selection of the trunk group to be used for a given call is determined by digit
translation on the trunk access code by the AAR/ARS routing tables. Assuming
an idle trunk in the selected group is found, a seizure signal (service request) is
sent to the distant switch. If the distant switch requires the called number, a start
dial signal is normally returned to the calling switch, indicating readiness to
accept digit transmission.
The start dial signal(s) used is dictated by the serving FX office, WATS office, or
local CO. For interconnection with other private switching systems, the System
Manager may select the start dial signal(s) to be used.
‘‘Trunk type’’ refers to the physical design of a trunk circuit. Trunk type and the
start dial signal are often used interchangeably, although trunk type is a more
accurate term. A brief description of the available trunk types follows:
■
Ground Start — A ground signal is sent over the trunk ring lead and is
received over the trunk tip lead.
■
Loop Start — A closure signal is sent through the loop formed by the trunk
leads.
Issue 3 March 1996
2-31
Functional Description
■
Immediate Start — No start dial signals are used. On outgoing calls, the
system waits at least 80 milliseconds (a configurable amount of time) after
sending the seizure signal before sending the digits required at the distant
switch. This gives the distant switch enough time to attach a digit receiver
to the call.
■
Wink Start — A momentary signal (wink) is sent to the distant switch when
the trunk is ready to receive digits.
■
Delay Dial — A steady signal is sent to the distant switch and is removed
when the trunk is ready to receive digits.
■
Automatic — No dialing is performed. The seizure signal sent or received
is sufficient to route the call. The call destination is specified when the
trunk group is administered. The destination can be the attendant group
or any extension number assigned in the system.
Trunk groups connecting with a WATS office, FX office, or local CO can be
ground or loop start. DID trunk groups can be immediate or wink start. Tie trunk
groups can be delay dial, wink start, immediate start, or automatic.
Trunk groups can be one-way incoming, one-way outgoing, or two-way. Whether
the trunk group is available for incoming, outgoing, or two-way traffic is called
direction. A two-way loop-start trunk is subject to glare. Glare occurs when the
distant switch is trying to use a given trunk for a call to a DEFINITY PBX at the
same time the DEFINITY system is trying to use the same trunk for a call to the
distant switch. Incoming calls are not aborted because of glare. The incoming
call will complete, and the outgoing call will receive reorder tone (G3i and
G3vs/G3s). In G3r and G3V2 and later releases, glare retry handling for two-way
trunks is administrable. Queuing at both ends of a two-way trunk group
compounds the possibility of glare and is, therefore, not recommended.
Each non-DCS outgoing and two-way trunk group can have a queue. If all trunks
in the group are busy, the call waits in the queue until a trunk becomes idle. The
queue length, which is the number of calls waiting, may be from one to 100. A
queue length of 0 (zero) indicates no queue has been established. This
information is entered on the trunk group form when the trunk group is
administered.
Dual Tone Multifrequency (DTMF) (touch-tone) signaling or rotary dial
(dial-pulse) signaling can be used between switches. The system can send or
receive either type of signaling required by the distant switch as well as
ISDN-PRI and R2-MFC and others.
An incoming trunk call to the system can be connected to another trunk, a voice
terminal, an attendant console, or an announcement. When the call is answered,
‘‘an answer supervision’’ signal is sent to the distant public network switching
office. This signal initiates the recording of the call details normally used for
charging. Any CO call routed outward is deemed ‘‘answered’’ 10 seconds
(system default; however, this may be administered as higher or lower on the
trunk group form) after the last digit is dialed. Tie trunk calls are deemed
2-32
Issue 3 March 1996
Network Services
‘‘answered’’ when answer supervision is returned from the far end or when
answer supervision time-out expires. Also, if there is a trunk incoming from one of
the previously listed offices on a call of this type, then answer supervision is sent
to that office. An incoming call to a Direct Department Calling (DDC) or Uniform
Call Distribution (UCD) recorded delay announcement is deemed ‘‘answered’’
when the calling party is connected to the announcement. Other types of
announcements, such as unassigned number announcements, are treated as an
unanswered call.
Issue 3 March 1996
2-33
Functional Description
System Management
System Management provides the capabilities to control and maintain the system
and also provides system usage reports to help determine if the system is being
used as intended. In short, System Management allows the System Manager to
establish the system, monitor its use, and make additions and/or changes as
necessary. System management devices are the Generic 3 Management
Terminal (G3-MT) or the Generic 3 Management Adjunct (G3-MA). The G3-MA
system management device is an enhanced PC-based administration system.
!
WARNING:
Secure your system from unauthorized access by following the guidelines
suggested in the GBCS Products Security Hand book, 555-025-600, and in
the "Security Measures" section, Chapter 1.
System Management features and functions are described in this chapter.
Functions are more fully described in the following documents.
■
DEFINITY Communications System Generic 3 V4 Implementation,
555-230-655
■
DEFINITY Communications System Generic 3 V2 Traffic Reports,
555-230-511
■
DEFINITY Communications System Generic 3r Maintenance, 555-230-105
Changes made to system translations are effected only at the single system for
which the changes were made. If a system is part of a network, changes may
need to be made at more than one system to effect the desired changes to the
network. Similarly, changes intended for only a single system could affect the
network. Therefore, the System Manager must understand the effect on the
network before making any changes.
System Management Features
The following features are associated with System Management:
2-34
■
Administration
■
Advice of Charge
■
Call Detail Recording (CDR)
■
Customer-Provided Equipment (CPE) Alarm
■
Facility Test Calls
■
Move Agent From CMS
■
Recent Change History
■
Report Scheduler and System Printer
■
Security Violation Notification
Issue 3 March 1996
System Management
■
System Measurements
■
System Status Report
System Administration
Allows the user to implement (initialize) and administer all the terminal and
system features and system parameters. System Administration allows the
following:
■
Initializing the system
■
Managing system, voice terminal, and data terminal features on a
day-to-day basis
■
Performing system back-up procedures
■
Monitoring, detecting, and determining system performance
■
Maintaining system security
System administration and maintenance are performed at the G3-MT or G3-MA,
a Remote Administration terminal, or AT&T location. The G3-MT and G3-MA are
referred to from here on as the administration terminal. The G3r multiple
administration feature supports up to eight simultaneous system management
sessions. Up to five of these sessions may be performing administration updates
simultaneously. Up to five of these sessions may be executing a maintenance
command simultaneously.
The administration terminal can be any of the following:
■
715 BCT
■
G3-MA
■
G3-MT
■
MS-DOS compatible PC with 4410 emulation software
The administration terminal must be located within 50 feet of the system cabinet
and must be connected directly to the “terminal” or “duplication option terminal”
connected on the Switch Processing Element (SPE). The administration terminal
consists of a video display and keyboard that allow a System Manager to input
system commands and translations. The administration terminal is first used to
initialize the system. After initialization, the administration terminal is used to
reconfigure translations and to monitor system performance. Remote AT&T
service locations have access to the same administration capabilities as the local
administration terminal.
G3V3 and later releases provide enhanced login/password security by adding a
security feature that allows the user to define their own logins/passwords and to
specify a set of commands for each login. For complete instructions about
logging in and password administration, see the AT&T document DEFINITY
Communications System Generic 3 V4 Implementation 555-230-655.
Issue 3 March 1996
2-35
Functional Description
Remote Administration
Allows the system to be administered from a remote terminal located either on or
off the customer’s premises. A terminal located more than 50 feet from the
system cabinet is considered remote. A remote administration terminal can be on
the same premises as the local administration terminal or it can be off-premises.
The remote terminal performs the same functions as the local administration
terminal.
The VT 220, 610 BCT, 615 MT BCT, 715 BCT, 4410 terminal, or 4425 terminal
may be used as either an on-premises or off-premises remote terminal. If the
remote terminal is a 4410 terminal, VT220, 513 BCT, 610 BCT, 615 MT, or 715
BCT, it must be connected to the system through a PDM, 7400A data module,
7400B data module, or Data Line circuit pack. If a 4425 terminal (models that
include a built-in modem) is used as a remote terminal, a PDM, 7400A is not
required. See the DEFINITY Communications System Generic 1 and Generic 3
Installation and Test manual, 555-230-104, for additional information.
Technical Service Center (TSC)
The TSC is an organization of AT&T service personnel who provide system
administration and maintenance from a remote location.
Personnel at the TSC access the system and perform administrative tasks
assigned to the System Manager. The administrative commands used by the
System Manager are also available to the TSC personnel. TSC personnel can
also execute maintenance routines.
During system access, the TSC personnel automatically receive major and minor
alarm notifications from the system. When an alarm is received, TSC personnel
can access the system and perform the following tasks:
2-36
■
Clear errors
■
Display alarms
■
Display errors
■
Download a copy of the system tape
■
Perform any required administration
■
Receive backup translations for the system
■
Set time and date
■
Test and busyout circuit packs, voice terminals, and trunks
■
Dispatch field technicians when required
■
Notify customer of disposition and status of alarms.
Issue 3 March 1996
Hospitality Services
Hospitality Services
The Hospitality Services features meet the lodging industry’s need to provide
services for their guests. The basic feature set is included in the basic voice
application software and is sometimes referred to as the hotel/motel feature
software package.
Hospitality Services Features
The following features are associated with Hospitality Services:
■
Automatic Wakeup
■
Do Not Disturb
■
Names Registration
■
Property Management System Interface
— Check-In/Check-Out
— Housekeeping Status
— Controlled Restriction
— Guest Information Input/Change
— Room Change/Room Swap
— Message Waiting Notification
Issue 3 March 1996
2-37
Functional Description
Call Center Services
The Call Center Services features support industries such as airlines, travel
agencies, and catalogs that have a large number of similar incoming and/or
outgoing calls. These features can provide balanced call distribution to a large
group of voice terminals.
Call Center Services Features
The following features are associated with Call Center Services:
■
Abandoned Call Search
■
Agent Call Handling
— Stroke Counts
— Call Work Codes
— Forced Entry of Stroke Counts and Call Work Codes
2-38
■
Automatic Call Distribution (ACD)
■
Basic Call Management System (BCMS)
■
Call Prompting
■
Call Vectoring
■
CallVisor (ASAI)
■
Expert Agent Selection (EAS)
■
Flexible Billing
■
Inbound Call Management
■
Intraflow and Interflow
■
Look Ahead Interflow
■
Malicious Call Trace (MCT)
■
Move Agent From CMS (See Ap pendix A, "System Parameters")
■
Multiple Call Handling
■
PC Application Software Translation Exchange (PASTE)
■
Queue Status Indications
■
Redirection on No Answer (RONA)
■
Service Observing
■
Voice Response Integration (VRI)
■
VuStats
Issue 3 March 1996
Feature Descriptions
3
Overview
This chapter defines the DEFINITY Communications System features. The
features are arranged in alphabetical order, regardless of the functional area to
which they apply. The information for each feature is usually presented under six
headings: Feature Availability, Description, Considerations, Interactions,
Administration, and Hardware and Software Requirements.
■
Feature Availability: Defines the release in which the feature is available.
■
Description : Defines the feature, describes what it does for the user or
how it serves the system, and briefly describes how it is used.
■
Considerations: Discusses the applications and benefits of the feature
and any other factors to be considered when the feature is used.
■
Interactions: Lists and briefly discusses other features that may
significantly affect the feature. Interacting features depend on each other;
one of the features must be provided if the other one is. Other features
may enhance each other; the features, in combination, provide improved
service to the user. Some features cannot coexist; one of the features
cannot be provided if the other one is. Finally, one feature can affect
another; the normal operation of one feature modifies, or is modified by,
the normal operation of the other feature.
■
Administration: States whether or not administration is required, how the
feature is administered, who administers the feature, and lists items
requiring administration.
■
Hardware and Software Requirements: Lists any additional hardware
and/or software requirements for the feature.
Issue 3 March 1996
3-1
Feature Descriptions
AAR/ARS Partitioning
Feature Availability
This feature is available with all Generic 3 releases.
Description
Provides for the Automatic Alternate Routing (AAR) and Automatic Route
Selection (ARS) services to be partitioned among as many as eight different
groups of users within a single DEFINITY Generic 3 switch. This provides
individual routing treatment for the different groups of users.
A partitioned user group consists of those users who are grouped together and
share the same Partition Group Number (PGN). The PGN is not a restriction, but
a means used to indicate the choice of routing tables to be used on a particular
call. Each Class of Restriction (COR) is assigned a specific PGN or Time of Day
specification. Different CORs may be assigned the same PGN. Therefore, it is
possible for members of the same partitioned user group to have different CORs.
When the "AAR/ARS Partitioning" feature is used in a hotel/motel or a hospital
environment, different facilities access is provided through ARS for guest/patient
voice terminals and administrative staff member voice terminals. For example,
within a hotel or motel, the guests and staff voice terminals might be partitioned
into two user groups. When a guest places an interstate call, the guest user
group’s ARS tables may specify that the call be routed using AT&T QUOTE
Service, a telephone billing information system that is used to bill back or allocate
long-distance charges. A similar call placed by a staff member might be routed
over a Direct Distance Dialing (DDD) trunk.
All partitioned user groups share the same pool of Routing Patterns. (See the
"Automatic Alternate Routing (AAR)" and "Automatic Route Selection (ARS)"
features for further explanations on routing.) The translation tables that specify
the Routing Pattern number are unique for each partitioned user group. Routing
Patterns may be shared among the user groups or may be dedicated to a
particular user group. Once a user activates the "Automatic Route Selection
(ARS)" or "Automatic Alternate Routing (AAR)" feature and dials enough digits for
the system to search for the Routing Pattern, the PGN of the originator’s COR is
used to select the table to look up the Routing Pattern.
Users of AAR/ARS Partitioning include the following:
3-2
■
Single-Line Voice Terminals
■
Multi-Appearance Voice terminals
■
Attendants
■
Remote Access Users
Issue 3 March 1996
AAR/ARS Partitioning
■
Data Endpoints
■
Incoming Tie Trunks
■
Other Trunks, used when calls are forwarded to an off-premises number
Considerations
With AAR/ARS Partitioning, different groups of users within the same system can
receive individual routing treatment. For example, the following types of
situations may require AAR/ARS Partitioning:
■
Groups of users with different routing preferences for calls to a given area
due to special billing needs
■
Groups of users who wish to have dedicated use of a particular network
facility
■
Groups of users in different businesses in one or more buildings serviced
by a single system
■
Data users who require special facility types on outgoing calls
Partition user groups are only used with UDP, AAR and ARS. There is no
capability to access the partitioned user groups directly. Operation of the groups
is completely transparent.
Interactions
The following features interact with the "AAR/ARS Partitioning" feature.
■
Brid ged Call Ap pearance
If a Bridged Call Appearance is used for an AAR or ARS call, the system
will use the PGN of the bridged principal’s extension instead of the PGN of
the originating user’s extension.
■
Call Detail Recording (CDR)
The PGN used to route the call is not recorded in CDR.
■
Call Forwarding All Calls
If a call terminates at a voice terminal that has Call Forwarding All Calls
activated and the forwarded-to number uses AAR or ARS, the COR of the
calling user is used to look up the PGN for the call.
■
DCS
The "AAR/ARS Partitioning" feature can cause different Routing Patterns to
be used on DCS calls. For example, one user’s Routing Pattern may
specify a DCS trunk group as a member of the pattern. A user of a second
PGN may use a different Routing Pattern that does not specify the DCS
trunk group. In this case, one user has DCS feature transparency and the
second user does not.
Issue 3 March 1996
3-3
Feature Descriptions
When a call routes over a DCS trunk, no PGN information is sent to the
far-end PBX. Thus, the far-end PBX only will be capable of using the
incoming trunk’s PGN to route the call.
■
Remote Access
If a Remote Access user activates ARS, the COR assigned to the barrier
code dialed (or the Authorization Code, if required) is used to select the
PGN for the call.
■
Straightforward Outward Completion and Through Dialing
If the attendant assists or extends a call for a user and activates ARS, the
attendant’s COR is used to select the PGN for the call.
■
Uniform Dial Plan (UDP)
Since UDP calls expand the dialed digits into seven-digit numbers and
then use AAR to route the call, these calls will make use of partitioning.
Once the call begins to be handled by AAR, the user’s active COR will be
used to identify the proper PGN to handle the call.
Administration
AAR/ARS Partitioning is administered by the System Manager. The following
items require administration:
■
Different Digit Analysis tables must be administered for each partitioned
user group.
■
A PGN must be assigned to each COR table. Up to eight PGNs can be
used. If the "Time of Day Routing" feature is assigned, a Time of Day Plan
Number is assigned to the COR instead of the PGN.
Hardware and Software Requirements
No additional hardware or software is required.
3-4
Issue 3 March 1996
Abandoned Call Search
Abandoned Call Search
Feature Availability
This feature is available with all Generic 3 releases.
Description
Provides identification of abandoned calls for CO offices that do not provide
timely disconnect supervision.
Before an incoming Automatic Call Distribution (ACD) split rings the hunt group
member or agent, the system checks to make sure the calling party has not
abandoned the call (hung up). If the calling party has abandoned the call, the
call does not ring the hunt group member or agent. Abandoned Call Search
adds an overhead of up to one second to each call delivered to an agent.
To see if the calling party has abandoned the call, after the call has been
abandoned by an announcement, the system must determine if the calling party
is still connected to the ground-start trunk at the central office (CO). To do this,
the system flashes (opens the tip-ring loop for 150 to 200 ms) the CO end of the
trunk. If the calling party is still connected, the CO will not respond. If the calling
party has hung up on the call, the CO will send a disconnect signal within 700 to
800 ms. The system interprets this as an abandoned call, releases the trunk, and
the call does not ring the hunt group member or agent.
Outside of the US, a flash of this duration may be responded to differently. Please
see the "Trunk Flash" feature for more information.
After it is administered for a trunk group, this feature is performed automatically
by the system. No operation is required by system users.
Considerations
Abandoned Call Search is suitable only for older COs that do not provide timely
answer supervision. Most COs provide timely disconnect supervision, and
therefore do not require the "Abandoned Call Search" feature. Some older COs
can take as long as two minutes to notify the PBX of a disconnect and, thus,
require the PBX to determine, within one second, whether the call has been
abandoned, prior to extending the call. Even with Abandoned Call Search or
disconnect supervision, a small probability exists that a call will be extended to
the destination hunt group after the caller has hung up. Abandoned Call Search
and disconnect supervision significantly reduce that probability.
Abandoned Call Search works only with ground-start analog trunks.
Issue 3 March 1996
3-5
Feature Descriptions
Abandoned Call Search allows agents and hunt group members to answer more
calls because time is not wasted on abandoned calls. In addition, call handling
statistics generated by the CMS are more accurate because the CMS knows
when a call is abandoned.
Interactions
None.
Administration
Abandoned Call Search is administered on a per trunk group basis by the
System Manager. Each ground start CO, FX, and WATS trunk group is
administered as either having Abandoned Call Search or not having it.
Hardware and Software Requirements
For G3i-Global, Abandoned Call Search requires the use of a TN747B CO Trunk
circuit pack. The same requirement is in effect if the serving CO is a No.1 or No.
5 Crossbar switch.
No additional software is required.
3-6
Issue 3 March 1996
Abbreviated Dialing (AD)
Abbreviated Dialing (AD)
Feature Availability
Abbreviated Dialing is available with all Generic 3 releases. Enhanced
Abbreviated Dialing (also known as Enhanced Number List) is optional with all
releases except G3vs/G3s ABP. Enhanced Ab breviated Dialing is not available
with G3vs/G3s ABP. Automatic Dialing Buttons and designated user
programming of group lists are available with G3V4 and later releases.
Description
Provides lists of stored numbers that can be accessed to place local,
long-distance, and international calls; to activate features; or to access remote
computer equipment. Stored numbers can be accessed by voice terminal users
and data terminal users. Certain stored numbers can also be accessed by
attendants.
Automatic Dialing Buttons, available with G3V4 and later releases, allow users
direct access to a designated number that is not stored on an Abbreviated
Dialing list. See "Access Options" later in this section for more information about
Automatic Dialing Buttons.
List Types
Desired numbers are stored in any of four types of lists. Each stored number is
one list entry. To use Abbreviated Dialing, a user accesses the appropriate list by
dialing an access code, and then dials the one-, two-, three or four-digit list entry
number where the desired number is stored. The number is then dialed
automatically by the system. For a frequently called number, the list and list entry
number can be stored on an Abbreviated Dialing button. In this case, simply
pressing the button places the call.
The following section describes the types of Abbreviated Dialing lists. The
number of lists per system and the number of entries per list is determined by the
type and version of the switch. See "System Hardware and Software Capacity
Limits" on page A-12 for more information.
■
Personal Number Lists
Allow voice and data terminal users to have a personal set of stored
numbers. A user can have up to three Personal Number Lists. The user, or
the System Manager, programs the Personal Number Lists. The System
Manager determines the users that are allowed to have a personal list and
the size of each list.
The Personal Number Lists are created automatically when the capability
of accessing a personal list is administered for the individual station.
Issue 3 March 1996
3-7
Feature Descriptions
■
Group Number Lists
Allow access by a group of users, such as purchasing or personnel
departments, who frequently dial the same numbers. An individual user
can access up to three specific Group Number Lists, as set by the System
Manager.
The Group Number Lists are administered by the System Manager. G3V4
and later releases also provide for the administration of a designated user
(extension number) who can program a Group Number List. The
designated user for each list is specified on the “Abbreviated Dialing
Group List” form.
■
System Number List
Can contain any number or dial access code. The System Manager
programs the System Number List and sets which users can access the
list. One System Number List is allowed per system.
■
Enhanced Number List
One Enhanced Number List is allowed per system in addition to the
System Number List. The Enhanced Number List can contain any number
or dial access code. The System Manager programs the Enhanced
Number List and sets which users can access the list.
NOTE:
The enhanced number list capability is an optional feature which, if
desired, must be purchased separately. The Enhanced Number List
option is called the "Enhanced Ab breviated Dialing (EAD)" feature.
List Entries
The following sections describe the numbering schemes used to select a list
entry once an Ab breviated dialing list is accessed.
Personal Number List Entries
For Personal Number Lists administered for 5 or 10 entries, the user dials a single
digit to access a list entry number. Entries are numbered 1 through 9 and 0 (list
entry 10). For example, to access entry 6 the user dials 6, to access entry 10 the
user dials 0.
For Personal Number Lists administered for more than 10 entries (G3V4 and later
releases only), the user dials a two-digit number to access a list entry. For
example, to access entry 6 the user dials 06, to access entry 100 the user dials
00.
3-8
Issue 3 March 1996
Abbreviated Dialing (AD)
Group Number and System Number
List Entries
G3V4 provides the option of selecting between two Group Number and System
Number List entry numbering schemes. The type of numbering scheme used is
administered on the “System-Parameters Customer-Options” form. The first
numbering scheme corresponds to the one used in G3V3 and earlier releases.
The second numbering scheme corresponds to the one used in G2 switches.
Table 3-1.
Group Number and System Number List Entry
Numbering Schemes
List Entry Number
User Dials (Scheme 1)
User Dials (Scheme 2)
1
2
.
.
.
11
12
..
..
..
01
02
..
..
..
10
11
..
89
90
91
..
..
20
21
..
99
00
01
..
..
10
11
..
89
90
91
..
..
100
10
00
Enhanced Number List
List entries for the Enhanced Number list are numbered 000 through 999 in G3V3
and earlier releases. With G3V4 and later releases, the system can be
administered to have list entry numbers of either 000 through 999 or 0000
through 9999.
List Assignments and Designations
Each extension number can be assigned up to three Ab breviated Dialing Lists
— List 1, List 2, and List 3. Each of these three lists is designated as being either
Personal, Group, System, or Enhanced. The three lists may be any combination
of the above as long as there is no more than one System and/or Enhanced List.
When a list is designated as being a Group List, the particular number of the
Group List is specified (for example, group list 42). Personal Lists must have a
group number as well (Personal Lists are designated P1, P2, P3, etc.).
Issue 3 March 1996
3-9
Feature Descriptions
To access Ab breviated Dialing, the user accesses List 1, List 2, or List 3 either by
dialing the access code or by using a button programmed with the access code.
The access codes for List 1, List 2, and List 3 are the same systemwide.
Therefore, it is possible for a System List or a particular Group List to have a
different access code at different voice terminals. For example, suppose the
feature access codes for List 1 and List 2 are 101 and 102, respectively.
One voice terminal may have List 2 administered as ‘‘group 42.’’ Another voice
terminal may have List 1 administered as ‘‘group 42.’’ In this case, the access
code for ‘‘group 42’’ is 102 for the first voice terminal and 101 for the second
voice terminal.
Privileged Lists
All Group Number Lists, the System Number List, and the Enhanced Number List
can be designated as Privileged by the System Manager. Calls automatically
dialed from a Privileged List are completed without Class of Restriction or FRL
checking. (FRLs are associated with the "Automatic Route Selection (ARS)" and
"Automatic Alternate Routing (AAR)" features.) This allows access to selected
numbers certain voice terminal users might otherwise be restricted from
manually dialing. For example, a voice terminal user may be restricted from
making long-distance calls. However, the number of another office location may
be long distance. This number could be entered in a list designated as
Privileged. The user could then call the office location using Ab breviated Dialing,
while still being restricted from making other long-distance calls.
Special Characters
A number stored in an Abbreviated Dialing List can be a combination of
numerical digits and special characters. A special character instructs the system
to take a different action when dialing reaches the point where the character is
stored. Each special character counts as two digits toward the maximum
number of digits in a list entry. Refer to the AT&T document DEFINITY
Communications System Generic 3 V4 Implementation, 555-230-655 for more
information. The following special characters can be stored:
■
Pause (~p)
When a Pause is included in a string of stored digits to be outpulsed over
a trunk, outpulsing of the digit(s) following the Pause is delayed 1.5
seconds. Outpulsing automatically resumes after expiration of the delay
timing.
The Pause is useful when there is good probability the far-end dial tone
(provided by another switch) will be returned within 1.5 seconds. Typical
applications include tandem switching through private networks and
end-to-end signaling over the public or a private network.
The pause characters may not operate properly if used on buttons
pressed after the call is connected. Use of pause characters on calls
where the total number of digits sent exceeds 36 may cause loss of digits.
3-10
Issue 3 March 1996
Abbreviated Dialing (AD)
■
Wait (~w)
When a Wait precedes, or is included in, a string of stored digits to be
outpulsed over a trunk, outpulsing of the digit(s) following the Wait is
delayed 5 to 25 seconds or until dial tone is detected, whichever occurs
first. Outpulsing resumes after the End-Wait signal is received or when
delay timing expires.
The Wait is useful in cases where dial tone delays of variable length and/or
network blocking outside the system are frequently experienced. Typical
applications include tandem switching through private networks and
end-to-end signaling over the public or a private network.
■
Indefinite Wait (~W)
When an Indefinite Wait precedes, or is included in a string, outpulsing of
the digits following the Indefinite Wait is delayed until dial tone is detected
no matter how long it takes or until the calling party goes on hook. The
Indefinite Wait is useful in situations where Dial Tone is frequently delayed
for many minutes.
■
Mark (~m)
When a Mark precedes, or is included in a string of stored digits, all digits
following the Mark are treated as end-to-end signaling digits to be
outpulsed over an outgoing trunk in “Touch-Tone Signal” form even if a
dial pulse trunk was used to set up the call. As a typical ap plication, a
DTMF data call can be made over a dial pulse trunk (for example,
retrieving messages from AUDIX). The mark character should be placed
immediately after the extension, before any digits being sent to the
answering station.
■
Suppress (~s)
When a Suppress precedes, or is included in a string of stored digits, the
system treats all digits following the Suppress the same as any other digits
for call setup and digit outpulsing. The Suppress character only affects
the display of the stored number. Stored numbers are normally displayed
when an alphanumeric display is provided through the "Voice Terminal
Display" feature; however, the digits following the Suppress character are
not displayed. The display shows the lowercase letter s instead of the
stored digits.
The Pause and Wait special characters are needed to delay outpulsing of the
initial digits following access of an outgoing trunk if the system does not know
when to start outpulsing over a trunk (for example, in Europe). Use of these
characters as the very first character could cause calls to be aborted. These
characters are used when outpulsing should be delayed until dial tone is
returned from a distant point reached through a switched connection outside the
system.
Access Options
Abbreviated Dialing numbers can be accessed by any of the following options:
Issue 3 March 1996
3-11
Feature Descriptions
■
Abbreviated Dialing-Code (AD Code)
This option allows users to access a stored number by dialing the
"Abbreviated Dialing (AD)" feature access code and a list entry number.
Each AD code automatically dials the number stored in the list the user
accessed.
■
Abbreviated Dialing-Button (AD Button)
This option allows multi-appearance voice terminal users and attendants
to access stored numbers by pressing one or more buttons. Each AD
button automatically dials the number stored in the list and the list entry
number administered to the button.
Access to any list and associated list entry number can be programmed in
an AD button on a multi-appearance voice terminal. An AD button on an
attendant console can be programmed to access a Group List, the
System List, or the Enhanced List and associated list entry number.
The System Manager administers the AD button. If the button is
administered to access a number in the user’s Personal Number List, the
user can change the number assigned to the button. If the number
assigned to the button accesses an entry on a Group List either the
System Manager or a designated user (G3V4 and later releases) can
make the change. If the number assigned to the button accesses an entry
on the System List or the Enhanced List only the System Manager can
make the change.
■
Automatic Dialing Button
Available with G3V4 and later releases, this option allows users to directly
dial numbers by pressing one or more buttons. Each Automatic Dialing
button is administered to automatically dial a number that is not stored on
any of the Ab breviated Dialing lists. The number can be up to 16
characters long. The Automatic Dialing buttons are programmed by the
user or the System Manager.
A separate list, called the 7103A Group Number List, is used only by 7103A
Fixed Feature voice terminal users as a group. This list allows button access to
stored numbers and can have eight list entries. Any number can be stored in the
7103A Group Number List; however, it is intended primarily for feature access
codes. The System Manager programs the 7103A Group Number List.
All users can program their Personal Number List, any AD button that accesses a
number from their Personal Number List, and their Automatic Dialing buttons.
Only designated users can program an AD button that accesses a number from
a Group Number List. Programming is done by dial access or by pressing the
PROGRAM button, if assigned.
3-12
Issue 3 March 1996
Abbreviated Dialing (AD)
Programming Personal Lists, Abbreviated
Dialing Buttons and Automatic Dialing Buttons
To program an entry in a Personal Number List, the user dials the Program
access code or presses the PROGRAM button, then dials the personal list number,
the Dial Code number, and the number to be stored (up to 24-digits), and then
presses either the # key or the AD button. Confirmation tone is heard when the
number is stored. While in the program mode, users can program all Personal
Number List entries, if desired. To exit the program mode, the user simply hangs
up.
To program an AD button administered to access a particular entry in the
Personal Number List, the user dials the Program access code or presses the
PROGRAM button, if assigned. The user presses the AD button, dials the desired
number (up to 24-digits), and presses the #. Confirmation tone is heard when the
number is stored. In the program mode, the user can program as many assigned
AD buttons (as well as Automatic Dialing buttons) as desired. To exit the
program mode, the user hangs up.
Only the System Manager and multi-appearance voice terminal users can
program special characters. Voice terminal users need PAUSE, MARK, WAIT,
INDEFINITE WAIT, and SUPPRESS buttons or a Function Entry button to program
special characters. Pressing a PAUSE, MARK, WAIT, INDEFINITE WAIT, or SUPPRESS
button programs the special character administered to the button. Pressing the
AD FUNCTION ENTRY button and then dialing 1, 2, 3, or 4 programs Pause, Wait,
Mark, or Suppress respectively. Special characters count as two toward the total
number of digits that can be stored in a list entry or button. See "Special
Characters" on page 3-10 for additional information.
Programming Group Lists
With G3V4 and later releases, voice terminal users can program the Group Lists
to which they are assigned as the designated user. For example, a department
secretary may be the designated user for a Group List created for the
department. Designated users are assigned (as Program Ext) per Group List on
the “Abbreviated Dialing Group List” form. Users who attempt to program group
lists for which they are not the designated user receive intercept tone.
The method a designated user will use to program a Group List is dependent
upon the access codes and buttons administered for the terminal and system.
The designated user can:
■
Program the Group List using the Program access code or AD Program
button (ABR_PROG) in conjunction with an Ab breviated Dialing (ABRV_DIAL)
button. In this case, the number to be programmed must be associated
with that AD button.
Issue 3 March 1996
3-13
Feature Descriptions
■
Program the Group List using the Program access code or AD Program
button (ABR_PROG) when an Abbreviated Dialing (ABRV_DIAL) button is not
available. In this case, the user can only program lists assigned (as List 1,
2 or 3) to the terminal he or she is using. Other lists for which the user is
the designated user cannot be programmed in this way.
Group Lists can only be programmed in this way if the “Ab br Dial
Programming By Assigned List” field is set to y on the “Feature-Related
System-Parameters” form.
■
Program the Group List using the AD Group List Program FAC, which is
available with G3V4 and later releases. When the AD Group List Program
FAC is used to program a group list, the user can program any list for
which they are specified as the designated user.
The following instructions describe how designated users program group lists
from their voice terminals. Group lists can also be programmed on the switch by
the System Administrator.
■
Programming the Group List With the AD Program Access Code or AD
Program Button With an Abbreviated Dialing Button
An Ab breviated Dialing button can be used by the designated user to
program the Group List number associated with that button. The user dials
the AD Program access code or presses the AD Program button. The user
then presses the AD button, dials the desired number, and then presses
the #. Confirmation tone is heard when the number is stored.
■
Programming the Group List With the AD Program Access Code or AD
Program Button (No Abbreviated Dialing Button)
The user dials the AD Program access code or presses the AD Program
button. The user then dials 1, 2, or 3 to select a Group List (administered
on their “Station” form) followed by the 2-digit List Entry Number of the
entry to be programmed. The user then dials the desired number, and
then presses the #. Confirmation tone is heard when the number is stored.
■
Programming the Group List With the AD Group List Program FAC
The user dials the AD Group List Program FAC. He or she then dials the
three, or four-digit Group List Number to select a Group List followed by
the two-digit List Entry Number of the entry to be programmed. The user
then dials the desired number, and then presses the #. Confirmation tone
is heard when the number is stored.
Considerations
Abbreviated Dialing provides easy access to selected numbers by decreasing
the number of dialed digits required to place the call. Instead of dialing the entire
number, the user merely dials a short code to access the desired number. The
system then dials the stored number automatically. For frequently called
numbers, an Ab breviated Dialing button or Automatic Dialing button can be
3-14
Issue 3 March 1996
Abbreviated Dialing (AD)
assigned, allowing the call to be placed by merely pressing the button. By
assigning a Privileged list of numbers, a user is allowed to place calls to selected
numbers that might otherwise be restricted.
Users can be assigned access to three AD lists. The three lists can be made up
of any combination of up to three Personal Lists, up to three Group Lists, the
System List, and the Enhanced List. A Personal List cannot be administered to an
attendant console.
A number stored in any list in the switch can contain up to 24 digits. A special
character used for Pause, Wait, Indefinite Wait, Mark, or Suppress counts as
2-digits.
A terminal or attendant cannot be removed if it is designated as the extension
number that is permitted to program a Group List.
Abbreviated dialing digits may be used after the call is connected to send digits
from the originator to other connected parties. Other parties may not use
abbreviated dialing buttons to send digits back to the originator. Pause
characters in abbreviated dialing strings may be ignored if used after the call is
connected, and may cause loss of digits when the total number of digits used
exceeds 36.
Security Measures
Privileged group, system and enhanced lists give access to calls from stations
that would otherwise be restricted.
Interactions
The following features interact with the "Abbreviated Dialing (AD)" feature.
■
Attendant Consoles
Automatic Dialing Buttons are not allowed on Attendant Consoles.
■
AUDIX Interface
When using an Ab breviated Dialing button to access AUDIX, the user’s
login and password may be assigned to the button.
■
Brid ged Call Ap pearance
A user, accessing Ab breviated Dialing while on a bridged call
appearance, accesses his or her own Abbreviated Dialing lists. The user
does not access the Abbreviated Dialing lists of the primary extension
associated with the brid ged call appearance.
Issue 3 March 1996
3-15
Feature Descriptions
A designated user permitted to program a Group List is not permitted to
program the Group List from the bridged call appearance of the
designated extension number.
■
Last Number Dialed
This feature places a call to the same number as called previously, even if
Abbreviated Dialing was used on the previous call.
If the previously called number was in an Abbreviated Dialing Privileged
List, and if the user is not normally allowed to dial the number because of
his or her Class of Restriction, Intercept Treatment is given when using
Last Number Dialed. To redial the number, the user must again use the
Abbreviated Dialing Privileged List.
■
Remote Access
Remote Access users cannot access Abbreviated Dialing.
Administration
Abbreviated Dialing is administered by the System Manager. However, an
Abbreviated Dialing Personal List can be programmed by either the System
Manager or the voice terminal user. With G3V4 and later releases, the Group List
can be programmed by a designated user or the System Manager.
The System Manager must establish a Personal Number List. For example,
during implementation, a voice terminal must first be assigned a Personal
Number List on the “Individual Voice Terminal” form. The list can be established
on the “Abbreviated Dialing Personal List” form or from the user’s voice terminal.
In order to use all members of a Personal List for an individual voice terminal, the
list must be modified to expand it to the maximum members for that list on the
Abbreviated Dialing List form.
The following items, if required, are set by the System Manager:
■
Feature Access Codes for List 1, List 2, and List 3, for accessing a
personal list. Also FAC for programming a personal or group list
■
Voice Terminal Assignments
— AD buttons, if desired
— AD Program button, if desired
— Automatic Dialing buttons, if desired
— Mark, Pause, Suppress, Wait and Function Entry buttons, if desired
— Access to as many as three lists
■
Data Module Assignments (Access to an Abbreviated Dialing list)
■
Abbreviated Dialing Lists
— Personal Number Lists
3-16
Issue 3 March 1996
Abbreviated Dialing (AD)
— Group Number Lists
— System Number List
— Enhanced Number List
— 7103A Group Number List
■
Wait Delay Interval (5 to 25 seconds)
■
Attendant Console Parameters
See DEFINITY Communications System Generic 3 Version 4 Implementation,
555-230-655 or DEFINITY Communications System Generic 3 V2/V3
Implementation, 555-230-653, for complete instructions for administering the
"Abbreviated Dialing (AD)" feature.
Hardware and Software Requirements
Additional tone detectors such as TN744C-Tone Detector/Call Classifier,
TN748C-Tone Detector, TN420C-Tone Detector, or TN2182-Tone
Clock/Detector/Generator may be required if the special wait character is used
frequently. See DEFINITY Communications System Generic 3 System
Description and Specifications, 555-230-206, for more specifics.
Optional software is required for the Enhanced Ab breviated Dialing list.
Issue 3 March 1996
3-17
Feature Descriptions
Add/Remove Skills
Feature Availability
This feature is available with all G3V3 and later versions with the "Expert Agent
Selection (EAS)" feature enabled.
Description
This feature allows agents using Expert Agent Selection (EAS) to add or remove
skills.
A skill is a talent or ability of an agent and a requirement of a caller that is
identified within the switch by a number. For example, if an agent has the ability
to speak English and Spanish, that agent could be assigned a Spanish speaking
skill that has a numerical identifier, such as 50. The agent can then add skill 50 to
his/her set of working skills. If a customer requires a Spanish-speaking agent, the
system can route the call to the agent(s) with that skill. Skills can be administered
for a vector directory number (VDN) and an ACD agent login ID, and can be
active for an ACD caller via vector commands. Each agent can have up to four
skills active at any one time.
NOTE:
In the EAS environment, agents must have at least one skill assigned to
them during a login session. Therefore, if an agent with only one skill tries to
remove that skill, the system does not remove the skill. Also, the system
does not allow an agent with four active skills to add a fifth skill.
This feature allows agents to add or remove a skill by dialing a feature access
code (FAC). Agents use one FAC to add a skill and another FAC to remove a
skill. Also, any voice terminal user with console permission can add or remove an
agent’s skill on behalf of the agent by entering the agent’s login ID.
Agents and supervisors can use queue-status indications, VuStats, or Call
Management System (CMS) or Basic Call Management System (BCMS)
information to determine if they need to add or remove a skill. When adding a
skill, the agent must specify if the skill is primary or secondary. A primary skill is
one that the agent answers before answering any secondary skills, if there are
calls in queue for both skills. Therefore, it is worth noting that adding or removing
a primary or secondary skill does impact how calls are distributed to an agent.
The system displays text to prompt the agent through the process of adding or
removing a skill (assuming the terminal is equipped with a display).
When an agent adds or removes a skill, the system displays on the voice terminal
(assuming the terminal is equipped with display) the updated set of skills. Each
skill number is preceded by either p for primary or s for secondary.
3-18
Issue 3 March 1996
Add/Remove Skills
If a supervisor with console permission adds or removes a skill for an agent, the
agent does not receive any notification that the change has taken place.
Feature History
This feature was available in the DEFINITY G2 Version 2 release with EAS.
Therefore, its addition to G3V3 and later releases fills a void in previous G3
releases. However, the feature has been enhanced in this release by the addition
of agent ability to designate a skill as primary or secondary when they add the
skill.
Considerations
A skill cannot be removed from an agent’s skill set if the agent is on a call for that
skill. A skill cannot be removed from an agent’s skill set if the agent is in the
After-Call-Work (ACW) state for that skill.
If a supervisor with console permission adds or removes a skill for an agent, the
agent does not receive any notification that the change has taken place. An
agent or other user does not need to be logged in for a skill to be added or
removed. Also, agents and users cannot add or remove a skill while on a call or
in ACW.
Interactions
■
Auto-Available Splits (AAS)
If an agent adds a skill that is administered as Auto-Available, the agent’s
login ID must have the “AAS” field set to y on the "Agent Login ID" form, or
the agent cannot add the skill.
■
BCMS
BCMS begins tracking the new skill as soon as it is ad ded. When an agent
removes a skill, the real-time agent information specific to that skill is
removed from the real-time reports. The data for the skill still appears on
the historical reports.
■
VuStats
Because VuStats displays information gathered by BCMS (whether BCMS
is enabled or not), the BCMS interaction mentioned above applies to
VuStats also.
Administration
EAS must be enabled on the “Feature-Related System-Parameters” form before
using the "Ad d/Remove Skills" feature.
Issue 3 March 1996
3-19
Feature Descriptions
Feature access codes (FACs) for adding and removing skills must be entered in
the “Feature Access Code” form. Also, for each class of restriction (COR), the
ability for users with that COR to add and remove skills must be enabled or
disabled. This is done on the “Class of Restriction” form. Console permissions
are administered on the “Class of Service” form.
Text for user-defined displays for the "Add/Remove Skills" feature are
administered on page 5 of the “Display-Messages Miscellaneous” form.
NOTE:
Skills are defined on the “Hunt Group” form. Each skill can be administered
on the ‘Vector Directory Number’ form or directly in vectors.
Hardware and Software Requirements
EAS is required.
3-20
Issue 3 March 1996
Administered Connections
Administered Connections
Feature Availability
Administered Connections is available with all Generic 3 releases except
G3vs/G3s ABP and replaces the Permanent Switched Calls feature of previous
System 75 releases and of DEFINITY Generic 1.
Description
Automatically establishes an end-to-end connection between two access/data
endpoints. The "Administered Connections" feature provides the following
enhanced capabilities.
■
Support of both permanent and scheduled connections
■
Auto Restoration (preserving the active session) for connections routed
over Software Defined Data Network (SDDN) trunks
■
Administrable retry interval (from 1 to 60 minutes) per Administered
Connection
■
Administrable alarm strategy per Administered Connection
■
Establishment/retry/auto restoration order based on administered priority
The status of an Administered Connection (disabled, connected, and so on) can
be displayed by entering the status administered-connection command from
the Management Terminal.
The endpoints which can be connected via the "Administered Connections"
feature are either access endpoints or data endpoints. Access endpoints are
nonsignaling trunks and data endpoints are devices that connect the switch to
data terminal/communication equipment. Throughout this section the term
endpoint is used to mean either data endpoint or access endpoint.
Access Endpoints
An access endpoint is either a nonsignaling channel on a DS1 interface or a
nonsignaling port on an Analog Tie Trunk circuit pack that is assigned a unique
extension. Since an access endpoint is nonsignaling, it will neither generate nor
respond to signaling. As a result, an access endpoint cannot be used as a
trunking facility (it cannot receive incoming calls or route outgoing calls). An
access endpoint is used primarily to support devices, switches, or services that
have a trunk interface but do not support signaling for the trunk. An access
endpoint may be designated as the originating (local) endpoint or destination
endpoint in an Administered Connection. The status of an access endpoint can
be displayed by entering the status access-endpoint command from the
Management Terminal.
Issue 3 March 1996
3-21
Feature Descriptions
If a data call/connection between two access endpoints is set up from a voice
station via the "Transfer" feature, the call can only be dropped (and the endpoints
freed) by busying out either one of the Access Endpoints or a trunk over which
the connection is routed (if one exists) from the Management Terminal. This is
required since neither of the endpoints can initiate a drop (access end points are
nonsignaling).
Typical Administered Connection Configurations
The "Administered Connections" feature allows a great amount of flexibility in
assigning the destination address of the connection. As a result, many different
configurations are possible with an Administered Connection. An Administered
Connection can be established between two endpoints on the same switch;
between two endpoints in the same private network, but on different switches; or
between an endpoint on the controlling switch and another endpoint off the
private network. In all configurations, the Administered Connection must be
administered on the same switch as the originating endpoint.
If the two endpoints of the Administered Connection are on two different switches
within a private network, normally, the connection will be routed through tie trunks
(such as ISDN-PRI, DS1 or analog tie trunks) and possibly intermediate switches.
However, if preferred, the connection can be routed through the public network.
The following are typical Administered Connection configurations and their
application examples:
■
A local data endpoint connects to a local or a remote access endpoint.
One example of this is an MPDM connecting to a T1 Multiplexer via a DS0.
■
A local access endpoint connects to a local/remote access endpoint.
Two examples are a DS0 cross-connect and a four-wire leased line
modem to a four-wire leased line modem connection via analog tie trunks.
■
A local data endpoint connects to a local/remote data endpoint.
One example is a connection between two 3270 data modules.
Establishment of Administered Connections
The originating switch will only attempt to establish an Administered Connection
if the following conditions exist:
a. the Administered Connection is enabled
b. the Administered Connection is due to be active (either a permanent
Administered Connection or the time of day requirements are satisfied if a
scheduled Administered Connection)
c. the originating endpoint is in the in-service/idle state
If the originating endpoint is not in-service/idle, no activity will take place for the
Administered Connection until the endpoint transitions to the desired state. The
3-22
Issue 3 March 1996
Administered Connections
destination address is used by the originating switch to route the connection to
the desired endpoint. When two or more Administered Connections are to be
established at the same time, they are established in priority order.
Administered Connection Establishment Retries
Administered Connection establishment attempts can fail for the following
reasons:
■
resources are unavailable to route to the destination
■
a required conversion resource is not available
■
access is denied. COR, FRL, BCC, or an attempt is made to route
voice-band-data over SDDN trunks in the 4ESS switch network (or other
public switch network)
■
incorrect destination address
■
destination endpoint is busy
■
other network or signaling failure
In the event of a failure, an error will be logged in the error log and an alarm will
be generated, if it is warranted by the alarming strategy. The reason an
Administered Connection has failed can be displayed by the System Manager
via the status administered-connection command. This information is also
contained in the error log.
As long as an Administered Connection is due to be active, continued attempts
to establish an Administered Connection will be made by the originating switch
unless the establishment attempt failed because of an administrative error (like a
wrong number) or service blocking condition (like outgoing calls barred).
Establishment attempts for Administered Connections that fail as a result of one
of these conditions will resume when the problem is resolved (that is,
Administered Connection administration has been changed). The frequency at
which failed establishment attempts are retried is determined by the
administered retry interval (1 to 60 minutes) of each Administered Connection.
Retries will be made after the retry interval has elapsed regardless of the
restorable attribute of the Administered Connection. If more than one
Administered Connection is to be retried at the same time, they will be retried in
priority order. When the customer changes the time of day on the switch, an
attempt will be made to establish all Administered Connections in the ‘waiting for
retry’ state.
Dropping an Administered Connection
Once established, an Administered Connection will remain active until one of the
following events occurs:
Issue 3 March 1996
3-23
Feature Descriptions
■
The Administered Connection is changed, disabled, or removed. (See the
“Administration” section for identification of which attributes, when
changed, will result in the dropping of an active Administered
Connection.)
■
The time of day requirements of a scheduled Administered Connection
are no longer satisfied.
■
One of the endpoints initiates dropping the connection. This could be a
result of a user initiated drop (in the case of a data endpoint),
maintenance activity resulting from an endpoint failure, or the busying out
of the endpoint or handshake failure. If the endpoints involved in an
Administered Connection are incompatible, the connection will
successfully connect before the handshake failure occurs.
NOTE:
Administered Connections between access endpoints will remain
connected even if the attached access equipment fails to
handshake.
■
An interruption (that is, facility failure) occurs in the path between the
endpoints involved in the Administered Connection.
No action is taken if an Administered Connection drops because it was
disabled/removed or is no longer due to be active. If an Administered
Connection drops because of changed Administered Connection attributes, an
immediate attempt will be made to establish the connection with the changed
attributes if it is still due to be active. Existing entries in the error/alarm log are
resolved if they no longer apply. If it can be determined that handshake failure
resulted in the drop ping of the connection, in the case of an Administered
Connection involving at least one data endpoint, no action will be taken for that
Administered Connection until the change administered-connection command
has been executed.
Administered Connection Failure:
Auto Restoration and Fast Retry
When an active (established) Administered Connection drops prematurely, either
auto restoration or fast retry will be invoked. It can be determined whether or not
auto restoration will be attempted for an active Administered Connection by
observing the contents of the restorable field displayed on the Status
Administered Connection screen.
Auto restoration will be attempted if the Administered Connection was optioned
for auto restoration and the connection was routed over SDDN trunks. During
restoration, connections are maintained between the switch and endpoint at both
ends of the connection. In addition to allowing the active session to be
maintained, this also provides a high level of security by prohibiting other
connections from intervening in active sessions. The ‘Auto Restoration’ feature
cannot guarantee restoration within a certain time period, but successful
3-24
Issue 3 March 1996
Administered Connections
restorations (involving remote endpoints on a G3i switch) must be completed
before the expiration of the 60-second endpoint holdover timer utilized during
restoration. If auto restoration is successful, the session that was active when the
failure occurred might be maintained (no guarantee). If the session is
maintained, the restoration is transparent to the user with the exception of a
temporary disruption of service while the restoration is in progress. A successful
restoration is reflected by the restored state on the Status Administered
Connection screen. The restored status will be displayed, even if the destination
endpoint was idle (that is, already dropped) when the restoration attempt arrived
at the destination node. (Although the restoration was successful, the data
session may not have been preserved.)
If the auto restoration function is not optioned or the Administered Connection is
not routed over SDDN trunk(s), the switch will immediately attempt to reestablish
the connection (fast retry). Fast retry will also be attempted if the originating
endpoint initiated the drop. In the event of a fast retry, connections are not
maintained on both ends. Fast retry will not be attempted for an Administered
Connection which was last established via fast retry, unless the Administered
Connection has been active for at least two minutes.
If the auto restoration or fast retry attempt fails to restore/reestablish the
connection, the connection will be dropped and the Administered Connection
will go into retry mode. Retry attempts will continue, at the administered retry
interval, as long as the Administered Connection is due to be active.
Interactions
The following features and functions interact with the "Administered Connections"
feature:
■
Abbreviated Dialing
Abbreviated dialing entries can be used in the “Destination Address” field.
Entries must comply with the restrictions of the dial plan.
■
AAR/ARS/Generalized Routing Selection (GRS)
These features may be used in the routing of an Administered Connection.
■
Busy Verification of Stations and Trunks
This feature does not apply to access endpoints because access
endpoints are used only for data.
■
Class of Restriction
A COR should be reserved for Administered Connection endpoints and
SDDN trunks. This would restrict endpoints, not involved in Administered
Connections, from connecting to SDDN trunks or endpoints involved in
Administered Connections.
■
Class of Service/Call Forwarding
Issue 3 March 1996
3-25
Feature Descriptions
An Administered Connection endpoint should be assigned a Class of
Service that will block call forwarding activation of the endpoint.
■
Data Call Setup
A Default Dialing destination should not be assigned to a data module that
is used in an Administered Connection.
■
Data Call Hotline
A hotline destination should not be assigned to a data module that is used
in an Administered Connection.
■
Digital Multiplexed Interface (DMI)
DMI endpoints can be used as the destination in an Administered
Connection. DMI end points do not have associated extensions, so they
cannot be used as the originator in an Administered Connection.
■
Facility Test Calls
The feature does not apply to access endpoints because an access
endpoint acts as an endpoint rather than as a trunk.
■
Hunting
A hunt group extension is not allowed to be used as the origination
extension of an Administered Connection.
■
Modem Pooling
If a conversion resource (pooled modem) is required in an Administered
Connection, one will be inserted. If no conversion resource is available,
the connection will be dropped.
■
Non-Facility Associated Signaling (NFAS) and D-Channel Backup
Auto Restoration for Administered Connections, initially routed over an
NFAS facility, may fail if the only backup route is over the facility on which
the backup D-channel is administered, since the backup D-channel may
not come into service in time to handle the restoration attempt.
■
Set Time Command
When the System Manager changes the system time via the set time
command, all scheduled Administered Connections are examined. If the
system time change causes an active Administered Connection to be
outside its scheduled period, the Administered Connection will be
dropped. If the time change causes an inactive Administered Connection
to now be within its scheduled period, the switch will attempt to establish
the Administered Connection.
Also, if any Administered Connection (scheduled or continuous) is in the
retry mode and the system time changes, the switch will attempt to
establish the Administered Connection immediately.
■
3-26
CDR
Issue 3 March 1996
Administered Connections
For an Administered Connection that uses a trunk which has CDR
enabled, the origination extension of the Administered Connection will be
used as the originator of the call.
CDR is not available for access endpoints.
■
System Measurements
Access endpoints are not measured. All other trunks in an Administered
Connection are measured as usual.
■
Terminal Dialing
It is recommended that the terminal dialing capability be turned off for
data modules involved in an Administered Connection.
NOTE:
This will stop call processing related messages (INCOMING
CALL,...) from being displayed on the terminal.
■
Trunk Groups
In order for auto restoration to be invoked, an Administered Connection
must be routed over SDDN trunks. Since a successful restoration
depends on there being an SDDN path over which to route the restoration
attempt, some SDDN trunks should be kept idle to be used in the event of
failure for restoration. SDDN trunk group usage should be restricted to
Alternating Current (AC) related traffic.
Administration
Each Administered Connection is administered by the System Manager. The
following items require administration.
■
Endpoints
If an Administered Connection involves local endpoints, the endpoints
must be administered before the Administered Connection using those
endpoints can be administered. An endpoint cannot be removed if it is
involved in a locally administered Administered Connection, or if it is
currently involved in an active Administered Connection. If the user
desires to change any of the translation data associated with an endpoint
(except for the “Name” field which may be changed at any time) that is
involved in an active Administered Connection, the Administered
Connection must first be disabled or removed.
■
Administered Connection
An Administered Connection must be administered on the same switch as
the originating endpoint. The System Manager may change the attributes
of an Administered Connection at any time, but not all changes take effect
immediately. These attributes are as follows (included in each description
is a statement as to whether or not changes take effect immediately):
Issue 3 March 1996
3-27
Feature Descriptions
— Originating Address — The address of the originating endpoint is
its local extension on the originating switch. When this attribute is
changed for an active Administered Connection, the connection will
be dropped and reestablished using the new originating address.
— Destination Address — The destination address is used to route
the Administered Connection to the desired destination. When this
attribute is changed for an active Administered Connection, the
connection will be dropped and reestablished using the new
destination address.
— Enable — The “Enable” field allows the System Manager to specify
whether the system should attempt to establish the connection
when it is due to be active. Answering yes to the enable option
indicates that the system should be established when the
Administered Connection is due to be active. Answering no
indicates that the System Manager does not want the Administered
Connection to be considered for activation at this time (that is, held
for future use). A disabled Administer Connection is displayed
along with the other Administered Connections administered locally
in response to the list administered-connection command. A
disabled Administered Connection may be enabled at any time.
Since Administered Connection administration is done on the
originating switch, disabling an Administered Connection can only
be done on the originating switch.
If an Administered Connection is currently active, answering no
causes the Administered Connection to be dropped immediately. If
an Administered Connection is disabled, answering yes will cause
the originating switch to attempt to establish the connection
immediately if the Administered Connection is due to be active. The
disabling and enabling of an Administered Connection after an
attribute of the Administered Connection has been changed
guarantees that the change will take effect immediately.
— Name — A one through 15 character long, optional “Name” field is
provided to allow for additional identification information. Changing
this field has no effect on the Administered Connection connection.
— Authorized Time of Day — An Administered Connection may be
continuous (permanent) or scheduled. Scheduled Administered
Connections are described by indicating the days of the week, start
time, and the duration for which the Administered Connection is to
be active. The modification of any of the attributes associated with
the authorized time of day will not affect the current status of an
Administered Connection unless the change results in activating or
deactivating an Administered Connection.
— Priority — The System Manager can specify the priority of a given
Administered Connection. This priority is used to determine the
order in which Administered Connections are established if two or
more Administered Connections are due to be active at the same
time. The “Priority” field allows the user to specify a number
3-28
Issue 3 March 1996
Administered Connections
between one and eight (with one being the highest and eight being
the lowest). Changes to the priority attribute have no effect on an
active Administered Connection.
— Auto Restoration — The System Manager may specify whether an
attempt should be made to restore an Administered Connection,
via the ‘Auto Restoration’ feature, if the connection is dropped due
to failure and the connection was routed over SDDN trunk(s).
Reestablishment (retry) of dropped connections is attempted
regardless of the value specified in this field. This field has no effect
on Administered Connections routed over non-SDDN trunks. The
System Manager must disable and enable an active Administered
Connection to have changes to this attribute take effect.
— Retry Interval — The System Manager must specify a retry interval
of 1 to 60 minutes. The default is two minutes. This interval is the
number of minutes waited before a retry is attempted. When this
field is changed, the new interval will be used for the next retry. An
Administered Connection, which is in retry mode when this field is
changed, will retry after the old interval has elapsed and then use
the new interval for the next retry time. Twenty-three of the
Administered Connections will be restored within the required time.
The remaining Administered Connections will be restored, but after
the time limit.
— Alarm Type — An alarm type of none, warning, minor or major
must be chosen. The default will be warning. None indicates that
no alarms will be generated on establishment or restoration failure.
A choice of warning will cause alarms to be generated and logged
in the alarm and error log. A minor or major indication will also
cause alarms to be generated and logged in the alarm and error
log and forwarded to an Operations Support System such as
INADS if OSS is administered.
Changing this field to none will cause an existing alarm to be
cleared. Changing the field to one of the other values will cause the
upgrading or the downgrading of an existing alarm.
— Alarm Threshold — The “Alarm Threshold” field indicates the
number of consecutive failures (1 to 10) that must occur before an
Administered Connection alarm is generated. Entering 1 in this field
will cause alarms to be generated immediately upon failure to
establish or reestablish an Administered Connection.
Changes to this field take effect immediately. A comparison of the
new value and the current retry count will be made to determine if
an alarm should be generated or possibly cleared due to the
change.
■
Access Endpoint
The access endpoint has the following attributes which must be
administered:
Issue 3 March 1996
3-29
Feature Descriptions
— Extension — This is a unique one- to five-digit identifier, consistent
with the current dial plan, by which this access endpoint is
addressed.
— Port — This is the port address of the DS1 or analog tie trunk port.
A DS1 trunk can be used regardless of the signaling mode of the
DS1 circuit pack.
— Name — This can be any alphanumeric string (up to 10
characters) representing a name that is useful to the customer.
— Communication Type — A communication type of 64K data, 56K
data, or voice-band data must be assigned. An access endpoint
on an analog tie trunk port is restricted to a communication type of
voice-band data. In addition, a communication type of 64K is not
allowed for access endpoints on DS1 circuit packs administered for
robbed-bit signaling.
— COR — A Class of Restriction may be administered for each
access endpoint.
— COS — A Class of Service may be administered for each access
endpoint. Class of Service administration should be used to block
call forwarding activation of an endpoint.
Hardware and Software Requirements
Hardware requirements vary depending on the type of Administered Connection
desired. The following hardware may be required for Administered Connections:
■
■
■
■
■
Access Endpoint Circuit Packs — TN767 DS1 Interface circuit pack
(TN464B/C/D support A-law), TN760B Analog Tie Trunk (TN760D
supports A-law).
Data Endpoint Circuit Packs — TN726 Data Line or TN754 Digital Line
(TN413, TN754B support A-law).
Data Modules — 700A/700D PDM or MPDM, 700B/700C/700E TDM or
MTDM, 7400D series voice terminal with DTDM, PC/PBX, 510D, 515BCT.
Trunk Circuit Packs — TN767 DS1 Interface circuit pack (TN464B/C/D
support A-law), TN760 Analog Tie Trunk (TN760D supports A-law).
TN758 Pooled Modem circuit pack.
No additional software is required.
3-30
Issue 3 March 1996
Administrable Language Displays
Administrable Language Displays
Feature Availability
This feature is available with Generic G3i-Global and all Generic V2 and later
releases.
The user-defined display language option is only available with the Generic V2
and later releases.
Description
There is a set of messages that appear on a DCP/ISDN-BRI Station/Attendant
users set that provide call related information.
The "Administrable Language Displays" feature allows 40-character display
station users or an attendant user to select a display language for these
messages. This display language selection is made via administration; with the
options being English (default), French, Italian, or Spanish. Note that the
messages themselves do not change, only the wording that is used to present
the message is changed.
The Generic V2 and later releases allow the addition of one user customized
language display message set to the system. This additional display message
set is entered into the system via administration by either a customer or an AT&T
in-country partner and is accessed by a user as their display language
preference by selecting the user defined display language option.
Feature Displays
This section shows the English, French, Italian, and Spanish language display
message sets subdivided by feature. Since none of the feature functions are
modified, no explanation of the feature is made.
The user-defined language display message set is the user customized
language display message set that was added to the system via administration.
If user-defined is selected as the display language preference and the
user-defined language display message set has not been entered into the
system, all display messages appear as a string of asterisks.
When the time is displayed, only the English display set uses the AM/PM
notation, all others use the 24 hour clock.
Automatic Wakeup
The following displays are associated with the "Automatic Wakeup" feature.
Issue 3 March 1996
3-31
Feature Descriptions
■
‘‘AUTO WAKEUP - Ext: xxxxx Time: --:-- xM’’ (English)
— French - ‘‘REVEIL AUTO. - POSTE: xxxxx HEURE: --:--’’
— Italian - ‘‘SERVIZIO SVEGLIA - Tel: xxxxx Ora: --:--’’
— Spanish - ‘‘DESPERT AUTOMA - EXT: xxxxx HORA: --:--’’
■
‘‘INVALID EXTENSION - TRY AGAIN’’ (English)
— French - ‘‘NUMERO DE POSTE EST ERRONE - REESSAYER’’
— Italian - ‘‘NUMERO ERRATO - RIPETERE’’
— Spanish - ‘‘EXTENSION NO VALIDO - INTENTE DE NUEVO’’
■
‘‘WAKEUP ENTRY DENIED - INTERVAL FULL’’ (English)
— French - ‘‘DEM. REVEIL REFUSEE - INTERVALLE PLEIN’’
— Italian - ‘‘SVEGLIA NON ATTIVATA - ORARIO OCCUP’’
— Spanish - ‘‘ENTRADA DENEGADA - INTERVALO COMPLETO’’
■
‘‘WAKEUP ENTRY DENIED - NO PERMISSION’’ (English)
— French - ‘‘DEM. REVEIL REFUSEE - SANS AUTORISATION’’
— Italian - ‘‘SVEGLIA NON ATTIVATA - NON PERMESSO’’
— Spanish - ‘‘ENTRADA DENEGADA - SIN PERMISO’’
■
‘‘WAKEUP ENTRY DENIED - SYSTEM FULL’’ (English)
— French - ‘‘DEM. REVEIL REFUSEE - ENCOMBREMENT’’
— Italian - ‘‘SVEGLIA NON ATTIVATA - CONGESTIONE’’
— Spanish - ‘‘ENTRADA DENEGADA - SISTEMA COMPLETO’’
■
‘‘WAKEUP ENTRY DENIED - TOO SOON’’ (English)
— French - ‘‘DEM. REVEIL REFUSEE - TROP TOT’’
— Italian - ‘‘SVEGLIA NON ATTIVATA - TROPPO PRESTO’’
— Spanish - ‘‘ENTRADA DENEGADA - MUY PRONTO’’
■
‘‘WAKEUP REQUEST CANCELED’’ (English)
— French - ‘‘DEMANDE DE REVEIL EST ANNULEE’’
— Italian - ‘‘RICHIESTA SVEGLIA CANENTRYATA’’
— Spanish - ‘‘SOLICITUD DE DESPERTADOR CANCELADA’’
■
‘‘WAKEUP REQUEST CONFIRMED’’ (English)
— French - ‘‘DEMANDE DE REVEIL EST CONFIRMEE’’
— Italian - ‘‘RICHIESTA SVEGLIA CONFERMATA’’
— Spanish - ‘‘SOLICITUD DE DESPERTADOR CONFIRMADA’’
■
3-32
‘‘Wakeup Call’’ (English)
Issue 3 March 1996
Administrable Language Displays
— French - ‘‘APPEL DE REVEIL’’
— Italian - ‘‘Serv. Sveglia’’
— Spanish - ‘‘Despierte’’
ASAI
The following display is associated with the "CallVisor Adjunct/Switch
Applications Interface (ASAI)" feature.
■
‘‘You have adjunct messages’’ (English)
— French - ‘‘MESSAGES SUPPLEMENTAIRES’’
— Italian - ‘‘MESSAGGI AGGIUNTIVI’’
— Spanish - ‘‘TIENE MENSAJES ADICIONALES’’
Busy Verification of Stations and Trunks
Table 3-2 lists the displays associated with the "Busy Verification of Terminals
and Trunks" feature.
Table 3-2.
Busy Verification of Stations and Trunks Displays.
English Display
French Display
Italian Display
Spanish Display
‘‘ALL MADE BUSY’’
‘‘TOUS OCC.’’
‘‘TUTTI OCCUPATI’’
‘‘TODAS OCUPADAS’’
‘‘BRIDGED’’
‘‘EN DERIVATION’’
‘‘OCCUPATO’’
‘‘PUENTEADA’’
‘‘DENIED’’
‘‘INTERDIT’’
‘‘NON PERMESSO’’
‘‘DENEGADO’’
‘‘INVALID’’
‘‘ERRONE’’
‘‘NON VALIDO’’
‘‘NO VALIDO’’
‘‘NO MEMBER’’
‘‘AUCUN MEMBRE’’
‘‘NESSUN ELEMENTO’’
‘‘NINGUN MIEMBRO’’
‘‘OUT OF SERVICE’’
‘‘HORS SERVICE’’
‘‘FUORI SERVIZIO’’
‘‘FUERA SERVICIO’’
‘‘RESTRICTED’’
‘‘RESTREINT’’
‘‘RISTRETTO’’
‘‘RESTRINGIDO’’
‘‘TERMINATED’’
‘‘TERMINE’’
‘‘TERMINATO’’
‘‘TERMINADO’’
‘‘TRUNK SEIZED’’
‘‘CIRCUIT SAISI’’
‘‘GIUNZIONE IMP.’’
‘‘ENLACE OCUPADO’’
‘‘VERIFIED’’
‘‘VERIFIE’’
‘‘VERIFICATO’’
‘‘VERIFICADO’’
Call Appearance Designation
For each of the display language options, the display to indicate call appearance
designation appears as:
■
‘‘a =’’ (English)
Call appearance buttons are designated on the display by a lower case
letter (a through z for the first 26 call appearances then A through Z) in
position 1, followed by an ‘‘=.’’
Issue 3 March 1996
3-33
Feature Descriptions
Call Detail Record
The following display is associated with the "Call Detail Recording (CDR)"
feature.
■
‘‘CDR OVERLOAD’’ (English)
— French - ‘‘SURCHARGE EDA’’
— Italian - ‘‘SVRACCARICO DAC’’
— Spanish - ‘‘SOBRECARGA DAT’’
Call Progress Feedback
Table 3-3 lists the call progress displays.
Table 3-3.
Call Progress Feedback Displays
‘‘English Display’’
(stands for)
‘‘French Display’’
(stands for)
‘‘Italian Display’’
(stands for)
‘‘Spanish Display’’
(stands for)
‘‘busy’’
(Extension Busy,
Intrusion Not Allowed,
Call Waiting Not Allowed)
‘‘OCCUPE’’
(Occupe)
‘‘occ’’
(Occupato)
‘‘OCUPADA’’
(Ocupada)
‘‘busy(I)’’
(Extension Busy,
Intrusion Allowed,
Call Waiting Not Allowed)
‘‘OCC.(E)’’
(Entree ligne
occupe)
‘‘occ(I)’’
(OccupatoIntrusione)
‘‘OCUP(I)’’
(Ocupadaintrusion)
‘‘ringing’’
(Extension Ringing)
‘‘SONNE’’
(Libre)
‘‘libero’’
(Libero)
‘‘LIBRE’’
(Libero)
‘‘wait’’
(Extension Busy,
Intrusion Not Allowed,
Call Waiting Allowed)
‘‘ATTENTE’’
(Attente)
‘‘auat’’
(Autoattesa)
‘‘ESPERA’’
(Espera)
‘‘(I) wait’’
(Extension Busy,
Intrusion Allowed,
Call Waiting Allowed)
‘‘(E) ATTENTE’’
(Entree ligne
attente)
‘‘(I) auat’’
(IntrusioneAutoattesa)
‘‘(I) ESPERA’’
(Intrusion,
en espera)
3-34
Issue 3 March 1996
Administrable Language Displays
Class of Restriction
Table 3-4 lists displays associated with the "Class of Restriction (COR)" feature.
Table 3-4.
Class of Restriction Displays
Restriction
‘‘English Display’’
‘‘French Display’’
‘‘Italian Display’’
‘‘Spanish Display’’
Toll
‘‘TOLL’’
‘‘INT.’’
‘‘TASS’’
‘‘TARF’’
Full
‘‘FULL’’
‘‘COM.’’
‘‘DISB’’
‘‘LLEN’’
No Restrictions
‘‘NONE’’
‘‘AUC.’’
‘‘ABIL’’
‘‘NING’’
Origination
‘‘ORIG’’
‘‘DEP.’’
‘‘ORIG’’
‘‘ORIG’’
Outward
‘‘OTWD’’
‘‘SOR.’’
‘‘USCN’’
‘‘SALI’’
Date/Time Mode and Formats
The following displays are associated with the ‘Date & Time’ feature.
If the time is not available:
■
English - ‘‘SORRY, TIME UNAVAILABLE NOW’’
■
French - ‘‘HEURE ET DATE INDISPONIBLES’’
■
Italian - ‘‘ORA E DATA TEMP. NON DISPONIBILI’’
■
Spanish - ‘‘HORA Y FECHA NO DISPONIBLES AHORA’’
If the time is available, Screen 3-1 lists the English date/time mode and formats
attributes; Screen 3-2 lists the French, Italian, Spanish, or user-defined date/time
mode and formats attributes;
— English