DiaPeerDef defines how to select the peer
to use when sending SWx requests to HSS. The HSS may be a directly
connected peer, or reachable with Diameter Routing Agent or some other
type of agent that routes the messages towards the HSS.
DiaPeerDef parameter value can be a configuration
file Identifier value or Diameter Auth-Application-Id
or Vendor-Specific-Application-Id/Auth-Application-Id that the peer has
advertised.
Multiple instances of DiaPeerDef
are allowed. The first entry is the primary peer to use. Entries will be
tried in the order they appear in the configuration file.
Starting with
Radiator 4.24, the recommended configuration is to define
HSSRealm and leave
DiaPeerDef
parameters undefined. This allows Radiator to use Diameter routing to
resolve the peer to send SWx requests to.
# We peer directly with HSS
<DiaPeerDef ...>
Identifier diapeer-hss
</DiaPeerDef>
# The configuration file Identifier to locate DiaPeerDef to use with HSS requests
DiaPeerDef DiaPeerDef-Identifier=diapeer-hss
#DiaPeerDef DiaPeerDef-Identifier=diapeer-hss-secondary
# An alternative is to use a peer that has advertised SWx
#DiaPeerDef Peer-Auth-Application-Id=3GPP:3GPP SWx
