NEC Electra Elite IPK II System User Manual page 664

Document Revision 4C
The two different SPIDs for each BRI line, are related to different trunk logical port
numbers. One 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.
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 (Program 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.

Default Setting
None
2 - 640
LOGICAL-PORT-NUMBER + 0 = SPID-1
LOGICAL-PORT-NUMBER + 1 = SPID-2
Electra Elite IPK II
ISDN Compatibility