This section describes the configuration parameters for
<DiaPeerDef>.
<DiaPeerDef> defines the Diameter peer this
Radiator instance connects to. Both Radiator instance and the Diameter
peer can initiate the connection.
A minimal
Radiator 3GPP AAA Server configuration requires one
<DiaPeerDef> clause for all used Diameter-based
AuthBys. If there is no <ServerDIAMETERTelco>
clause defined, <DiaPeerDef> clauses must have
the Initiator flag set to connect to the Diameter
peers.
A
<ServerDIAMETERTelco> clause
allows accepting incoming Diameter connections. When the
<ServerDIAMETERTelco> is configured, Radiator
acts as a Diameter responser. The settings for the connecting peers are
fetched from the
<DiaPeerDef> clauses.The
clauses are matched against the incoming
CER (Capabilities Exchange Request)
from the peer.
Note
At least one
<DiaPeerDef> clause is always
required.
If the
<ServerDIAMETERTelco>
clause is configured but there are no
<DiaPeerDef> clauses, the incoming
CER messages are rejected by Radiator. A
<DiaPeerDef> is required to form a successful
CEA (Capabilities Exchange Answer) back to the peer.
Note
A
<DiaPeerDef> with an empty parameter list
matches to any Diameter peer. This is useful when defining default
settings for incoming connections from any Diameter peer.
