AT&T 1987 User Manual

555-520-200

Issue 1, June 1987

AT&T System 25

Reference Manual

© 1987 AT&T
All Rights Reserved

Printed in USA

TO ORDER COPIES OF THIS DOCUMENT REFER TO DOCUMENT NUMBER 555-520-200.

Contact: Your AT&T sales representative or

Call: 800-432-6600, Monday to Friday between 7:30 am

and 6:00 EST, or

Write: AT&T Customer Information Center

2855 North Franklin Road
P.O. Box 19901
Indianapolis, Indiana 46219

Every effort was made to ensure that the information in this document was complete and accurate at
the time of printing. However, information is subject to change. This document will be reissued
periodically to incorporate changes.

Reference Manual

Prepared by System 25

Document Development Group and the

AT&T Documentation

Management Organization

FCC NOTIFICATION AND REPAIR INFORMATION

AT&T SYSTEM 25

This telephone equipment is registered with the Federal Communications Commission (FCC)
in accordance with Part 68 of its Rules.
following:

MEANS OF CONNECTION

Connection of this telephone equipment to the nationwide telecommunications network shall
be through a standard network interface USOC RJ21X jack. Connection to private line

network channels requires USOC RJ2GX jack for tie lines or USOC RJ21X jack for off­premises station lines.

NOTIFICATION TO THE TELEPHONE COMPANY

If the system is to be connected to off-premises stations (OPSs), you must notify the
telephone company of the OPS class of service, OL13C, and the service order code, 9.OF.

These can be ordered from your telephone company.

In compliance with the Rules, be advised of the

Upon the request of the telephone company, inform them of the following:

—

The Public Switched Network “lines” and the Private “lines” to which you will
connect the telephone equipment.

—

The telephone equipment’s “registration number”
(REN) from the label on the equipment.

—

For private line connections, provide the facility interface code, TL31M for tie lines.
You must also specify the service order code, 9. OF.

—

The quantities and USOC numbers of the jacks required.

—

For each jack, provide the sequence in which lines are to be connected; the type lines
and the facility interface code and the ringer equivalence number by position, when
applicable.

This telephone equipment should not be used on coin telephone lines. Connection to party
line service is subject to state tariffs.

REPAIR INSTRUCTIONS

If you experience trouble with this telephone equipment, contact the AT&T Business
Customer Service Center on 1-800-242-2121. The telephone company may ask that you
disconnect this equipment from the network until the problem has been corrected or until
you are sure that this equipment is not malfunctioning.

and “ringer equivalence number”

RIGHTS OF THE TELEPHONE COMPANY

If your telephone equipment causes harm to the telephone network, the telephone company
may discontinue your service temporarily.

If possible, they will notify you in advance. But
if advance notice isn’t practical, you will be notified as soon as possible. You will be
informed of your right to file a complaint with the FCC.

Your telephone company may make changes in its facilities, equipment, operations, or
procedures that could affect the proper functioning of your equipment. If they do, you will
be notified in advance to give you an opportunity to maintain uninterrupted telephone

service.

HEARING AID COMPATIBILITY

The voice terminals described in this manual are compatible with inductively coupled
hearing aids as prescribed by the FCC.

FCC REGISTRATION INFORMATION

Registration Number

Ringer Equivalence

AS593M-71565-MF-E

0.5A

Network Interface RJ21X or RJ2GX

PRIVATE LINE SERVICE

Service Order Code

9.OF

Facility Interface Code

● Tie Lines TL31M

● Off-Premises Stations OL13C

FCC WARNING STATEMENT

Federal Communications Commission (FCC) Rules require that you be notified of the
following:

● This equipment generates, uses, and can radiate radio frequency energy and, if

not installed and used in accordance with the instruction manual, may cause
interference to radio communications.

● It has been tested and found to comply with the limits for a Class A computing

device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to
provide reasonable protection against such interference when operated in a
commercial environment.

● Operation of this equipment in a residential area is likely to cause interference in

which case the user at his or her own expense will be required to take whatever
measures may be required to correct the interference.

DANGER

The AT&T System 25 cabinets are not user serviceable.
Some voltages inside the cabinets are hazardous. This

equipment is to be serviced only by qualified technicians.

CONTENTS

SECTION l—OVERVIEW

SECTION 2—FEATURES AND SERVICES

SECTION 3—FUNCTIONAL DESCRIPTION

SECTION 4—HARDWARE DESCRIPTION

SECTION 5—TECHNICAL SPECIFICATIONS

SECTION 6—ENVIRONMENTAL REQUIREMENTS

SECTION 7—PARTS INFORMATION

SECTION 8—REFERENCE DOCUMENTATION

SECTION 9—GLOSSARY

SECTION 10—INDEX

SECTION 1—OVERVIEW

This reference manual provides general technical information on AT&T System 25 (System

25). It includes a description of the system, its hardware and software, features and
services, environmental requirements, and technical specifications. This manual is intended
to serve as an overall technical reference for System 25.

This manual replaces AT&T System 25 Reference Manual (555-50-200, Issue 1), which
covered Release 1 Version 1 (RIV1 ) of System 25.
coverage plus complete information on R1V2, a more powerful and versatile configuration of
the system.
particularly in the area of networking.

● The Virtual Facilities addition enhances the customer’s outgoing network

R1V2 provides new features and services that enhance system operation,

Here are some of the improvements:

capabilities.

● The AT&T STARLAN NETWORK (STARLAN NETWORK) Access feature provides

connectivity between System 25 and an associated STARLAN NETWORK.

●

Switched Loop Attendant Console operation makes the handling of incoming calls

from the network more efficient than in RIV1.

● With the Tandem Trunking feature, tie trunks can be used to call through System 25

to reach another switching system (CO or PBX).

● New voice terminals are provided for meeting specific system user needs.

This new issue contains the original

● A new voice feature, Last Number Dialed, is added, and existing voice features are

improved.

●

Data services are enhanced with new options for placing and controlling calls.

Both RIV1 and R1V2 of System 25 are described in this manual. Unless specifically marked
as “VI” or “V2”, all of the information pertains to both versions. VI information applies
only to RIV1 systems; V2 information applies only to R1V2 systems.

Organization

The manual is divided into 10 Sections. The remaining Sections are as follows:

● SECTION 2–FEATURES AND SERVICES

● SECTION 3–FUNCTIONAL DESCRIPTION

● SECTION 4–HARDWARE DESCRIPTION

●

SECTION 5–TECHNICAL SPECIFICATIONS

●

SECTION 6–ENVIRONMENTAL REQUIREMENTS

● SECTION 7–PARTS INFORMATION

● SECTION 8–REFERENCE DOCUMENTATION

● SECTION 9–GLOSSARY

● SECTION 10–INDEX

1-1

System 25 Description

System 25 (Figure l-l) is an advanced digital switching system that integrates voice and
data communications. It not only provides the features of a state-of-the-art PBX, but goes a
step further by allowing data to be switched point-to-point without first being converted to
analog format.

This capability can be used to set up connections between data terminals,

word processors, personal computers, and host computers.
System 25 uses intelligent port circuits equipped with distributed network processor

elements to provide (essentially) nonblocking voice and data switching.
Voice communications features combine traditional telephone features, such as Call Transfer

and Hold, with advanced features, such as Individual and Group Call Coverage, Hands-Free­Answer On Intercom, and Speed Dialing (see Section 2, “Features and Services”).

Data communications features provide switched data connections supporting transmission of
voice and data over Premises Distribution System wiring. Data connections can be made
between two digital data modules (asynchronous data units), two analog modems, or between
an analog modem and a digital data module.

Release 1 Version 2 (R1V2) also provides access

to STARLAN NETWORKs.
The system has data modules that provide an RS-232 interface for full duplex, asynchronous,

transmission of data up to 19,200 bps, and an integrated 212A-compatible modem pool
resource.

System 25 supports the following:

● Trunk and Network Facilities–Dual Tone Multifrequency (DTMF) and Dial Pulse

Signaling on incoming and outgoing trunks (dial pulse only on DID trunks).

—

Loop Start (LS)

—

Ground Start (GS) (Strongly Preferred over Loop Start in most installations)

—

Tie Trunks (Type I and Type I Compatible E&M, Type V Simplex)

—

Direct Inward Dialing (DID)

● Voice Terminals – Single-Line Touch-Tone, Single-Line Rotary (V2), MET, and

MERLIN®

● Data Facilities

—

Digital Data End Points – RS-232 Interfaces via Asynchronous Data Units

—

Analog Data End Points — Tip/Ring-Type Modem Interfaces

—

STARLAN NETWORK Access (V2 only).

● Networking Capability

—

Tie Trunks

—

Tandem Trunking

—

Endpoint in Electronic Tandem Network (Tributary only, not Satellite)

—

Endpoint of Enhanced Private Switched Communications Services (EPSCS)

—

Endpoint of Tandem Tie Trunk Network (TTTN)

—

Endpoint of Common Control Switching Arrangement (CCSA).

1-2

EMERGENCY
TRANSFER
UNIT

SINGLE-LINE
VOICE

TERMINALS

MULTILINE
VOICE
TERMINALS

DIRECT TRUNK
ATTENDANT
CONSOLE OR
SWITCHED LOOP
ATTENDANT
CONSOLE

ATTENDANT
DIRECT
EXTENSION
SELECTOR
CONSOLE

-48V DC

ANALOG

HYBRID

HYBRID

HYBRID

DIGITAL SWITCH

COMMON
CONTROL
COMPLEX

SWITCHING

NETWORK

(PORTS)

SYSTEM ADMINISTRATION

RS-232C

RS-232C

RS-232C

ANALOG FACILITIES

DATA

ANALOG

TERMINAL
OR

ADVANCED ADMINISTRATION
PC TERMINAL

ASYNCHRONOUS
DATA

UNIT (ADU)

MODEM

TAPE

BACKUP

UNIT

SMDR
OUTPUT
DEVICE

TRUNK FACILITIES

l DID

l

FX, WATS (LOOP/GROUND START)

l TIE

l

CO (LOOP/GROUND START)

l

PAGING SYSTEMS

RS-232C

RS-232C

HOST COMPUTERS
TERMINALS

STARLAN
NETWORK
WORKSTATIONS

STARLAN
NETWORK
PRINT & FILE
SERVICES

STARLAN
NETWORK
HOSTS

STARLAN
NETWORK
GATEWAY

ANALOG

AUXILIARY TRUNKS

Figure 1-1. System 25 Block Diagram

1-3

.

MUSIC SOURCE

. EXTERNAL ALERTS

.

DELAY ANNOUNCEMENT

.

DICTATION EQUIPMENT

.

PAGING SYSTEMS

.

DICTATION EQUIPMENT

Call Handling Capabilities

System 25 can be arranged as a stand-alone system or can be part of a private network. The

system provides 256 ports to support the following:

● 115 simultaneous two-party conversations

● Traffic Handling Capacity of 4140 CCS/Hour (Trunking Limited)

● Busy Hour Call Capacity of 2500 calls (DTMF Register Limited)

● Up to 104 trunk ports including Central Office (CO), DID, Tie, Foreign Exchange

(FX), Wide Area Telecommunications Service (WATS), and 800 Service

● An Auxiliary Trunk interface for paging (Vl and V2) and dictation systems (V2).

● Up to 240 ports that support a combination of the following:

—

Up to 200 ports for voice terminals and auxiliary feature port equipment.

—

Up to 104 data ports providing RS-232C connections to data terminals,
personal or multiport computers.

Refer to Hardware and Software Parameters as provided in “Technical Specifications”
(Section 5) for detailed specifications.

Safety

System 25 meets all requirements found in Underwriters Laboratories Standard for

Telephone Equipment (1459).

Business Communications Needs

The remainder of this Section describes how System 25’s R1V2 features may be used to
satisfy a customer’s communications needs.

This material may be thought of as the reverse

of the “Features and Services” section which follows.

The business communications capabilities of the majority of small businesses with more

than thirty phones are provided by a Private Branch Exchange (PBX). System 25 is a PBX

designed to meet the business communications needs of customers in the 30 to 150 station

range.

The communications needs of most business customers may be broken down into five basic
categories. Customer experience has shown that a PBX needs to provide–

● Prompt handling of incoming calls to maximize revenue opportunities and client

satisfaction,

● Ease of access to and cost control of outgoing calls over public network and private

facilities,

● Easy movement of calls between on-premises phones and between on-premises and

off-premises phones,

● Sharing of data between PCs and/or host computers and data terminals, and

● Growth and rearrangement of facilities.

The following pages outline System 25’s outstanding ability to provide these services.

1-4

Incoming Business Communications

Successful call termination is the key to capturing all incoming communications associated
with revenue issues, client inquiries, decision data, etc. Call termination involves identifying
the called party and routing the call to a primary or secondary answering position. System
25 provides powerful tools for both call screening and call termination.

● Attendant Consoles allow one or two attendants to answer, screen, and steer

incoming calls using either Direct Trunk or Switched Loop operation.

With
attendant operation, incoming calls can be screened and forwarded to the appropriate
party for resolution, messages taken for absent clients, or forwarded to alternate
locations. Calls may arrive over any of the network facilities described in later
sections of these notes.

● Direct Inward Dialing allows incoming callers to reach specific individuals or

facilities without attendant assistance. This allows specific numbers to be advertised

for direct customer access to brokers, emergency services, etc. over a shared pool of

DID trunks.

● Direct Group Calling (DGC) allows incoming calls to be directed to a specific group

of stations.

Calls to a DGC group hunt for an idle station in a circular manner,

starting at the station following the last one called. If all group members are busy,

calls are queued and can be sent to a delay announcement. A DGC group can
terminate calls to sales, services, computer, announcement, etc. over either ordinary
CO trunks or DID trunks.

● Personal Lines provide dedicated outside lines for multiline voice terminal users and

are accessed via a dedicated button for both incoming and outgoing service. Up to
sixteen terminals may share a Personal Line with up to four parties simultaneously
off-hook. A personal line provides direct access to brokers, emergency service, etc.
over a dedicated loop start or ground start trunk.

Frequently, the called party is not available to handle an incoming call. System 25 provides a
number of methods for redirecting incoming calls to alternate resources.

● Call Following allows users who are away from their phone to receive calls at

another phone.

25 voice terminal and receive their calls at that terminal.

Users may login their Personal Dial Code (PDC) at any other System

This feature supports

roving personnel and shared office space for company staff.

● Call Coverage allows calls that are not answered within a specified number of rings

to be redirected to an individual covering station and/or a group of covering stations.
This is especially useful for Boss-Secretary arrangements, staff backup, and message
service.

This feature is versatile enough to permit suitable alternate answering
arrangements for virtually every level of employee. Special features, such as the
Send All Calls feature, which routes a user’s calls directly to covering station(s),
accommodate the day-to-day variations that occur in an employee’s work schedule.

● Station Hunting provides automatic redirection of incoming calls to an idle member

of a hunt group when the called party is busy.

l Call Pickup allows a user to answer a call ringing at another terminal. Directed Call

Pickup allows a user to answer a call ringing at any terminal by dialing the call
pickup code and the PDC of the ringing station.

Group Call Pickup permits calls to

any other terminal in the call pickup group to be answered by dialing the group call

pickup code. With Call Pickup, users do not have to leave their phone to answer
other’s calls. This feature is especially useful for local coverage in group offices not

1-5

supported by secretarial service and equipped with economical single-line phones.

When alternate resources are not available to handle an incoming call, System 25 provides
for attendant handling of the call utilizing camp-on, redirection and/or message service.

● Camp-On allows the attendant to extend an outside call to a busy station. A burst of

tone is heard at the called station to notify the user of the camped-on call. The
caller is placed on hold and hears music-on-hold, if available. When the user hangs
up, the camped-on call begins ringing immediately. Only one call may be camped on
at a time. The Return Coverage on Busy feature returns unanswered camped-on calls

to the attendant for service after a specified interval.

● Return Coverage on Don’t Answer returns unanswered attendant-extended calls for

additional service (redirection/messaging).

● Messaging Service supports activation of an LED at the called station to indicate

that the attendant, message desk, or another station has a message for the user.

Special arrangements are needed to handle incoming calls during periods when the normal

staff is not available, for example at night and on weekends. System 25’s Night Service
feature allows on-duty personnel to answer incoming attendant-seeking calls when the
attendant is not on duty. Directed Night Service redirects incoming attendant-seeking calls
to designated voice terminals, such as a guard desk or coverage position. Trunk Answer
From Any Station allows users to answer incoming calls from any station by dialing the
Night Service access code. Night personnel can be alerted by a Night Bell.

Outgoing Business Communications

One of the key functions of a customer premises communications system is to provide easy
access to the most cost effective network facilities for outgoing calls. The system needs to be
capable of steering calls based on cost, and must also keep records of incoming and outgoing

calls and associated costs. Building on its ground start trunk capability, System 25 features

control costs and record usage as follows.

●

Call Restrictions allow the manager to restrict users from making certain types of
calls. Restriction is administered through outward restriction, toll call restriction,

and facility access restriction.

● Automatic Route Selection provides manager defined routing of calls over the

telecommunications network based on preferred routes (normally the least expensive
route available at the time the call is placed) with capacity for multiple common
carriers and routing through tandem switch points. The user dials a standard DDD
number and the system selects the call route.

●

Station Message Detail Recording (SMDR) generates detailed call information on all
incoming and outgoing calls and sends this information to an output device (PC or
printer).

● Call Accounting Systems provide multiple types of customer reports on

communication costs and usage.
Account Code Entry allows a user to associate calls with an account code for charge-

●

back purposes.

1-6

Ease of access to multiple types of network facilities (provided for minimum cost) is
managed by:

● Automatic Route Selection (ARS) allows the customer to dial a standard DDD

number. ARS selects the preferred route and does any number conversions required
for the facilities selected.

● System 25’s Virtual Facility feature provides convenient and inexpensive access to

OCCs. This feature provides access to OCC facilities over a user specified

physical

facility; dedicated OCC trunks are not needed. Local OCC access numbers and
account codes are automatically added by System 25. System 25’s Virtual Facility
feature is fully integrated with its ARS, Toll Restriction, and SMDR/CAS features.

● Last Number Dialed automatically saves the last number dialed and allows the user

to retry the number without redialing. (Multiline voice terminals only)

● Repertory Dialing allows multiline voice terminal users to store a telephone number

or account and associate that number with a button on their voice terminal.
Pressing a Repertory Dial button is equivalent to dialing the stored number (one­touch dialing).

● System Speed Dialing allows all users to dial 90 selected numbers using three-digit

codes. Users can also program up to seven Personal Speed Dial Numbers which are
accessible only from their terminals. System Speed Dialing can be used by the system
administrator to hide business account codes from users.

● Pooled Facility-Dial Access allows both multiline and single-line voice terminal users

to access a common pool of trunks for outgoing calls by dialing a facility access code,

or, on multiline voice terminals, by pressing a button . This grouping provides

resource pooling which results in better service with a given number of trunks.

● Personal Lines provide dedicated outside lines for multiline voice terminal users.

Personal lines are accessed via a dedicated feature button. Up to sixteen terminals
may share a personal line.

● Third-Party Call Setup allows PCs to set up calls between a System 25 voice/data

terminal and any other facility. A PC application program could use this capability
to retrieve information from a database.

Last Number Dialed, Repertory Dialing and Speed Dialing are also applicable to dialing and
managing internal calls. Personal lines provide both incoming and outgoing service.

Internal Call Movement

Typically, about 40 percent of PBX calls are internal calls, call transfers to another location,
conference of multiple locations, temporarily suspended calls, page to locate the called party,
etc. Rapid placement of internal calls and easy call movement from the answering station to
a new station are supported in System 25 with numerous features.

To provide easy internal call setup, System 25 provides the following features.

● Direct Station Selection (DSS) allows one-button access from a multiline voice

terminal to another voice terminal, a pooled facility, paging zone or DGC group. The
DSS status LED reflects the idle/busy status of the associated termination point.
This feature is used to track and contact frequently called associates.

1-7

Automatic Intercom allows multiline voice terminal users to call each other by use of

●

a dedicated line appearance. A private dedicated path ensures that a path is always
available. This feature is frequently used in Boss/Secretary arrangements.

The Dial Plan for System 25 is based on the concept that, whenever possible, calls

●

should be placed to individuals rather than to pieces of equipment. To implement this
concept, individuals are assigned Personal Dial Codes (PDCs) and are allowed to
login those PDCs at other terminals. The system automatically routes the call to the
home terminal or logged-into terminal.
of reaching the called party.

In addition, the dial plan is built on a flexible

This significantly increases the probability

numbering scheme which allows the number of dialed digits to match assigned PDCs
(2/3/4 digit dial plans) and to be administered to match telephone company assigned
Direct Inward Dialing numbers.

Efficient internal call termination is supported with the following features.

● Distinctive Ringing provides two types of ringing to allow users to distinguish

