The SR OS may initiate termination of the peering connection because of the following reasons:
peer shutdown
This refers to graceful termination by initiating a Disconnect Peer Request (DPR) message from either side of the connection.
watchdog timeouts
The peer is unresponsive and consequently the TCP connection is forcefully closed.
message authorization failure during the Capability Exchange phase with the peer
There is no support for common application or hostnames mismatch.
failure to verify the following AVPs in incoming Diameter Base messages
CEA: Origin-Host
DWR: Origin-Host, Origin-Realm, Origin-State-Id
DWA: Origin-Host, Origin-Realm, Origin-State-Id
DPR: Origin-Host, Origin-Realm
DPA: Origin-Host, Origin-Realm
These values of these AVPs are checked against:
Origin-Host: peer name configuration
Origin-Realm: learned from CEA
Origin-State-Id: learned the first time seen in either CEA, DWR, DWA