My Oracle Support Banner

DSRDSA Wrong "AVP_Multiple_Instance_Check" "Specific AVP Screening" Stateless Rule (Doc ID 2643027.1)

Last updated on MAY 01, 2020

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 8.2.0 and later
Tekelec

Symptoms

In case of Diameter Answer timeout, the Origin Peer name fetch mechanism of DSA is not working correctly.

It should be using the DSR Origin Host and Origin-Realm because in case of an answer timeout, it will never have those values from peer, but instead, it tries to find the Origin name from an answer that was never received, hence causing a debug error.

Issue can be recreated by using the DSA stateless rules in "Detection Only" mode. Now if DSR does not receive an answer response in time, it should be creating an answer message using the stateless rules "AVP_Multiple_Instance_Check" and "Specific AVP Screening" but instead it sends the standard cause timeout is expired (as the peer has not responded with an answer within the time).

The stateless rules that are being used are:

DSA Mode of operation:

DSR sent own answer by cause timeout is expired (opposite peer haven't sent any answer).

According to dsa log files, there are the same debug message

"Fetching Origin PeerName from diameter msg failed.. AVP Name and Its Value of currently processed message"

 

 

Because DSR haven't received from opposite peer any answer DSA script haven't fetched "Origin Peer name" from diameter message.

Instead that script should be instructed to use DSR Origin-Host(random.random.com), Origin-Realm(random.com) in case of an answer timeout condition, but it doesn't use.

Changes

 New configuration

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.