Avaya Octel 200 Installation And Maintenance Manual page 877

15.1 DPNSS INTEGRATION OVERVIEW
Available beginning with Serenade 3.0, the DPNSS integration uses the DTIC card as the connection
between the message server and the PBX. Each DTIC card can have up to 30 ports authorized with
capacity-on-demand. The Adaptive Integration feature supports message-waiting indication (MWI) and
called party identification (CPI). Refer to the Adaptive Integration chapter for more information about
Adaptive Integration.
This chapter describes the DPNSS integration in general, with this section presenting specific ways in
which the DPNSS approach to basic message-waiting and called-party identification functions differ from
those described in the Adaptive Integration chapter. Refer to the configuration notes for specific PBX
integrations related to DPNSS switches.
With DPNSS integration, one digital pathway between the PBX and the Octel 200/300 message server
transmits both call information and voice communication. The pathway is provided by a 2- MB,
32-time-slot digital link from the PBX to the E1−DTIC card: the first time-slot, time-slot 0, is for
synchronization; time-slot 16 is the D or data channel that transmits the call information; and the other 30
time-slots are B or bearer/voice channels.
With the direct DPNSS link to the PBX, the message server appears as another PBX on the DPNSS
network. Using channel 16, routing information is sent so that the destination PBX, the message server,
has information about the source of the call and the reason for its arrival. This information is provided in
"Supplemental Information Codes." The called-party ID, or the destination address, follows the
supplemental information codes, where appropriate. The message server processes information from the
data channel, answers the call, and plays the appropriate greeting. Message-waiting indication is set and
canceled using a supplemental code, so there is no need to designate ports to perform MWI tasks.
As with other DSP-based cards, the DTIC processed the voice signal received from the PBX in digitized
form. The encoding algorithm used by DPNSS switches is A-law; because of this, it is important to
ensure that the message server is set up correctly to be compatible.
As noted later in this chapter, the messages sent through the data channel from one DPNSS switch to
another are extensive, and they provide much more information than is available with earlier integrations.
Such earlier integrations, based on the RS232 SMDI protocol or on collecting call- record data by
emulating telephones with LED displays, typically provide only the following:
Type of call—direct or forwarded
-
Source—calling party ID, if internal; or trunk group, if external
-
Destination—called party
-
Reason for the call, if forwarded
-
With this limited information, the typical configuration for integrated systems is such that the caller who
has entered digits to reach an extension is transferred, the PBX forwards that caller back to a different
port, and the transferring port hangs up. With the DPNSS integration, the transfer and forwarded back
scenario no longer applies. For example, when a call extended through the DPNSS switch reaches a
station that is busy, that condition is identified in the call record, the call remains on the channel that
answered originally, and the caller is prompted, as would be expected, based on the configuration. In
general, then, the user class of service would not be configured for transfer to ringing, although it is
possible to do so. If so configured, the calling party hears a few seconds of silence, followed by ringing.
If not configured for transfer to ringing, the calling party hears silence or music while on hold, until the
call is connected.
PB60019-01
DPNSS Integration 15-1
Octel 200/300 S.4.1