ATT System 25 Reference Manual

							Command Mode
Table 2-G.Partial List of Permissible Data Port (TN726) Options
OPTIONDEFINITION
Speed (61-68)†Autobaud, Low*,
300, 1200, 2400, 4800, 9600, 19200
Parity (69)Odd, Even, 0, 1.The 0 and 1 choices are not shown
on the user’s display.
Enable Command Mode (70)Yes or No. Must be On for Command Mode
(i.e., Command Mode Menu display). Not shown on
user’s options display.
Allow user to
change data port options? (71)Yes or No. Used to enable/disable User Changeable
Options feature. Not shown on user’s options display.
Permit Mismatch (72)Yes or No. Allows two data endpoints to
communicate at different rates.
Local Echo (73)Yes or No. Determines whether characters from the
data equipment will be echoed by System 25 during
Command Mode.
Answer Text (75)Yes or No. Enables call progress messages to be
displayed at the called data endpoint.
Connected Indication (77)Yes or No. Yes indicates that users who have
Command Mode enabled will receive the
“CONNECTED” message when a connection has
been established. If Command Mode is disabled, the
Data Line port control lead will be “raised” when a
connection is established. Usually set to “No” for
host computer endpoints.
Disconnect/Recall SequenceOne Long Break or Two Short Breaks; the sequence
(74)used to disconnect a data call.
* A terminal whose baud rate is low cannot use the Command Mode feature. Call
origination at this terminal must be via Transfer To Data.
† Numbers in ( ) indicate the action numbers used to administer data port options.
2-99 
						

							FEATURES AND SERVICES
Table 2-H.Typical Option Profiles for Data Port Endpoints
Options
Speed (highest)
Parity
Enable Command Mode
Permit Mismatch
Local Echo
Answer Text
Connected Indication
Disconnect/Recall
SequenceData Term.
or PC
19200(Auto)
Even
Yes
Yes
Yes
Yes
Yes
Br-Br
Host
Computer
9600 *
Even
Yes
No
No
No
No
Br-Br
Modem
(users)
Modem Speeds
Even
Yes
Yes
Yes
Yes
Yes
Br-Br
Modem
(computer)
Modem Speeds
Even
Yes
No
No
No
No
Br-Br
* or 9600( Auto) if not not used primarily for Host-Host communications
2-100 
						

							Communications Access Manager (CAM)
Communications Access Manager (CAM)
The Communications Access Manager (CAM) program facilitates communication between
workstations on the AT&T STARLAN NETWORK (STARLAN NETWORK) and workstations on
System 25.
Since CAM has a built-in interface to System 25’s Command Mode, it is an ideal
communications application for PCs connected to System 25. Detailed procedures for using
CAM can be found in the CAM User Guide. The material here provides a brief overview of
CAM capabilities.
CAM is a MS-DOS application program that provides an enhanced calling interface and
terminal emulation for PCs. CAM, combined with System 25’s Third-Party Call Setup feature,
provides the capabilities of an integrated voice /data workstation, specifically:
l A 200-entry directory for automatic dialing of voice and data calls
l VT100 terminal emulation with:
— file transfer with error checking
— unattended remote access operation with mail
l On-line HELP that is accessible from almost anywhere within the program.
CAM runs on the AT&T PC6300 or compatible PC with at least 384K bytes of memory,
running MS-DOS Version 2.0 or later (when connected to System 25) or MS-DOS Version 3.1
or later (when connected to the STARLAN NETWORK).
The PC running CAM can be connected to System 25 in one of two ways (Figure 2-13):
1. By the PC’s RS-232 COM port to the System 25 via an ADU/DLC connection
2. As a STARLAN NETWORK workstation to the System 25 via the STARLAN Interface
CP.
CAM interfaces with System 25’s Command Mode to provide call control. The Third-Party
Call Setup feature provides voice call origination.
The STARLAN NETWORK communication driver (NAUCOM) is used before CAM is run on a
STARLAN NETWORK workstation. The Extended Device driver (CAM232) is used when
CAM is run on a PC connected to a System 25 DLC port.
The default screen presented when the user accesses CAM is the phone directory screen.
The phone screen is divided into five partitions:
l Call Appearance area—provides call appearance for voice lines and data lines for
each extension shown. A call timer for each line is also displayed.
l Feature Selection area—allows the user to select the voice or data line to be used,
initiate the call, and start the timer by function keys. Additional function keys may be
assigned to Repertory Dialing numbers.
2-101 
						

							FEATURES AND SERVICES
