The proxyrl.ini file supports a feature called smart static accounting, which lets you specify that the accounting packets for a proxy or directed realm are forwarded to a list of one or more proxy realms. These groups of realms can also be used for static accounting configured in proxy.ini.
Parallel proxy accounting can be used to forward accounting packets to multiple target realms simultaneously. To enable parallel proxy accounting, you must set the Block parameter in the RealmName.pro file to 0 for all the target realms. The arguments on the right Primary, Wait, and NoWait for the realms decide whether SBR Carrier will send Accounting-Response if forwarding to one or more target realms fails.
The proxyrl.ini file consists of a number of sections that you name. Each section name is referenced in the StaticAcctRealms parameter in the [Acct] section of a .pro or .dir file. Following the section name, you can list a number of proxy realm names, in the following format:
[smartAcct1] realm1=Primary realm2=Wait realm3=NoWait
Primary—Response from the realm is required before sending an Accounting-Response to the NAD. If there is a timeout, no Accounting-Response will be sent.
To discard the accounting request if one or more target realms marked as “Primary” fail to respond, you must set the SuppressResponseIfStaticAcctFails parameter to yes in the [Configuration] section of the proxy.ini file.
Wait—Response or timeout from the realm is required by SBR Carrier before sending an Accounting-Response to the NAD.
NoWait—Neither response from the realm nor timeout is required by SBR Carrier before sending an Accounting-Response to the NAD. The default value is NoWait.
Parallel proxy is not supported for directed realms (defined in .dir files).
To avoid an infinite loop, the list of static accounting servers must not include realms that use the list. If you include a realm in a list of static accounting servers and specified the same realm in proxy.ini as doing static accounting, the realm receives duplicate accounting packets.
When you configure the .pro file, you must ensure at least one system is referenced in the TargetsSection.