Planning guidelines, Task list: changing trunk-to-trunk transfer status – Lucent Technologies MERLIN LEGEND 6 User Manual

Page 280

Advertising
background image

MERLIN LEGEND Communications System Release 6.0
System Manager’s Guide

555-660-118

Issue 1

February 1998

Managing the System

Page 6-50

Changing Trunk-to-Trunk Transfer Status

6

Planning Guidelines

6

SECURITY

l

ALERT:

!

The default setting for all extensions, including voice messaging
(VMI) ports and remote access barrier codes, disallows trunk-to-trunk
transfer. If you elect to enable this feature at an extension, consider
the risk of toll-fraud abusers obtaining access to your system and
calling out of the system using this feature. For more information
about protecting your system from fraudulent toll charges, see
Appendix A, “Customer Support Information.”

Valid Entries

Enabled, Disabled

A single-line telephone can never perform a trunk-to-trunk transfer unless it is
plugged into a port programmed as a VMI port.

Task List: Changing Trunk-to-Trunk
Transfer Status

6

o

Obtain the following forms, as appropriate:

— Form 4b, Analog Multiline Telephone

— Form 4d, MLX Telephone

— Form 4e, MFM Adjunct: MLX Telephone

— Form 4f, Tip/Ring Equipment

— Form 5a, Direct-Line Console (DLC): Analog

— Form 5b, Direct-Line Console (DLC): Digital

— Form 5c, MFM Adjunct: DLC

— Form 5d, Queued Call Console (QCC)

— Data Form 1a, Modem Data Station

— Data Form 1b, 7500B Data Station

o

If necessary, read “Transfer” in the

Feature Reference for detailed

information about this feature.

o

Plan changes and record the new values on the form(s).

o

Open the System Programming menu from the console or a PC with SPM.

o

Program the change(s), following the instructions for “Trunk-to-Trunk
Transfer” in

System Programming, Chapter 3, or the summary

programming instructions below.

Advertising