Lucent Technologies MERLIN LEGEND Release 5.0 System Programming Manual page 700

Communications system
Hide thumbs Also See for MERLIN LEGEND Release 5.0:
Table of Contents

Advertisement

MERLIN LEGEND Communications System Release 5.0
System Programming 555-650-111
4
Programming Procedures
System Features
Common carriers are required by law to collect their tariffed charges. While
these charges are fraudulent charges made by persons with criminal intent,
applicable tariffs state that the customer of record is responsible for payment
of all long-distance or other network charges. Lucent Technologies cannot
be responsible for such charges and will not make any allowance or give any
credit for charges that result from unauthorized access.
To minimize the risk of unauthorized access to your communications system
follow these basic rules:
Remote Access Trunk Assignment
Use this procedure to assign or remove the trunks used for remote access. You
can also use this procedure to specify whether the Remote Access feature is
dedicated (always used for remote access) or shared (used for remote access
only when Night Service is activated).
Trunks used for dedicated remote access must not be assigned to ring into a
calling group or the QCC queue (Hybrid/PBX mode only).
Use a nonpublished remote access number.
Assign barrier codes randomly to users on a need-to-have
basis, keeping a log of ALL authorized users and assigning
one code to one person.
Use random sequence barrier codes, which are less likely to
be broken.
Deactivate all unassigned codes promptly.
Ensure that remote access users are aware of their
responsibility to keep the telephone number and any barrier
codes secure.
When possible, restrict the off-network capability of
off-premises callers using the Call Restrictions and
Disallowed List capabilities.
When possible, block out-of-hours calling.
Frequently monitor system call detail reports for quicker
detection of any unauthorized or abnormal calling patterns.
Limit remote call forward to persons on a need-to-have
basis.
Always use the longest length password allowed on the
system.
Passwords should consist of a random, non-repetitive,
hard-to-guess sequence of digits.
4
Issue 1
June 1997
Page 4-293

Advertisement

Table of Contents
loading

Table of Contents