How it Works

The following table lists the impact of dynamic update to the various Diameter endpoint configurations:

Dynamic Update of Diameter Endpoint Configuration

Configuration

Dynamic Change

Impact on Existing Sessions

Connection attributes:

  • BaseMsg attributes, such as retransmissionTimeout, retransmissions

  • connectionTimeout

  • responseTimeout

  • originStateId

  • Origin attributes, such as Host Address, Host Name, and Realm

  • Peer attributes, such as address, port, and realm

Allowed

Change in connection attributes has the following impact:

  • RPC is deregistered and registered with new values for all peers in the endpoint profile.

  • All the messages initiated on the peer fail when the connection is down.

  • All the requests in transit on the peer are dropped. Server can’t send request messages (RAR) and response messages (CCA) on these connections for existing calls.

DisconnectPeerRequest Properties:

  • drainTime

  • rebootTime

  • doNotTalkTime

  • busyTime

Not allowed

When the DisconnectPeerRequest Properties are updated for a peer, the new values are effective only after the pod restart or after the connection is reset.

Route-entry update or addition

Allowed

An update or addition to route entry has the following impact:

  • Route entries are recreated after change.

  • After a peer is deregistered, all route entries for the peer are deleted.

Diameter-endpoint profile removal

Allowed

The removal of an endpoint profile has the following impact:

  • All the peers of the endpoint profile are deregistered.

  • Existing calls using these peers or routes fail.

  • No new calls are initiated on those peers.