ATT System 25 Reference Manual

							STARLAN NETWORK Access
ACCESS must be used in conjunction with the AT&T STARLAN NETWORK Server
software (Version 2.0 or later). Installation software furnished with ACCESS requires
the STARLAN NETWORK client installation diskette in order to install ACCESS.
l Communications Access Manager (CAM)
CAM is an MS-DOS applications program that provides an enhanced calling interface
and terminal emulation for PCs connected to System 25 or a STARLAN NETWORK.
This connection must be through a DLC or a STARLAN NETWORK that is, in turn,
connected to System 25 by a STARLAN CP. Refer to the Communications Access
Manager (CAM) Program feature description for a more detailed description of the
program.
STARLAN INTERFACE Circuit Pack
The STARLAN INTERFACE CP (ZTN84) requires a single modular connection to the
STARLAN NETWORK (see Figure 2-45). It provides an interface between System 25’s Time
Division Multiplex (TDM) bus and STARLAN NETWORK’s packet switched network. The
STARLAN CP provides four full-duplex data connections at speeds up to 9,600 bits per
second.
The STARLAN CP operates in two modes: Gateway Mode and Bridge Mode. Gateway mode
supports connections from System 25 data terminals to STARLAN NETWORK UNIX® system
hosts, or from STARLAN NETWORK UNIX system hosts or client workstations to System 25
hosts or modem pools. In Bridge Mode,the STARLAN CP passes the STARLAN
NETWORK’s Universal Receiver Protocol (URP) through System 25 to a local or remote PC.
This is referred to as Bridge Mode and provides a through connection between PCs running
ACCESS and a STARLAN NETWORK. The proper mode (Bridge or Gateway) is auto-
selected by the system.
The STARLAN NETWORK View of System 25
From the STARLAN NETWORK, the STARLAN CP functions like a STARLAN NETWORK
workstation equipped with a Network Access Unit (NAU). The NAU enables STARLAN
NETWORK workstations and servers to access and exchange data over the network. Plug
number 1 of the STARLAN CP octopus cable should be connected to an “IN” jack on the
Network Extension Unit (NEU) (see Figures 2-46 and 2-47).
Calls from STARLAN NETWORK to System 25
A STARLAN NETWORK workstation accesses a host computer connected to System 25
(either a local host or a remote host that can be reached using the Modem Pooling feature).
1.The STARLAN NETWORK workstation loads CLIENT and NAUCOM and then CAM
software (discussed in the Communications Access Manager Program feature
description) and selects a directory entry for the host.
2.   CAM communicates with the STARLAN CP to place the call.
2-295 
						

							FEATURES AND SERVICES
3.  After a connection message is received, CAM automatically switches to terminal
emulation (data) mode.
4.The user may now log into and converse with the remote host
5.   To disconnect, the user selects the CAM disconnect command
Figure 2-45.STARLAN NETWORK and System 25 Configuration
The System 25 View of a STARLAN NETWORK
From System 25, the STARLAN CP looks and functions like a TN726 DLC (with only four
ports). The STARLAN CP differs from the DLC in that, when it is dialed, the STARLAN CP
auto-answers the call and provides a second dialing prompt for completing the call to a
STARLAN NETWORK address. Depending on user’s data terminal type, the STARLAN CP
automatically selects the operating mode and enables the user to access and exchange data
over the network as described below.
Procedures for setting up connections (calls) between STARLAN NETWORK devices and
devices connected to System 25 vary, depending on both calling and called device.
Generally, a two-stage dialing procedure is used.The scenarios described below cover most
situations.
2-296 
						

							STARLAN NETWORK Access
Calls from System 25 to the STARLAN NETWORK
A.An MS-DOS PC connected to System 25 uses the STARLAN NETWORK ACCESS
software to run STARLAN NETWORK applications.
The PC may be connected either to a System 25 DLC port or to an analog station or
trunk port. (The latter arrangement uses System 25’s Modem Pooling feature.)
A typical call is as follows:
1.The PC user loads ACCESS and is automatically connected to the STARLAN
NETWORK. (The STARLAN CP phone number may be entered when
ACCESS is installed.)
2.The PC user may now access the STARLAN NETWORK just as if he/she
were a client connected to the STARLAN NETWORK through an NAU.
Note:Applications that are to be run frequently or are large (>10K
bytes) should be copied to the user’s disk before they are
run.
B.   A Data terminal user accesses a UNIX system host on the STARLAN NETWORK.
When the user dials the STARLAN CP, the CP answers in Gateway Mode and
presents the user with a “STARLAN Address” prompt.
A typical call is as follows:
1.The user dials the STARLAN CP.
2.   The STARLAN CP provides the address prompt. The user enters the logical
name of the STARLAN NETWORK host (for example, 3B2).
3.   The user is connected to the UNIX system host and receives the host login
prompt.
Flow Control
Software flow control (XON/XOFF) may be enabled or disabled by System 25 data endpoints.
After the “STARLAN Address” prompt is returned to the user, a CONTROL-X may be
entered instead of a logical name.The user will be prompted further to enable or disable
flow control. After that, the user is again prompted for a STARLAN address. This option
also works for calls from the STARLAN NETWORK to System 25.
Data Call Disconnect
Data calls may be disconnected at either endpoint.Connections are dropped through the
normal disconnect procedures of each network.If a failure in the established connection
occurs, call disconnections are initiated from both sides.
2-297 
						

							FEATURES AND SERVICES