between outside calls and inside calls,
Hands-Free Answer on Intercom (HFAI) allows Speakerphone and HFAI terminals

●

to auto-answer inside or attendant extended calls. With HFAI active, the set
generates a tone burst over its speaker to alert the calling and called party of the call
completion.

Both parties may then converse;

no action by the called party is

required.

Frequently, the first termination point for a call is not its final destination. To support
internal call movement, System 25 provides the following features.

● Transfer allows a user to transfer any call to another voice terminal. This feature

supports transfer of calls from the answering position to another location for
completion of a transaction. Examples are secretary to boss, office to lab, broker to
specialist, etc.

Conference allows up to five parties (maximum two outside), including the originator,

●

to participate in a call.

This feature supports add-on of additional parties to a call

for joint consultation, crisis management, schedule coordination, etc.
Hold allows a user to suspend a call. The Hold feature allows users to temporarily

●

disconnect from one conversation and either place or answer another call. Music or
information bulletins may be provided to the held party. Called parties frequently
use the hold period to access computer data bases, search categories and/or consult
with others via a second phone call.

● Call Park allows a user to place a call or conference on hold and then pick up the call

from any voice terminal.

The user can page another party to pick up the parked call

or may move to another location and then re-access the call.

Data Communications

Small Business customers have started to integrate PCs into their day-to-day business

operations. Businesses have found a need to access the data bases (sales, inventory,

personnel) in these PCs from more than one location (both on- and off-premises). System 25

data features are specially engineered to enhance a user’s ability to access data from

multiple locations.

System 25 has been designed to help these businesses use their personal
computers, data terminals and host computers more effectively by providing the following
features.

1-8

● Circuit switched data communications up to 19,200 bps (RS232 interface). This

provides circuit switched connections from asynchronous data terminals, PCs, or host

computers to host computers or network facilities. Users can be located and/or

moved to any on-premises office equipped with the standard AT&T four-pair wiring
plan. Thus an asynchronous terminal or PC can have access to multiple host
computers, remote data bases via a modem pool, and a local area network
(STARLAN) via System 25’s STARLAN NETWORK gateway.

● Packet switched data connections at 1 million bps over AT&T’s STARLAN

NETWORK local area network. This provides data transfer between client PCs and
servers (PCs/host computers/printers, etc.) on the local area network (LAN). LAN
users can be located and/or moved to any on-premises office equipped with standard
AT&T four-pair wiring.

The LAN allows PCs to share facilities (printers, disk

systems, modem pools, etc.)

● System 25’s STARLAN NETWORK ACCESS software and STARLAN NETWORK

gateway provide access to the STARLAN NETWORK for off-premises and occasional
on-premises users. These users do not need to install a Network Access Unit (NAU)
in their PCs to use the STARLAN NETWORK ACCESS software. The data transfer
rate is limited to 9600 bps or, for off-premises users, by the modem.

LAN users can access hosts connected to System 25, or, if their System 25 is equipped
with a modem pool, remote hosts.

Finally, terminals and PCs connected to System 25

data ports can access host computers on the LAN.

Frequently a user needs to access a LAN data base at or from a remote location (home,
motel, client office, branch, etc.). To support out-of-building access to computer data over
network facilities or OPS lines, System 25 provides the following features.

Modem pooling allows data terminals to communicate over analog facilities utilizing

●

the standard dialing plan and provides full access to all network facilities, cost
control

mechanisms, ARS, and

incoming

call

management

tools

(DID/attendant/DGC, etc.).

● Transfer to data allows a data call to be set up on a voice terminal and then be

transferred to a data terminal or computer.

This feature can also be used to enter an

account code for the data call.

The System 25 STARLAN NETWORK gateway allows the LAN environment to be

●

extended to occasional users or remote locations.

Off-premises users can access the

LAN utilizing all the network features, cost control mechanisms, and incoming call

management facilities of System 25.

The data transfer rate is governed by the

modem.

Setting up data communications with PCs, host computers, and/or remote access can be a
source of confusion for occasional users.

Special data features are provided by System 25 to

assist the user in utilizing its rich set of data communications capabilities.

The integrated voice-data dialing plan recognizes the different types of data

●

endpoints (digital/ analog and remote/local) in a connection and automatically
inserts the required data communication equipment.

In addition, autobauding

supports the alignment of equipment with the capacity to transmit at different data

rates.

● Station Hunting supports the use of a single dial code to access a group of host

computer ports.

1-9

●

Terminal Dialing provides the user with fast access to data communications via

keyboard dialing at a terminal or PC.

●

Command Mode provides a menu of data services supporting terminal dialing, and
display and control of user data port options.

A user friendly Change Options menu

is provided for user administration of data options.
Expert Mode is an enhancement that provides an alternative method of accessing

●

Command Mode functions. Expert Mode eliminates the display of menus and allows
multiple commands to be entered on a single line.

Expert mode lends itself well to

computer-driven scripts for call setup.

●

Communication Access Manager (CAM) is an MS-DOS* software application that
provides a phone manager for placing voice and data calls for the user and VT100†
terminal emulation.

CAM may be used on either STARLAN NETWORK client
workstations or on PCs connected to System 25. CAM has a 200-entry directory with
one-touch dialing for both voice and data calls and auto-login capability for data calls

to host computers.

CAM’s Remote Access feature provides password protected
unattended access to PC files and electronic mail. File transfer is supported with the
popular XMODEM protocol.

●

STARLAN NETWORK ACCESS is an MS-DOS application that allows PCs not
connected to the STARLAN NETWORK to call through the System 25 STARLAN
NETWORK Interface and run STARLAN NETWORK client software to access file
and printer servers on the STARLAN NETWORK. ACCESS uses a PC’s serial
communications port to communicate with the STARLAN NETWORK Interface.
ACCESS is compatible with NETBIOS, permitting execution of most applications
written for the IBM‡ PC Network and IBM Token Ring Network.

Growth & Rearrangement

Historical data indicates that clients in the System 25 station range have a need for
communications systems capable of significant growth and rearrangement. Clients need
flexibility over the life of the system to easily add capacity, move stations, modify cost
control options, etc.

The architecture of System 25 was implemented with the objective of

meeting this need.

Advanced Administration (optional) is an easy-to-use, menu driven personal computer

●

software package for configuring the rich set of system options.

● Uniform Wiring Plan (four-pair) allows a building to be prewired for the rich set of

AT&T Small Business PBX service offerings. This modular wiring plan supports client
reconfiguration of an office with variations in station type (Analog, MET, MERLIN,

futures) and data configurations (LAN, asynchronous, synchronous). It supports

simultaneous voice and data from standard four-pair modular jacks.

●

System 25/75/85V2 Standard Architecture supports efficient growth with modular
cabinets, universal carrier slots, non-blocking network and uniform wiring plan. (See

* Registered trademark of Microsoft Corp.
† Trademark of Digital Equipment Corp.
‡ Trademark of International Business Machines Corp.

1-10

Figures 1 and 2.) Every circuit slot in the system can be used for trunk cards or
voice/data station cards. All these attributes allow the client to add future capability
without breakage and re-engineering of existing equipment. Thus, the client is able to
minimize initial investment while not restricting future growth.

Over time, the type of tools and facilities that a business utilizes changes. It is important
that a PBX provide support for the full set of Telco network options over its installed life,
even when only a subset is initially used. Trunks link two switching systems, such as System
25 and the local Central Office or System 25 and another PBX. System 25 supports five
different telephone company trunk interfaces to provide desired connectivity at minimum
expense.

Thus the opportunity exists to select the best trunk types, depending on tariffs and

customer needs.

● Loop Start (LS) trunks for public network access at minimum tariff. These trunks

handle outgoing and incoming attendant calls, incoming DGC calls, outgoing pooled

facility calls, and personal line calls.

● Ground Start (GS) trunks for public network access. These trunks handle the same

type of calls as LS trunks. They provide protection against call reorigination without
toll restriction, more reliable automatic route selection, virtual facilities, SMDR and
CAS. Simultaneous incoming and outgoing call seizure of the same trunk under
heavy traffic conditions is essentially eliminated with ground start trunks. GS
trunks should usually be selected in preference to LS trunks unless tariff
considerations are overriding.

Note, however, that Centrex Service requires LS

trunks.

● Direct Incoming Dial (DID) trunks for dialing a station directly from outside

(attendant assistance not required). Outside dial access to stations, trunks (optional),
and answering groups (Direct Group calling) is provided.

● Tie Trunks for linking PBXs with dedicated private circuits for high volume calling.

Dial access to stations, other trunks, answering groups (Direct Group Calling) and an
Electronic Tandem Network endpoint capability are provided.

● Off-Premises Stations (OPS) allow a single-line voice terminal to be located remotely

and connected to System 25 via arrangements with the local Telco. This service is
used to provide users at secondary sites (or their residences) many of the same
features as an on-premises single-line station.

To enhance the usage and control of the above set of network facilities, System 25 provides
the rich set of access features outlined in the Outgoing Business Communications Section. In
addition, System 25 can support networking between systems by:

. Serving as an endpoint on an electronic tandem network (ETN) using its tie trunks

and flexible dialing plan.

. Serving as an off-network or on-network access point with its dial access/transfer

between tie-trunks and Telco trunks (LS/GS/DID). This allows usage of tie trunks
to reach a distant System 25 and then connect through that System 25 to local Telco
facilities to complete the call.

To support efficient utilization of trunks, they can be grouped together (up to 16 groups) if
all trunks in the group perform the same function. This resource pooling provides better
service with a given number of trunks, and simplifies administration and calling.

1-11

Types of trunks which can be assigned in System 25 are:

● Central Office, which provide a link with the local telco for incoming and outgoing

calls (LS/GS)
Foreign Exchange (FX), which connect to a CO other than the local CO for high

●

volume calling from a distant location

● Wide-Area Telecommunications Service (WATS), which connect to an Outward

WATS office or a dial “800” Service Office
Direct Inward Dial (DID), which provide incoming service from a CO to directly

●

access a station or facility (STARLAN NETWORK interface, trunk group)

Tie trunks, which provide a link with another private switching system.

●

To support efficient utilization of this rich set of network options, System 25 provides the
functions outlined in the Outgoing and Incoming Business Communications sections.

Conclusions

System 25 has been targeted at providing excellent small business communications capability
at the right price. The thousands of systems in service in the first year of production have
confirmed that these capabilities are an excellent match with small business customers’
communications needs.

1-12

LIST OF FIGURES

Figure 2-1.
Figure 2-2.
Figure 2-3.

Figure 2-4. Console Buttons and Display . . . . . . . . . . . . . . .

Figure 2-5. Switched Loop Attendant Console Connections . . . . . . . . .

Figure 2-6.
Figure 2-7.
Figure 2-8.
Figure 2-9.

Figure 2-10. Typical SMDR Call Detail Report . . . . . . . . . . . . .

Figure 2-11. SMDR Call Record Format . . . . . . . . . . . . . . . .

Figure 2-12. SMDR Call Record Header Format . . . . . . . . . . . . .

Figure 2-13. SMDR Output Equipment or Call Accounting System—On-Premises

Figure 2-14. SMDR Output Equipment or Call Accounting System—On-Premises

Figure 2-15. SMDR Output Equipment–On-Premises Switched

Direct Trunk Attendant Console . . . . . . . . . . . . . .

Direct Trunk Attendant Console Connections . . . . . . . . .

Switched Loop Attendant Console . . . . . . . . . . . . .

Model 23A1 Attendant Direct Extension Selector Console . . . . .

Attendant Direct Extension Selector Console Connections . . . . .

Automatic Route Selection Flow Chart . . . . . . . . . . .

Automatic Route Selection Routing Pattern . . . . . . . . . .

Direct Connections (Sharing Same AC Outlet) . . . . . . . . .

Direct Connections (Greater Than 50 Feet From System

Cabinet) . . . . . . . . . . . . . . . . . . . . . .

Connections . . . . . . . . . . . . . . . . . . . . .

2-13
2-16
2-17
2-20
2-24
2-26
2-28
2-54
2-59
2-69
2-70
2-71

2-72

2-73

2-74

Figure 2-16. SMDR Output Equipment—Off-Premises Direct Connections . . . .

Figure 2-17. SMDR Output Equipment–Off-Premises Switched

Connections . . . . . . . . . . . . . . . . . . . . .

Figure 2-18. Communications Access Manager Architecture . . . . . . . . .

Figure 2-19. Asynchronous Data Unit Interface Signals . . . . . . . . . .

Figure 2-20. Dictation System Connections (FCC Registered) . . . . . . . .

Figure 2-21. Digital Tape Unit . . . . . . . . . . . . . . . . . . .

Figure 2-22. Digital Tape Unit–On-Premises Direct Connections (Sharing Same AC

Outlet) . . . . . . . . . . . . . . . . . . . . . .

Figure 2-23. Delay Announcement Equipment Connections (FCC

Registered) . . . . . . . . . . . . . . . . . . . . .

Figure 2-24. External Alert Connections . . . . . . . . . . . . . . .

Figure 2-25. Supplemental Alert Adapter Connections . . . . . . . . . . .

-iv-

2-75

2-76

2-99
2-107
2-119
2-120

2-121

2-126
2-140
2-141

Figure 2-26.

500A/502A Headset Adapter . . . . . . . . . . . . . . .

2-146

Figure 2-27.

Figure 2-28.

Figure 2-29.

Figure 2-30.
Figure 2-31.
Figure 2-32.

Figure 2-33.

Figure 2-34.

Figure 2-35.
Figure 2-36.
Figure 2-37.
Figure 2-38.

Typical Headset Adapter Connections For 7300H Series Multilane Voice
Terminals (Except 34-Button Deluxe, BIS, or BIS with

Display) . . . . . . . . . . . . . . . . . . . . . .

Typical Headset Adapter Connections For 34-Button Deluxe, BIS, or

BIS with Display Voice Terminals . . . . . . . . . . . . .

Typical Headset Adapter Connections For 12-Button MET

Sets . . . . . . . . . . . . . . . . . . . . . . .

Music-On-Hold Equipment Connections (FCC Registered) . . . . .

Music-On-Hold Equipment Connections (Non-Registered) . . . . .

Delay Announcement Equipment Connections (FCC

Registered) . . . . . . . . . . . . . . . . . . . . .

Paging Equipment Connections Using CO Trunk Ports (FCC

Registered) . . . . . . . . . . . . . . . . . . . . .

Paging Equipment Connection to TN763 Causing 278A

Adapter . . . . . . . . . . . . . . . . . . . . . .

10B Emergency Transfer Unit (ETU) . . . . . . . . . . . .

Emergency Transfer Unit Connections . . . . . . . . . . . .

Multiple ETU Arrangements . . . . . . . . . . . . . . .

Speakerphone Adjuncts . . . . . . . . . . . . . . . . .

2-147

2-148

2-149
2-168
2-169

2-174

2-179

2-180
2-191
2-192
2-193
2-208

Figure 2-39.

Figure 2-40.

Figure 2-41.
Figure 2-42.
Figure 2-43.

Figure 2-44.

Figure 2-45.
Figure 2-46.

Figure 2-47.

Figure 2-48.
Figure 2-49.
Figure 2-50.
Figure 2-51.

Speakerphone Connections For 7300H Series Multilane Voice Terminals

(Except 34-Button Deluxe) . . . . . . . . . . . . . . . .

Speakerphone Connections For 34-Button Deluxe Multiline Voice

Terminals . . . . . . . . . . . . . . . . . . . . .

Speakerphone Connections For 12-Button MET Sets . . . . . . .

STARLAN NETWORK and System 25 Configuration . . . . . . .

STARLAN NETWORK Connection to System 25 (With 2500 Single-

Line Telephone) . . . . . . . . . . . . . . . . . . .

STARLAN NETWORK Connection to System 25 (With ATL-Type

Telephone) . . . . . . . . . . . . . . . . . . . . .

Model 703 System Administration Terminal . . . . . . . . . .

SAT On-Premises Direct Connections (Sharing Same AC

Outlet) . . . . . . . . . . . . . . . . . . . . . .

SAT On-Premises Direct Connections (Greater Than 50 Feet From

System Cabinet) . . . . . . . . . . . . . . . . . . .

SAT On-Premises Switched Connections . . . . . . . . . . .

SAT Off-Premises Direct Connections . . . . . . . . . . . .

SAT Off-Premises Switched Connections . . . . . . . . . . .

Command Mode Menu Tree . . . . . . . . . . . . . . .

2-209

2-210
2-211

2-216

2-219

2-220
2-228

2-229

2-230

2-231
2-232
2-233
2-254

- v -

TABLE 2-A. System Features . . . . . . . . . . . . . . . . . . .

TABLE 2-B. Network Features . . . . . . . . . . . . . . . . . .

TABLE 2-C. Data Features.. . . . . . . . . . . . . . . . . . .

TABLE 2-D. Station Features . . . . . . . . . . . . . . . . . . .

TABLE 2-E. Attendant Features . . . . . . . . . . . . . . . . . .

TABLE 2-F. Partial List of Permissible Data Port (TN726) Options . . . . . .

2-2
2-3
2-3
2-4
2-5

2-97

TABLE 2-G. Typical Option Profiles for Different Types of Data Port

Endpoints . . . . . . . . . . . . . . . . . . . . .

TABLE 2-H. Call Progress Messages for Data Terminal Dialing . . . . . . .

TABLE 2-I. LED Indications . . . . . . . . . . . . . . . . . . .

TABLE 2-J. User Changeable Options . . . . . . . . . . . . . . . .

2-98
2-114
2-157
2-253

-vi-

SECTION 2—FEATURES AND SERVICES

This section describes the System Features,

Network Features, Data Features, Station
Features, and Attendant Features of AT&T System 25. It also covers certain services that
support and implement the features; included in this category are the digital tape unit, the
dial plan, system administration, and system maintenance. A general discussion of data
topics is also provided.

The feature descriptions are arranged in alphabetical order, regardless of the feature group
to which they belong.

Information for each feature is presented under five headings:

Description, Considerations, Interactions, Administration, and Hardware Requirements.

● Description

Defines the feature, describes what it does for the user, and how it is used.

● Considerations

Discusses the applications

and benefits of the feature, followed by feature

parameters and factors to be considered when the feature is used.

● Interactions

Lists and briefly describes other features that can affect the feature being described.
Interacting features are those that:

—

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 operation of one feature modifies, or is modified by,
the operation of the other.

—

Enhance each other—The features, in combination, provide improved service
to the user.

● Administration Requirements

States whether or not administration is required and lists items requiring
administration.

● Hardware Requirements

List any additional hardware needed to use the feature.

Tabular listings of features by group (System,

immediately follow this introduction.

Each type, standard, or optional of the feature, is also

Network, Data, Station, or Attendant)

noted on these lists:

● Standard features—Built into each system (always provided but can require

administration to make them operational)

● Optional features–Such

as Music-On-Hold, require both administration and

additional hardware.

Features restricted to single-line or multiline voice terminals are noted where applicable.
The MET sets operate the same way as 5-button 7300H series voice terminals, unless
otherwise noted.

2-1

System Features

System features (Table 2-A) are those that affect the entire operation of the system. All
system features are available with both Vl and V2.

TABLE 2-A. System Features

FEATURE NAME

FEATURE

TYPE *

Call Accounting
Dial Plan S
Dictation System Access

Digital Tape Unit
Direct Group Calling
Direct Group Calling Delay Announcement

End-to-End Signaling
Extended Stations
External Alerts

Intercept Treatment With Reorder Tone
Interdigit Timeouts
Music-On-Hold

Night Service (Directed and TAAS )
Night Service Delay Announcements
Out-Of-Building Stations

Paging System Access
Personal Dial Codes

Pooled Facility-Dial Access

Power Failure Transfer
Remote Administration Interface
Station Message Detail Recording

System Administration
System Maintenance
Touch-Tone and Dial Pulse Service

S/O†

O

O
O

S

O

S
O
O

S
S
O

O
O

O
S
S

O
O
O

O
S
S

* Feature types: S= Standard; O= Optional (requires additional equipment).

† S/O - Standard for Directed, Optional for TAAS Night Service.

2-2

Network Features

This group of features (Table 2-B) supports communications with the public network and
with other locations in the private network of which System 25 can be a part.

TABLE 2-B. Network Features

FEATURE NAME

FEATURE

TYPE *

Automatic Route Selection

Direct Inward Dialing
Off-Premises Stations

Tandem Trunking (V2)
Tie Trunks
Trunk Groups
Virtual Facilities (V2)

S
O
O

O
O

S

S

Data Features

Data Features (Table 2-C) support the switched data services of the system. Data services
provide switched connections between analog and digital data endpoints.

TABLE 2-C. Data Features

FEATURE NAME

MULTILINE TERMINAL

BUTTON LABEL †

FEATURE

TYPE *

Command Mode
Communications Access Manager (V2)
Data Call Setup

Data Services Overview

Data Terminal Dialing
Expert Mode (V2)

Modem Pooling
AT&T STARLAN NETWORK Access (V2)

Third-Party Call Setup (V2)
Transfer to Data
User Changeable Options (V2)

[DATA]

S
O
S

S
S

O
O

S
S
S

* Feature types: S= Standard; O= Optional (requires additional equipment).

† Bracketed items are associated voice terminal feature button labels;

these labels are also used in feature descriptions where applicable.

2-3

Station Features

The many Station Features (Table 2-D) available allow individual user needs to be met. As
these needs change, assigned features can also be changed.

Station Features provide many

important services that help save time and make calling more convenient.

TABLE 2-D. Station Features

FEATURE NAME

Account Code Entry
Automatic Intercom
Busy-to-Idle Reminder

Call Accountability
Call Coverage-Group
Call Coverage-Individual

Call Following (Forwarding)
Call Park
Call Pickup
(’all Progress Tones
Calling Restrictions
Conference
Conference Drop
Direct Station Selection (DSS)
Distinctive Ringing

Exclusion
Hands-Free-Answer On Intercom

Headset Adapter Adjunct

Hold
Last Number Dialed (V2)
Line Selection

Line Status And I-IJse Indications
Manual Signaling
Messaging Services

Personal Lines
Pooled Facility-Button Access
Program

Recall
Repertory Dialing
Send All Calls
Speaker (Spokesman Service)
Speakerphone Adjunct
Speed Dialing
Station Hunting
Station-To-Station Message Waiting
Test
Transfer
Trunk-To-Trunk Transfer

SINGLE-LINE MULTILINE TERMINAL FEATURE

TERMINAL

x [ACCT ENTRY] s

x

x [COVER-GRP]
x
x x s
x x s
x x s
x
x x s
x x s

x s

x

x x
x s

x

x x
x

x x
x
x

x x s

x x s

BUTTON LABEL † TYPE*

[AUTO ICOM] s

x s
x

[COVER-IND]

x s

[DSS or FLEX DSS]

x

[EXCLUSION] s
[AIJTO ANS] o

[LAST # DIALED]

x

[SIGNAL] s

x
[PERS LINE]
[FACILITY]

x

[REP DIAL] s
[SEND ALL CALLS] s

x s

x

[MSG WAIT] s

x

s
s
s

s
s

o

s

s

s

s
s
s
s
s

o
s

s

s

* Feature types: S= Standard; O= Optional (requires additional equipment).

† Bracketed items are associated voice terminal feature button labels;

these labels are also used in feature descriptions where applicable.

2-4

Attendant Features

Attendant Features (Table 2-E) are available to the attendant using the Direct Trunk
Attendant Console (DTAC) or the Switched Loop Attendant Console (SLAC) (V2 only) and

(optionally) a Direct Extension Selector Console.

In addition, most multiline voice terminal

station features are available to the attendant.

TABLE 2-E. Attendant Features

FEATURE NAME

CONSOLE BUTTON

LABEL

Attendant Call Extending [START]
Attendant Camp-On
Attendant Cancel

Attendant Console, Direct Trunk
Attendant Console, Switched Loop (V2)
Attendant Display (V2; SLAC only)

Attendant Direct Extension Selection
Attendant Forced Release V2; SLAC only)
Attendant Join (V2; SLAC only) [JOIN]

Attendant Message Waiting (DTAC)
Attendant Message Waiting (SLAC)

Attendant Position Busy
Attendant Release

Attendant Return-Coverage-on-Busy [RTN-BUSY]‡
Attendant Return-Coverage-on-Don’t-Answer
Attendant Source/Destination (V2; SLAC only)

Attendant Splitting One-Way Automatic
Attendant System Alarm Indication [ALARM]
Message Center-Like Operation (V2; SLAC only)
Night Service [NIGHT]

[CANCEL]

[FORCED RELEASE]

[ATT MSG]
[ATTENDANT
MESSAGE WAITING]
[POS BIJSY]
[RELEASE]

[RTN-DA]‡
[SOURCE]

[DEST]

FEATURE

†

TYPE *

S
S
S

O
O
S

O
S
S

S

S
S
S

S
S
S
S

S
S
S
S

Feature types: S=Standard; O=Optional.

*

Bracketed words are the labels for button-activated features;

†

these labels are also used in feature descriptions where applicable.

This button is assigned on the DTAC only.

‡

2-5

ACCOUNT CODE ENTRY

Description

Allows voice terminal users to associate an account code with incoming and outgoing calls.
This is accomplished by entering the account code at the voice terminal before hanging up.
The account code is appended to the SMDR call record and can be used later for accounting

or billing purposes.

To association account code with a call, the user, after completing a call but before hanging

up, must:

● Single-Line Voice Terminal User:

—

Flash the switchhook and dial *O; then dial the account code directly or dial a
System or Personal Speed Dial Number that contains the account code. If the
number is entered incorrectly, redial

*0 and the correct number before

hanging up.

● Multilane Voice Terminal User:

—

Press Account Code Entry (ACCT ENTRY) button and then dial the account

code directly or dial a System or Personal Speed Dial Number that contains
the account code. A Repertory Dial (REP DIAL) button can also be used to
enter an account code.

If the number is dialed incorrectly, press ACCT

ENTRY again (before hanging up) and dial the correct number.

● When the correct number of account code digits have been entered (o r# is entered to

signal end-of-dialing), Confirmation Tone followed by Dial Tone is returned to the
user and the account code is appended to the SMDR call record.

Account Code Entry is optional.

Considerations

Account Code Entry provides an easy method of allocating the costs of specific calls (and
associated staff time) to the correct project, department or user. The account code is
appended to the SMDR call record and sent to the SMDR output channel.

Account Codes can include up to 15 digits.

The validity of the entered account code is not checked by the system.

If the user is active on a call, invoking the feature will drop the call.

Incorrectly dialed codes (prior to last digit entry) can be corrected by dialing *0 or pressing
ACCT ENTRY and reentering the code.

before completing entry are recorded and cannot be corrected.
If, before all digits have been entered, (1) the user goes on-hook, (2) a button other than

ACCT ENTRY is pressed, or (3) 30 seconds have elapsed since the feature was invoked, the
SMDR call record will show the digits dialed up to that point.

If a call is on hold, this feature cannot reinvoked.

Partial account codes entered by going on-hook

2-6

Interactions

● Conference: If more than one user attempts to enter an account code on a

Conference Call, the first to enter a code will prevail.
Repertory Dialing: An Account Code can be stored on a REP DIAL button. Press

●

REP DIAL after ACCT ENTRY has been pressed.
Speed Dialing: An Account code can be stored in System or Personal Speed Dial

●

Number.
Transfer: A user can transfer a call to another user, then, before hanging up, enter

●

an account code. Subsequent account code entries for the same call will be ignored,
even though confirmation tone has been returned.

Administration Requirements

System:

● Maximum number of Account Code digits (0-15)--Default = 15.

Voice Terminal: (Station Port)

Multiline terminals–Account Code Entry Button is required.

●

● Single-line terminals–none.

Hardware Requirements

Requires an RS-232 compatible 80-column ASCII (serial) printer or other device to output

Station Message Detail Recording (SMDR)/Account Code entries.

2-7

ATTENDANT CALL EXTENDING

Description

Allows the attendant to put a call in a special hold condition, call another station, then
connect the two calls together.
separate the call from the console or remain connected to the other parties. Attendant Call
Extending is a feature used at either a Direct Trunk Attendant Console (DTAC) or a

Switched Loop Attendant Console (SLAC).

The attendant can withdraw from the connection and

Note: In general, the attendant
the standard multiline voice terminal Transfer feature, to extend calls. If Transfer is
used, busy or unanswered calls cannot return to the attendant console for further
handling.

The attendant, after placing or answering a call, can use Step 1 or 2 to extend this call to an
inside extension or Step 1 to extend it to an outside number:

1. Press START to place the incoming call on hold via the Attendant Splitting One­Way Automatic feature.
requested inside or outside number.

or

2. Press the Selector Console Group Select and Direct Extension Selection (DXS)

buttons associated with the requested inside station. This operation is equivalent to
pressing START and dialing the extension.

If ringing tone is heard, the attendant presses RELEASE (Manual Release) to connect the
caller to the ringing line and separate the call from the console. As an alternative, the
attendant can press any facility button such as System Access, Automatic Intercom, or an
outside line (Attendant Automatic Release) to complete the call extending procedure.

The attendant has the option of staying connected to the ringing line to announce the call
before connecting the two parties.
other parties in a 3-way connection by using the Attendant Join feature.

should not use the TRANSFER button, which invokes

After receiving Dial Tone, the attendant then dials the

The attendant can then release or (SLAC only) join the

If busy tone is heard and Attendant Camp-On (see associated feature description) is not
desired, the attendant presses CANCEL and is reconnected to the calling party.

If busy tone is heard on a call to an inside station and Attendant Camp-On is desired, the
attendant presses RELEASE or any facility button.
the call waits at the called voice terminal. When a busy single-line station goes on-hook, or
a busy multiline station System Access button becomes idle, the call automatically begins
ringing at the station. Only one Camped-On call is permitted per voice terminal.

Calls extended to an

to the Attendant Console on an idle LOOP button (SLAC only) or on the Return-On-Don’t-

Answer (RTN-DA) button (DTAC only). Calls camped-on at a

not answered within a specified time return to the Attendant Console on an idle LOOP
button (SLAC only) or on the Return-On-Busy (RTN-BUSY) button (DTAC only). If a SLAC
is not available to incoming calls (busy on another call, in Position Busy mode, etc.), a
returning call remains in the console queue until the console can handle it. If the Return
buttons on a DTAC are busy, an extended call remains at the called terminal until that
button becomes idle.

idle voice terminal that are not answered within a specified time return

2-8

The called party hears a tone burst, and

busy voice terminal that are

Considerations

Attendant Call Extending allows the attendant to utilize the additional attendant related

features such as Attendant Splitting One-Way (automatically places incoming canon hold),

Release, Cancel, Return-On-Don’t-Answer,

Return-On-Busy, Forced Release (SLAC), Join

(SLAC), and Source/Destination (SLAC).

Interactions

Refer to the other Attendant Feature descriptions for information on related features (Table
2-E).

Administration Requirements

System:

● Number of seconds before a Camped-On call returns to the Attendant Console (1-120

seconds), or No Attendant Camp-On (0) - Default = 30 seconds

Number of rings before unanswered call returns to the Attendant Console (1-31) -

●

Default = 5.

Hardware Requirements

Selector Console (optional)

2-9

ATTENDANT CAMP-ON

Description

Allows the attendant to extend a trunk call to a busy voice terminal and leave it waiting or

“camped on”

this call at the busy terminal.

there. After hearing busy tone, the attendant presses RELEASE to camp-on

When this is done, a burst of tone is heard in the handset of
the called terminal and the caller is placed on hold (hearing music-on-hold if available).
When a System Access button at a multiline set becomes idle or a single-line terminal hangs

up, the camped-on call is connected automatically and ringing begins. Only one call can be

camped-on to a voice terminal.

This feature is referred to as a “Waiting Call” in the User

Guides for the System 25 voice terminals.

Considerations

A camped-on call can be answered by a busy single-line user without losing the current call

by momentarily pressing the switchhook (which places the current call on hold) and then
dialing *9. Multiline terminal users cannot do this. However, if they have a System Access­Originate Only button, they can place both calls on hold, go off-hook on that button and dial
*9 to pick up the camped-on call.

If the camped-on call is not answered within a specified time, the call will be returned to the
Attendant Console in one of the following ways:

● Switched Loop Attendant Console: The call returns to the common queue, where

it remains until the console can receive it at a LOOP button.

● Direct Trunk Attendant Console: The call returns to the Return-On-Busy (RTN-

BUSY) button. If that button is busy, the call remains camped-on at the called
terminal until the RTN-BUSY button of the console becomes idle.

Interactions

● Call Coverage/Direct Group Calling (DGC): If the called party is a member of

a hunt or Call Coverage group (or, for V1 systems only, a DGC group) and all
members of the group, or all receivers of the Coverage group are busy, the call will
not hunt or receive coverage. Once camped-on, calls will no longer hunt or receive
coverage even if the hunted-to station or group member becomes idle.

● Direct Group Calling: For V2, the attendant can camp-on more than one call per

DGC group. For VI, the attendant can camp-on only one call per DGC group; if the
attendant attempts to camp-on a second call, it is immediately returned on the RTN­BUSY button on the DTAC. Voice terminals in the group do not receive a burst of
tone when a call is camped on.

● Direct Inward Dialing (DID): DID calls can be covered by the attendant and

then given Camp-On treatment.

They do not automatically receive Call Waiting.

Refer to the Attendant Feature descriptions for information on other related features (Table

2-E).

2-10

Administration Requirements

System:

● Number of seconds before a camped-on call returns to the Attendant Console (1-120

seconds) or No Attendant Camp-On allowed (0) - Default = 30 seconds.

Hardware Requirements

None

2-11

ATTENDANT CANCEL

Description

Allows the attendant to terminate an attempt to extend any incoming call if the called

station does not answer, or if the station answers but declines to accept the call. Before
pressing RELEASE, the attendant presses CANCEL and is automatically reconnected to the
calling party.

Pressing CANCEL when the Start facility is not active will be ignored.

Considerations

Attendant Cancel allows the attendant to terminate a call transfer attempt and return to
the incoming held party via a one-button operation.
handle calls quickly and efficiently.

Interactions

None

Administration Requirements

This enhances the attendant’s ability to

None Required

Hardware Requirements

None

2-12

ATTENDANT CONSOLE, DIRECT TRUNK

Description

In System 25, the Attendant Console is used to answer incoming trunk calls that are not
directed to specific user stations, to answer calls from inside users, to extend calls to inside
stations and outside numbers, and to assist system users in placing outgoing calls and
setting up conferences.

The attendant can also manage and monitor some areas of system

operation. System 25 R1Vl supports only the Direct Trunk Attendant Console (DTAC). The

R1V2 supports either the DTAC or the Switched Loop Attendant Console (SLAC), that is

described in the next subsection of this manual.
The DTAC (Figure 2-1) is a 34-Button Deluxe Voice Terminal administered with special

features, buttons, and capabilities to serve as an attendant position. In addition to the
attendant features, all standard multiline terminal features are also available. (Refer to the
Hardware Description section of this manual for a complete identification of the external
controls, indicators, and components of the basic voice terminal. )

DIRECT TRUNK ATTENDANT

CONSOLE

OPTIONAL SELECTOR

CONSOLE

Figure 2-1. Direct Trunk Attendant Console

The DTAC is always equipped with the following feature buttons that provide unique
attendant console functions.

Each button has a green status LED that indicates when the

feature is activated.

● Start [START] Initiates the call extending process by placing a caller on hold and

providing internal dial tone to the attendant

● Cancel [CANCEL]: Terminates the

“Start” operation and reconnects the attendant

to the calling party.

● Release [RELEASE]: Releases the attendant from an active call and completes the

call extending process.
Return-On-Busy [RTN-BUSY]: Camped-on calls are returned to the console on

●

this button if not answered within a specified interval.

2-13

● Return-On-Don’t-Answer [RTN-DA]: Extended calls not answered are returned

to the console on this button if not answered within a specified interval.
Attendant Message Waiting [ATT MSG]: Used by the attendant to remotely

●

control Message LEDs on voice terminals.

● Alarm [ALARM]: The associated status LED flashes when a system trouble has

been detected; the LED can be changed from flashing to steadily lit by pressing the
button.

Two other attendant-only features are assigned to console feature buttons if required,

Position Busy [POS BUSY] and Night Service [NIGHT]. In a dual attendant console system,
Position Busy removes an Attendant Console from service. Only one of two consoles can be
in the “Position Busy” mode at a time.

When Night Service is activated, attendant-seeking
calls can ring a night bell, can be directed to assigned voice terminals, or can be sent to a
night service announcement.

Considerations

Direct trunk operation means that trunks are terminated on individual buttons, called
Personal Line buttons, where outside calls are answered and originated. The console can
have several incoming calls ringing simultaneously.

Each console can also have an optional Attendant Direct Extension Selector Console to

enhance internal calling.

The Selector Console is described in the “Attendant Direct

Extension Selection” subsection.

Dual Console Operation:

A System 25 can be equipped with up to two DTACs that operate simultaneously when both
are in service.

If the system has two attendant consoles, one is called the first attendant
console (primary attendant console in VI); the other is called the second attendant console
(secondary attendant console in Vi). The calls in the following list will be routed to the first
attendant console.

● Dial “0” calls

● DID calls to unassigned numbers (when administered to route to the attendant)

● Calls to Floating Personal Data Codes (FPDCs) not logged in (when administered to

route to the attendant)

If the first attendant has activated the Position Busy feature or is busy on both System
Access buttons, these calls will be routed to the second console. If that console is also busy
on both System Access buttons, busy tone is provided to the calling party.

For V2 only: See the “Call Coverage—Individual” feature description for information about

simulating additional System Access buttons for handling more incoming calls.

System users and DID callers can reach a particular attendant by dialing that personal Data

Codes (PDC).

Position Busy:

A POS BUSY button can be assigned to each console; this permits selection of one of two
modes of operation:
(Note that only one console is allowed to be inactive at any given time.) An associated POS
BUSY status LED is lighted when the console is inactive.

(1) simultaneous operation or (2) only one Attendant Console active.

Ringing is disabled on all trunk

2-14

terminations on the rightmost two columns of buttons of the inactive console. Ringers
disabled on an inactive console will be enabled on the active console for those trunks with
dual appearances (appearances on both consoles).

All other features on all buttons,
including those on the associated Attendant Direct Extension Selector Console will continue
to function normally even though the console is inactive.

Interactions

A DTAC cannot operate in the same system with a SLAC.
Refer to the Attendant Feature descriptions for information on other related features as

listed in Table 2-E.

Administration Requirements

System:

● Assign Primary and Secondary Attendant Positions (Vi)

● Display attendant position number (first or second) (V2)

● Assign number of rings before unanswered calls return to the Attendant Positional-

31) -Default = 5 rings

● Send DID calls to unassigned numbers to the Attendant Position (Yes, No) -Default

= Yes

● Send calls to Floating Personal Dial Codes that are not logged-in to the Attendant

Position (Yes, No) -Default = Yes

● Assign number of seconds before an unanswered Camped-On Call returns to the

Attendant Console (1-120 seconds), or No Attendant Camp-On (0) - Default = 30
seconds.

Attendant Console: (Station Port)

● Voice terminal type = 309 (V2)

● Special Programmable Buttons:

—

Night Service

—

Position Busy

—

Attendant Message Waiting (assigned by default).

Note: The following buttons are predefined on the Attendant Console and are
not administrable:

–

Alarm

—

Return-On-Don’t-Answer

—

Return-On-Busy

—

Start

– Cancel

2-15

—

Release

● Trunk terminations–The following is required for each trunk terminated on the

console (administered as Personal Line appearances; DID trunks cannot be
terminated on a DTAC):

Trunk Number

—

Make this the Principal Station (owner) of the trunk (Yes, No)

—

Enable Ring (Yes, No).

Hardware Requirements

Each console requires a port on a ZTN79 ATL Line circuit pack.
Figure 2-2 provides a connection diagram for the DTAC.

SYSTEM 25

CABINET

ZTN79

HYBRID

LINE CP

PART OF

OCTOPUS CABLE

— — — —
— — — —

Ž

— — — —

PART OF SIP

SIP

ADAPT

W1

B1

C1

DIRECT TRUNK

ATTENDANT

CONSOLE T1

— — — —

— — — —

LEGEND :

TYPICAL-103A CONNECTING BLOCK*

B1 —
C1 –

MODULAR CORD (D8W-87) - FURNISHED WITH SET
OCTOPUS CABLE (WP90780) - PEC 2720-05P

C2 –

7305H02B DELUXE 34-BUTTON VOICE TERMINAL - PEC 3162-417

T1 –

4 PAIR INSIDE WIRING CABLE*

W1 –

* –

FURNISHED BY INSTALLER

RANGE: WITHIN 2000 FEET OF SYSTEM CABINET (LOCAL POWER REQUIRED >1000 FEET)

Figure 2-2. Direct Trunk Attendant Console Connections

2-16

ATTENDANT CONSOLE, SWITCHED LOOP (V2)

Description

In System 25, the Attendant Console is used to answer incoming trunk calls that are
specified to ring at an attendant position, to answer calls from inside users, to extend calls
to inside stations and outside numbers, to assist system users in placing outgoing calls, and
to set up conferences.

The attendant can also manage and monitor some areas of system
operation. System 25 R1V1 supports only the Direct Trunk Attendant Console (DTAC),
which is described in the preceding subsection of this manual. The R1V2 supports either the
DTAC or the Switched Loop Attendant Console (SLAC), but not both in the same system.

The SLAC (Figure 2-3) is a 34-Button Built-In Speakerphone (BIS) Voice Terminal with a

