how to handle DPR in diameter and when DPR will send? is any condition for sending DPR?
I want to know that: how to send DPR in diameter. Is there any particular condition for sending DPR? In my code I have already done DWR & DWA and CEA & CER. DPR is sent after CER or before CEA.
java tcp sctp diameter-protocol
edited Jan 3 at 13:11
Armali
7,7001138106
asked Jan 3 at 11:06
Kamal KumarKamal Kumar
203
add a comment |
I want to know that: how to send DPR in diameter. Is there any particular condition for sending DPR? In my code I have already done DWR & DWA and CEA & CER. DPR is sent after CER or before CEA.
java tcp sctp diameter-protocol
edited Jan 3 at 13:11
Armali
7,7001138106
asked Jan 3 at 11:06
Kamal KumarKamal Kumar
203
add a comment |
I want to know that: how to send DPR in diameter. Is there any particular condition for sending DPR? In my code I have already done DWR & DWA and CEA & CER. DPR is sent after CER or before CEA.
java tcp sctp diameter-protocol
edited Jan 3 at 13:11
Armali
7,7001138106
asked Jan 3 at 11:06
Kamal KumarKamal Kumar
203
I want to know that: how to send DPR in diameter. Is there any particular condition for sending DPR? In my code I have already done DWR & DWA and CEA & CER. DPR is sent after CER or before CEA.
java tcp sctp diameter-protocol
java tcp sctp diameter-protocol
edited Jan 3 at 13:11
Armali
7,7001138106
asked Jan 3 at 11:06
Kamal KumarKamal Kumar
203
edited Jan 3 at 13:11
Armali
7,7001138106
asked Jan 3 at 11:06
Kamal KumarKamal Kumar
203
edited Jan 3 at 13:11
Armali
7,7001138106
edited Jan 3 at 13:11
Armali
7,7001138106
edited Jan 3 at 13:11
Armali
7,7001138106
7,7001138106
asked Jan 3 at 11:06
Kamal KumarKamal Kumar
203
asked Jan 3 at 11:06
Kamal KumarKamal Kumar
203
asked Jan 3 at 11:06
Kamal KumarKamal Kumar
203
203
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
DPR means a Diameter peer wants to disconnect from a Diameter peer its currently connected to.
Its all on the base RFC. I suggest to read every command you want to implement:
rfc 6733:
5.4. Disconnecting Peer Connections
When a Diameter node disconnects one of its transport connections,
its peer cannot know the reason for the disconnect and will most
likely assume that a connectivity problem occurred or that the peer
has rebooted. In these cases, the peer may periodically attempt to
reconnect, as stated in Section 2.1. In the event that the
disconnect was a result of either a shortage of internal resources or
simply that the node in question has no intentions of forwarding any
Diameter messages to the peer in the foreseeable future, a periodic
connection request would not be welcomed. The Disconnection-Reason
AVP contains the reason the Diameter node issued the Disconnect-Peer-
Request message.
The Disconnect-Peer-Request message is used by a Diameter node to
inform its peer of its intent to disconnect the transport layer and
that the peer shouldn't reconnect unless it has a valid reason to do
so (e.g., message to be forwarded). Upon receipt of the message, the
Disconnect-Peer-Answer message is returned, which SHOULD contain an
error if messages have recently been forwarded, and are likely in
flight, which would otherwise cause a race condition.
The receiver of the Disconnect-Peer-Answer message initiates the
transport disconnect. The sender of the Disconnect-Peer-Answer
message should be able to detect the transport closure and clean up
the connection.
answered Jan 6 at 10:36
kurdtkurdt
283212
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54021084%2fhow-to-handle-dpr-in-diameter-and-when-dpr-will-send-is-any-condition-for-sendi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
DPR means a Diameter peer wants to disconnect from a Diameter peer its currently connected to.
Its all on the base RFC. I suggest to read every command you want to implement:
rfc 6733:
5.4. Disconnecting Peer Connections
When a Diameter node disconnects one of its transport connections,
its peer cannot know the reason for the disconnect and will most
likely assume that a connectivity problem occurred or that the peer
has rebooted. In these cases, the peer may periodically attempt to
reconnect, as stated in Section 2.1. In the event that the
disconnect was a result of either a shortage of internal resources or
simply that the node in question has no intentions of forwarding any
Diameter messages to the peer in the foreseeable future, a periodic
connection request would not be welcomed. The Disconnection-Reason
AVP contains the reason the Diameter node issued the Disconnect-Peer-
Request message.
The Disconnect-Peer-Request message is used by a Diameter node to
inform its peer of its intent to disconnect the transport layer and
that the peer shouldn't reconnect unless it has a valid reason to do
so (e.g., message to be forwarded). Upon receipt of the message, the
Disconnect-Peer-Answer message is returned, which SHOULD contain an
error if messages have recently been forwarded, and are likely in
flight, which would otherwise cause a race condition.
The receiver of the Disconnect-Peer-Answer message initiates the
transport disconnect. The sender of the Disconnect-Peer-Answer
message should be able to detect the transport closure and clean up
the connection.
answered Jan 6 at 10:36
kurdtkurdt
283212
add a comment |
DPR means a Diameter peer wants to disconnect from a Diameter peer its currently connected to.
Its all on the base RFC. I suggest to read every command you want to implement:
rfc 6733:
5.4. Disconnecting Peer Connections
When a Diameter node disconnects one of its transport connections,
its peer cannot know the reason for the disconnect and will most
likely assume that a connectivity problem occurred or that the peer
has rebooted. In these cases, the peer may periodically attempt to
reconnect, as stated in Section 2.1. In the event that the
disconnect was a result of either a shortage of internal resources or
simply that the node in question has no intentions of forwarding any
Diameter messages to the peer in the foreseeable future, a periodic
connection request would not be welcomed. The Disconnection-Reason
AVP contains the reason the Diameter node issued the Disconnect-Peer-
Request message.
The Disconnect-Peer-Request message is used by a Diameter node to
inform its peer of its intent to disconnect the transport layer and
that the peer shouldn't reconnect unless it has a valid reason to do
so (e.g., message to be forwarded). Upon receipt of the message, the
Disconnect-Peer-Answer message is returned, which SHOULD contain an
error if messages have recently been forwarded, and are likely in
flight, which would otherwise cause a race condition.
The receiver of the Disconnect-Peer-Answer message initiates the
transport disconnect. The sender of the Disconnect-Peer-Answer
message should be able to detect the transport closure and clean up
the connection.
answered Jan 6 at 10:36
kurdtkurdt
283212
add a comment |
DPR means a Diameter peer wants to disconnect from a Diameter peer its currently connected to.
Its all on the base RFC. I suggest to read every command you want to implement:
rfc 6733:
5.4. Disconnecting Peer Connections
When a Diameter node disconnects one of its transport connections,
its peer cannot know the reason for the disconnect and will most
likely assume that a connectivity problem occurred or that the peer
has rebooted. In these cases, the peer may periodically attempt to
reconnect, as stated in Section 2.1. In the event that the
disconnect was a result of either a shortage of internal resources or
simply that the node in question has no intentions of forwarding any
Diameter messages to the peer in the foreseeable future, a periodic
connection request would not be welcomed. The Disconnection-Reason
AVP contains the reason the Diameter node issued the Disconnect-Peer-
Request message.
The Disconnect-Peer-Request message is used by a Diameter node to
inform its peer of its intent to disconnect the transport layer and
that the peer shouldn't reconnect unless it has a valid reason to do
so (e.g., message to be forwarded). Upon receipt of the message, the
Disconnect-Peer-Answer message is returned, which SHOULD contain an
error if messages have recently been forwarded, and are likely in
flight, which would otherwise cause a race condition.
The receiver of the Disconnect-Peer-Answer message initiates the
transport disconnect. The sender of the Disconnect-Peer-Answer
message should be able to detect the transport closure and clean up
the connection.
answered Jan 6 at 10:36
kurdtkurdt
283212
DPR means a Diameter peer wants to disconnect from a Diameter peer its currently connected to.
Its all on the base RFC. I suggest to read every command you want to implement:
rfc 6733:
5.4. Disconnecting Peer Connections
When a Diameter node disconnects one of its transport connections,
its peer cannot know the reason for the disconnect and will most
likely assume that a connectivity problem occurred or that the peer
has rebooted. In these cases, the peer may periodically attempt to
reconnect, as stated in Section 2.1. In the event that the
disconnect was a result of either a shortage of internal resources or
simply that the node in question has no intentions of forwarding any
Diameter messages to the peer in the foreseeable future, a periodic
connection request would not be welcomed. The Disconnection-Reason
AVP contains the reason the Diameter node issued the Disconnect-Peer-
Request message.
The Disconnect-Peer-Request message is used by a Diameter node to
inform its peer of its intent to disconnect the transport layer and
that the peer shouldn't reconnect unless it has a valid reason to do
so (e.g., message to be forwarded). Upon receipt of the message, the
Disconnect-Peer-Answer message is returned, which SHOULD contain an
error if messages have recently been forwarded, and are likely in
flight, which would otherwise cause a race condition.
The receiver of the Disconnect-Peer-Answer message initiates the
transport disconnect. The sender of the Disconnect-Peer-Answer
message should be able to detect the transport closure and clean up
the connection.
answered Jan 6 at 10:36
kurdtkurdt
283212
answered Jan 6 at 10:36
kurdtkurdt
283212
answered Jan 6 at 10:36
kurdtkurdt
283212
answered Jan 6 at 10:36
kurdtkurdt
283212
283212
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54021084%2fhow-to-handle-dpr-in-diameter-and-when-dpr-will-send-is-any-condition-for-sendi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
