Published on iptel.org (http://www.iptel.org)

avp_radius

By greger
Created 2006-12-09 20:16

Standard

avp_radius module allows loading of user's attributes into AVPs from Radius. User's name and domain can be based on From URIi [1], Request URI, or authenticated credentials. The module assumes that Radius returns the AVPs as values of reply attribute SIP-AVP. Its value must be a string of form "name:value"

Juha Heinanen

jh@tutpro.com [2]>

Revision History
Revision $Revision: 1.3 $ $Date: 2005/08/24 22:26:17 $

i [3], Request URI, or authenticated credentials.

The module assumes that Radius returns the AVPs as values of reply attribute SIP-AVP. Its value must be a string of form "name:value" or of form "name#value". In the first case, value is interpreted as a string and in the second case as an int (second case has not been implemented yet).

The module prefixes each attribute name as returned from Radius by string "caller_" or "callee_" depending if caller's or callee's attributes are loaded.

i [4]-Caller-AVPs), but uses the user in the Request URI. This is useful for the case where a call has been forwarded by callee (Request URI) and you need to look up whether callee is allowed to forward the call to ex. PSTNi [5] or if the call should be anonymous (i.e. not show info about who diverted the call).

AVP name returned from Radius is prefixed by string "caller_", if avp_load_radius parameter is "caller" or "digest", and by "callee_", if parameter is "callee".

Example 3. avp_load_radius usage

...
avp_load_radius("callee")
...