

If you don't specify a rate for the -c option, BRM silently ignores all dollar charges in the CDR file. BRM cannot rate a charge without a rate name. To rate based on session cost, specify the rate name after the -c option. BRM silently ignores this part of the charge if it cannot be rated. To rate based on session length, specify the rate name after the -s option. The optional parameters -s, -c, -u and -m determine the specific behavior of pin_ipass_loader as follows: The pin_ipass_loader utility provides two possible ways to rate a session: based on session length or dollar charge from iPass. The following example shows a CDR file with a single call. To run pin_ipass_loader, use this command: pin_ipass_loader -f input_file
#Ipass norwood how to
This example shows how to configure the RADIUS configuration file ( BRM_home /apps/radius/config) to support a typical iPass roaming solution: This example shows how to configure the $MODULES section of the RADIUS configuration file ( BRM_home /apps/radius/config) to forward requests to iPass:Įxample RADIUS Configuration File for iPass This example shows how to set the destination of the iPass-enabled RADIUS server in the $CORE section of the RADIUS configuration file (BRM_home /apps/radius/config, where BRM_home is the directory in which BRM components are installed): You must configure mod_proxy to forward the requests to the iPass-enabled RADIUS server. Use the send option to append the Class = " ipass" attribute-value pair in the auth_accept reply to the NAS and check for the appropriate Class attribute value. The mod_proxy module should be the last authentication module in the chain.Īfter the authentication request is passed to the iPass-enabled RADIUS server, the NAS (network access server) sends the corresponding accounting requests to signal the start and end of the session. Setting the Ignore-No-Entry option allows the request to pass on to the next module instead of returning a NAK (not acknowledged). To satisfy this criteria, all authentication modules that precede mod_proxy in the chain must use the Ignore-No-Entry option. The mod_proxy module must be configured to check for this symbol.Īny authentication modules configured in the module chain that precede the BRM authentication module, mod_pin, must not authenticate the user. For iPass roaming requests to be processed:
