Oracle Communications Diameter Signaling Router (DSR)
 

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

In this Document

Goal

Solution

Patch

References

Created from <SR 3-13235752301>

Applies to:

Goal

Why is Pending Answer Timer Not Working As expected in DSR 7.1.2

Solution

A Pending Transaction Timer limits the time that Diameter Routing Layer (DRL) will wait for an Answer response after forwarding a Request message to an upstream Peer Node. When this time-limit is exceeded, DRL will abandon invoke message rerouting.

The user can create one or more Pending Answer Timer and then define, through configuration, which Pending Answer Timer will be will be assigned to a forwarded transaction. The system always consists of a “DEFAULT” Pending Answer Timer, which is always used if no other Pending Answer Timer selection rule takes precedence.

When DRL selects a viable Connection for forwarding a Request message to an upstream Peer Node, it determines which Pending Answer Timer value to use based on the following precedence selection rules (highest to lowest priority):

1. If Transaction Configuration Set is selected on ingress Peer Node from which the Diameter Request was received, use Transaction Configuration Set and apply ‘longest/strongest’ match search criteria for Diameter Request message parameters comparison and if a match is found, apply PAT assigned to Transaction Configuration Rule defined under this Transaction Configuration Set, if it exists.
2. The Pending Answer Timer assigned to the Routing Option Set for the Ingress Peer, if it exists.
3. The Pending Answer Timer assigned to the egress Peer Node to which the Request message will be forwarded, if it exists.
4. Search Default TCS and apply ‘longest/strongest’ match. Use PAT associated with best match, if any is found.
5. “DEFAULT” Pending Answer Timer.

However because of a Bug the precedence is really this:

1. If Transaction Configuration Set is assigned to ingress Peer Node
2. PAT assigned to the Routing Option Set for Ingress Peer
3. Egress PAT assigned to Ingress Peer Node
4. Egress PAT Assigned to Egress Peer Node to which request will be forwarded
5. Default Transaction Configuration Set (TCS) with longest/strongest match
6. Default Pending Answer Timer

Patch

Patch 26372862 was developed to fix this issues in DSR 7.2.0.0-72.25.0.

MOP to apply the patch is on: https://stbeehive.oracle.com/content/dav/st/DSR%20Technical%20Support%20Center%20(DSR%20TSC)/Public%20Documents/MOP%20LIBRARY/Orange%20France_Prod_DSR720_Patch_26372862_MOP%20v1.2.pdf

References

This solution has no attachment