Recurrent Cost Control Balance
The Recurrent Cost Control Balance feature in the OCS.io is designed to monitor and control expenses related to specific types of usage, such as calls to off-net destinations. It allows service providers to set up and manage balances dedicated to monitoring the expenditure of money for these types of usage.
When setting up a Recurrent Balance, service providers can define the validity period, specifying how long the allocated free units remain active and available for usage. They can also configure whether unconsumed units are rolled over to the next period and, if so, for how long. This allows customers to carry forward unused units and maximize their usage over an extended period.
In cases where rollover units are available, service providers can set the priority of consumption for rolled-over units. For example, they can prioritize the usage of newly allocated free units before utilizing any carried-forward units, ensuring that customers fully utilize the most recent allocations first.
The system configures up to three independent notifications based on predefined threshold levels to keep customers informed about their spending. These thresholds can be set at various utilization percentages, such as 0%, 80%, and 100%. When the configured thresholds are reached, the system triggers notifications, providing customers with timely information about their expenditures and allowing them to manage their usage accordingly.
In addition to notifications, service providers can configure the behavior when the balance is exhausted for a certain type of usage. They have the option to reject further usage of that type once the balance reaches zero. This feature ensures that customers do not exceed their allocated budget or go beyond the predefined limits.
Configuration in the GUI
This section describes how to configure Recurrent Cost Control Balance in the GUI.

Item | Description | ||
---|---|---|---|
Create Balance At |
Chose when recurrence occurs:
|
||
Every X (Recurrence Period) |
Enter the length of the Recurrence Period. |
||
Execute immediately |
If checked, Balance is applied immediately. If not checked, Balance is applied from the next Recurrence Period. |
||
Pro-Rate when Activated |
If checked, Balance is Pro-Rated. This is applicable when the state becomes Active for the first time. |
||
Pro-Rate when Not Charged |
If checked, Balance is Pro-Rated. This is applicable only for the Suspended state when the appropriate State Reason is flagged as Charged. |
||
Pro-Rate Mode |
Choose how Pro-Rate functionality behaves:
|
||
Recurrence Cycles |
Enter the number of Recurrence cycles for which Balance is applied. |
||
Granted Balance |
Enter Balance which will be granted. |
||
Reject when 100% Threshold reached |
If checked, charging of event will be rejected when 100% threshold is reached.
|
||
First Usage |
If checked, the First usage Notification will be triggered. |
||
On Recurrence |
If checked, the On Recurrence Notification will be triggered. |
||
Threshold #1 (%) |
If a value is provided, the Threshold #1 Notification will be triggered when the defined threshold is reached. |
||
Threshold #2 (%) |
If a value is provided, the Threshold #2 Notification will be triggered when the defined threshold is reached. |
||
Threshold #3 (%) |
If a value is provided, the Threshold #3 Notification will be triggered when the defined threshold is reached. |
||
Include sub-classes |
If checked, subordinate Charging Classes will be included in the evaluation of Balance application. |
||
List of Charging Classes |
Check all Charging Classes for which Balance will be applied. |