Lucent Technologies MERLIN LEGEND Release 7.0 System Planning Manual page 229

MERLIN LEGEND Communications System Release 7.0
System Planning 555-670-112
4 Features
Group-Assigned Features
Planning Form Instructions
1. Review the Employee Communication Survey analysis and determine the
number of calling groups needed, using the following guidelines:
2. For each calling group, make a copy of both sides of Form 7d, Group
Calling.
3. For each group, on the front of Form 7d, list the extensions and lines/trunks
assigned to the group:
a.
b.
Assign up to 32 calling groups with up to 20 members for each
group. Each telephone user can be a member of only one
calling group.
Designate up to 80 lines/trunks to ring directly into a calling group.
Incoming calls on a given line/trunk can be directed to only one
calling group.
If the MERLIN LEGEND Mail or other supported VMS is being used,
either on the local system or a remote system (Centralized Voice
Messaging), reserve one or more calling groups for that feature.
A calling group may have up to one non-local member (Release 6.1
and later). If a calling group has a non-local member, that is the only
member allowed in the calling group. Local and non-local members
cannot be in the same calling group. A calling group containing a
single non-local member can be used for the same purposes as a
calling group containing only local extensions. This includes night
service, group coverage, calling group overflow coverage, and QCC
queue overflow coverage across a private network to a centralized
VMS/AA, non-local calling group, QCC queue, DLC, or any
individual extension on a remote MERLIN LEGEND, DEFINITY
ECS, or DEFINITY Prologix system, or to the PSTN via UDP
routing.
Write the group number in the Group No. space. Start with and
number sequentially.
Write the name of the group in the Group Name space. See the
survey analysis.
NOTE:
If the system has MERLIN LEGEND Mail or other supported
VMS, fill in only the group number and group name here,
then fill in the rest of the Group Calling information on the
applicable forms for that VMS.
Issue 1
April 1999
4-31
4