DOCSEARCHbyAlgolia
Submit Docs

JeraSoft Billing Documentation

website·Indexed 32 days ago

https://docs.jerasoft.net

User guides and API documentation for JeraSoft Billing, including instructions for rate management, statistics reporting, system configuration, and integrations with external systems. Covers version 3.28 and upcoming releases.

Tokens
439.7K
Snippets
1.1K
Records
3.6K
Agent score
50%

What's inside JeraSoft

  1. Overview of Invoice Templates management

    The Invoice Templates tool allows for the creation of custom invoice templates to streamline the invoicing process. The management interface consists of a table with the following columns:

    • ID: Identification number of the template.
    • Name: The name of the template.
    • Type: The format of the template (.pdf or .xls).
    • Reseller: The list of resellers assigned to the template.
    • Notes: Additional information regarding the template.

  2. Overview of JeraSoft Billing Webhooks

    JeraSoft Billing uses webhooks to notify external systems when important billing events occur, such as the creation or modification of a client or DID assignments. When an event triggers, the system sends an HTTP POST request containing a detailed event-specific payload to a pre-configured URL. These webhooks are executed by the "Provisioning Manager" system service.

  3. Overview of System Notifications package

    The System Notifications package allows developers to access and monitor system alerts and status updates in real time. It is specifically used to track license alerts, overload warnings, and general system status to identify critical events as they occur.

  4. Overview of the Balance Report tool

    The Balance Report tool allows users to analyze funds by displaying a client's full charges and payments history for a selected period. The tool supports exporting report data to .csv, .xls, and .xlsx formats.

  5. Overview of Traffic Processing and Number Translation

    The Traffic Processing section is used to configure and perform number translations by adding or removing rules. The section is divided into two main tabs: 'Traffic Processing' and 'Orig/Term Rules'. Rules are identified by an ID and organized by Stage and Order.

  6. Overview of Call Shops management

    The Call Shops section is used to create and manage call shop networks. Each call shop is treated as a RADIUS-based customer; therefore, RADIUS must be enabled for this section to function correctly. The section provides a centralized list of call shops including their names, balances, and associated rate tables.

  7. Overview of the Provisioning API UI section

    The Provisioning API section allows for the configuration and monitoring of hooks used for real-time integration with 3rd party systems (such as softswitches, gateways, and CRM systems). It triggers pre-defined handlers when specific system events occur.

    To access this section, navigate to: Integration → Provisioning API.

    Handler Column Definitions

    • ID: The handler's unique identification number.
    • Priority: The execution order of the handler.
    • Name: The title of the handler.
    • Event: The specific system event the handler responds to.
    • Handler: The category and location of the handler. Supported types include:
      • HTTP scripts: Called via POST requests (most common).
      • Local server scripts: Called locally on the server (specific use cases).

  8. Overview of JeraSoft Billing Dynamic Routing

    The JeraSoft Billing Routing Module provides dynamic (external) routing capabilities, supporting integration via RADIUS Protocol or SIP Redirect Server depending on the switch manufacturer. Dynamic routing is managed through three core components: Routing Plans, Routing Policies, and Routing Table generation.

  9. Overview of Reports, Queries, and Monitoring package

    The Reports, Queries, and Monitoring package allows developers to manage scheduled monitoring rules based on stored report queries. This system is primarily used for fraud detection, hacking prevention, and detecting routing alterations. Rule execution is managed by the "Reports Monitoring" system service.

  10. Overview of Traffic Processing for number translations

    The Traffic Processing section is used to configure and manage number translations through the creation and removal of rules. It is organized into two primary tabs: 'Traffic Processing' and 'Orig/Term Rules'. Rules are executed based on a specified 'Order' and are categorized by 'Stage' (Initial, After Client, After Rate, or After Routing).

  11. Overview of the Provisioning API UI section

    The Provisioning API section allows for the configuration and monitoring of hooks used for real-time integration with 3rd party systems (such as softswitches, gateways, and CRM systems). It triggers pre-defined handlers when specific system events occur. To access this section, navigate to Integration → Provisioning API.

  12. Overview of Number Portability in JeraSoft Billing

    The Number Portability section manages local databases of number ranges and individual numbers downloaded via the Files Collector. This allows the system to handle Local Number Portability (LNP) and Mobile Number Portability (MNP) during call routing.

    Provider Behaviors:

    • TJA (RN): During call translation, the system verifies the TJA number and changes the Destination Number to '372+RN' Number.
    • Numuri/TJA (Owner): The system verifies the number and applies a dynamic tag (the owner's name) to the call for billing purposes.