Diameter Answer Timeout (ms)

Enter the period of time (in milliseconds) before a non-responded request is handled as an error, i.e. an Error Answer Message is returned. See the section, Special Error Handling, in The Diameter Base Protocol for further information.

Timeout Resolution (ms)

Enter the interval at which the Answer Timeout should be checked.

Enable Debug Events

Select this checkbox to enable debug mode. Useful for testing purposes.

Enable Runtime Validation

Select this checkbox to enable runtime validation of the Diameter messages against the command and AVP definitions in the Diameter Application profile.

The following is validated in incoming and outgoing messages:

• Occurrences and position of AVPs

• The setting of AVP flags i.e. M-bit and P-bit

• The setting of command flags i.e. Proxiable (p-bit) and Error (e-bit)

When runtime validation is selected, incoming messages that fail the validation are rejected by the Diameter Stack agent, and the appropriate result code is applied in an error answer message.

Do Not Create Outgoing Connections

Select this check box checkbox to prevent the agent from actively trying to connect or reconnect if a connection is lost, with peers. When this option is checked, the agent is said to run in passive mode.

Bind On All Interfaces

Select this checkbox to allow the agent to bind on interfaces other than just the Diameter identity. For example, in a Kubernetes solution.

Keystore Path

The path to a keystore file that contains the private key of the Diameter Stack, and any certificates needed to verify peers. This parameter is only applicable if TLS security is used for one or more of the peers in the routing profile. The path is relative to the Execution Context on which the Diameter Stack runs.

Keystore Password

The path to a keystore file that contains the private key of the Diameter Stack, and any certificates needed to verify peers. This parameter is only applicable if TLS security is used for one or more of the peers in the routing profile. The path is relative to the Execution Context on which the Diameter Stack runs.

Security Profile

Click Browse to select a security profile with certificate and configuration to use, if you prefer to use a secure connection. Refer to Security Profile for more information.

Watchdog

Enter the watchdog timer interval TWINIT. For information about TWINIT, see RFC 3539.

Maximum Message Size (B)

Enter the maximum number of bytes allowed in a single Diameter message.

Socket Write Timeout

(ms)

Enter the timeout value for writing to a socket. If the write operation is blocked for longer than the timeout period, the peer will be disconnected. Write blocks may occur if the receiving peer is overloaded.

Connect Timeout (ms)

Enter the timeout value for peer connection attempts. This setting is only applicable to TCP connections.

Connect Interval (ms)

Enter the minimum time interval between connection attempts when routing messages from a workflow and the peer connection is not established. An interval timer is started at the first connection attempt; subsequent connection attempts to the same peer are then suppressed until the timer has expired.

When realm-based routing is used, the connect interval is applied only if all configured peers in the realm are down.

Error Route

When there is an error in an incoming message, the Diameter Stack agent creates a DiameterErrorUDR that can be routed to the workflow. Use Error Route to select the outgoing route for UDRs of this type. You can disable the routing of these UDRs by selecting (None), which is the default value. For information about DiameterErrorUDR, see the section, DiameterErrorUDR, in The Diameter Base Protocol.

Connection Monitoring Route

If you want to send connection-related messages and ConnectionLost UDRs to the workflow, use the Connection Monitoring Route option to select the outgoing route for UDRs of this type. You can disable the routing of these UDRs by selecting (None), which is the default value.

The UDR types that are routed are the following:

• Capabilities_Exchange_Request (Diameter.Base)

• Capabilities_Exchange_Answer (Diameter.Base)

• Device_Watchdog_Request (Diameter.Base)

• Device_Watchdog_Response (Diameter.Base)

• ConnectionLost (Diameter)

For information on the ConnectionLost UDR, see The Diameter Base Protocol.

Use Waiting Messages Limit

When the Diameter Stack agent acts as a client and cannot send a message to a target peer, the message is kept in a queue until it is sent or a timeout occurs. In case of a timeout, a DiameterErrorUDR is routed back to the workflow.

Select this check box to limit the number of messages that can be stored in the message queue, and enter the number of messages that can be queued. When the limit is exceeded, the first message in the queue is removed and handled as if a timeout has occurred. The default value is 500.

Peer Profile Mappings

Click Configure to set specific mappings for peers that you do not want to use the default Diameter Application profile, which is set in the General tab. To configure the mappings, you enter the Peer Identity and the Diameter Application profile that you want the specified peer to use. The peer identity can be a regular expression.

The number of mappings configured is shown on the Configure button.

For each peer that connects, the specific Diameter Application profile used is chosen by first checking each Peer Profile Mapping as ordered in the Peer Profile Mappings list. If the peer identity matches the configured name or pattern, this profile is chosen. If no peer profile mapping matches, the default Diameter Application profile is used.