Oracle Communications Diameter Signaling Router (DSR)
 

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

In this Document

Goal

Solution

References

Created from <SR 3-12169982321>

Applies to:

Goal

This issue will affect customers in 5.x using mediation, and with working String enums conditions, and they want to upgrade to 6.x or above.

• In DSR 5.x, String Enumerations (enums) parameters are allowed. Not enforced by application or GUI.
• In DSR 6.x/7.x, String enums are not allowed. Even though, the GUI will allow the user to provision them.
• In DSR 7.3, String enums will not be allowed by the application or GUI.

Solution

The enum value is strictly considered to be an integer on the Rule Templates screen in the conditions. The problem is that there is an inconsistency between the Enumerations and the Rule Templates screens as defined in the DSR FD: The Enumerations screen really allows the user to define string values, even the help page suggests that, but they are later not supported correctly as conditions on the Rule Template screen (DSR 6.x and 7.x). The enum definition does not indicate what kind of value it holds, i.e. string or numeric, and the Rule Template always assumes numeric values.

Development does have a recommendation on how to migrate the customer to a condition that will allows Strings.

One way to make this condition work is to use a string type instead of an enum:

1. Make a copy of the Rule Template and change the right value type of the second condition from enum to DiameterIdentity. Change the name of the template because it must be unique. Do NOT change the name of the conditions.
2. Move the new Rule Template to "test" and then to "active" state on the "State & Properties" screen.
3. Go to the "Rule Sets" screen of the old template, and export the rules, save the file.
4. Go to the "Rule Sets" screen of the new template, and import the rules from the saved file.
5. Verify that the new template contains the desired values, the Origin-Host column should contain the realm values.
6. Go to the "Triggers" screen, and replace the old template with the new one.

References

This solution has no attachment