General Platform Enhancements

PPL Auditing By Enity

When PPL Auditing is enabled on a card, all state machine activity on the card is recorded in an audit log on either a per-PPL component basis or an individual entity basis. A log consists of a number of audit entries, each representing a state transition on a specific entity (channel). The length of the audit entries varies per PPL component.

Under busy call conditions, the user has the option of initiating PPL Auditing on an entity basis instead of PPL Auditing on a component basis. This option provides the user with more accurate error auditing. Enabling the auditing function on an entity basis allows the auditing buffer to store only the information pertaining to user-selected entities. When auditing on a component basis, the ability to determine the cause of a problem can be lost. This is because the multi-entities that overload the auditing buffer can be overwritten due to a large volume of incoming voice traffic.

Important! Before initiating the PPL Audit function, contact Excel Technical Support for information on selecting the Audit Type options in the PPL Audit Configure and PPL Audit Query messages.

Modified API Messages

The following API Messages were modified to support this feature:

• PPL Audit Configure (0x00DC)

• PPL Audit Query (0x00DD)

Technical Publications

This feature is documented in the following technical publications:

• API Reference: Refer to the two messages above in Chapter 1, and to the chapter, PPL Component Information.

• Refer to the PPL Developer's Guide, PPL Introduction chapter, in the section PPL Auditing.

• Developer’s Guide: Overview, System Maintenance chapter, in the section PPL Auditing.

Matrix Redundancy for Half-Calls

This feature provides additional redundancy support during Matrix Controller switchovers by maintaining calls that are answered but not connected. This redundancy is important for many applications (media server, call centers, outbound dialing, prepaid card recharge) with non-connected ports that were previously purged on switchover.

Technical Publications

Refer to the following in the Developer’s Guide: Overview:

• The Layer 4 Call Control chapter, CSP Call Control Control Call Flow section, Redundancy for Answered But Non-Connected Channels subsection.

• New configuration byte in CH - Channel Management (0x0061) component in the chapter Layer 4 Call Control PPL Information.

Two-Byte Sequence Number Field

This feature increases the number of bytes used in the Sequence Number field of a message header to two bytes (16 bits) instead of one byte (8 bits). This feature expands the amount of sequence numbers that can be outstanding for an API message.

This feature is required to enable higher performance on interfaces where numerous outstanding messages could be needed, like TCAP/SCCP.

Technical Publications

This feature is documented in the API Reference as follows:

• Chapter 1, in the section Introduction to API Messages

• Generic Card Configure (0x0122) message

• Generic Card Query (0x0123) message

• Matrix/Host Sequence Number TLV (0x0640)