Lucent Technologies MERLIN LEGEND 5 - Manual (Page 202)

MERLIN LEGEND Communications System Release 5.0
System Manager’s Guide
555-650-118
Issue 1
June 1997
Putting the System to Work
Page 5-22 Scenario 3: A Dual-Location Company
5
SECURITY l ALERT:
!
The MERLIN LEGEND Communications System ships with ARS activated
and all extensions set to Facility Restriction Level 3, allowing all
international calling. To prevent toll fraud, ARS Facility Restriction Levels
(FRLs) should be established using:
■ FRL 0 for restriction to inside calls only
■ FRL 2 for restriction to local calls only
■ FRL 3 for restriction to domestic long distance (excluding area code
809 for the Dominican Republic as this is part of the North American
Numbering Plan, unless 809 is required)
■ FRL 4 for international calling
Each extension should be assigned the appropriate FRL to match its calling
requirement. All voice mail port extensions not used for outcalling should be
assigned to FRL 0.
Scenario 3: A Dual-Location Company 5
This scenario describes a medium-sized mail-order company with supervised
groups of order-takers and customer service representatives; the company also
sells to large corporate customers through a field sales force. The various
departments and staff are in two different cities, and the company uses two
different MERLIN LEGEND Communications Systems, both in Hybrid/PBX mode.
In this company, the system manager allocates more time to system operations
than in the two previous scenarios; she also acts as Manager of Information
Systems for the company’s computer systems.
Company needs and the solutions provided by the system fall into the following
categories:
■ General. Broad concerns that affect the company as a whole and require
basic decisions about the lines/trunks used in the system, as well as
system modes of operation.
■ Work Groups. Groups of people who work together have specific
communications needs.
■ Individuals. Individuals, such as the system manager and off-site
employees, have needs that general planning does not meet.
NOTE:
Previous scenarios described many system features, for example,
call coverage. Therefore, this scenario highlights additional needs
and features not yet discussed. In this scenario, such features as
coverage and calling restrictions are mentioned only briefly.
Figure 5–5 illustrates the locations and staffing.