RE: : RE: AAA Transport Profile and Application Failure
"STURA Marco Consultant" <[email protected]>
| Newsgroups | gmane.ietf.aaa |
|---|---|
| Message-ID | <[email protected]> |
Rakesh Mehta wrote >As per section 6.1 of RFC 3588(as mentioned in this mail), even diameter stack is working in server mode; it can create DIAMETER_UNABLE_TO_DELIVER >message with E bit set and send to proxy if local application is not available to process the message. >I believe this should be true for client side also, because the same scenario can occur for client side. can any person verify for me please??? I don't think this is the case. A Diameter client is not generating responses for requests it generated, clients just wait for answers. However, your case should be true for server initiated requests (e.g. RAR). Regards Marco