Diameter Transport

The transport part of the message contains parameters related to identifying a message and controlling the transmission of a Diameter message. For requests from application serves, these parameters are combined with parameters from the Diameter command to configure the handling and routing of the message.

This part of the message is marked by the <diameter/> tag and contains information related to sending/receiving messages, but are not part of the Diameter command.

These are the parameters for sending a message (bold means mandatory, italic - optional):

• trans_id: Unique identifier per direction used to match requests and answers and identify a certain Diameter transaction. In Diameter -> TCP application direction, this is set by the YATE Diameter level and it must be returned in the answer sent by the TCP application. In the TCP application -> Diameter direction, the TCP application sets it in the request and the Diameter level will return in the answer. The identifier has no required format, must be only a uniquely generated string per Diameter transaction.
• local_node: Identifier of the local node (${realm}/${host}) to use for sending a request from the TCP application. If not present, one must be set in connection. configuration of the listener. The one present in XML will override the configured one.
• timeout: setting the timeout for a request in the TCP application -> Diameter direction. This allows overriding the configured Diameter timeout setting (optional). It can also be set in connection. configuration or in diameter configuration. This is in milliseconds.

Example:

<m>
  ...
  <diameter>
    <timeout>60000</timeout>
    <local_node>example.com/hss.example.com</local_node>
    <trans_id>hss/123456</trans_id>
  </diameter>
  ....
</m>