16-character display module.

capabilities to serve as an attendant console.

standard multiline terminal features are also available.

It is administered with special buttons, features, and

In addition to the attendant features, most

(Refer to the “Hardware
Description” section of this manual for a complete identification of all the external controls,
indicators, and components of the basic voice terminal. )

SWITCHED LOOP

ATTENDANT CONSOLE

OPTIONAL SELECTOR

CONSOLE

Figure 2-3. Switched Loop Attendant Console

Associated with the SLAC are message center-like capability and display support. The
message center feature provides for efficient handling of calls that should be sent to message
takers. These calls are directed to a message center console position through administration
of call type translations.

Display service allows identifiers (names) to be assigned to
extension numbers and trunks. The system then displays the appropriate information to the
attendant when calls are processed at the console.

Fixed Buttons (Figure 2-4)

The SLAC has five fixed line appearance, or “LOOP,” buttons where all incoming calls are
answered. Each button has a red I-use LED and a green status LED. These buttons
represent voice links (loops) between the console and the switch. The loops also provide the
paths for outgoing calls.

2-17

In addition to the LOOP buttons and standard multiline terminal buttons (HOLD,
TRANSFER, etc.), the console is equipped with the following feature buttons that provide
unique

attendant functions. Unless noted, the buttons have green status LEDs.

●

Start [START]: Initiates the call extending process by placing a caller on hold (on
the Source button) and providing internal dial tone to the attendant. No LED.

●

Cancel [CANCEL]: Terminates the

“Start” operation and reconnects the attendant

to the calling party (on the Source button). No LED.

●

Release [RELEASE]: Releases the attendant from an active call and completes the
call extending process. No LED.

●

Source [SOURCE]: Reconnects the attendant to the calling party after a call has
been initiated to the called party but before the two parties have been connected
together.

●

Destination [DEST]: Connects the attendant to the called party again after the
attendant has operated the Source button to speak to the calling party.

●

Join [JOIN]: Joins together (in a 3-way connection) the attendant and the other
parties in an extended call. No LED.

●

Forced Release [FORCED RELEASE]: Drops all active parties from a call. No
LED.

●

Last Number Dialed [LAST # DIALED]: Redials the last number dialed. No
LED.

●

Position Busy [POS BUSY]: Temporarily removes the attendant position from
service.

Attendant Message Waiting [ATTENDANT MESSAGE WAITING]: Used by

●

the attendant to remotely control Message LEDs on voice terminals.

●

Alarm [ALARM]: The associated status LED flashes when a system trouble has
been detected; the LED can be changed from flashing to steadily lit by pressing the
button.

●

Inspect [INSPECT]: Puts the display into a mode for inspecting the status or
stored information of certain buttons.

●

Scroll [SCROLL]: Causes display to present additional call information, when
available. No LED.

●

Local [LOCAL]: Allows display to be used for clock and calendar functions. No
LED.

The buttons not assigned to normal voice terminal functions or to attendant functions are
defaulted to the Flex DSS feature.

One of these programmable buttons can be assigned to

Night Service, if the feature is required, and any of the others to multiline voice terminal
features.

Programmable Feature Buttons (Figure 2-4)

The features in the following list can be assigned to the programmable feature buttons. On
the SLAC these buttons are not equipped with lamps for indicating feature status conditions.

● Exclusion

2-18

● Manual Signaling

● Transfer to Data

● Account Code Entry

● Auto Intercom

● Auto Answer

● Direct Facility Access

● Direct Station Selection (DSS)

● Flex DSS

● Repertory Dialing.

The last two features can be programmed with dialable numbers by the attendant. When a
call is placed using a Flex DSS button or a Repertory Dial button, one of the five switched
loops is automatically selected for routing the call to the switch.

Display (Figure 2-4)

The SLAC contains an alphanumeric call information display. This module is built into the
top of the console.
controls, and a thumbwheel Contrast adjustment.

It contains a 16-character 5x7 dot matrix liquid crystal display, timer

Timer functions are available only when
the attendant presses the Local button. The Time/Timer Exit button allows the user to select
ordinary clock/calendar display or a timer.

In the Time mode, Set, Fwd, and Rev are used to

set the clock. In Timer mode, Start and Stop are used to time events.

The primary purpose of the console display is to provide the attendant with descriptive

information about incoming and outgoing calls. This information includes extension numbers

and associated names, trunk identifiers, reasons for call return and redirection, and number
of calls waiting in the queue for service.

Refer to the “Attendant Display” feature

description, for a detailed discussion of call information displays.

Considerations

An R1V2 system configuration can support either one or two SLACs or one or two DTACs,
but not a combination of a SLAC and a DTAC.

The Switched Loop Console derives its name from the ability of the system to hold incoming
attendant-bound calls in a queue and switch them on voice loops to an available console.
Calls are directed to a console in a preadministered, prioritized sequence. The SLAC differs
from the DTAC in the following basic respects:

● It receives calls one at a time, regardless of the number of incoming calls to the

system (at the DTAC, many incoming calls can be ringing simultaneously).

● It displays pertinent information about incoming and outgoing calls.

● It can serve as an attendant console, a message center, or a combination of both.

● It has speakerphone and Hands-Free Answer on Intercom (HFAI) capabilities.

The optional Direct Extension Selector Console can be connected to a SLAC to provide
busy/idle status of inside stations and quick calling of their extension numbers. In a system
with two consoles, either or both can have a Selector Console as an adjunct. The Selector
Console is described in the “Attendant Direct Extension Selector Console” subsection.

2-19

Switched Loop Operation

All calls that are intended for an attendant position are first routed by the system to a
common queue where they wait to be sent to a console.
consoles, the same queue serves both consoles.

When an attendant console becomes available

In a configuration having two

to receive a call, the system removes a call from the queue and directs it to an idle loop on
the console.
accordance with administered priorities.

Calls are selected from the queue on the basis of “first in/first out” and in

An available attendant console is one that is not

active on a call, has no calls ringing, has at least one LOOP button idle, is not in Position
Busy or Inspect mode, and is not in a split condition.

In a two-console arrangement, each console can be administered to receive all types of calls
or to receive only specific types.

A call that can be received by either position goes to the

first available attendant; when both are available, the call goes to the attendant who has

been idle the longest time.

If one of the two consoles is in “Position Busy” mode, all calls

(except Attendant PDC, Attendant PDC via DID, and DGC calls) direct to the other one.

RED
I-USE-

GREEN
STATUS

Start

Set

Loop

● Loop

●

● Loop

●

● Loop

●

● Loop

●

Conference

Drop

Timer

stop

Rev

Time/
Timer

Exit

●

Alarm

●

● Pos

● Busy

● Flex

DSS

●

●

Source

●

●

Des t

●

Transfer

Hold

Contrast

-------------

Flex DSS

Flex DSS

Flex DSS

Flex DSS

Flex DSS

Flex DSS

Flex DSS

Flex DSS

Cancel

Start

Attendant
Message

.

Waiting

Local

Forced
Release

Last #
Dialed

Flex DSS

Flex DSS

Flex DSS

Flex DSS

Flex DSS

Flex DSS

Join

Release

.

Inspect

Scroll

Figure 2-4. Console Buttons and Display

2-20

An incoming call from the queue to a console appears on one of the five LOOP buttons; the
attendant is alerted to the call by audible ringing, a steadily lighted red lamp, and a flashing

green lamp.

While the call is ringing and while the attendant is handling the call, the
system will direct no more calls to the console. After the attendant ends or releases the call
or puts it on hold, another call can come in on an idle button.

It should be emphasized that even when all LOOP buttons on a console are idle, only one call

can be directed from the queue to the console.

If the attendant puts a call on hold, that
LOOP button is no longer available, but a new call can come in on another button that is
idle.

Answering a Call on a LOOP Button

At an available SLAC, an incoming call will ring at an idle LOOP button automatically
selected by the system.

The attendant has only to lift the handset to answer the call;

pressing the button is not necessary.

Placing a Call on a LOOP Button

In general, originating a call at an idle SLAC involves going off-hook and then dialing the
desired number. However, if Prime Line Preference has been changed to a non-LOOP button,
the attendant will have to press an idle LOOP button before dialing.

If the console is not idle, the attendant can generally use one of these procedures:

● Split the active call (that is, put it on temporary hold by pressing the Start button)

and place another call on the same button;

this is the normal call-extending

procedure.

● If the Automatic Hold feature is enabled, press another LOOP button to place a new

call; the first call goes on hold.

● If the console does not have Automatic Hold (that is, it has the default Automatic

Release), use the Hold button to put the active call on hold; then select a new loop to
place a new call.

Dual Console Operation

A System 25 can be equipped with up to two SLACs, which operate simultaneously when
both are in service. Both consoles can receive the same types of calls, or each can be

administered to receive only certain types.

Busy below), most calls are directed to the other.

When one console is out of service (see Position

Either or both consoles can function as a

message center.

Inside users can reach either attendant by dialing O, or a particular one by dialing the
attendant’s PDC. The DID callers use the Attendant DID number.

Position Busy

Operation of the Position Busy button by the attendant makes the console unavailable to
most incoming calls from the common queue and directs the calls to another answering
station. The only types of calls that are not diverted by Position Busy are Attendant DID,

DGC, and PDC calls. The placing of outgoing calls is not affected. When the Position Busy
condition is active, the green status lamp of the button lights steadily. Position Busy is
similar to the Send All Calls feature, that is not administered on the SLAC.

The Position Busy feature is automatically assigned to a button position (see Figure 2-4)
when the console is administered. In a one-console configuration, however, the feature is
enabled only if a multiline voice terminal in the system is administered as a receiver of calls

2-21

from the common queue while the console is unavailable. If this is not done, the button
should be reassigned to another of the permissible features.

In a two-console configuration, an attendant in Position Busy mode will be covered by the
other attendant. Only one console can be in Position Busy mode at a time.

Call Types

The following types of attendant-seeking calls are sent to the common queue and then
directed to an idle LOOP button at a console:

● Dial Operator calls (placed from inside stations by dialing O)

● Call Following calls logged in at the console

●

Calls to Floating Personal Dial Codes (FPDCs) that are not logged in at a specific
station

● Direct Inward Dialing (DID) calls to numbers that are not assigned to specific

stations

● Attendant DID calls, including Direct Group calls

●

Calls to the attendant’s Personal Dial Code (PDC), including DGC calls

● Coverage calls for which the common queue is a covering receiver

● Returning calls.

The order in which calls are serviced is established by system administration. Each type of
call is assigned a priority that determines its position in the common queue with respect to
other types.
attendant system,

System administration also establishes where the calls go. Obviously, in a one-

all calls automatically go to that attendant. If a system has two

attendants, however, administration can direct calls of each type (with the exceptions noted

below) to either position or to both positions.
Call Following and Attendant PDC calls can be assigned priorities but cannot be directed to

a specific attendant in a two-position system.

Any trunk except types 901-902 and 1003-1008
(DID and Dial-in Tie Trunks) can be assigned a priority and be directed to a specific
attendant position or to both.

Calls accessed by dialing a code [call pickup at other extensions, Trunk-Answer-from-Any­Station (TAAS) Night Service calls, and calls parked by other stations] are originated at a

LOOP button and brought to the console on that same button. These calls do not enter the

common queue.

Ringing

The SLAC receives normal ringing on incoming calls.

Abbreviated alerting (one short burst

of ringing), accompanied by a change in the LOOP button wink rate, indicates to the
attendant that a held call has exceeded the preset hold time interval. Abbreviated alerting
can also be administered as a reminder for new calls entering the queue.

Interactions

A SLAC cannot operate in the same system with a DTAC.
Connection of a headset adapter to the SLAC allows the optional use of a headset instead of

the handset in handling calls.

2-22

Call Originations

Placing a new call from an active console causes interactions with the currently active call.
At a console that has the default Automatic Release feature, the active call is dropped when
the attendant presses anew LOOP button. The new loop becomes the active one; dial tone is
provided, and the attendant can dial a number. If the optional Automatic Hold feature is
administered, the interrupted call is put on hold instead of being lost.

If anew call is originated with the START button or at the Selector Console, the active call
is split. The current loop becomes the active loop for the new call. The display shows the
split call information. This is the normal operating procedure for extending calls.

When a Rep Dial button is pressed while the console is active on a call, the active party is
not dropped or split, and the display does not change. If the active call is with an inside
station, pressing Rep Dial has no effect. But if the active call is on an outside trunk, then
pressing Rep Dial will cause the digits stored on the button to be sent out over the trunk
(“thru-dialing” or “end-to-end signaling”).

When an active call is put on hold manually by operation of the HOLD button, the system
does not automatically select a new loop for placing a call. In this case, the attendant can
select a new loop by pressing an idle LOOP button, then dial a number. Pressing a DSS, Flex
DSS, Auto Intercom, Last Number Dialed, Rep Dial, or Selector Console button will select a

new loop and dial a number in a single operation.

Attendant Features

Refer to the Attendant Feature descriptions for information on other related features (Table
2-E).

Administration Requirements

Station Port:

● Assign voice terminal type.

Assign Prime Line Preference (default: top LOOP button).

●

● Assign flexible buttons.

● Enable ring reminder when calls enter queue.

Trunk Port:

● Assign priorities to calls directed to the console queue.

Assign the attendant(s) to handle calls from this trunk.

●

● Assign unique trunk identifiers.

System:

● Assign DID number for attendant “0” treatment.

● Assign Call Coverage Group number for which the console queue is to serve as a

receiver.

● Assign Automatic Hold or Automatic Release.

● Assign Hold timer interval.

Assign destination of held calls that time out.

●

2-23

● Assign call type priorities and attendant specification.

● Assign call types and attendant specification for Message Center-Like operation in a

two-console configuration.

● Assign Position Busy

“backup’’ station, inapplicable.

Hardware Requirements

Each console requires a port on a ZTN79 ATL Station circuit pack.

Figure 2-5 provides a connection diagram for the SLAC.

SYSTEM 25

CABINET

ZTN79

HYBRID

LINE CP

PART OF

OCTOPUS CABLE

— — ——

— — ——

C2

.

— — ——

— — ——

PART OF SIP

SIP

ADAPT

W1

SWITCHED LOOP

C1

ATTENDANT

CONSOLE T1

— — ——

LEGEND :

TYPICAL-103A CONNECTING BLOCK*

B1 -

MODULAR CORD (D8W-87) - FURNISHED WITH SET

C1 -

OCTOPUS CABLE (WP90780) - PEC 2720-05P

C2 -

7305H04C BUILT-IN SPEAKERPHONE VOICE

T1 -

W1 -

*

-

RANGE :

TERMINAL
4 PAIR INSIDE WIRING CABLE*
FURNISHED BY INSTALLER

WITHIN 2000 FEET OF SYSTEM CABINET (LOCAL POWER REQUIRED >1000 FEET)

- PEC 3162-DIS

Figure 2-5. Switched Loop Attendant Console Connections

2-24

ATTENDANT DIRECT EXTENSION SELECTION

Description

Permits the attendant to extend calls to stations by pressing one or two buttons instead of
pressing START and dialing the PDC or DDC. Each attendant console in a system can have
an associated Direct Extension Selector Console.

A Selector Console can be used with either
a Direct Trunk Attendant Console (DTAC) in an R1V1 or R1V2 system or with a Switched
Loop Attendant Console (SLAC) in an R1V2 system.

The Selector Console is also used by the attendant for simply calling inside stations, in
addition to “extending” calls.

The Selector Console (Figure 2-6) has an array of 100 Direct Extension Selection (DXS)
buttons plus seven Group Select buttons and a Test button. The DXS buttons are labeled 00
through 99. Pressing a Group Select button causes the DXS buttons to be associated with
PDCs from an associated hundreds group. Default assignments for the Group Select buttons
are 200-299, 300-399, etc., up to 800-899. Group Select buttons can be assigned any hundreds
group in the dialing plan.

Pressing a DXS button when off-hook on an incoming call is equivalent to pressing START
and dialing a station.

Such action will busy out the Start facility until the call is released.

The Selector Console can be used to monitor the on-hook/off-hook status of stations in the

system. If the attendant, while on-hook, presses a Group Select button, the Group Select
LED and the LEDs of any busy stations in that group will light steadily.

The DXS button LED (and, in R1V2 systems, the Group Select button LED) associated with
a particular station will flash when one of the following events occurs:

● The station calls the attendant

A call extended by the attendant to the station returns on a RTN-BSY or RTN-DA

●

button (DTAC only) or on a LOOP button (SLAC only)

The station is covered and a call to it is redirected to a COVER button (DTAC only)

●

or to a LOOP button (SLAC only).

The LEDs stop flashing when the call is answered. When the attendant answers a returning
call, the LEDs will return to the state that reflects the current on-hook/off-hook status of

the station.

In all of the above cases, the Group Select lamp associated with the current

“hundreds page” remains lighted steadily.

An outside call can be parked via the Selector Console by pressing one of the eight DXS
buttons that can be programmed with Call Park extension numbers. On the DTAC, the
facility status LED of the parked call winks (to indicate that the call is on hold) and the
status LED on the Selector Console lights steadily. On the SLAC, the call is removed from
the attendant console, with the Selector Console LED lit steadily.

A call parked via the Selector Console and not picked up within 2 minutes will return to the
console.

The status LED of the parked-on button will flash while the call is ringing the

attendant.

A call parked via the Selector Console can be picked up at any voice terminal by dialing the
Call Park retrieval code (*8) and the number on which the call is parked.

2-25

91

90

❑

❑

81

80

❑

❑

71

70

❑

❑

60

61

❑

❑

51

50

❑

❑

41

40

❑

❑

31

30

❑ ❑

20

❑
❑

❑

21

❑

11

10

❑

01

00

❑ ❑

❑

\

96

86

76

66

56

46

36

26

16

❑

06

97

❑

❑

87

❑

❑

77

❑

❑

67

❑

❑

57

❑

❑

47

❑

37

❑

27

❑

❑

17

❑

❑

07

❑

❑

❑

❑

93

92

❑ ❑

❑

82

83

❑

72

❑

62

❑

52

❑

42

❑

32

❑

22

❑

12

❑

02

❑

❑

❑

❑

❑

73

❑

❑

63

❑

❑

53

❑

❑

43

❑

❑

33

❑ ❑ ❑

❑

23

❑

❑

13

❑

03

❑

❑ ❑

95

94

❑

85

84

❑

75

74

❑

65

64

❑

55

54

❑

45

44

❑ ❑

35

34

25

24

❑

15

14

❑

❑

05

04

❑

❑
❑

❑
❑
❑

❑
❑
❑

❑

98

88

78

68

58

48

38

28

18

08

99

❑

89

❑

79

❑

69

❑

59

❑

49

❑

39

❑

29

❑

19

❑

09

❑

/

❑

100 DXS
BUTTONS

WITH LEDS

\

GROUP SELECT BUTTONS
AND ASSOCIATED LEDS

NOTE:

STATUS LEDs are located
to the left of each DXS

button (00-99) under

transparent front cover.

Figure 2-6. Model 23A1 Attendant Direct Extension Selector Console

/

TEST

BUTTON

2-26

The rightmost button on the bottom of the console is a Test button. When it is pressed, all
DXS LEDs will light sequentially; a second press allows individual LEDs to be tested and a
third press ends the test.

Considerations

When there are two Attendant Selector Consoles in the system the Group Select button
assignments are identical.

Whenever an administrative change is made to one console, the

other console is automatically changed.

Buttons on the Selector Console point to either station PDCs, FPDCs (FPDCs), Call Park

codes, DGC access codes, or (V2) pooled facilities.

Calls extended by the Selector console are

directed as described in the “Personal Dial Codes’’ feature description.
When a station calls the attendant, the associated LED on the Selector Console will flash

while the call is ringing and will light steadily when the attendant answers the call. The
LED will light steadily whenever the terminal is off-hook.

Station busy indication is not

provided for buttons pointing to FPDCs.
If a call to a PDC is directed to a COVER or LOOP button on the Attendant Console, the

covered status LED of the voice terminal on the Selector Console will flash and then go dark
when the call is answered by the attendant.

If the covered call was intended for a FPDC
that was logged in at a terminal with attendant coverage, the Selector Console status LED
associated with the FPDC (if assigned) will flash. In this case, the Cover button status LED

will also flash (DTAC only).

A call can arrive at an Attendant Console SYSTEM ACCESS or LOOP button because the
PDC or FPDC is logged in at the Console or because the FPDC is not logged in. For these

calls, the status LED on the Selector Console will not light.

If the attendant extends a call to a station or DGC group and that call returns to the
attendant, the status LED of the called station or group on the Selector Console will flash
and then go dark when the call is answered by the attendant. This is true regardless of the
login status of the PDC.

Interactions

● Attendant Position Busy: The Selector Console functions normally when the

associated Attendant Console is in the inactive mode.

. Attendant Return-Coverage-On-Busy/Or-Don’t-Answer: If a call to a FPDC

is returned to the attendant on a RTN-BUSY or RTN-DA button or on a LOOP
button, the status LED of the FPDC on the Selector Console will flash during ringing
and go dark when answered.

. Call Coverage: If the attendant receives a coverage call for a FPDC, the associated

status LED on the Selector Console will flash and then go dark when the call is
answered by the attendant.

● Direct Group Calling: When all stations in a DGC group are busy, the DXS status

LED on the Selector Console lights.

2-27

Administration Requirements

Special Feature Ports:

● Requires a port assignment on a ZTN79 ATL Station Circuit Pack (CP) for each

Selector Console.

● Assign Group Select button hundreds groups.

System:

● Assign Attendant Call Park codes.

Hardware Requirements
Requires an Attendant Selector Console, and a port interface on a ZTN79 ATL Station CP.
The Selector Console requires a KS-22911, List 1 Power Supply, associated 115V ac power

outlet, and a 400 B-type Adapter.

The 400B2 Adapter provides power to the console at the

wall jack. The Console connects to a port on the ZTN79 ATL Station CP.
Detailed connection information is provided in Figure 2-7. Descriptions of the Station

Interconnect Panel(SIP), Trunk Access Equipment (TAE), and associated cables and

adapters, as shown on the figures, are provided under the heading “Connectivity” in Section

4.

SYSTEM 25

CABINET

ZTN79

HYBRID

LINE CP

LEGEND :

B1 ­B2 ­C1 ­C2 ­C7 ­P1 ­T1 ­W1 -

*-

RANGE :

PART OF

OCTOPUS CABLE

— — ——

C2

.

— — ——

— — ——

— — ——

TYPICAL-103A CONNECTING BLOCK*
40062 ADAPTER ­MODULAR CORD (D8W-87)
OCTOPUS CABLE CABLE (WP90780) - PEC 2720-05P
CORD D6AP-87 ­KS22911 POWER SUPPLY, - FURNISHED WITH CONSOLE
23A1 DXS CONSOLE - PEC 62509
4 PAIR INSIDE WIRING CABLE*

FURNISHED BY INSTALLER

WITHIN 2000 FEET OF SYSTEM CABINET

(LOCAL POWER REQUIRED >1000 FEET)

PART OF

FURNISHED WITH CONSOLE

FURNISHED WITH CONSOLE

SIP

SIP

ADAPT

- FURNISHED WITH CONSOLE

W1

B1

400B2
ADAPT

C7

-48VDC

P1

B2

C1

ATTENDANT

SELECTOR

CONSOLE

T1

Figure

2-7. Attendant Direct Extension Selector Console Connections

2-28

ATTENDANT DISPLAY (V2; SLAC Only)

Description

Provides displays of call-related information on a 16-character screen at the top of the
Switched Loop Attendant Console (SLAC). The following types of data are automatically

presented for calls handled at the console:

● The extension number and name of an inside party called from the console

● The extension number and name of an inside party calling the console

● Called extension number and trunk identification on incoming trunk calls

● Digits dialed on outgoing trunk calls

● Calling and called party identification on internal coverage calls

● Call type and reason for return or redirection

● Number of calls waiting in the common queue to be serviced.

A secondary, or

Inspection, mode allows the attendant to make the console temporarily

unavailable to incoming calls and get information about held calls, trunk availability,

numbers assigned to Repertory Dialing, Automatic Intercom, DSS, or Flex DSS buttons, and
the number currently stored on the Last Number Dialed button. The display module
provides clock/timer functions in the Local mode.

Call Information Display

The console display can generate up to two screens of information. Screen 1 is the normal
display presented for all calls. No action by the attendant is required to access this screen.
Screen 2, activated by pressing the SCROLL button, contains support information about a
call, such as the calling party on a coverage call. If Screen 2 does not appear after SCROLL
is pressed, then no additional information is available for viewing.

● Extension number and calling/called party name

● Redirection descriptors:

> for a coverage call

} for a returning call

