Comment #12 on issue 2504 by brainslog: JDiameter: change disconnect-cause
http://code.google.com/p/mobicents/issues/detail?id=2504
Attaching proposed patch, with Stack and MUX changes.
RFC3588-bis clarifies why REBOOTING should be used. With both BUSY and
DO_NOT_WANT_TO_TALK_TO_YOU, receiver of DPR with above result code SHOULD
NOT attempt reconnection.
REBOOTING 0
A scheduled reboot is imminent. Receiver of 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.
Receiver of 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. Receiver of DPR
with above result code SHOULD NOT attempt reconnection.
Attachments:
issue-2504.patch 17.3 KB
