MERLIN LEGEND Communications System Release 7.0
Feature Reference 555-670-110
Features
Primary Rate Interface (PRI) and T1
Night Service
Paging
Personal Lines
Pools
Queued Call
Console
Remote Access
Ringing Options
System Access/
Intercom Buttons
SMDR
A PRI B-channel can be assigned to a Night Service group (Release 4.1
and later systems only) if its B-channel group has been programmed for
routing by line appearance. If the Routing by Dial Plan option has been
selected for a PRI B-channel group, its lines cannot be assigned to a
Night Service group.
If the extension for an incoming call matches a group paging extension,
the call is treated as an unassigned DID call.
Data lines cannot be used for paging.
A personal line can be assigned to an extension to represent a PRI line
with routing by dial plan. When an incoming call arrives, the green LED
associated with the personal line lights steadily, and ringing on an SA
button occurs; the LED does not flash to indicate that a line/trunk is
ringing.
A personal line can be assigned on a voice telephone for monitoring the
status of a data line; however, users must not use the personal line to
attempt to complete a call.
Data lines (especially T1 data) should not be put in the same pool as
voice lines. System alarms eventually result if voice extensions try to
access data lines.
Data lines should not be programmed to terminate at a QCC.
A PRI line that has been programmed for routing by dial plan should not
be programmed for remote access.
Digital data calls do not receive distinctive ringing or Ring Timing options.
T1 lines must not be shared between voice and data extensions with
Shared SA buttons. The lines are programmed for either voice-only or
data-only service.
The line/trunk number of a PRI line is shown in the LINE field of the
SMDR report. The restriction code for the FTS2000 network is shown in
the ACCOUNT field.
Call timing begins when the PRI line is selected. The Called Number field
shows the number dialed by the user before any digits are manipulated by
ARS or PRI tables (Network Selection Table, Special Services Selection
Table, or Call-by-Call Services Table). In Release 2.1 and later systems,
call timing begins when the call is answered at the far end. Calls that are
not answered, therefore, do not create an SMDR call record.
If the SMDR feature is not enabled to record incoming calls, the system
does not accept Account Code Entry information for these calls.
Issue 1
April 1999
551
Need help?
Do you have a question about the MERLIN LEGEND Release 7.0 and is the answer not in the manual?