& for a call that is being extended.

● Call type indicators that track call status or inform the covering attendant why the

user did not answer:

s for Send All Calls

b for call to busy station
n for no answer
d for DGC call
f for Call Following

2-29

p for Call Park
o for not logged-in FPDC.

● Number of calls waiting in the common queue (l-9 or ! for 10 or more)

● Trunk identification for incoming outside calls

● Conference information.

Considerations

The attendant display provides pertinent information about the currently active call. The
following examples show some typical screens.

Incoming DID call:

2085 DID 3

The first four digits are the DID number assigned to the attendant. The digit 3 is the
number of calls waiting in the queue.

Incoming call from a system user:

1463 Pearson, M

The first four digits are the call

ing user’s extension number. No calls are in the queue.

Incoming coverage call:

>1566 Davis, T 5

A call to T. Davis on extension 1566 is directed to the common queue for coverage. The
attendant can determine the caller’s identity by pressing SCROLL. The following display
appears on screen 2.

2381 Harmon, B s

The call type indicator s means that Harmon’s call was sent to coverage because Davis
activated the Send All Calls feature.

2-30

Returning parked call:

}801 Park

I

The call parked on extension 801 at the Selector Console is returning to the attendant.

Call from console to system user:

1728 Burns, R !

The extension number and name of the called party are presented. The ! symbol indicates
that 10 or more calls are waiting in the queue.

Outgoing trunk call:

912126378888

The display shows the digits (up to 14) of the dialed outside number. Digits in excess of 14
are displayed on screen 2.

Call from inside station extended to another inside extension:

4

2344 Carter, M 7

The attendant answers the incoming call, and the caller, Carter, asks to be connected to
another inside party.
following information:

When the attendant presses START, screens 1 and 2 provide the

&

2344 Carter, M &

7

2-31

The call from Carter has been split while the call is extended. After the attendant dials the
desired PDC, screen 1 displays called party identification, and screen 2 remains unchanged:

&1397 Phelps, T 7

2344 Carter, M &

If the attendant now presses RELEASE, both screens go blank. If the attendant presses

JOIN, the two parties and the console are connected together; screen 1 displays conference

information:

CONFERENCE 3 7

Conference set up by attendant:

After the attendant has called all the conferees and connected them together on a LOOP
button, screen l displays the type of call and the number of parties, including the console:

CONFERENCE 4 7

If the attendant releases, the screen goes blank.

Inspection Mode

Pressing the INSPECT button puts the console in the inspection mode. In this condition the

console is unavailable to incoming calls and the attendant can get information about held

calls, trunk availability, and numbers assigned to certain buttons. Pressing the INSPECT

button a second time will restore the console to normal operation, as will a change of

switchhook state (on-hook to off-hook, or vice versa), selection of an idle loop, or 15 seconds

of inactivity (timeout).

While the inspection mode is active, the attendant can press any of the following buttons to

provide special information on display screen 1.

Loop button where a call is ringing or on hold–The original message that appeared

.

when the call first arrived at the console is displayed; for a multiparty call,
“CONFERENCE N” N=number of conferees) is shown.

.Direct Facility Access button–The display shows the number of trunks that are busy

within the selected trunk group; the format of the message is “XX of YY BUSY. ”

. Repertory Dial, Automatic Intercom, DSS, Flex DSS, or Last Number Dialed–The

number stored on the button is displayed.

2-32

Pressing any button other than those
INFORMATION” to be displayed.

Timer Functions

The LOCAL button allows the attendant to have access to the Timer controls on the left side
of the display module.
alarm functions. The local mode is canceled when the LOCAL button is pressed again, a new
call arrives, or a call is placed.
console for detailed information on using the Timer controls.

Interactions

The display provides a display for each call placed or answered at the console.

Administration Requirements

Directory type information must be administered in the form of user and group names
corresponding to extension numbers and identifiers for incoming trunks. Although system
administration allows up to eleven characters for display IDs, only the first nine characters
are shown on the SLAC display.

Hardware Requirements

In the local mode, the screen can provide clock, calendar, timer, and

Refer to the customer instruction booklet packed with each

listed above causes a message such as “NO

None

2-33

ATTENDANT FORCED RELEASE (V2; SLAC Only)

Description

Drops all active parties from a call in which the attendant and one or more other parties are
connected together.
button while connected to other callers in a conference-type call. The other parties will be
disconnected from the console and from each other. After Forced Release has taken place,
the attendant can receive anew call from the console queue or place a call.

Considerations

Forced Release differs from Release in an important respect. Simple Release separates the
attendant from an extended call or a conference call, but leaves the other parties connected
together; Forced Release completely disconnects all parties.

When the attendant is connected to only one other party, Forced Release has the same result
as Release (that is, the call is ended). If the attendant has already Released, Forced Release
has no additional effect.

Interactions

Refer to the Attendant Feature descriptions for information on related features (Table 2-E).

The attendant uses the feature by pressing the FORCED RELEASE

Administration Requirements

None

Hardware Requirements

None; the FORCED RELEASE button is a standard fixed feature button on the SLAC.

2-34

ATTENDANT JOIN (V2; SLAC Only)

Description

Allows the attendant, while extending an incoming call, to connect together the calling
party, the called party, and the console in a 3-way call.

The attendant activates the feature by pressing the JOIN button while still connected to one

of the other parties.

Considerations

The join feature cancels a split condition.
The attendant can use the Join feature to stay on unextended call and give assistance to the

other parties.

Interactions

Once the JOIN button has been pressed, there is no way to “unjoin” the calling and called
parties (that is, separate them back into SOURCE and DEST).

Refer to the Attendant Feature descriptions for information on related features (Table 2-E).

A joined call can be expanded into a conference call by adding more parties.

All parties can talk to each other.

Administration Requirements

None

Hardware Requirements

None; the JOIN button is a standard fixed feature button on the SLAC.

2-35

ATTENDANT MESSAGE WAITING

Description

Allows the attendant to remotely control the status of Message LEDs on user stations.

Considerations

This feature allows the attendant to notify stations that a message is available for them.
The attendant can activate the Message LED of the station while either (1) ringing, (2)

receiving Busy Tone, or (3) talking to a station.

The status of the Message LED of the called
party is reflected by the green status LED of the Attendant Message Waiting button in any
of these cases.

Note: The Attendant Message Waiting button on the Direct Trunk Attendant Console
(DTAC) is labeled ATT MSG. On the Switched Loop Attendant Console (SLAC), the
name is completely spelled out.

To activate (light) a user’s Message LED in any of these cases, the attendant presses the
Attendant Message Waiting button.

(If the signaled voice terminal is not equipped with a

Message LED, the attendant’s LED will remain dark.)
If the attendant presses the button a second (or third) time before hanging up, the user’s

Message LED will turn Off (and back On), etc.
The red I-Use LED associated with the Attendant Message Waiting button on the DTAC is

inoperative.
The attendant can turn On or turn Off a user’s Message LED without disturbing the user by

going off-hook on a System Access or Loop button, pressing the Attendant Message Waiting
button, and then dialing the station.

Confirmation tone is returned, and the user’s Message

LED will turn on. To turn it off, press the button again.
This feature is not the same as the Station-To-Station Message Waiting or the Call Coverage

Message Waiting features.

Refer to the “Messaging Services” feature description for a

summary of all system Messaging Services.

Interactions

●

Conference: Pressing ATT MSG while on a conference call will be ignored.

●

Coverage Calls: The attendant can light the Message LED of the covered station
when receiving a coverage call for the station.

●

Hands-Free Answer On Intercom: If the attendant lights the Message LED on a
voice terminal with AUTO ANS button active, the auto-answer function will turn off,
allowing subsequent calls to receive coverage as assigned.

Administration Requirements

Attendant Position (Station Port):

● Assign ATT MSG button (defaulted).

Hardware Requirements

Stations must have a Message indicator (not assignable).

2-36

ATTENDANT POSITION BUSY

Description

Allows an Attendant Console to be placed in an inactive mode.

Systems with Direct Trunk Attendant Console(s) (DTAC)

There must be two Attendant Consoles in the system before this feature can be activated. A
Position Busy (POS BUSY) button can be assigned on each of the consoles. Pressing POS
BUSY at one of two active consoles causes the POS BUSY status LED to light and the
console to be placed in the inactive mode.
LED to go dark and the console to be reactivated.
Attendant Console is active is ignored (i.e.,
time. )

When a console is in the inactive mode, ringing is disabled on facility appearances on the
two rightmost button columns only.
normally. Calls to floating PDCs not logged in,
transferred to the active console. Internal calls to the PDC of the inactive console will still
be directed to that console.

Incoming calls on lines that normally ring at only the inactive console will now ring at the
active console if they have an appearance there.

All buttons on the inactive console will continue to function normally, including the Selector
Console buttons.
leftmost two columns of buttons on the inactive console are not affected by the Position Busy
feature.

Calls can be originated by the inactive console. Call appearances in the

Pressing POS BUSY a second time causes the

Pressing POS BUSY when only one

only one console is allowed to be inactive at a

The (green) status LEDs will continue to operate

DID calls, and dial “O” calls will be

The attendant can press a Direct Station Selection (DSS), Automatic Intercom (AUTO
ICOM), or a Direct Facility Access (FACILITY) button and then receive busy-to-idle
reminder when the facility becomes idle.

All dial “O” calls, calls to FPDCs not logged in, calls to unassigned DID numbers, and calls

to facilities in the rightmost two columns of buttons of the console that appear at both
consoles will be directed to the active console.

Note that if a personal trunk appears on only one DTAC, incoming calls on those trunks will
not receive service when the console is inactive. For this reason, it is strongly recommended
that each DTAC attendant be assigned a Call Coverage-Individual (COVER-IND) button for
the other console so that these calls can be covered. Also, be sure to make the Attendant
Console the principal station (owner) on all trunks that are to receive coverage by the other
attendant.

Systems with Switched Loop Attendant Console(s) (SLAC)

In order for the Position Busy feature to be operational, the system must have either two
attendant positions or one position plus a multiline voice terminal administered as a

“backup.”
make it inactive and cause most calls in the common console queue to be directed to the
active console.
Busy condition at a time.
terminal, pressing the POS BUSY button will make the SLAC inactive, and most calls from
the common queue will be directed to the

If the system has two consoles, pressing the Position Busy button on one will

Each attendant covers for the other. Only one console can be in Position

If the system has one console with an administered

backup voice

backup terminal.

2-37

A console in Position Busy mode can receive attendant PDC, DID, and DGC calls, and

outgoing calls can still be placed. Local functions can be activated.

Considerations

Position Busy allows one of two attendant positions to be made inactive when not required.
This is useful in situations where calling traffic requires only one console operator.

Interactions

● Attendant Call Extending: Unanswered calls extended by an inactive console will

return to the active console on the Return-On-Don’t-Answer (RTN-DA) button
(DTAC only) or on a Loop button (SLAC only).

● Attendant Camp-On: Calls Camped-On by an inactive console will return to the

active console when Camp-On timeout occurs.
Attendant Message Waiting: An inactive attendant is permitted to control voice

●

terminal Message LEDs.
Automatic Intercom: The inactive attendant is permitted to place Automatic

●

Intercom calls. DTAC only: Automatic Intercom calls to the inactive attendant will
not ring at the console or be transferred to the active attendant when the AUTO
ICOM button is located in one of the two rightmost button columns

● Call Coverage:

DTAC only: If the active attendant is a coverage receiver for the inactive attendant,
coverage is invoked and calls will appear at the active attendant’s Cover button. If
the inactive attendant is a coverage receiver for the active attendant, coverage, when
activated, is invoked at all coverage stations including the inactive attendant.
However, if the Cover button is located in one of the two rightmost button columns,
coverage calls will not ring at these buttons.

SLAC only: All Calls covered by the common queue will be directed to the active
console.

●

Call Park: A call parked on the inactive attendant console will return to the
inactive console if the call times out; calls parked via the Selector Console will return
to the active console.

Direct Group Calling: If the inactive attendant is a member of a DGC Group, calls

●

directed to the group will be routed to the inactive attendant. The attendant must
dial *4 (activate DGC Group “Make Busy”) to busy out from the group. Dialing *6
deactivates the “Make Busy” function.

● Direct Inward Dialing: All DID calls to unassigned DID numbers will be

transferred to the active attendant.

● Night Service: An inactive attendant that is a Directed Night Service receiver will

receive Night Service calls.

● Personal Dial Codes: If a PDC/FPDC is logged in at an inactive attendant

console, then calls to this PDC/FPDC will go to the active attendant (SLAC) or to
the inactive attendant (DTAC only). All calls to floating PDCS not logged in will be
transferred to the active attendant.

2-38

. Personal Lines (Trunk Appearances) on DTACs : All calls to trunks having an

appearance in either of the two leftmost button columns will ring normally at the
inactive console.
rightmost button columns will not ring.
the active console, they will ring there even if they do not normally.

.

Program: The Program feature remains active at the inactive console.

All calls to trunks having appearances in either of the two

If these trunks also have an appearance at

. Programmable Buttons:

active on the inactive console.

Administration Requirements

Voice Terminal: (Station Port)

●

Assign Position Busy button on DTAC. A Position Busy button is defaulted to the
SLAC; it can be assigned to another feature if desired.

●

Assign COVER-IND buttons between consoles (DTAC only).

Hardware Requirements

None

All DSS, Flex DSS, and REP DIAL buttons remain

2-39

ATTENDANT RELEASE

Description

Releases the attendant from an extended call. There are two forms of Attendant Release:
Manual and Automatic. This feature applies to the Direct Trunk Attendant Console (DTAC)
and the Switched Loop Attendant Console (SLAC).

Manual Release:

Pressing RELEASE releases the attendant from an extended call and completes the
associated call transfer. The status LED of the original calling facility will change from
hold to busy for direct trunk terminations and from hold to idle for other call facilities (e.g.,

Loop, Return- On-Busy, Return-On-Don’t-Answer,

System Access).
Calls cannot be released to Reorder or Dial Tone.
Pressing CANCEL terminates the destination call and reconnects the attendant to the

calling party.
operation will be terminated (the calling party remains on hold). In this case, the attendant
can go off-hook and press the held call appearance button to reconnect to the calling party.

Automatic Release:

This feature simplifies the attendant procedures by eliminating the need for the attendant to
press RELEASE when releasing from one call to handle another. Selection of any new line
facility while active on the Start button will automatically release the first call. At release,
the status LED of the first calling facility will change from hold to busy for direct trunk
terminations and from hold to idle for other call facilities (e.g., Loop, Return-On-Busy,
Return-On-Don’t-Answer, Cover, Automatic Intercom, DSS, and System Access).

If the attendant goes on-hook without first releasing a call, the call extending

Cover, Automatic Intercom, DSS, and

The Automatic Hold feature can be administered for the SLAC as an alternative to
Automatic Release.

place a call or pick up a held call, the active call is put on hold—not released.

Considerations

Attendant Manual Release improves attendant efficiency in handling calls by allowing the
attendant to release an extended call without having to wait for the called station to answer.

Attendant Automatic Release enhances the attendant’s ability to handle many calls by
eliminating the Release operation when answering a second call.

The Release function is inhibited whenever the Start facility is connected to Reorder or Dial
Tone. Pressing CANCEL will terminate the destination call and reconnect the attendant to
the calling party.

Administering the Automatic Hold option instead of Automatic Release reduces the
occurrence of accidentally dropped calls.

If the attendant, active on a loop call, presses another loop button to

2-40

Interactions

● Attendant Camp-On: External calls that are released when Busy Tone is heard

will be camped on.

Administration Requirements

None.

Hardware Requirements

None.

2-41

ATTENDANT RETURN COVERAGE ON BUSY

Description

Allows a camped-on call at a busy station or DGC Group to be returned to the attendant for
service after a specified time period.

A camped-on call not answered within 1 to 120 seconds (administrable) after the attendant
releases the call will return to the console in one of the following ways:

●

On the Return-On-Busy (RTN-BUSY) button at a Direct Trunk Attendant Console
(DTAC).

●

On a LOOP button at a Switched Loop Attendant Console (SLAC; V2).

To answer a returned call at a DTAC, the attendant presses RTN-BUSY (if not selected by
Ringing Line Preference. ) A returned call can be reextended via the START button or a
Selector Console button. In either case, the Return-On-Busy button is idled as soon as the

attendant releases.

To answer a returned call at a SLAC, the attendant merely lifts the handset to be connected

to the ringing loop.

When the RTN-BUSY button is busy at a DTAC, the calling party will remain on-hold; if a

loop is not available at a SLAC, the returning call remains in the console queue. The system
will continue to attempt to ring the called station until the RTN-BUSY button is idle or a
loop is open.

When Attendant Camp-On is not provided (Camp-On return time set to zero
seconds), calls released by the attendant to busy tone are returned to the console
immediately.

Considerations

Attendant Return-Coverage-On-Busy allows the attendant to service calls not answered
within specified time intervals. This provides the calling party better service and results in

fewer lost calls.

Interactions

●

Attendant Camp-On: External calls that are released when Busy Tone is heard
will be camped on.

●

