DSR 7.2.0 | Query On Remote BUSY Congestion Feature
(Doc ID 2570552.1)
Last updated on FEBRUARY 11, 2020
Applies to:Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.2.0 and later
Qn1:If our DSR received a 3004(diameter_too_busy) answer message. It will cause the connection congestion. But the real situation is just one message too busy is received, but the peer node is not too busy. Can we configure count of the message number of 3004, about 10 diameter_too_busy message to the set the connection congested.
Qn2:The Connection is considered to be BUSY after receiving a DIAMETER_TOO_BUSY response?
Qn3:No Request messages can be forwarded to (or rerouted to) this connection until the Remote Busy Abatement Timeout expires?
Qn4:If the Connection is Congested, how DSR will deal with the message? Drop it ? Or answer with error result-code?
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