Third-Party Call Setup
A data terminal (on System 25) or workstation (on the STARLAN NETWORK) can set up a
call between two other stations (voice or data) using the Third-Party Call Setup feature.
Since voice port/data port associations are not meaningful for STARLAN CP ports,
STARLAN NETWORK workstations must always specify the Personal Dial Code of the
source voice terminal or the Data Dial Code of the source data terminal. Note that this
feature can only be administered for the STARLAN CP ports as a group, and not for
individual STARLAN NETWORK workstations.
When placing voice calls using CAM, Third-Party Call Setup is used automatically.
Wiring
The STARLAN NETWORK wiring plan is based on standard 4-pair building wiring. The
STARLAN NETWORK uses two pairs of the 4-pair cable, allowing the remaining two pairs to
be used for voice service.STARLAN NETWORK data is transmitted over pairs two and
three. Figures 2-46 and 2-47 provide typical connection information.
A Y-adapter may be used to combine/split the pairs at the System 25 cross-connect field.
STARLAN NETWORK NAUs provide an RJ11 phone jack that terminates pair 1. Single line
sets may be plugged directly into this jack (Figure 2-46). MERLIN Communications System
sets require an ATL adapter and local power (Figure 2-47).
ATL Adapters
The ATL adapter (KS23475) is a connection block that provides: 48V dc power from T1 (via
modular cords C4 and C1) to the ATL phone, data connections from the STARLAN
workstation, and phone connections from the ATL phone (via modular cord C1) over a
shared common cable (C3) to System 25. The phone and data connections are on separate
wire pairs that are split-out at the SIP “Y” adapter (A1). Phone wiring is cabled to the ATL
Line CP (ZTN79) by octopus cable C2, and data wiring is cabled to the NEU by modular cord
C1.
Administration Requirements
The STARLAN CP is administered as a type of data port. Some items administered on one
port are automatically administered for all four ports on the CP, others are individually
administrable.
Individually Administrable (default):
l DDC of port
l DDC to hunt to next (none)
l Display ID
2-298 
						

							STARLAN NETWORK Access
Common Administration (default):
l CO trunk pool dial restriction (no)
l Other trunk pool dial restriction (no)
l Outward restriction
l Toll Restriction Class (none)
l ARS FRL (3)
l Restrict Third-Party Call Setup feature (yes)
Hardware Requirements
Requires a STARLAN INTERFACE CP. Each CP provides four interface ports between the
System 25 and the STARLAN NETWORK.
2-299 
						

							FEATURES AND SERVICES
NAU -NETWORK ACCESS UNIT - PEC 2614-100
NEU -NETWORK EXTENSION UNIT - PEC 261O-OO1
ZTN84 -STARLAN CP - PEC 62518
ZTN78 -TIP/RING LINE CP - PEC 62504
TN742 -ANALOG LINE CP - PEC 63511
A1 -WP90851-L1 (Y ADAPTER) - PEC 2750-T05 (NOTE 1)
A2 -858A ADAPTER
B1 -103A CONNECTING BLOCK*
C1 -MODULAR CORD D8W-87 (FURNISHED WITH NAU)
C2 -OCTOPUS CABLE WP90780 - PEC 2720-05P (NOTE 1)
C5 -MODULAR CORD D4BU-87 (FURNISHED WITH PHONE)
W1 -FOUR PAIR BUILDING WIRING*
NOTE 1: C2 AND A1 ARE NOT REQUIRED IF NO PHONE IS
PLUGGED INTO THE NAU.
* FURNISHED BY INSTALLER
Figure 2-46.STARLAN NETWORK Connection to System 25 (With 2500 Single-Line
Telephone)
2-300 
						

							STARLAN NETWORK Access
