Lucent Technologies MERLIN LEGEND Release 7.0 Feature Reference page 770

MERLIN LEGEND Communications System Release 7.0
Feature Reference 555-670-110
Features
Tandem Switching
Callback
(continued)
CTI Link
Digital Data Calls
Night Service
Personal Lines
Pools
If a caller attempts Selective Callback upon hearing a busy tone and the
busy condition is not derived from the originating system, Selective
Callback has no effect. A caller can use Selective Callback to queue for
Route 1 when all local routes for a networked call are busy.
In Release 6.0 and later systems (Hybrid/PBX mode only), operation for
non-local dial plan extension calls, both incoming and outgoing, in
PassageWay Telephony Services applications depends upon the
application implementation as well as the type of private networked trunk
(PRI or tie) that carries calls. See
6.0 and Later Systems Only)'' on page 217
In Release 6.0 and later systems (Hybrid/PBX mode only), digital data
calls between networked systems must travel over PRI tandem trunks or
T1-emulated tie data tandem trunks. 2B data is supported when two
B-channels or T1 channels are available. Digital data calls can take place
at 64- and 128-kbps data speeds over tandem PRI trunks that are routed
for data-only or voice/data operation. T1-emulated tie data tandem
facilities are UDP-routed for data only; 56- and 112-kbps data speeds are
supported on these facilities.
In Release 6.0 and later systems (Hybrid/PBX mode only), if Night
Service is programmed with outward restriction, the restriction does not
apply to non-local dial plan calls. Exclusion lists apply only to the local
system's extensions and do not apply to UDP calls.
Transitions into and out of Night Service must be made locally. For
example, an operator cannot turn on Night Service at a remote system.
During Night Service operation, a user can call into a shared remote
access trunk and use remote access to reach non-local extensions.
During Night Service operation, an intersystem call to a member of a
Night Service group rings at all member extensions.
Transitions into and out of Night Service must be made locally. For
example, an operator cannot turn on Night Service at a remote system.
Private trunks should not be assigned to a Night Service group.
To avoid toll fraud, private networked trunks must not be assigned to
extensions as personal lines.
All private trunks must be assigned to pools of trunks that are of the same
type (PRI, analog tie, T1-emulated tie voice, or T1-emulated tie data). For
security reasons, dial access and Pool button access to these pools
should not be permitted.
Pool Status buttons show the busy or not-busy status of private trunk
pools as well as outside trunk pools.
When PRI tandem trunks are available, their pools should be assigned as
Route 1 for the purpose of UDP routing.
''Private Network Operation (Release
for details.
Issue 1
April 1999
710