Attendant Console, Direct Trunk: As long as an Attendant Console remains
active, the call will return to the attendant who transferred it.

●

Attendant Console, Switched Loop (V2): A returning call is directed from the
console queue to a LOOP button on any available console that is administered to
receive it.

●

Attendant Direct Extension Selection: If a call to a Floating PDC (FPDC) is
returned to the attendant, the FPDCs status LED on the Selector Console will flash
during ringing and go dark when the call is answered.

●

Direct Group Calling: External calls that are camped onto a DGC group that does
not have a delay announcement will return to the attendant console after the

specified number of rings.

2-42

. Send All Calls (DTAC only): If Send Al

ring at the DTAC.

Administration Requirements

System:

Calls is activated, returning calls will

. Assign number of seconds before unanswered camped-on calls return to the

Attendant Position (1-120 seconds, or O for No Camp-On) - Default = 30 seconds.

Hardware Requirements

None

2-43

ATTENDANT RETURN COVERAGE ON DON’T ANSWER

Description

Allows unanswered calls extended by the attendant to be returned to the attendant for

additional service.
Calls that are not answered after a specified number of rings will transfer ringing to the

Return-On-Don’t-Answer (RTN-DA) button on a Direct Trunk Attendant Console (DTAC) or

to a LOOP button on a Switched L

OOP Attendant Console (SLAC). If the called voice

terminal has call coverage, the timing for return begins only after the coverage station
begins ringing.

When the RTN-DA button is busy, calls will continue to ring at the called station until the
button is idle. If a LOOP button is not available, the returning call stays in the common
queue until it can be serviced.

To answer a returned call at a DTAC, the attendant presses RTN-DA (if not selected by
Ringing Line Preference.) The call can be reextended via the START button or Selector
Console. In either case the button is RTN-DA button is idled as soon as the attendant
releases.

To answer a returned call at a SLAC, the attendant merely lifts the handset to select the
line.

Considerations

Attendant Return-Coverage-On-Don’t-Answer allows the attendant to service calls not
answered within a specified number of rings. This provides the calling party better service

and results in fewer lost calls.

Interactions

● Attendant Console, Direct Trunk: As long as an Attendant Console remains

active, the call will return to the attendant who extended it.

● Attendant Console, Switched Loop: A returning call is directed from the

common queue to a LOOP button on any available console that is administered to
receive it.

● Call Coverage:

DTAC only: Whenever a DTAC attendant is a call coverage receiver for a particular

call coverage group and a call is placed from the attendant position via the Start

button or the Selector Console to a voice terminal in that group, the Call Coverage­Group (COVER-GRP) button on the Attendant Console will not track the call
(COVER-GRP button status LED will not flash). If the call remains unanswered, it

will return to the Attendant Console on the RTN-DA button rather than the
COVER-GRP button.

SLAC only: Whenever the common queue is a receiver for a particular call coverage

group and a call is placed from the attendant position via the START button or the

Selector Console to a voice terminal in that group, an unanswered call will return to

the attendant queue as a Return-On- Don’t-Answer call (instead of as a coverage

2-44

call).

● Send All Calls (DTAC only): If Send All Calls is activated, returning calls will

ring at the DTAC.

Administration Requirements

System:

Assign number of rings before call return to the Attendant Position (1-31) - Default

●

= 5 Rings.

Hardware Requirements

None

2-45

ATTENDANT SOURCE AND DESTINATION (V2; SLAC Only)

Description

Allows the attendant, while extending a call, to switch back and forth between the calling
party (the source) and the called party (the destination) before connecting them together.

Pressing the SOURCE button on the SLAC after the called party has been reached has these
results:

The called party (the destination) is put on hold.

●

●

The attendant is reconnected to the calling party (the source).

●

The green status lamp of the DEST button starts winking to indicate that the
destination is on hold.

●

The green status lamp of the SOURCE button goes from winking to dark.

Pressing the DEST button after the source has been reconnected has these results:

●

The source is put on hold (again).

●

The attendant is reconnected to the destination.

●

The green status lamp of the SOURCE button starts winking to indicate that the
source is on hold.

●

The green status lamp of the DEST button goes from winking to dark.

Considerations

The Source/Destination feature is useful when the attendant needs to talk to each party

privately before connecting them.

Interactions

The Source/Destination feature can only be activated before the two parties are connected
together.

When the attendant presses JOIN, the other parties and the attendant are joined in a 3-way
connection.

When the attendant presses RELEASE, the other parties are connected, the call is separated
from the console, and the attendant is free to handle other calls.

After the source and destination parties are connected together, the SOURCE and DEST

status lamps go dark.

Administration Requirements

None

Hardware Requirements

None; the SOURCE and DEST buttons are standard fixed feature buttons on the SLAC.

2-46

ATTENDANT SPLITTING ONE-WAY AUTOMATIC

Description

Allows the attendant to converse privately with a called party while the calling party is split

away on hold.
When the attendant presses START (or a DXS button) to extend an incoming call to a called

party, the calling party is automatically split away from the connection and placed on hold.
This allows the attendant to talk privately with the called party before extending the call.
The attendant can then press RELEASE to complete the transfer or CANCEL to drop the
called station and return to the incoming call.

If the console is a SLAC, the attendant can also use the Join and Source/Destination
features while in the Start mode. Refer to the descriptions of these features for details.

Considerations

Attendant Splitting One-Way Automatic allows the attendant to (1) announce a call, (2)
determine privately whether the called party is available to receive the call, and (3) obtain
information if necessary to redirect the call or take a message.

Interactions

. Attendant Source/Destination (V2; SLAC only): This feature can be used after

reaching the called party.
calling party and the called party before connecting them together.

It allows the attendant to speak privately to both the

. Music-On-Hold: Music-on-hold is not provided to the calling party while the call is

split from the console.

Administration Requirements

None

Hardware Requirements

None

2-47

ATTENDANT SYSTEM ALARM INDICATION

Description

Provides an Alarm on the Attendant Console to alert the attendant to problems detected by
the system software.
detected fault persists longer than four minutes, or if more than five transient faults per
hour are detected.

The ALARM LED on the Attendant Console will flash whenever a

The alarm indication should be reportd immediately to your AT&T

Systems Technician.

The alarm type that causes an alarm indication is referred to as a Permanent System
Alarm. These alarms are faults that can cause degradation of service and require immediate
attention.

If a flashing ALARM button is pressed, the LED will change from flashing to steadily lit. A
new trouble situation will cause a steady ALARM LED to start flashing again. Only when
the trouble has been corrected will the LED turn off.

Considerations

The ALARM LED on the Attendant Console provides a warning as soon as the fault is
detected. This permits a quick response to system detected faults.

In a two-attendant system, both consoles track problems.

Interactions

None

Administration Requirements

None

Hardware Requirements

None

2-48

AUTOMATIC INTERCOM

Description

Allows a multiline voice terminal user (or attendant) to place and answer calls to and from
another station by use of a dedicated button appearance.

Automatic Intercom provides a private path between

two designated multiline voice
terminals. To place an Automatic Intercom call, the calling party presses the Automatic
Intercom (AUTO ICOM) button and goes off-hook.
and the called party receives standard ringing.

The calling party hears ringback tone

The status LED associated with the button
is steadily lit at the calling voice terminal and flashing at the called voice terminal. To
answer an Automatic Intercom call, the called party presses AUTO ICOM (not necessary
with Ringing Line Preference ) and goes off-hook.

The AUTO ICOM status LED lights steadily whenever the other party is off-hook. This
provides each party with a station-busy indication for the other.

To activate the busy-to-idle
reminder, the user can press AUTO ICOM (remaining on-hook). A short burst of tone is
provided when the other party goes on-hook.

The user can then go off-hook, and the call will

be placed; the user does not press the AUTO ICOM button again.
Pressing AUTO ICOM to invoke the busy-to-idle reminder overrides Prime Line Preference.

Once activated, the feature can only be canceled by preelection of another button or
answering an incoming call.

See the “Busy-to-Idle Reminder” feature description for more

information.
At a Switched Loop Attendant Console, operation of an AUTO ICOM button seizes an idle

loop button for the outgoing call. An incoming intercom call arrives on a loop button and
does not flash at the AUTO ICOM button of the console.

Considerations

The intercom feature should not be confused with ordinary station-to-station calling inside

the system using dialed PDCs.

With Automatic Intercom, users who frequently call each
other can do so by pressing one button instead of dialing a PDC. In addition, the station­busy indication and busy-to-idle reminder provide additional utility to users.

This feature is similar to Direct Station Selection (DSS), except that the buttons must

always be assigned in pairs (i. e.,
point to a single-line set.

Also, Automatic Intercom calls arrive at the AUTO ICOM button,

between two sets.) Hence, an AUTO ICOM button cannot

thereby providing calling party ID; DSS calls arrive on System Access buttons.

Interactions

● Attendant Position Busy: The inactive attendant is permitted to place Automatic

Intercom calls. For DTAC only: Automatic Intercom calls to the inactive attendant
where the AUTO ICOM button is located in one of the two rightmost button columns
will not ring at the console, nor can they be covered by the active attendant. For
SLAC only: Automatic Intercom calls to the inactive attendant will ring at the
inactive SLAC.

● Call Coverage: Automatic Intercom calls are considered private and do not receive

call coverage.

2-49

●

Call Pickup: When an Automatic Intercom call is picked up via Call Pickup, the

AUTO ICOM status LED on the called voice terminal lights steadily. The called
party can press AUTO ICOM to enter the call at any time.

● Direct Group Calling: Automatic Intercom calls cannot be directed to DGC groups.

● Exclusion: Any attempt to engage Exclusion while active on an Automatic Intercom

call will drop the other party.

● Last Number Dialed (V2): Numbers called using an AUTO ICOM button are not

saved by the Last Number Dialed feature.

● Line Selection (Prime Line Preference): When the Automatic Intercom line is

assigned Prime Line status, the AUTO ICOM button must be pressed to activate the
busy-to-idle reminder even though the I-use LED is already lighted steadily.

Administration Requirements

Voice Terminal: (Station Port)

● Assign AUTO ICOM buttons to voice terminals in pairs. Voice terminals can have

several AUTO ICOM buttons assigned for direct access to multiple stations.

Hardware Requirements

None

2-50

AUTOMATIC ROUTE SELECTION (ARS)

Description

Provides for the routing of calls over the telecommunications network based on preferred
routes (normally the least expensive route available at the time the call is placed.)

An ARS pattern can be composed of two subpatterns (time of day determines which

subpattern is selected), each consisting of up to three routes, associated Facility Restriction
Level (FRL) codes (described below), and CO overflow flags. A route is identified by
specifying a Facility Access Code for the pooled facility (trunk group); for V2 systems only,
a route may also be identified by specifying a Virtual Facility code.

A trunk group (or virtual facility, for V2) can be used in more than one ARS pattern and
more than once within a pattern.

Call routing can be specified by as many as eight routing patterns. Each pattern contains a
sequential list of routes (for example, trunk groups) the system can use to complete a call.
Number translations (deletion and addition of dialed digits) necessary to route the call is
determined on a trunk group basis.
are busy or the route FRL is too high is optional.

Overflow to the local CO when all trunks in a pattern

If all trunks in a pattern are busy

(including CO trunks if overflow is allowed), the call queues on the first route in the pattern.
All calls placed using the ARS access code (default = 9) are routed via the feature. The

dialed numbers that follow the ARS access code are generally seven or ten digit DDD
numbers preceded by a “l” if required by the serving Central Office. Numbers preceded by a
“0” are routed over the local CO pooled facility.

Typically, a dialed 7-digit number consists of a CO code and exchange number in the form
NXX-YYYY where N = 2-9, X = 0-9, and Y = 0-9. A 10-digit number consists of an area
code, CO code, and exchange number in the form NPA-NXX-YYYY where N = 2-9, P = 0-1,

A = 1-9, X = 0-9, and Y = 0-9.
Each route in a pattern has an associated FRL (0-3). This FRL may differ each time the

facility is specified as a route.

A facility with a FRL of “0” is least restricted to callers; a

FRL of “3” is the most restricted. Similarly, each station in the system is assigned an FRL
(0-3). A terminal assigned an FRL of “0” has the least ARS privileges (i.e., routes with

FRLs of 1-3 are restricted); a FRL of “3” provides the most privileges. A station’s FRL
must be equal to or greater than the routes FRL to use the route.

The ARS feature, when accessed, selects a pattern as follows:

● Emergency Number Calls (routed via the local CO facility)

● International Calls (routed via the administered international pattern)

● Calls made to specified COs or seven digit telephone numbers within the Home

Number Plan Area (HNPA). These calls are routed as specified in the HNPA
Exception Lists, or else via the NPA Routing Table or (by default if not otherwise
specified) the local CO facility.

● Calls made to NPAs outside the HNPA, sometimes referred to as Foreign NPAs

(FNPAs). The route selected depends on the type of call, as follows:

—

FNPA special number calls (includes all “800”, “900”, and Telex 510, 610, 710,
and 810 numbers). For V2 systems, each FNPA of the form N00 and
be assigned to a routing pattern.

For V1 systems, these calls are routed via

N10 may

the local CO facility.

2-51

—

FNPA calls made to numbers specified in the FNPA Exception List.

—

All other FNPA calls.

ARS Flow Chart

Figure 2-8 provides a simplified ARS flow chart. Bracketed numbers (e.g., [401], [601])
provide a link between ARS administrable action numbers and the associated item on the
flow chart.
description in association with the System

Certain readers may find this reference useful when reading the following

25 Administration Manual. Administrable System,

Station, Toll Allowed, and Trunk action numbers are also noted where applicable.
The ARS feature is accessed when a user dials the ARS access code. As shown on Figure 2-

8, the number dialed is first checked against the Emergency Numbers List. This list consists
of special service codes (911) and up to three customer-defined seven digit numbers. If the
number dialed matches one of the numbers on the list, the call is immediately routed via the
local CO facility. All user call restrictions are disregarded.

If the number dialed is not on this list, a check is made to determine if the terminal is

allowed to originate outside calls.

If the terminal is outward restricted, the caller receives
Reorder Tone; otherwise, the dialed number is checked against any toll restrictions that
apply.

Terminals may be assigned a Toll Restriction Class (1-4), or be unrestricted (Class 0).
Terminals assigned Toll Restriction Class 1 have the most privileges, those assigned Class 4
have the least privileges.
system.

Up to 64 3-digit CO codes and 6-digit NPA plus CO codes may be divided among the

There are four associated Toll Call Allowed Lists (l-4) in the

four lists.
Numbers dialed from voice terminals assigned Toll Restriction Class 1 are checked against

all four Toll Call Allowed (TCA) Lists; numbers dialed from Class 2 terminals are checked
against TCA Lists 2-4; numbers dialed from Class 3 terminals are checked against TCA Lists

3-4; and numbers dialed from Class 4 terminals are checked against List 4 only. If the

number dialed does not appear on a list,

the user receives Reorder Tone. Calls originated at

unrestricted (Class 0) terminals are not screened.
Calls are checked to determine if they are international calls or operator calls. Dialed

numbers “01” or “011” signify international calls, “0” plus a number other than “l” signify
operator calls.
selected and the call routed accordingly.

If the call is an international call, the international routing pattern is

Operator calls are routed via the local CO facility.

Calls within the HNPA are checked against the HNPA Exception Lists. There may be up to
four of these lists, each with an associated ARS Routing Pattern. Up to 800 (64 in R1V1) 3-

digit office codes may be divided among the four lists (eight entries may be 7-digit numbers.)

If a match is found, the call is routed via the associated ARS Routing Pattern. If no match
is found the dialed number is routed via the HNPA pattern (specified in the NPA Routing
Table ), or if none is specified, via the local CO facility.

If a number is entered more than once in the exception list, the pattern used will be the
pattern associated with the more specific number.

The NPA Routing Table is simply a listing of North American Plan NPAs and Special
Number NPAs (V2), each having an associated ARS Routing Pattern (all North American
NPAs are assigned routing pattern 1 by default). A dialed NPA that is listed in the table is
routed using the associated Pattern.

Calls to NPAs not listed are routed via the local CO

facility.

2-52

V1 Systems Only: For calls outside the HNPA (FNPA calls), a check is made against a

non-administrable Special Numbers List. The numbers in the list include all “800” and
“900” numbers and Telex codes 510, 610, 710, and 810. If a match is found, the call is routed

via the local CO facility.

For FNPA calls not on the Special Numbers List (Vi), the dialed numbers are checked

against the FNPA Exception List (Vl and V2). Up to 32 entries may be assigned to the list.

Each entry must consist of a 3-digit NPA code, 3-digit CO code, and two additional digits
(for a total of 8 digits). The last two digits may be “.”, which match any digit. Each entry
has an associated ARS Routing Pattern. If a match is found, the call is routed using this
pattern. If no match is found, the call is then checked against the NPA Routing Table. A
dialed NPA that is listed in the table is routed using the associated Pattern. Numbers that
don’t match are routed via the local CO facility.

ARS Routing Pattern Table

Figure 2-9 provides a block diagram of an ARS Routing Pattern. Up to eight of these
patterns may be administered in the system.
may be chosen based on the time of day. Each subpattern (A and B) can contain up to three

allowed routes. If all routes in a subpattern are busy, a CO overflow flag (when set) allows
the call to be routed via the local CO facility; otherwise, the call will queue on the first route
in the subpattern.

Administrable Start and Stop times (Hour and Minute) for Routing Subpattern A specify
when Subpattern A should be used to route calls.
other times.

Each pattern consists of two subpatterns that

Subpattern B is used to route calls at all

Each route is specified by its trunk group facility access code (or Virtual Facility code in V2)

and an associated FRL.
An FRL is typically lower for the first route in a subpattern and increases with each

additional route in the pattern.
FRL for the route to be selected. The system first checks the Route #1 for an available
trunk on which to route the call. If the route is busy, Route #2 is checked, then Route #3, if
required. If all routes in the subpattern are busy and the CO overflow flag is set, the voice

terminal FRL is checked against an associated Overflow FRL before routing the call. For V1
only: If the voice terminal is allowed access to the local CO trunk pool, the system, on
overflow, will attempt to place the call regardless of the associated FRLs.

If all routes in a subpattern are busy and the CO Overflow flag is not set, or all CO trunks

are busy, the call returns to the first route in the subpattern and is queued (if the station

FRL permits access to the first route). The caller is placed in an off-hook queue indicated by
five short bursts of tone (Preferred Routing Tone). The order of service in the queue is First

In First Out (FIFO). An ARS user placed in an off-hook queued state always has precedence
over users with a Direct Facility Access buttons. There are 16 slots available in the ARS
queue.
caller receives Reorder Tone instead of being queued.

Once a route has been selected, the entries in a Digit Translations Table associated with the
selected route’s trunk group (or Virtual Facility in V2) is checked. Based on an associated

NPA and the NPA dialed, the system can remove up to 10 digits and then add a pattern of
up to 5 digits as specified to route the call.

A route #1 must be specified in the subpattern for a call to queue. If it is not, the

A terminal’s FRL must be equal to or greater than the route

2-53

STATION USER

DIALS ARS

ACCESS CODE

[401]

NUMBER DIALED
ON EMERGENCY
NUMBERS LIST

