RADIUS can be used to allow new handsets to be registered dynamically without individual configuration by using RADIUS authentication to an external RADIUS server. RADIUS is also used to make call routing decisions.
RADIUS accounting can be used to log calls as they start and end to an external RADIUS server.
RADIUS accounting logs each call leg, so a typical call has an incoming and outgoing leg.
The update includes the call duration, which is the time spent ringing for the interim update, and the connected duration in the stop message. The event timestamp sent is the start of the call, even in the stop message.
RADIUS authentication is used for REGISTER and INVITE messages, and any may be used for some others in future.
radius-challenge
settings. Otherwise the FB6000 will send a challenge automatically and only send a RADIUS authentication when the authenticated message is received.For registration the reponse allows the registration or rejects it. If allowed, a called-station-id attribute can be used to define the registered connection as a tel:number
URI for call routing. Without this, the registration is not logged on the FB6000 and it is assumed the RADIUS server will record where to send calls based on the registration.