Diameter Signaling Router (DSR): When manually disabling a connection, when does Disconnect Peer Request (DPR) message include Disconnect-Cause value of 2?

Asset ID:	1-71-2396838.1
Update Date:	2018-05-14
Keywords:

Solution Type Technical Instruction Sure

Solution 2396838.1 : Diameter Signaling Router (DSR): When manually disabling a connection, when does Disconnect Peer Request (DPR) message include Disconnect-Cause value of 2?

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.0.1 and later
Information in this document applies to any platform.

Goal

When the DSR transmits a Disconnect-Peer-Request (DPR - Command Code 282), when does it include the Disconnect-Cause AVP (273) of DO_NOT_WANT_TO_TALK_TO_YOU?

Solution

Per RFC6733 (Diameter Base Protocol), Disconnect Peer Request (DPR) can have three values for Disconnect-Cause AVP (273). These are REBOOTING (0), BUSY (1), and DO_NOT_WANT_TO_TALK_TO_YOU (2).

With REBOOTING, the RFC indicates receiving peer MAY attempt reconnection. For the others, the RFC indicates that the peer SHOULD NOT attempt reconnection.

In the DSR design, REBOOTING is used for peer connections that are being manually disabled when configured as Responder type. This aligns to the idea that it is valid for the peer to re-attempt connection. DO_NOT_WANT_TO_TALK_TO_YOU is used for the same situation when the connection is configured in the DSR as Initiator type, since it will be the DSR's job to re-initiate the connection when manually re-enabled.

Attachments

This solution has no attachment