| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:dpi:bras_bng:radius_integration:radius_accounting:setup [2024/09/26 15:29] – external edit 127.0.0.1 | en:dpi:bras_bng:radius_integration:radius_accounting:setup [2025/04/29 07:39] (current) – elena.krasnobryzh |
|---|
| {{indexmenu_n>3}} | {{indexmenu_n>3}} |
| |
| Radius Accounting packages are sent by default to 1813 Radius server port. | RADIUS Accounting packages are sent by default to 1813 RADIUS server port. |
| You can specify a different port globally for all the radius servers or specifically for a given radius server: | You can specify a different port globally for all the RADIUS servers or specifically for a given RADIUS server: |
| * ''radius_acct_port'' option defined in the fastpcrf.conf configuration file specifies the default accounting port | * ''radius_acct_port'' option defined in the fastpcrf.conf configuration file specifies the default accounting port |
| * ''acct_port'' option is applied for a given radius server: | * ''acct_port'' option is applied for a given RADIUS server: |
| ''radius_server=secret@192.168.200.1%eth1:1812;acct_port=34567'' | ''radius_server=secret@192.168.200.1%eth1:1812;acct_port=34567'' |
| |
| You can also specify a secret for Radius accounting for each server separately; this can be done using the | You can also specify a secret for RADIUS accounting for each server separately; this can be done using the |
| ''acct_secret'' option of ''radius_server'' parameter: | ''acct_secret'' option of ''radius_server'' parameter: |
| |
| The ''qwerty'' secret will be used for authorization requests in the example above, and ''123456'' will be used for the accounting ones. | The ''qwerty'' secret will be used for authorization requests in the example above, and ''123456'' will be used for the accounting ones. |
| |
| =====The following additional parameters related to the Radius Accounting can be specified in the fastpcrf.conf===== | =====The following additional parameters related to the RADIUS Accounting can be specified in the fastpcrf.conf===== |
| |
| * ''radius_max_acct_connect_count'' – the maximum number of connections used to transfer the accounting data, the default value is 2. Each connection can be used to handle no more than 256 requests simultaneously.\\ This parameter limits the maximum Radius server load. | * ''radius_max_acct_connect_count'' – the maximum number of connections used to transfer the accounting data, the default value is 2. Each connection can be used to handle no more than 256 requests simultaneously.\\ This parameter limits the maximum RADIUS server load. |
| |
| * ''radius_acct_interim_interval'' – the time interval, in seconds, for sending the interim accounting. The default value is 1800 seconds. The minimum allowed value is 60 seconds.\\ It should be noted that the time interval for sending interim statistics can be specified for each user separately using the Acct-Interim-Interval attribute containing within the Access-Accept/Access-Reject response to the Access-Request authorization request. Value 0 means that interim statistics will not be sent. | * ''radius_acct_interim_interval'' – the time interval, in seconds, for sending the interim accounting. The default value is 1800 seconds. The minimum allowed value is 60 seconds.\\ It should be noted that the time interval for sending interim statistics can be specified for each user separately using the Acct-Interim-Interval attribute containing within the Access-Accept/Access-Reject response to the Access-Request authorization request. Value 0 means that interim statistics will not be sent. |
| * 1 - since the Start event.\\ When the ''acct_start_point=0'' is used within the ''acct_check_idle_mode=1'' mode all the "parasite" traffic being accumulated since the last Stop event will fall into new accounting session.\\ When the ''acct_start_point=1'' is used instead all the "parasite" traffic being accumulated since the last Stop event will be ignored.\\ Also, due to the time delays between accounting "activating" and the actual netflow statistics gathering, the outgoing traffic statistics may be slightly distorted (downwards). | * 1 - since the Start event.\\ When the ''acct_start_point=0'' is used within the ''acct_check_idle_mode=1'' mode all the "parasite" traffic being accumulated since the last Stop event will fall into new accounting session.\\ When the ''acct_start_point=1'' is used instead all the "parasite" traffic being accumulated since the last Stop event will be ignored.\\ Also, due to the time delays between accounting "activating" and the actual netflow statistics gathering, the outgoing traffic statistics may be slightly distorted (downwards). |
| |
| * ''acct_auth_sync'' - [SSG 8.1+] authorization and account synchronization. Disabled by default (no synchronization). Some billing systems (e.g. LanBilling) require the current account session to be closed before sending an Access-Request.\\ The ''acct_auth_sync=1'' setting synchronizes the accting and authorization: when an auth-request arrives, the SSG closes the current acct session (sends acct Stop), waits for a response from Radius to acct Stop, and only then sends an Access-Request auth-request with the new acct sessionId. In addition, [SSG 9.2+] when closing an account session by idle timeout PCRF sends a notification to SSG about session closure; in this case SCAT resets the authorization status, which further leads to subscriber reauthorization - sending ''Access-Request''. | * ''acct_auth_sync'' - [SSG 8.1+] authorization and account synchronization. Disabled by default (no synchronization). Some billing systems (e.g. LanBilling) require the current account session to be closed before sending an Access-Request.\\ The ''acct_auth_sync=1'' setting synchronizes the accting and authorization: when an auth-request arrives, the SSG closes the current acct session (sends acct Stop), waits for a response from Radius to acct Stop, and only then sends an Access-Request auth-request with the new acct sessionId. In addition, [SSG 9.2+] when closing an account session by idle timeout PCRF sends a notification to SSG about session closure; in this case SSG resets the authorization status, which further leads to subscriber reauthorization - sending ''Access-Request''. |
| |
| * ''acct_disable_interim_update'' - prohibiting the sending of Interim-Updates. | * ''acct_disable_interim_update'' - prohibiting the sending of Interim-Updates. |
| * ''acct_disable_interim_update=0'' — by default, Interim-Update is sent | * ''acct_disable_interim_update=0'' — by default, Interim-Update is sent |
| * ''acct_disable_interim_update=1'' — do not send an Interim-Update | * ''acct_disable_interim_update=1'' — do not send an Interim-Update |
