The Radiator reference manual describes the details of Radiator configuration file and the statements that you can use in the configuration file to control the behaviour of the Radiator server, radiusd.

Radiator policy and charging support distribution comes with its own goodies directory which has configuration samples for PCRF, PCEF, and other applications. There are also examples for setting up SQL DB schemas and utilities for testing.

In general terms, the configuration file allows you control the following things:

Radiator Diameter configuration requires defining one or more Diameter peers, the required Diameter applications and possible the Diameter server for accepting incoming Diameter connections from the peers. If no Diameter peers are configured, the Diameter applications can not create outgoing connections. Also, at least one Diameter peer definition is required to accept incoming Diameter connections from the peers.

Diameter peers are defined with <DiaPeerDef ...> clauses. Diameter applications that create outgoing connections use the parameters in DiaPeerDef to locate the destination host. The attributes advertised with the CER (Capabilities Exchange Request) messages sent to the peers during the initial capability negotiation phase are also defined in DiaPeerDef clauses.

Radiator can support different Diameter applications, such as Relay, PCRF or OCS (Online Charging System) simultaneously. Some applications, such as PCRF, may require defining additional clauses as described in this manual.

Some Diameter applications , such as the relay application <AuthBy DiaRelay> or online charging system <AuthBy DiaOCS> process messages from peers that have initiated a Diameter connection towards Radiator. To receive incoming connections, you need to define a <Server DIAMETERTelco> clause. This clause uses DiaPeerDef clauses to create a correct answer to the incoming CER from the connecting peers.