Diameter: How a Diameter message flows from one Diameter node to another Diameter node by using the peer table ?

Question

I know Diameter client can re-transmit the request message until it receives the answer message.
But what about when a Diameter node has sent answer message to the last received request from its peer and that's is not received but its peer. In this case, from Diameter client node transaction is not completed since it did not receive answer message but from other node point of view it has responded with answer and transaction is completed.

Answer 1

Hi Harshita,

From RFC 6733 - Section 2.6 Below fields of Peer Table are required for diameter message flow
1. Host Identity :this field contains the contents of the Origin-Host AVP found in the CER or CEA message.
2. StatusT: This is the state of the peer entry, and it MUST match one of the values(Closed,Wait-Conn-Ack,Wait-I-CEA,Wait-Returns,R-Open,I-Open,Closing).
3. Static or Dynamic:Specifies whether a peer entry was statically configured or dynamically discovered.
4.Expiration Time: Specifies the time at which dynamically discovered peer table entries are to be either refreshed or expired.
5.TLS/TCP and DTLS/SCTP Enabled: Specifies whether TLS/TCP and DTLS/SCTP is to be used when communicating with the peer.

Thanks