Lucent Technologies MERLIN LEGEND Release 6.1 Feature Reference page 771

MERLIN LEGEND Communications System Release 6.1
Feature Reference 555-661-110
Features
Uniform Dial Plan Features
Messaging
Music On Hold
Night Service
Paging
Park
Personal Lines
Pickup
Pools
Messaging features generally do not work across a private network. They
only work for extensions connected to the same system.
A user cannot turn a message light at a non-local dial plan extension off
or on. Only an integrated VMI port can turn a message light on or off
across a private network (Release 6.1 and later systems).
An operator cannot inspect the message status of an extension.
Music On Hold sources cannot be shared by networked systems.
Calls between systems in a private network are treated as outside calls;
for this reason, callers hear Music On Hold as though they were outside
callers.
All Night Service group extensions and lines must be on the local switch,
as must be any Night Service alerts.
If Night Service is programmed with outward restriction, the restriction
does not apply to non-local dial plan calls. Exclusion lists do not apply to
intersystem calls.
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.
In Release 6.1 and later systems (Hybrid/PBX mode only), Night Service
coverage can be provided across a private network to a centralized
Automated Attendant, a non-local calling group, a QCC queue, a DLC, or
any individual extension on the remote system.
Loudspeaker and voice paging calls cannot be made to non-local dial
plan extensions or paging groups.
Park zones must be in the local system. Calls cannot be parked at remote
park zones.
Private networked trunks should not be assigned to extensions as
personal lines.
A call at a non-local extension cannot be picked up.
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 Switched 56). For
security and speed 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 and outside trunk pools.
When PRI tandem trunks are available, their pools should be assigned as
Route 1 for the purpose of UDP routing.
Issue 1
August 1998
Page 722