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-13082760551>

Applies to:

Goal

------To address the issue of Rules not seeming to work for special cases where rules involve "starts with" -------

We have seen the issue in cases involving "OrigHost StartsWith" in Peer Route Rules

The issue can manifest itself by a rule (which should be encountered) not being encountered when a particular rule (which should not be encountered) is present.
This can be seen when a new rule is added that seems to break other rules. The problem would be the new rule that is added and not the one it breaks. This now problematic rule would also not be encountered for messages that should encounter it.

Ultimately it boils down to a peer route rule that should be encountered is not being encountered and the message "no peer route rule found" is being returned by the DSR.

Solution

This issue was reproduced by our development support and was addressed via Bug ID 24588860.

There are a number of workarounds that have been seen to work for this issue.

Note: It is assumed that the Peer Route Rule in question, the rule that should be encountered, has already been determined. It's expected that this rule would have "OrigHost StartsWith" as a part of its condition.

Possible workarounds:

a) Remove the rule in question and re-add it.  (this has worked in some cases but not all)

b) Making adjustments to the priority of the rule. (this is customer specific and depends on the priority of the rule with regards to other rules but has been known to work)

c) Changing the condition of the rule to remove the "StartsWith". (this seems to be a reliable option)

The fix for this bug has been included in DSR 8.0.
See release notes for DSR 8.0 (https://docs.oracle.com/cd/E76907_01/docs.80/E86806_rev_03.pdf) to confirm the presence of Bug ID 24588860.

This solution has no attachment