MERLIN LEGEND Communications System Release 5.0
Feature Reference
555-650-110
Issue 1
June 1997
Applications
Page I-70
ExpressRoute 1000
I
including Group IV fax, videoconferencing, and rapid data transfer. For
more information about digital facilities and adjuncts, see the following
topics:
■
“Basic Rate Interface (BRI)” on page 82
■
“CTI (Computer Telephony Integration) Link” on page 173
■
“Digital Data Calls” on page 183
■
“Primary Rate Interface (PRI) and T1” on page 441
■
‘‘Videoconferencing’’ on page I-60
■
■
‘‘Ascend Pipeline 25-Px’’ on page I-72
The ExpressRoute 1000 is an ISDN terminal adapter, also referred to as a
digital
modem
, that allows users to perform high-speed data transfer internally through
the MERLIN LEGEND Communications System and over ISDN or T1 Switched
56 lines, at 64 kbps or 56 kbps. The ExpressRoute 1000 cannot take advantage
of 2B data connections.
NOTE:
For the most complete information about using terminal adapters with the
system, see the
Data/Video Reference.
includes details about how the system functions with digital
communications devices.
The ExpressRoute 1000 supports data calls over Primary Rate Interface
B-channels (at 64 kbps), Basic Rate Interface B-channels (at 64 kbps), and T1
Switched 56 lines (at 56 kbps).
Feature Interactions
9
Account Code Entry
Account Code Entry can be entered for calls made by digital data
workstations.
Authorization Code
Data calls can use authorization calls. If Account Code Entry is also used,
the authorization code must be entered after the account code.
Auto Dial
An ExpressRoute 1000 can make a call using an Auto Dial button by
dialing the virtual number of the button (for example,
#01
).
Automatic Route
Selection
Data calls can be made using ARS. ExpressRoute 1000s simply dial the
ARS dial-out code (usually
9
) followed by the telephone number to make
calls using ARS. The data calls
must
be routed through ARS pools that
have only PRI, NI-1 BRI, and/or Switched 56 T1 data lines.
Barge-In
Data calls cannot be barged into.
Call Waiting
Call waiting does not work with data calls. The call appears to wait but
does not arrive when the extension becomes available.