EX-RS232C
COMMUNICATIONSDRIVER
ACCESS
MANAGER
NAUCOM
DRIVER
PERSONAL COMPUTERRS-232-C
PORT
STARLAN
NAU PORT
Figure 2-13.Communications Access Manager Architecture
l   Personal Directory area—holds a maximum of 200 entries, displayed 10 entries at a
time. Each screen is arranged alphabetically.
l   Message and Status area—contains prompts and messages for the user for the
action being executed.
l   Command Line area—contains commands available to the user for the area being
worked in. Commands are executed when the user presses the  key and the
first letter of the command.
The user may access the following commands:
—
Data mode—provides the user with the terminal emulation screen.
—
Edit—provides the user with the directory edit screen. Allows the user to
add, modify, and erase directory entries, group names, and feature functions.
Directory entries contain name,number with auto login script, comment,
group, and voice/data fields.Data entries also have parameter setup, a
screen with fields for speed, parity, permit mismatch, and number of bits.
The parameter setup allows speeds of 2400, 4800, 9600, and Autobaud.
—
Find—allows the user to search directory entries by name or group ID.
—
Restore—displays the first 10 entries of the directory after a Find.
—
Print—prints the entire contents of the directory on device LPT1.
—
Setup—provides the user with the setup screen. Allows the user to view or
change the following options:communications port, printer port, speed,
parity, character size,return key code, autotimer, flow control, extension
numbers, remote access enable, remote access password, and remote
greeting.
2-102 
						

							Conference
Conference
Description
This feature allows up to five parties, including the conference originator, to participate in a
conference call. Any voice terminal user (the ATL cordless telephone user cannot participate
in a conference call), including operators at Direct Trunk Attendant Consoles and Switched
Loop Attendant Consoles, can set up conferences.Refer to the description of “Conference
Drop” for additional information on conferencing.
Multiline Voice Terminals:
Multiline voice terminal users can add another (external or internal) party to an existing call
by pressing the CONFERENCE button. This places the first party on Special Hold (indicated
by a broken flutter on the line appearance button) and the system selects an idle SYSTEM
ACCESS or LOOP (Switched Loop Console) button and provides system dial tone. The user
may dial the desired number or select another facility to dial the party to be conferenced-in.
Subsequently, pressing the held line button completes the conference. If the facility to be
added is busy, the conference will be denied.
Users can conference up to two outside facilities (trunks), and up to five parties in all. Any
attempt to add a sixth party will be denied, and the sixth party will be dropped. This limit is
for the conference as a whole. Other conference inside stations are also prohibited from
adding a third outside party or sixth party.
Single-Line Voice Terminals:
The single-line voice terminal user can establish a conference by momentarily pressing the
switchhook, which puts the first party on hold, receiving Recall Dial Tone, and then dialing a
second party.After connection to the second party, another press of the switchhook
establishes the conference. A third press of the switchhook will drop the second party,
restoring the original call. The user cannot put a conference that he/she has established on
hold. Other internal conferees (multiline or single-line) may then add additional parties to the
conference up to the five party/two outside line maximum.
Considerations
The Conference feature allows any voice terminal user to set up conference calls. Non-
attendant users do not need the assistance of the attendant.
Waiting for an added party to answer and announcing the purpose of the call before adding
the party to the conference is good operating practice.
A ringing line can be added to a conference and counts as one of the conferees. A queued
or Call Waiting call can be added to a conference and counts as two conferees until it is
completed; when completed it counts as one conferee.
2-103 
						

							FEATURES AND SERVICES
Interactions
The following features interact with Conference.
Account Code Entry, Forced (FACE): Calls can be conference in both directions between a
FACE-restricted station and a non-FACE station.
Account Code Entry, Optional: If more than one user attempts to associate an account code
with a Conference Call, the first to activate the feature will prevail.
Attendant Message Waiting:Pressing the Attendant Message Waiting (ATT MSG) button
while on a conference call will be ignored.
Bridging of System Access Buttons:A station user can make conference calls on Bridged
Access (BA) buttons using the normal conference feature operations. When a call is held for
conference by pressing the CONFERENCE button, an idle System Access (SA) button or an
idle SA-Originate Only button, if available, is automatically selected by the system for placing
the new call. If neither of these button types is idle, the user can manually select a BA
button or any other call appearance button on which to place the new call.
While a bridging station or principal is in the process of setting up a conference call, the
green status LED of the held call’s BA button or SA button has a broken flutter indication.
Other bridging or principal stations that are actively bridged to the call have steadily lighted
green status LEDs; stations that are not active on the call have winking status LEDs
(indicating that the appearance is on hold).
Callback Queuing: A queued call can be part of a conference, unless a Call Waiting call is
already part of the conference.A queued call counts as two conferees until it is completed.
Call Waiting: A call receiving special ringback can be part of a conference, unless a queued
call is already part of the conference.A waiting call counts as two conferees until it is
completed.
Display: Call descriptor “  ” appears in position 15 of Screen 1 for a call containing more
than two active parties; position 16 contains the actual number of conferees. The number of
conferees is displayed at each terminal in a conference call and is updated as the status
changes.
Screen 1324 Tango,S^4
The “ 
^ ” and the number of conferees overwrite whatever was in positions 15 and 16 of the
current display.
When a queued call is added to a conference, the associated displays are modified in only
one respect: the Q symbol appears as the first character of the queued call display. When
the queued facility becomes available and the call is made, “Q” is removed.
When a nondisplay station originates a trunk call, then conferences the call with an inside
display station and drops off, the display shows the trunk name only, not the originally-dialed
digits.
2-104 
						

							Conference
