NEC SL1000 Features And Specifications Manual page 444

SL1000/SL1100
• Basic Rate Interface (BRI)
Caller ID Name to Single Line Terminal is NOT supported for ISDN (BRT) Trunks.
The system is compatible with ISDN Basic Rate Interface (BRI) services. BRI services currently
supported include:
- Basic BRI Call Control (BCC)
- Point-to-Point BRI Terminal Connection (no daisy-chaining)
- Multipoint BRI Terminal Connection (daisy-chaining)
BRI services require the installation of 2BRIDB-C1. Each 2BRIDB-C1 has two BRI circuits. The
2BRIDB-C1 mounted to the 008E-A1/000E-A1 (SL1000) 084M-B1/080E-B1/008E-B1/000E-B1
(SL1100) unit.
For each BRI line, two different Terminal Endpoint Unidentified (TEIs) are assigned to two different
Service Profile Identifiers (SPIDs).
The two different SPIDs for each BRI line, are related to different trunk logical port numbers. One
I BRI provides two trunk logical ports when it is connected to a CO line. Each SPID is assigned to a
different TEI. This relationship is made in the initialization of the BRI line when it is connected to the
CO.
This relationship between SPID and TEIs are created as follows.
LOGICAL-PORT-NUMBER + 0 = SPID-1
LOGICAL-PORT-NUMBER + 1 = SPID-2
When using the SMDR reports for BRI, all incoming BRI calls are displayed under the CLASS
column as IVIN.
• Automatic Data Link Failure Recovery
If a data link error is detected by the BRI ETU, the system tries to recover the data link and send the
SPID to the central office. To provide this enhancement, the BRI ETU must be able to indicate to the
system when a data link error has occurred.
In addition to the BRI Interface ETU, BRI Services require the installation of NT1 Network
Terminators and interconnecting cabling.
• CO Line Service is not supported
ISDN-BRI cannot be configured for CO Emulation
• BRI and DID Callers with Non-Matching SPID Numbers
This feature allows you to determine whether the system checks the called party number with the
SETUP message and the SPID setup. Depending on the system programming, this can allow DID
calls to be received on BRI trunks and direct them according to the DID Translation Table (PRG
22-11).
• Special Conditions Related to Ordering DID Service For ISDN-BRI
Telcos may refer to this in different ways. The reference Verizon uses to order such service is
Additional Directory Numbers with no new terminating equipment (only a dialable number). When
you want Additional Directory Numbers to hunt when a B-Channel is busy, the service may be
called Busy Diversion.
• Calling Party Number (CPN) presentation from station is available for virtual extensions.
• The trunk setting (PRG 20-19-09) for sending the caller name on outgoing ISDN calls takes priority
over the same setting for the station (PRG 15-01-01).
• When programmed, Calling Party Name will be sent on calls that originate from a station (MLT, SLT,
or IP Multiline) or an incoming trunk (Analog or ISDN).
• Calling Party Name supports up to 12 ASCII characters.
• When a call originates from a virtual extension, the Calling Party Name for the virtual extension is
sent. It does not follow the setting in PRG 15-18-02.
• Calling Party Name is dependant upon the carrier. The network carrier must allow the SL1000/
SL1100 to edit the Calling Party Name information.
• SL1000/SL1100 does not support ISDN sub-addressing.
Default Settings
None
1-434
ISSUE 2.0
ISDN Compatibility