2.0 Mb DTI/PRI Administration and Maintenance Guide Book ... - Home

Chapter 3 — DPNSS1/DASS2 features description and implementation Page 729 of 1536
At the gateway node, if mixed MCDN/DPNSS1 route lists are programmed,
an incoming MCDN call using an outgoing DPNSS1 route for the first call
attempt (without Executive Intrusion) will also use a DPNSS1 route for the
Executive Intrusion request.
On the Option 11 the following hardware is required:
— DPNSS1 XPRI2 – NTAK799.
Feature interactions
Interactions with other DPNSS1 Supplementary Services
DPNSS1 Diversion
In the following scenario an Executive Intrusion request is made on a diverted
call (Immediate). Set B has diversion immediate active to set C (set B is on a
third-party PBX). Set C may be on the same node or on another node. C is
busy on an call with another set. The attendant calls B. The answer to the
Initial Service Request Message (ISRM) is a Number Acknowledge Message
(NAM) with a Destination Address of C. The attendant position then sends a
regular ISRM to C. Since C is busy, the attendant receives Clear Request
Message (CRM) in response to the ISRM. The attendant presses the BKI key.
In this case, an Executive Intrusion ISRM is sent to C, and C is considered the
requested party.
In the following scenario an Executive Intrusion request is made on a diverted
call (Busy). Set B has diversion on busy active to set C. Set C may be on the
same node or on another node. Both B and C are busy on calls with other sets.
The attendant sends a regular ISRM to C. Since C is busy, the attendant
position receives a Clear Request Message in response. The attendant presses
the BKI key. In this case, an Executive Intrusion ISRM is sent to C, and C is
considered the requested party.
DPNSS1 Route Optimization
If the requested party is involved in a Route Optimization process when it
receives an Executive Intrusion request, the request is rejected. Conversely,
the originating, requested and unrequested parties will be able to send a Route
Optimization request only after the Executive Intrusion conference reverts to
a simple call. Finally, if an Executive Intrusion request is received after a
Route Optimization Request Supplementary Information String has been sent
but Route Optimization has not actually commenced, the Route Optimization
process is aborted and the Executive Intrusion may proceed.
Option 11C 2.0 Mb DTI/PRI Administration and Maintenance guide