Oracle Communications Diameter Signaling Router (DSR)
 

PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
 

In this Document

Goal

Solution

Created from <SR 3-13400283141>

Applies to:

Goal

The goal of this article is to clarify a behavior change with respect to the Destination Host (DH) Attribute Value Pair (AVP) by the Policy Diameter Routing Agent (PDRA) application on the Diameter Signaling Router (DSR) before and after enabling the PCRF Pooling feature.

Solution

Prior to enabling PCRF Pooling feature in Policy and Charging Applications (PCA) / PDRA application, the Diameter message handed from the feature to the Diameter Routing Layer (DRL) of the DSR would always have a Destination-Host (DH) AVP. If the message arriving at the DSR did not originally have a DH AVP, PDRA would add the AVP with the selected PCRF as the destination-host.

Once PCRF Pooling is enabled, a different code path is traversed in the PDRA application.  When PDRA completes processing the message, it is handed back to the DSR's Diameter Routing Layer (DRL) with no Destination-Host AVP changes. If the original message arriving at the DSR had a DH AVP already populated, that DH remains unaltered.  If the original message did not have a DH AVP, then none will be present when DRL receives the processed message from PDRA.

This change has implications if the Diameter Configuration on the DSR inspects the message for DH AVP as a rule condition. For example, when PDRA sends the processed message to the Diameter Routing Layer, if it passes through a Peer Route Table (PRT) and one of the Peer Route Rule conditions includes checking for the presence, absence, or specific content of the Destination Host AVP then the behavior may be different before and after PCRF Pooling is enabled. Operators may need to assess the influence this change may have on routing their messaging traffic, and adjust their Diameter Configuration accordingly.

This solution has no attachment