Feature interactions
Feature packaging
A call with new Bearer Capability encodings will only terminate to a BRI
terminal. If the terminating terminal is not a BRI terminal, the call is blocked.
Voice calls are successful between BRI and PRI with no restrictions.
The following feature interactions are unique to BRI/PRI basic data call
interworking.
•
ISDN BRI Data Call
Added IEs (such as LLC and HLC) and the expanded set of supported
data values for the Bearer Capability IE enhance BRI's ability to support
a variety of circuit switched data calls.
•
ISDN PRI D-channel Error Reporting and Monitor
The DCH table supports the new IEs in the PRI call messages. The DCH
monitor displays the new IEs and a label for monitor level 2.
•
Incoming Digit Conversion
If an incoming SETUP message with the new Bearer Capability
encodings goes through incoming digit conversion, it must be translated
to a BRI DN. If the terminating DN is not a BRI DN, the call will be
blocked.
•
Network Alternate Route Selection
If an outgoing call contains a SETUP with a new Bearer Capability
encoding, it can only be terminated on PRA/ISL trunks with RCAP
configured. This means that at least one entry in the RLB must be
PRA/ISL and have the DCH RCAP configured for BRI. NARS will
continue to search the RLB until it finds RCAP=BRI. An outgoing call
is blocked if RCAP is not configured, or if all trunks with RCAP
configured are busy.
BRI/PRI, as a feature, has no packaging requirements. However, the
requirements for ISDN BRI and ISDN PRI must be met.
International ISDN PRI Feature description and administration
BRI/PRI Basic Call Interworking
Page 291 of 1814