(911, AND

THREE CUSTOMER
DEFINED 7-DIGIT
NUMBERS

[601-603]

YES

CALL ROUTED
VIA LOCAL
CO FACILITY

VOICE TERMINALS
“RESTRICT
OUTWARD
CALLS” = YES

NO

STATIONS

I

[13]

YES

CALLING USER
RECEIVES SYSTEM
REORDER TONE

NO

VOICE TERMINAL
ASSIGNED TOLL
RESTRICTION
CLASS 1-4

STATIONS
[14]

YES

NUMBER DIALED ON TOLL CALL
ALLOWED LIST? 64 CODES MAY
BE DIVIDED INTO 4 LISTS OF YES
ANY LENGTH

TOLL ALLOWED

[1-3]

NO

STATION USER
RECEIVES SYSTEM
REORDER TONE

NO

NUMBER DIALED
INTERNATIONAL,
OPERATOR, OR
OTHER

OPERATOR

ROUTE CALL
VIA LOCAL
CO FACILITY

ROUTE CALL
VIA
INTERNATIONAL
ROUTING
PATTERN

[ 402]

OTHER
(SHEET 2)

INTERNATIONAL

Figure 2-8. Automatic Route Selection Flow Chart (Sheet l of 2)

2-54

FROM

SHEET 1

NUMBER DIALED
WITHIN HOME
NPA?

SYSTEM [30]

YES

V1 ONLY: NUMBER
DIALED ON SPECIAL
NUMBERS LIST

(ALL 800,900,
AND TELEX 510,
610, 710, AND
810 CODES)

YES

NUMBER DIALED
ON FNPA
EXCEPTION

NO

LIST

NO

YES

CALL ROUTED
VIA ASSOCIATED
ROUTING PATTERN

AREA CODE ON

NO

NPA ROUTING

TABLE [300]

CALL ROUTED
VIA ASSOCIATED
ROUTING PATTERN

YES

NUMBER DIALED
ON HOME NPA
EXCEPTION

LISTS

[500]

YES

CALL ROUTED
VIA
ASSOCIATED
ROUTING
PATTERN

NO

CALL ROUTED
VIA LOCAL
CO FACILITY

HOME AREA CODE
ON NPA ROUTING
TABLE [300]

NO

CALL ROUTED
VIA LOCAL
CO FACILITY

YES

Figure 2-8. Automatic Route Selection Flow Chart (Sheet 2 0f 2)

CALL ROUTED
VIA ASSOCIATED
ROUTING PATTERN

2-55

The following tones are associated with ARS:

●

Confirmation–Indicates that a queued call is being serviced (trunk available to route
call )

Busy—Indicates that the called number is busy

●

● Reorder–Indicates that all trunks are busy, the ARS queue is full, or that ARS

calling is denied.

● Preferred Route Tone—Five very short tones that indicate that your call has been

queued for the preferred route.

Considerations

With ARS, users do not have tc worry about accessing a particular pooled facility to make a
long distance call. The user simply dials the ARS access code and the desired number. The
system then routes the call via the facility best suited for that call.

The following provides a summary of the ARS call routing controls provided by the feature:

●

Emergency Numbers

List: 911, and up to three customer-defined, 7-digit

numbers.

● Toll Call Allowed Lists: 1-4 lists, 64 entries maximum between all lists. Entries

may be 3-digit CO codes or 6-digit NPA plus CO codes. (Administrable for uses
besides ARS)

Station Toll Restriction Class: l-4 Classes (Administrable for users besides ARS)

●

HNPA Exception List: 1-4 Lists, each with an associated ARS Routing Pattern.

●

800 (64 in Vl) 3-digit CO codes entries maximum between all lists (eight of the
entries may be 7-digit numbers.)

● NPA Routing Table: Entries may include every North American NPA (and Special

Number NPAs in V2), each with an associated ARS Routing Pattern. All NPAs are
assigned Routing Pattern #1 by default.

FNPA Special Numbers List (VI only): Routes all “800”, “900”, and Telex 510,

●

610, 710, and 810 numbers via the local CO trunk group (not administerable)
FNPA Exception List: One List with up to 32 eight-digit numbers. Each entry has

●

an associated ARS Routing Pattern.

Digit Translations Tables: One per trunk group (Vl and V2) or Virtual Facility

●

(V2 only).

A system can have up to eight ARS Routing Patterns assigned. Each pattern can contain up
to six routes (three per subpattern).

Interactions

● Calling

administered, prevent calls from routing via ARS. Pooled facility access restrictions
do not apply. In fact, the recommended arrangement to ensure that users make
maximum use of ARS is to block dial access to most trunk groups, so that users must

dial the ARS access code to place calls.

Restrictions: Outward Restriction and To1l Restriction, when

2-56

● Direct Facility Access Button: Multiline voice terminal users who have pressed

FACILITY to activate the busy-to-idle reminder must wait until all queued ARS
users have been serviced.

● Virtual Facilities (V2 only): Virtual Facilities may be used in place of trunk

groups in ARS routing patterns. When used with ARS, a digit translation scheme

may be associated with each virtual facility. See the “Virtual Facilities” feature

description for more information.

Administration Requirements

System:

● Specify your area code (HNPA )

ARS

● ARS Access Code (1-9999) - Default = 9

International ARS Routing Pattern Number (1-8) - No default

●

Three Emergency Numbers Lists (7-digit numbers) - No default

●

● NPA Routing Table (NPA code and associated pattern number 1-8) - Default = 1

● HNPA Exception List:

—

List Number (l-4)

—

Pattern Number (1-8)

—

Exception Numbers (NXX or NXX-YYYY). Last three digits may be “.”

● FNPA Exception Telephone List

—

Pattern Number (1-8)

—

Telephone Number (8-digits in the form NPA-NXX-YY). Last two digits may

“ ”

be .

● Digit Translations Table

—

Trunk Group Facility Access Codes (1-9999) or, in V2, Virtual Facility Codes

(#190-#199)

—

Associated NPA (NPA)

—

Number of digits to remove for calls within associated NPA (1-10 digits,
none)

—

Digit pattern to add for calls within associated NPA (maximum of 5 digits) ­Default = none

—

Number of digits to remove for calls not in associated NPA (1-10, none) ­Default = O

—

Digit pattern to add for calls not in associated NPA (maximum of 5 digits) ­Default = none

● ARS Routing Pattern:

Pattern Number (l-8)

2-57

—

Subpattern A Start and End Time (Hour: Minute)

—

Subpattern A and B–Route 1, 2, and 3 Facility Access Codes (1-9999) or, in

V2, Virtual Facility Codes (#190-#199)

Subpattern A and B—Route 1, 2, and 3 FRLs (0-3)

—

Subpattern A and B Overflows to CO facility (Yes, No)
Subpattern A and B Overflow FRL (0-3).

Terminal (Station Port)

● ARS FRL Level (0-3).

Hardware Requirements

None

2-58

ROUTING

PATTERNS

(1-8)

ROUTING SUBPATTERNS (RSP) A AND B

RSP A ROUTE 1

START/
STOP
TIME
[101],
[102]

POOLED
FACILITY
ACCESS
CODE

[110]

ROUTE 2 ROUTE 3

POOLED
FACILITY
ACCESS
CODE

[120]

POOLED
FACILITY
ACCESS
CODE

[130] [140]

CO

OVERFLOW

FLAG

[100]

[ 200]

RSP B

FRL (0-3) FRL (0-3) FRL (0-3) FRL (0-3)

[111] [121]

ROUTE 1

POOLED
FACILITY
ACCESS
CODE

[210]

FRL (0-3) FRL (0-3) FRL (0-3) FRL (0-3)

[211] [221]

DIGIT TRANSLATIONS

TABLE ASSOCIATED

WITH POOLED FACILITY

(OR VIRTUAL FACILITY, V2

ONLY) DELETE DIGITS

(0-10) ADD DIGITS

(MAX 5) [700S)

ROUTE 2

POOLED
FACILITY
ACCESS
CODE

[ 220]

ROUTE

SELECTED

[131] [141]

ROUTE 3

POOLED

FACILITY
ACCESS
CODE

[230]

[221] [241]

CO

OVERFLOW

FLAG

[ 240]

ALL ROUTES
BUSY

ROUTE CALL

VIA DDD
NETWORK

YES

NO

QUEUE

ON

ROUTE 1

Figure 2-9. Automatic Route Selection Routing Pattern

2-59

BUSY-TO-IDLE REMINDER

Description

Enables a multiline voice terminal user to be alerted by a single ring as soon as a busy
internal station, DGC group, or facility (trunk group) becomes available. The feature can be
activated only for stations, DGC groups, and trunk groups represented on the terminal by
DSS, FLEX DSS, AUTO ICOM, and FACILITY buttons.

Before making a call to a station,

the multiline voice terminal user can check the green

status LED of the station button. If it is lit, the station party is off-hook. To be alerted
when the party hangs up and is available again, the user (while on-hook), presses the button
of the station. The red I-use LED lights, indicating that Busy-to-Idle Reminder is in effect.

When the other party hangs up, the user’s terminal rings once. The user simply goes off­hook, and the station is called; the user does not have to press the button again.

If the user calls a station by pressing a FLEX DSS, DSS, or AUTO ICOM button and
receives busy tone, the user must hang up before activating Busy-to-Idle Reminder.

When all the trunks in a pool represented by a FACILITY button are busy, the green status
LED is lighted.

The user can activate Busy-to-Idle Reminder in the same way as for a
station call, by pressing the FACILITY button while on-hook. When a trunk becomes idle,
the terminal rings once. The user goes off-hook and is automatically connected to the trunk.

To complete the call the user dials the desired outside number.

Considerations

Busy-to-Idle Reminder gives the multiline voice terminal user a way to get quick access to a
station or trunk group that has just become available after being busy. Access to the station
or trunk is not reserved for the user who activates this feature; any other user has equal
access to the idle facilities.

On some multiline voice terminals, FLEX DSS, DSS, AUTO ICOM, and FACILITY buttons
do not have status and I-use LEDs. This makes Busy-to-Idle Reminder less convenient to
use because the user must first call the facility to determine if it is available. If it is not,
the user activates the feature by hanging up and pressing the button again. When the
reminder ring sounds, the user must then remember which button was used to initiate the
call.

Interactions

● Busy-to-Idle Reminder cannot be used with the Last Number Dialed, Personal Line,

or Repertory Dialing features.

Administration Requirements

None

Hardware Requirements

None

2-60

CALL ACCOUNTABILITY

Description

Allows system users to charge outside calls made from other users’ stations to their own
PDCs.

To charge a call to his or her own PDC, the user dials ## followed by the PDC immediately
upon receiving first dial tone to place a call. When second dial tone is returned, the user
dials the desired number in the normal way.

After completion of the call, the SMDR record will reflect the “accountable” PDC (that is,

the caller) in the “PDC’’ field, and the PDC of the voice terminal used in the “STN’’ field.

Considerations

Call Accountability, if used consistently, helps to ensure that calling costs are attributed
accurately to the personnel who incur the costs.
from their own stations or when making inside calls from any station.

Interactions

All of the following conditions apply only when a user is calling from another user's station.

Users do not use this feature when calling

. Account Code Entry: This feature can be used on the same call with Call

Accountability.

. Call Accounting: The caller’s PDC that is entered by the Call Accountability

procedure is integrated into the reports generated by Call Accounting systems.

. Direct Facility Access: When a call is made using a Facility button, ##PDC must

be dialed before pressing the button.

. Repertory Dialing: When a call is made using a Rep Dial button, ##PDC must be

dialed before pressing the button.

. Speed Dialing: When a call is made using Speed Dialing, ##PDC must be dialed

before dialing the Speed Dialing code.

Administration Requirements

None

Hardware Requirements

None

2-61

CALL ACCOUNTING

Call Accounting is the collecting, processing, and use of information about all trunk calls
placed from and received by System 25. It is intended to help customers control telephone
use and manage associated costs.

Detailed call data is available at Interface Port 3 of the Digital Switch’s Call Processor
Circuit Pack. This data can be fed to one of the following peripheral equipment systems:

Station Message Detail Recording (SMDR) equipment for printing a standard call

.

report.

● A Call Accounting System (CAS) for preparing a variety of cost estimate reports and

for providing management and directory type services.

Two station features of System 25 are also related to Call Accounting and are covered in
separate subsections of this manual.
users to associate specific

Accountability provides users with the means to properly identify calls they make from
stations other than their own. The information gathered from these two features is part of
the data output from the processor to the SMDR or CAS.

The remainder of this subsection is dedicated to coverage of SMDR and CAS.

Station Message Detail Recording (SMDR)

account codes with their calls, when necessary.

Account Code Entry allows individual voice terminal

Call

Description

SMDR records detailed call information on all incoming and outgoing (external) calls and
sends this information to an (optional) output device.

The call records can be used to compute costs, allocate charges, and analyze calling patterns.
The output device can be any serial RS-232 compatible DTE device capable of receiving the
data (must supply DTR on pin 20) and either printing the call records or storing and

analyzing them. (80 character ASCII records are sent to the output device.)

The SMDR RS-232 port interface is provided by a DUART driver (68681). It is a one-way

port transmitting data to the output device.
and no flow control mechanisms are provided. The standard data transmit rate is 1200 bps.
(Also operates at 300 bps.)

Call Records

The call records provide detailed information concerning both incoming and outgoing calls.
Call detail records are generated during call processing and are sent to the SMDR output
device in ASCII format. SMDR records are provided for:

Voice Records: The system prints call records for incoming calls and for outgoing

.

calls that exceed a specified duration. For special types of calls such as conference
or transferred calls, one call record is reported for each trunk seized, regardless of
the number of parties connected to the call. The call’s duration is from the time the
last digit was dialed until the last person hangs up.
trunks have been bridged together.

No characters are read by the port interface,

Data on inside calls is not collected.

No indication is provided that

2-62

.

Data Records: The system prints call records for incoming and outgoing (external)
data calls. Calls are considered data calls if they involve a data extension.

The following list describes the SMDR data collected for each call and the number of
characters in each field. All information is right justified in its field, unless otherwise

indicated. The record is provided in a standard 80-column format. The headings for each
record item are noted in bold type. These headings are printed across the top of each page.
Page advance is determined by counting lines based on a fixed page length. Each record is

followed by a carriage return and a line feed.
The system can provide for the storage of up to 100 SMDR records. If more than 100 records

are received while the printer is disconnected, a message
Overflow” is provided when a printer is re-attached.

The SMDR call detail (Figure 2-10) contains the following information for each call record:

“Calls Lost Due To Call Record

. TYPE (Column 1)

All voice calls are labeled C, data calls are labeled D. (“TYPE” is not printed as a

column heading)

. Blank (Column 2)
. DATE (Columns 3-10)

The date the call is originated.

. Blank (Column 11)

. TIME (Columns 12-16)

The time the trunk is seized is listed using a 24-hour clock. For example, 2:01 PM is
listed as 14:01. Seconds are truncated.

. Blank (Column 17)

. CALLED NUMBER (Columns 18-35)

For outgoing calls, up to 15 digits may be recorded, excluding the ARS or facility
access code but including the O or 1 prefix (to identify local and toll calls) and 950-

XX and 10 XXX interconnect access codes.

10
between the fourth and fifth digits from the right, one between the seventh and eight
digits from the right, and the other between the tenth and eleventh digits from the
right. Numbers longer than 15 digits will be truncated. For Repertory Dial and

Speed Dial numbers,
reported under the FAC heading; the number remaining after the facility is extracted
will be reported as the called number.

An incoming call is identified by the word IN.

the facility will be extracted from the stored number and

Space is allotted for three dashes, one

. Error Character - Question Mark or Blank (Column 36). Indicates number dialed

exceeded 15 digits.

. Blank (Column 37)
. DUR (Columns 38-45- Duration)

For incoming calls, this provides the time between trunk seizure and disconnect,
rounded to the nearest second. For outgoing calls, it provides the time between the
last digit dialed until the last station on the call hangs up, less an estimated time for

call setup (15 seconds), rounded to the nearest second. A call transferred between a

2-63

number of voice terminals will reflect the total call duration. The maximum time
that can be reported is 95 hours, 59 minutes, and 59 seconds.

. Blank (Column 46)
. FAC (Columns 47-51- Facility)

Indicates the facility used to place the call. For outgoing calls including speed dialed
numbers, the pooled facility selected by ARS or the facility access code that was

dialed (or that corresponds to the facility button that was pressed) is identified. For

incoming calls and Personal Line calls, the trunk number is identified.
For V2 only: If a virtual facility was used to complete the call, the applicable Virtual

Facility Code (#190-#199) is identified in this field.

.

Blank (Column 52)

.

STN

(Column 53-56)

Identifies the voice or data terminal responsible for the call. If an account code is
entered, the voice terminal where the code is entered is reported. If no account code
is entered, the terminal originating an outgoing call is identified, or the last terminal
connected to an incoming call is identified.

For an incoming call to a DGC group that is connected to an announcement but is
never answered, 0 will be recorded in the STN field. If the call is answered by a
station after receiving announcement, the station answering the call will be recorded.

For V2 only: If an outgoing call is originated by a tandem tie trunk, the tandem
trunk’s Facility Access Code (FAC) is recorded in this field. If no FAC exists for this
trunk, then the 4-digit trunk number (9

XXX) will appear.

For V2 only: If an outgoing call is originated by a DID trunk, 0000 is recorded in this
field.

. Blank (Columns 57 ,58)
. ACCOUNT (Columns 59-73)

Lists the Account Code associated with the call, if one was entered. On conference
and transferred calls, the first account code entered is recorded and subsequent
account code entries are ignored.

. Blank (Column 74)
. PDC (Columns 75-78)

Identifies the user responsible for outgoing calls.
accountability login (##PDC) entered at the originating voice terminal. If

accountability is entered, the PDC field is blank.

Figure 2-11 and Figure 2-12 summarize the Call Record and Call Record Header formats.

Considerations

SMDR provides detailed call information on incoming and outgoing calls. This information
can be used to facilitate cost allocation, traffic analysis, and detection of unauthorized calls.

The user is identified by the call

no call

2-64

Interactions

. Account Code Entry: Allows users to have an account code or project number

associated with each call record.

. Direct Group Calling (DGC): For an incoming call to a DGC group that is

connected to an announcement and never answered, “O” will be reported in the

“STN” field of the call record. If the call is answered by a station after receiving the

announcement, that station will be listed in the “STN” field.

. Modem Pooling: SMDR records do not reflect modem pool resource usage.

. Tandem Trunking (V2 only): If an outgoing call is originated by a tandem tie

trunk, the tandem trunk’s FAC is recorded in the STN field. If no FAC exists for
this trunk, then the 4-digit trunk number (9
are affected.

Administration Requirements

System:

XXX) will appear. No other SMDR fields

. Send SMDR records To SMDR Port (Yes, No) - Default = Yes

. Minimum length (seconds) of calls that are reported by SMDR (10-255) - Default =

40.

Hardware Requirements

An AT&T Model 475 printer or any standard RS-232 serial 80-column ASCII printer is
required for printing the SMDR output.

that all calls are recorded. An AT&T Call Accounting System may also be used as the

SMDR output device (see below).

The printer can be directly connected to Port 2 of the Call Processor ZTN82 (V1) or ZTN128
(V2), or switched access (either on- or off-premises) can be provided. Connection is the same
as described for the SAT.

Detailed connection information is provided in Figures 2-13 through 2-17
Maximum cabling distances are provided in Section 5, “Technical Specifications.”

Call Accounting System (CAS)

Two types of CASs can be used with System 25:

CAS Model 100—A discrete microprocessor unit with cartridge-packaged software

.

and a built-in power supply.
CAS Model 200, 300, 500, or 2000 Software Package associated with an AT&T

.

Personal Computer (PC) 6300.

The printer must be dedicated to SMDR to ensure

2-65

Description

CAS Model 100:

The CAS 100, when connected to a serial printer and the System 25 SMDR port, calculates
the cost of calls made to outside numbers, stores the cost information, and generates
chronological and summary reports.

After each incoming or outgoing call is completed, a call record is printed on the
Chronological Report. Each call record includes the date and time of the call, the Personal
Dial Code (PDC) of the station involved, the call’s duration (in minutes), the call type (voice
or data), the calculated cost, and the number of the facility on which the call was made. If
the call is outgoing, the call record also includes the number dialed, a two-character
abbreviation for the area to which the call was made, an account code, and the PDC claiming
accountability for the call.

When a call record with a new date is received by the CAS 100, the previous day’s
Chronological Report is ended and reports containing summary information are printed.
Four summary reports are produced:

. Calls by Hour of the Day
. Calls by Facility Used
. Calls by Extension Number
. Calls by Account Code.

These reports summarize the information presented in the Chronological Report and list the
total number of calls, their total duration, and the total cost.

Switches inside the CAS Model 100 cabinet allow the System Administrator to control the
system options that determine report parameters.

CAS Models 200, 300, 500, and 2000:

The System 25 SMDR interface provides direct output to an AT&T PC 6300 Personal

Computer equipped with MS-DOS (V2.11 or later) and a CAS software package (i.e., Model
200, 300, 500, and 2000) that calculates the cost of calls and provides basic and sophisticated
call reports.

After a telephone call is completed, System 25 sends a call record to the AT&T PC 6300 via
the SMDR interface channel. The PC must be equipped with CAS software. Call records are
collected by the PC and held in a buffer until they are processed. When a call record is
processed, a cost is calculated and assigned to it.
information, is then stored on a hard disk for subsequent retrieval.

Two modes of operation are available for PC 6300 operation:

.

Dedicated Mode: The PC is dedicated to one and only one task–processing call
records.

That cost, along with other call record

. Multi-Function Mode: Allows the user to print reports, edit files, and run other

PC-based programs while the CAS continues to collect and buffer call records in the
background. The user must enter the Dedicated Mode to process calls and generate
reports.

2-66

The CAS performs three main functions; (l) call record processing, (2) report generation, and
(3) CAS system management.

provided. The followings a brief description of each function:

1. Process Calls: Involves screening call records, calculating the cost of valid calls,
anti storing the call records.

2. Generate Reports: Allows the user to print the stored call record information
organized in one of several different ways.

own special combination of reports from the following:

Summary Reports—A collection of reports that condense and summarize

.

call record information by total number of calls, duration, and cost. The
reports can be organized by department, call type, cost center, trunk,
extension, cost, duration, time of day, date, and account code.

Organization Detail Report–A detailed report of each call record in the

.

system, sorted by department, cost center, and extension.
Selection Report—This report can contain at a user’s option, summary or

.

detailed information based on any combination of the following items: time
of day, date, cost, duration,
number, call type, department, or cost center.

Account Code Detailed Report—A detailed report on call records sorted by

.

account code. This report can be used for billing clients for calls made in
their behalf.

In addition, a limited directory lookup and message center is

Users can select a report or set up their

extension, access code, account code, dialed

Preselected Reports—Allows up to five predefine reports, which can

.

include any of the above mentioned reports. These reports can run upon
request or at a specified time and date.

3. System Management: Allows the user to perform several functions. These
include editing the table of departments, cost centers, and extensions; setting up
account codes; defining preselected reports; and keeping call rate information up to
date. System configuration may be changed.
CAS of changes in System 25 (e.g., dial access codes, trunks) or changes in charge
rates.
passwords, deleting call records, determining call processing options, and
performing various disk maintenance operations.

4. Directory Lookup and Message Center: Allows the user to look up anyone by
last name, first name, or extension. Messages can be recorded for individuals and
can be printed or displayed.

System housekeeping may also be performed. This includes establishing

This allows the user to inform the

2-67

The following table summarizes CAS station and account code capacities.

AT&T CALL ACCOUNTING SYSTEMS

CAS Model Stations

200 100 5000

300

500 500 5000

2000 2000 15000

Refer to the CAS documentation supplied with the software package for additional
information.

Considerations

The CAS provides customers with an efficient tool to control and manage their telephone
usage and costs.
analysis, and abuse control.

Interactions

None

The information available can be used to facilitate cost allocation, traffic

150

Account Codes

5000

Administration Requirements

System:

Send SMDR Records To SMDR Port (Yes, No) - Default = Yes.

Minimum length (seconds) of calls that are reported by SMDR (10-255) - Default =

.

40.

Hardware Requirements

CAS Model 100 requires a CAS Microprocessor and a Custom Cartridge containing rate
information specific to your location.

CAS Model 200, 300, 500, or 2000 applications software must be run on an AT&T PC 6300
equipped with MS-DOS (V2.11 or later).

Refer to Figures 2-13 and 2-14 for typical CAS connection information.

2-68

C
C
C
D
C
C
C
D
D

C
C
C
C
C
C
C
C
C
D
C
C
C
C
C

DATE

10/08/85
10/08/85
10/08/85
10/08/85
10/08/85
10/08/85
10/08/85
10/08/85
10/08/85
10/08/85
10/08/85

10/08/85

10/08/85
10/08/85

10/08/85
10/08/85

10/08/85

10/08/85
10/08/85
10/08/85
10/08/85
10/08/85
10/08/85
10/08/85

TIME

11:14
11:14
11:15
11:17
11:19
11:20
11:34
11:44
11:50
12:14
12:24
13:27
13:14
13:23
13:28
13:33

13:45
14:14
14:24
14:34

14:43
15:14
15:16
15:19

CALLED NUMBER

1-232-566-1321

IN
1-322-564-1376
1-222-564-2171

IN
IN

1-242-563-1324

555-4541

1-252-514-3176

IN
1-222-566-2544
1-333-513-1376
1-244-564-3121

IN

IN
1-222-516-1176

555-2541
1-222-563-4321
1-343-516-2574

555-3141

IN
1-343-564-1321
1-222-566-1321

IN

DUR

00:15:41
00:09:05
00:29:50
00:10:45
00:05:32
00:29:45
00:19:00
00:05:35
00:19:45
00:25:42
00:10:35
00:15:05
00:09:40

00:15:45
00:19:35
00:19:40
00:09:05
00:20:42
00:10:05
00:09:45
00:19:32
00:20:45
00:19:45
00:19:45

FAC STN

9

1794

2145

3214 1744

2342

2145

3414 1566
3421

3214

2342

1324

9

1744

9

2001

3455

9

1677

9

2312

9

3455

1492

1244

9
9

3566

9

2001

3421
1492

9
9

3655
4321

9
9

1244

9

4633
2351
1794

9
9

1794
1794

ACCOUNT PDC

123489764321341

766544

76322 3422

323489764321341 3422

123489764321341 4271

123489764321341

763444 3465

1234893764321341

4271

3254

4271

4271

Figure 2-10. Typical SMDR Call Detail Report

2-69

ASCII CHARACTER

POSITION

(Column Number)

DESCRIPTION

VALID

CHARACTERS

01
02

03-04

05

06-07

08

09-10

11

12-13

14

15-16

17

18-35

36
37

38-39

40

41-42

43

44-45

46

47-51

52
53-56
57-58
59-73

74
75-78

79

80

Call Type
Space
Date: Month

/
Date: Day
/
Date:Year
Space
Time:Hour

Time: Minute
Space
Dialed Number
Error Character
Space
Duration:Hour

Duration: Minute

Duration: Second
Space
Facility
Space
Station
Space
Account Code
Space
Personal Dial Code

C or D

0-9

/

0-9

/

0-9

0-9

0-9

0-9, Space, -, IN

?, or Space

0-9

0-9

0-9

Space, 0-9, #

0-9, Space

0-9, Space, #, ?

0-9, Space

Carriage Return

Line Feed

Figure 2-11. SMDR Call Record Format

2-70

ASCII CHARACTER

POSITION

00
01-03
04-07
08-12
13-16
17-23
24-29

30
31-36
37-38
39-41

42-48
49-51
52-54

55-57
58-62

63-69

70-76

77-79

80

81

DESCRIPTION

(top of form)
Space
DATE
Space

TIME

Space
CALLED
Space

NUMBER

Space
DUR
Space
FAC

Space

STN
Space

ACCOUNT

Space
PDC
(Carriage Return)
(Line Feed)

Figure 2-12. SMDR Call Record Header Format

2-71

SYSTEM 25

CABINET

ZTN82

OR ZTN128

CALL

PROCESSOR

LEGEND:
C1 -MODULAR CORD (D8W-87) - PEC 2725-07G

C2 -OCTOPUS CABLE (WP90780) - PEC 2720-05P
355A ADAPTER RS 232 PLUG TO MODULAR JACK - PEC 2750-A24
355AF ADAPTER RS 232 RECEPTACLE TO NODULAR JACK - PEC 2750-A25

PART OF
OCTOPUS
CABLE

— — —
— ——

C2

.

— ——

— — —

PART OF

SIP

Z21OA

ADAPT .

C1

355A/AF

SMDR OUTPUT
DEVICE/CALL

ACCOUNTING

SYSTEM

Figure 2-13. SMDR Output Equipment or Call Accounting System—On-Premises

Direct Connections (Sharing Same AC Outlet)

2-72

SYSTEM 25

CABINET

ZTN82

OR ZTN128

CALL

PROCESSOR

C2

PART OF
OCTOPUS
CABLE

PART OF

SIP

Z210A
ADAPT.

C1

355AF

ADAPT.

C3

Z3A4

ADU

C1

SMDR OUTPUT

DEVICE

OR CALL

ACCOUNTING

SYSTEM

LEGEND:

B1 - TYPICAL-103A CONNECTION BLOCK*
C1 - MODULAR CORD (D8W-87) - PEC 2725-07G
C2 - OCTOPUS CABLE (WP90780) - PEC 2720-05P
C3 - EIA CROSS OVER CABLE (M7U-87) - PEC 2724-30C
C4 - ADU CROSS-OVER CABLE (D8AM-87) - PEC 2724-38X

355AF ADAPTER RS-232 RECEPTACLE TO MODULAR JACK - PEC 2750-A25

248B ADAPTER –

20210 TRANSFORMER –

400B2 ADAPTER –

NOTE: CAS MODELS 100 AND 200 REQUIRE Z3A4 ADU.

*

- FURNISHED BY INSTALLER

W1 - 4 PAIR INSIDE WIRING CABLE*

Z3A1 ADU –
Z3A4 ADU –

C7 -

Z3A1

OR Z3A4

ADU

(NOTE)

EQUIPPED WITH A THREE FOOT PLUG-ENDED EIA CORD - PEC 2169-001
EQUIPPED WITH A 3 FOOT RECEPTACLE ENDED EIA CORD
MODULAR POWER CORD (D6AP-87)

MODULARIZES 2012D TRANSFORMER

POWER ADAPTER

15-18V AC TRANSFORMER

C1

B1

W1

2012D
TRANS.

PEC 21691

248B
ADAPT.

C4

C7

Figure 2-14. SMDR Output Equipment or Call Accounting System—On-Premises

Direct Connections (Greater Than 50 Feet From System Cabinet)

2-73

SYSTEM 25

CABINET

ZTN82

OR ZTN128

CALL

PROCESSOR

(PORT X)

TDM

BUS

TN726

DATA
LINE

TN726

DATA
LINE

LEGEND:

B1 – TYPICAL-103A CONNECTING BLOCK*

C1 – MODULAR CORD (D8W-87) - PEC 2725-07G
C2- OCTOPUS CABLE (WP90780) - PEC 2720-05P
C3 – EIA CROSS OVER CABLE (M7U-87) - PEC 2724-30C
W1

355AF -ADAPTER (RS-232 RECEPTACLE TO MODULAR JACK) - PEC 2750-A25

Z3A1 ADU – EQUIPPED WITH A 3 FOOT PLUG-ENDED EIA CORD - PEC 2169-001

248B ADAPTER– MODULARIZES 2012D TRANSFORMER

2021D TRANSFORMER -

*

– FURNISHED BY INSTALLER

Z3A4 ADU – EQUIPPED WITH 3 FOOT RECEPTACLE ENDED EIA CORD - PEC 2169-004

400B2 ADAPTER – POWER ADAPTER

C7

PART OF
OCTOPUS

CABLE
———

C2

.

———

———

C2

.

———

C2

– 4 PAIR INSIDE WIRING CABLE*

15-18V AC TRANSFORMER

- MODULAR CORD (D6AP-87)

PART OF

SIP

Z210A

ADAPT. ADAPT.

Z210A

ADAPT.

PART OF

C1

PART OF

SIP

2012D 248b
TRANS.

SIP

SIP

ADAPT .

355AF

400B2
ADAPT.

W1

ADAPT.

C1

B1

\

PEC 21691

/

C1

C7

Z3A1/A4

Z3A4

ADU

ADU

SMDR OUTPUT

DEVICE

(NOTE)

NOTE: OUTPUT DEVICE OR MULTILINE VOICE

TERMINAL WITH DATA BUTTON DIALS PORT X DDC TO
ESTABLISH DATA CONNECTION TO ZTN-82.

Figure 2-15. SMDR Output Equipment

2-74

—On-Premises Switched Connections

SYSTEM 25

CABINET

ZTN82

OR ZTN128

CALL

PROCESSOR

PART OF
OCTOPUS
CABLE

———
———

C2

.

———
———

>

PART OF

SIP

Z21OA
ADAPT.

C1

CO OR PRIVATE
LINE CIRCUIT

CONNECT VIA TAE

C3

355AF

TYPICAL

MODEM

TELCO

CENTRAL

OFFICE

LEGEND :

C1

- MODULAR CORD (D8W-87) - PEC 2725-07G

C2 -

355AF ADAPTER -

C3 - EIA CROSS OVER CORD (M7U-87) - PEC 2724-30C

SMDR

OUTPUT
DEVICE

OCTOPUS CABLE (WP90780) - PEC 2720-05P

(RS-232 RECEPTACLE TO MODULAR JACK) - PEC 2750-A25

TYPICAL

MODEM

Figure 2-16. SMDR Output Equipment—Off-Premises Direct Connections

2-75

SYSTEM 25

CABINET

ZTN82

OR ZTN128

CALL

PROCESSOR

TN758

POOLED

MODEM

TDM

BUS

LEGEND :

TN726
DATA
LINE

TN742

ANALOG

LINE

CO

TRUNK

FACILITY

355AF ADAPTER -

Z3A4 ADU -

248B ADAPTER -

400B2 ADAPTER -

20210 TRANSFORMER -

PART OF
OCTOPUS

CABLE

———

C2

.

———

———

C2

.

———

CONNECTED

AS OPS
OR CO
FACILITY

MODULAR CORD (D8W-87) - PEC 2725-07G

C1 -

OCTOPUS CABLE” (WP90780) - PEC 2720-05P

C2 -

EIA CROSS OVER CABLE (M7U-87) - PEC 2724-30G

C3 -

OFF PREMISES STATION

OPS -

RS-23Z RECEPTACLE TO MODULAR JACK PEC 2750-A25*

EQUIPPED WITH 3 FOOT RECEPTACLE - PEC 2169-004
MODULARIZES 2012D TRANSFORMER
POWER ADAPTER

15-18V AC TRANSFORMER

MODULAR POWER CORD (D6AP-87)

C7 -

PART OF

SIP

355AF

Z210A

ADAPT.

———————

Z210A
ADAPT.

———————

C1

ADAPT.

PART OF

SIP

400B2
ADAPT.

2012D 248B
TRANS.

CO CABLE

———————————

———————————

ADAPT.

CENTRAL

OFFICE

I

SMDR

OUTPUT DEVICE

OPS OR CO TRUNK

C7

I

PEC 21691

Z3A4

ADU

TYPICAL

MODEM

(212 TYPE)

*

- FURNISHED BY INSTALLER

Figure 2-17. SMDR Output Equipment—Off-Premises Switched Connections

2-76

CALL COVERAGE—GROUP

Description

Allows calls to covered stations to be redirected to a group of covering stations.

A total of 32 standard Call Coverage Groups may be assigned; for V2 systems, an additional

32 “DGC” call coverage groups maybe assigned.

Each standard group may be covered by up

to eight call coverage receivers (buttons). There is no limit on the number of covered users

(senders) that each Call Coverage Group can include, but a covered user can be assigned to

only one Call Coverage Group.

Each call coverage receiver must have a multiline set
equipped with a Cover (COVER-GRP) button, except as noted below. A covering set may be
assigned more than one COVER-GRP button for the same or different groups.

In R1V2 Systems equipped with a Switched L
queue can serve as a standard coverage group receiver.

OOP Attendant Consoles (SLAC), the console

The consoles cannot have COVER-

GRP buttons, so the queue directs coverage calls to LOOP buttons.
Direct Group Calling (DGC) Groups may be designated as Call Coverage Group receivers in

V2 Systems. This provides the capability for System 25 to support “non-integrated” voice
mail systems as well as allow the formation of coverage pools.

Senders may be either single-line or multiline voice terminals. In V2 systems, receivers may

be single-line voice terminals if part of a DGC Call Coverage Group. Multiline voice
terminals may always be used as receivers

Standard Group Coverage

When a call arrives at a voice terminal that has group coverage, the COVER-GRP or LOOP
button status LED at the covering voice terminals will flash. Covering voice terminals will
begin to ring after a specified number of rings at idle covered voice terminals. If there is no
idle system access button at the covered station (sender), the call receives coverage
treatment, and the call immediately rings at the covering terminal(s). If no idle cover
button is available at the covering terminal(s), the calling party receives a busy signal. In
V1 Systems, the call will not receive coverage treatment if both system access buttons on the
sender’s station are busy; the calling party receives busy signal.

Ringing may be turned off at standard receiver stations for each covering button, as desired
(not recommended).
indication received at the covering station.

If this option is selected, a flashing status LED will be the only

In addition, Call Coverage ringing may be turned

off on internal calls (if desired) on a system-wide basis.

A member of a standard receiver group can use the Line Selection (Preelection) feature to
answer covered calls even before any audible alerting has begun at the covering user’s
terminal. This is useful if the user knows that the covered party is unavailable.

A covered voice terminal may elect to have calls covered while it is busy on another call.
Calls directed to an idle button on a busy covered multiline voice terminal will start ringing
at the covering terminal after a single burst of ringing at the busy covered voice terminal.
If there is no idle Cover button on the covering voice terminal, the call will queue and will
ring at the first available coverage receiver (V2 only); in a V1 system, the call will not

receive coverage treatment.
ringing immediately at the covering terminal.

Calls directed to a busy single-line voice terminal will start

If there is no idle Cover button on any
covering terminal, either individual or group, the call will not receive coverage and the
calling party will receive Busy Tone.

2-77

Calls sent to coverage will continue to ring at single-line sender terminals but will cease
ringing at multiline sender terminals.
incoming call appearance button, and that button’s status LED continues to reflect the
status of the call. In particular, covered calls to multiline sets remain available and can be
entered by the called (sender) station.

If a covered station activates the SEND ALL CALLS button, calls will be directed to
coverage immediately, with or without a single-ring reminder, as administered.

A station can provide (or receive) Individual Call Coverage (see Call Coverage-Individual)
and also be a member of a Call Coverage Group (sender or receiver). Unanswered calls to a
station, provided both Individual and Group Call Coverage, will first ring at the Individual
Coverage station and then, after a second delay cycle and still unanswered, will ring at the
Group Coverage station.

In the latter case, the calls will remain on the

Calls from a covering station to a covered station will not be covered unless the covered
station has additional coverage.

provides coverage.

DGC Group Coverage (V2 only)

Calls proceeding to the DGC–Call Coverage Receiver Group hunt in a circular fashion for
the first idle station, starting from the last station to receive a call. If all DGC members are
busy, both internal and external calls continue to ring and/or flash at the covered station
and any individual coverage receiver’s station(s) until a DGC station becomes idle. If a DGC

group is used for both DGC calls and group coverage, trunk calls into a DGC group have

priority over coverage calls. Calls sent by coverage to a DGC–Call Coverage Group member
station do not receive additional call coverage.

This is an important consideration when the attendant

DGC groups cannot be call coverage senders to another DGC–Call Coverage Group.
However, calls made directly to a DGC member can be covered by another DGC–Call
Coverage Group.

Once a call has been redirected to a DGC–Call Coverage Group member, the call is

transferred to the covering station.
The call is not accessible at the covered station nor any individual coverage receiver once it
is redirected to an idle DGC station.
accessible at the covered station until a member is available.

DGC–Call Coverage Groups count against the system specified maximum number of DGC
groups, but
stations per Call Coverage Group does not apply when administering a DGC group as a Call
Coverage Group.
allowed.

Considerations

Call Coverage provides a way to redirect calls to alternate answering positions. The feature
is versatile enough to permit suitable alternate answering arrangements for virtually every
level of employee. Special functions, such as the Send All Calls feature, accommodate the

day-to-day variations that occur in an employee’s work schedule.

not against the number of Call Coverage Groups. The limit of eight receiving

A maximum of ten stations per DGC–Call Coverage Receiver Group is

The call continues ringing until answered or dropped.

If all DGC members are busy, the call remains

2-78

Interactions (Standard Group Coverage)

●

Attendant Console, Direct Trunk: If the Direct Trunk attendant is a receiver for
a Call Coverage Group and extends a call (using the Start button or Selector Console)
that is unanswered/busy to a member of the group, the call will return On the
Return-On-Don’t-Answer (RTN-DA) or Return-On-Busy (RTN-BUSY) button, not on

the attendant’s COVER-GRP button.

● Automatic Intercom: Auto-Intercom calls do not receive call coverage.

● Call Coverage—

Individual: Unanswered calls to a station, provided both

Individual and Group Call Coverage, will first ring at the Individual Coverage station
and then, after a second delay cycle and still unanswered, will ring at the Group
Coverage station.

●

Call Coverage/Station Hunting: A call to a busy single-line voice terminal that is
both a member of a Station Hunting group and a Call Coverage sender will first hunt
for an idle station to service the call. If none is available, the call will be sent to
coverage.

● Call Pickup: Call Pickup is independent of call coverage. When a call is answered

via Call Pickup, all Cover buttons associated with the called party go idle.

●

Direct Group Calling (DGC): A call to a DGC group member will receive coverage

if the member is also a Call Coverage sender. Calls to a busy DGC group do not
receive call coverage.

Instead, after a predefined number of rings, the call will be
transferred to delay announcement (if provided), or ringing will be transferred to all
button appearances of the line.

● Exclusion: If a call coverage receiver invokes Exclusion after answering a coverage

call, all other terminals (including the attendant and the covered station) are
excluded from the call. The covered user cannot enter the call until EXCLUSION is
pressed a second time by the covering user.

● Hands-Free-Answer On Intercom: An incoming (inside) call will not receive call

coverage if auto-answer is activated, since the set will answer the call (whether the
user is present or not.).

● Night Service: Directed Night Service calls do not receive call coverage.

● Personal Dial Codes: Calls directed to a station because another non-floating PDC

is logged in there

do not receive the coverage treatment of the logged-in station.

Such calls return to their home station and receive that station’s coverage
(immediately upon return).
receive the

same coverage treatment as any other calls to the logged-into station.

Calls to logged-in

floating PDCs, on the other hand,

They, of course, have no home station to return to.

● Personal Lines: Personal line calls receive the coverage of the principal (owner)

station for that line. Other line appearances (even if administered to ring) will not
receive coverage.

● Tie Trunks: Tie Trunk calls directed at a user with call coverage receive normal call

coverage treatment.

2-79