NAU - NETWORK ACCESS UNIT - PEC 2614-100
NEU - NETWORK EXTENSION UNIT - PEC 2610-001
ZTN79 - ATL LINE CP - PEC 62505
ZTN84 - STARLAN CP - PEC 62518
A1 -“Y” ADAPTER WP90851-L1
- PEC 2750-T05 (NOTE 1)A2 -858A ADAPTER
A3 -ATL ADAPTER (NOTE 1)
B1- CONNECTING BLOCK 103A*C1- MODULAR CORD D8W-87 (FURNISHED WITH NAU AND PHONE)C2 - OCTOPUS CABLE WP90780 - PEC 2720-05P
C3 - 6 INCH MODULAR CORD (PART OF A3)
C4 - 7 FOOT MODULAR CORD (PART OF A3)
T1- 48 VOLT DC POWER SUPPLY KS22911 (NOTE 1)W1- FOUR PAIR BUILDING WIRING*
NOTE 1: PEC 62520 INCLUDES A1, A3, AND T1
* FURNISHED BY INSTALLER
Figure 2-47.
STARLAN NETWORK Connection to System 25 (With ATL-Type Telephone)
2-301 
						

							FEATURES AND SERVICES
Station Hunting
Description
This feature provides linear, circular, or combinational hunting sequences for calls to busy
single-line voice terminals and data terminals.
Calls to a busy terminal may hunt to (only) one other terminal; however, up to five terminals
may hunt to the same terminal.
Although hunting is not available to or from multiline terminals, single-line terminals may have
their calls covered by multiline terminals.
Station Hunting takes precedence over Coverage. Calls to a single-line
assigned both Station Hunting and Coverage will first hunt. If no
available, the call goes to coverage.
The following are examples of the three types of hunting allowed:
l Linear Hunting Example:
Terminals x, y, and z are arranged for linear hunting as follows:voice terminal that is
hunted-to station is
(1) Terminal x hunts
to Terminal y; (2) Terminal y hunts to Terminal z, and (3) Terminal z does not hunt.
An incoming call to a busy terminal in the chain will hunt in one direction only.
Hunting will be toward the terminal that does not hunt.
l Circular Hunting Example:
Terminals x, y, and z are arranged for circular hunting as follows: (1) Terminal x
hunts to Terminal y, (2) Terminal y hunts to Terminal z, and (3) Terminal z hunts to
Terminal x.
An incoming call to a busy terminal in the chain hunts in one direction until it finds an
idle terminal and then rings at that terminal.Any coverage options assigned to that
terminal will then be invoked. If the hunt finds all terminals busy, it will stop at the
called terminal. Any coverage options assigned to the called terminal will then be
invoked.
l Combinational Hunting Example:
Terminals w, x, and y all hunt to Terminal z.
An incoming call to a busy w, x, or y Terminal will ring at Terminal z, and any
coverage options assigned Terminal z will be invoked. If Terminal z is busy, the call
remains at the called terminal. Any coverage options assigned the called terminal will
then be invoked.
2-302 
						

							Station Hunting
Considerations
Station Hunting provides several flexible alternatives to ensure that calls do not go
unanswered. Note that only calls to busy terminals will hunt; once a call begins ringing at a
terminal it will remain there unless picked up or covered.
Interactions
The following features interact with Station Hunting.
Attendant Camp-On: When the attendant extends a call to a busy terminal in a hunt group,
the call hunts for an idle terminal. If none is found, the call Camps-On to the called terminal.
Callback Queuing: If all stations of a hunt group are busy, the call queues only for the dialed
station in the group.
Call Waiting:If all members of a hunt group are busy and the originally-dialed station has
Call Waiting, the caller hears special ringback until the station becomes available to answer
the call.
Coverage: Station Hunting initially overrides all coverage options. When a call to a voice
terminal that has Coverage exhausts the terminal hunting possibilities, coverage is invoked.
Following/Forwarding: Calls signed in at, or forwarded to, a station in a hunt group will hunt
and ring an idle station if the home station is busy. If all members of the group are busy and
the away, or forwarded-to, station has Call Waiting, the caller hears special ringback until the
away station becomes available to answer the call.
A call to a forwarding station in a hunt group will first ring at the away, or forwarded-to,
station. After an administered number of rings, the call returns to the hunt group; if all
members are busy, the call continues to ring at the away station until a hunt group member
becomes available.
Administration Requirements
Voice or Data Terminal Port:
l Assign PDC/DDC of terminal to hunt to next.
2-303 
						

							FEATURES AND SERVICES
Station Message Detail Recording (SMDR)
Description
This feature provides detailed call information records on all incoming and outgoing trunk
calls and sends this information to an (optional) output device. Data on inside calls is not
collected.
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.No characters are read by the port interface, 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:
l 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.No indication is provided that
trunks have been bridged together.
l 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 “Calls Lost Due To Call
Record Overflow” is provided when a printer is re-attached.
2-304