You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to RFC6733, sections 5.4.1. Disconnect-Peer-Request and specifically 5.4.3. Disconnect-Cause AVP, which is sent with the Disconnect-Peer-Request:
5.4.3. Disconnect-Cause AVP
The Disconnect-Cause AVP (AVP Code 273) is of type Enumerated. A
Diameter node MUST include this AVP in the Disconnect-Peer-Request
message to inform the peer of the reason for its intention to shut
down the transport connection. The following values are supported:
REBOOTING 0
A scheduled reboot is imminent. A receiver of a DPR with
above result code MAY attempt reconnection.
BUSY 1
The peer's internal resources are constrained, and it has
determined that the transport connection needs to be closed.
A receiver of a DPR with above result code SHOULD NOT attempt
reconnection.
DO_NOT_WANT_TO_TALK_TO_YOU 2
The peer has determined that it does not see a need for the
transport connection to exist, since it does not expect any
messages to be exchanged in the near future. A receiver of a
DPR with above result code SHOULD NOT attempt reconnection.
However, when Disconnect-Cause AVP 0 REBOOTING is sent from a server, the jDiameter client doesn't attempt to reconnect. This means that if a peer is restarted for maintenance, the jDiameter stack will mark it as DOWN and will never attempt to reconnect to it.
The text was updated successfully, but these errors were encountered:
Awaiting merge of #156 before I raise a pull request for commit f5dfa15 - due to the business constraints of delivering functionality, this work has been done in succession in order to deliver a jDiameter stack which meets our project's requirements.
Hello @StephenDwyer-kcom ,
We would like to share with you our Extended DRA product sheet, our Extended DRA implements a core module on top of jDiameter.
We also offer support bundles that can be used for professional services as in support and/or extra development. https://paicbd.com/blog/extended-dra/extended-dra-product-sheet/
Looking forward to hearing from you.
Best Regards,
PAiC BD Sales
According to RFC6733, sections 5.4.1. Disconnect-Peer-Request and specifically 5.4.3. Disconnect-Cause AVP, which is sent with the Disconnect-Peer-Request:
However, when Disconnect-Cause AVP 0 REBOOTING is sent from a server, the jDiameter client doesn't attempt to reconnect. This means that if a peer is restarted for maintenance, the jDiameter stack will mark it as DOWN and will never attempt to reconnect to it.
The text was updated successfully, but these errors were encountered: