PPL Component Addressing

Overview

This section lists the PPL Components and the associated AIBs used for PPL messages.

Guidelines

The following are guidelines for the information in the tables later in this section.

PPL timer and configuration bytes are stored on a per channel basis.

The PPL Transmit Signal Configure message (0xD2) is applies to the E1 and T1 protocols.

The tables later in this section show the AIBs used to address the various PPL components in these PPL-related API messages listed below:

PPL Assign (0xD1)

PPL Audit Configure (0xDC)

PPL Audit Query (0xDD)

PPL Configure (0xD7)

PPL Data Query (0xDE)

PPL Event Indication (0x43)

PPL Event Request (0x44)

PPL Timer Configure (0xCF)

The PPL Transmit Signal Configure message is not included in the tables because it uses the Channel address AIB only.

For span/channel addressed state machines, the following messages can use either a single entity or range address method:

PPL Assign (0xD1)

PPL Configure (0xD7)

PPL Timer Configure (0xCF)

PPL Transmit Signal Configure (0xD2)

For span/channel addressed state machines, the following messages use a single entity address method only:

PPL Audit Query (0xDD)

PPL Data Query (0xDE)

PPL Event Indication (0x43)

PPL Event Request (0x44)

For information on AIB formats, refer to the Address Elements chapter.

 

PPL Events

The PPL Event Indication and PPL Event Request messages are used to send and receive additional call processing data about the call.

 

PPL Event Request

This message is initiated by the host, and sends an external event directly to the specified PPL component.

 

PPL Event Indication

This message enables the PPL component on the CSP to report external events to the host application.

The PPL Event Request and PPL Event Indication messages must include the PPL component and event. They can include optional data in an ICB.

ICB subtype values can include Layer 3 (ISDN, SS7, SIP, or H.323) parameters. Refer to the Information Control Blocks chapter.