JeraSoft Documentation Portal
Docs for all releases
This section allows rerating calls, SMS, data. It's useful when some changes were applied to the rates, currencies, client accounts, or you need to correct errors with a Mismatches Report.
Screenshot: xDRs Rerating section
The whole procedure consists of the following 3 steps:
|Information Block||Field Description|
On the Filters menu, select the required parameters for the report. To cancel any filter, click on the delete icon next to the filter.
You can start a quick search by typing filters' names in the field at the top of a drop-down menu with filters.
|Period||Specify the time interval for the report and a timezone. Please note that the Period field is mandatory.|
|Service||Indicate a target type of services from the Services section|
There are the following accessible additional filters:
|Client||Define a client for the report.|
|Code||Define a code of a needed destination.|
|Code Name||Enter a code name of a desired destination.|
Specify a call origin for the report:
Indicate the status of the call for the report:
|Gateway||Define a target gateway.|
|Tag||Specify target tags|
Indicate a respective type:
Choose an appropriate type:
Select the continuance of the call:
This form contains settings of the output data of the report.
Dst Code Deck
Select a respective code deck for the report from the drop-down menu.
2. Then, you will see a respective notification, and you will need to approve the process by clicking the Confirm Rerating button.
Screenshot: xDRs Rerating approval notification
3. Finally, the calls will undergo rerating, and you will need to wait for the system procedure to be completed. You can see the respective number of calls for the rerating on the toolbar at the top of the page.
Screenshot: xDRs in the queue for rerating
You will also receive the following notification: xDRs have been added to queue now. Please wait while the system processes them. Then, you need to run the Calculator in the System Services section.
The xDRs rerating is a time-requiring procedure. It's not recommended to create a rerating query with large chunks of information (for example, rerating 3 million calls at once).