Exclusion: Exclusion may be invoked before establishing a conference. If it is invoked after the
conference is established, all internal conferees will be dropped (except for the party that invoked
Exclusion).
Extended Stations: An Extended Station counts as one of the two allowable outside lines on a
conference call.
Forwarding: If one of the called parties for a conference is a forwarding station, its forwarded-to
station will be the conference facility.
If a conference call is transferred to a forwarding station, it will be given normal Forwarding
treatment.
Music-On-Hold: Music-On-Hold may be enabled or disabled for “Special Hold” through a System
Administration item. However, if the outside line is already part of a conference, music is not heard.
Off-Premises Stations (OPS): For conference purposes, an OPS counts as one of the two
allowable outside lines.
Paging System Access: A paging zone may not be conferenced.
Park: Park may be used to place a conference on hold. Parked conference calls do not return to the
parking station (they remain parked).
If a 5-person conference is parked, the conferee who parked the conference will be dropped when
someone picks up the parked conference.
Remote Access: Remote Access callers cannot use the Conference feature.
Trunk-To-Trunk Transfer: Trunk-to-trunk transfers may be set up using the Conference feature.
The conference must include an incoming trunk call on either a ground start, loop start (if trunk-to-
trunk transfer is allowed by System Administration), DID, or tie trunk if it is to continue after all inside
stations have dropped off.
Public Station: If a PUBLIC Station, a toll class 5 station, creates a conference, the Class 5
restriction level of this station applies. If a non-PUBLIC station creates a conference call with a trunk
in the call and drops off before dialing the outside number, the restriction level will become 5 if the
only remaining station(s) is a PUBLIC station. This also applies for bridging of System Access and
Personal Line Buttons.
November 19952-105 
						

							Features and Services
Conference Drop
Description
This feature allows a voice terminal user, except for the attendant at a Switched Loop Attendant
Console (SLAC), to selectively drop a previously added party from a conference call. At a SLAC, the
attendant can drop conferees only before they have been added to conference.
Multiline Voice Terminals (except SLAC):
On a multiline voice terminal, pressing the DROP button and then pressing the button appearance
of a conference party drops that party from the conference.
If a station called for a conference does not answer, the conferencing user should drop the call by
pressing and releasing the switchhook before returning to the conference. Otherwise, the ringing line
will be added to the conference.
Switched Loop Attendant Consoles:
Once a conference has been set up and all the parties can talk to each other, the SLAC attendant
cannot selectively drop a conferee. Individual members of the conference wishing to drop out must
hang up. However, while still setting up a conference, the attendant can drop calls before they have
been conferenced in, as follows:
l A call to an inside party rings unanswered or returns busy tone—hang up.
l A call to an outside party rings unanswered or returns busy tone—press another LOOP
button or RELEASE or FORCED RELEASE.
l A call to an inside or outside party is completed but the person cannot participate—press
another LOOP button or RELEASE or FORCED RELEASE.
It is good operating practice to wait for the called party to answer before adding the party to a
conference.
All Multiline Terminals:
If all System 25 stations hang up on a conference with two outside lines, the outside parties will
remain conference (until one of them hangs up) if at least one is an inbound call on a ground start,
tie, or DID trunk or an inbound call on a loop start trunk if loop start trunk-to-trunk transfer is allowed
by System Administration. If not, the call will be terminated when the last inside user disconnects
from the conference.
Single-Line Voice Terminals:
A single-line terminal user, after having established a three-party conference, can drop the second
party and retain the first party by pressing the switchhook.
2-106November 1995 
						

							Conference Drop
Considerations
Conference Drop allows users to conference lines appearing on their terminals and then
remove them from the conference when appropriate.
The only parties that a user should try to drop from a conference are those that the user
actually added.If a user tries to drop a party who previously added the user to a
conference, other parties may also be dropped.
Interactions
The following feature Interacts with Conference Drop.
Callback Queuing: If the user is off-hook on the queued call button, pressing the DROP
button and then the queued call button cancels the queued call.
2-107 
						

							FEATURES AND SERVICES
Coverage, Group
Description
This feature allows calls to covered stations to be redirected to a group of covering stations.
A total of 32 standard Coverage Groups may be assigned; an additional 32 “DGC” Coverage
Groups may be assigned.Each standard group may be covered by up to eight coverage
receivers (buttons). There is no limit on the number of covered users (senders) that each
Coverage Group can include, but a covered user can be assigned to only one Coverage
Group. Each 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 systems equipped with a Switched Loop Attendant Consoles (SLAC), the console queue
can serve as a standard coverage group receiver.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 Coverage Group receivers. 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. Receivers may be single-line
voice terminals only if part of a DGC 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. If no idle cover button is
available at the covering terminal(s), the calling party receives a busy signal.
Ringing may be turned off at standard receiver stations for each covering button, as desired
(not recommended).If this option is selected, a flashing status LED will be the only
indication received at the covering station.In addition, 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 (Preselection) 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 system will periodically
check for an idle Cover button and ring at the first available coverage receiver.
Calls
directed to a busy single-line voice terminal will start ringing immediately at the covering
2-108