Skip to end of metadata
Go to start of metadata

Before diving into the DIDs configuration process, let's say you have a DID operator (Voxbone on a chart below) and a client - holder of a DID number (Client A). The Client A receives a call from someone (Client B). In this case, a calling party (Client B + Voxbone) will be originating a call, and the called party (Client A) will be terminating it.

On a chart below, you can see how this call will look like:

Chart: Basic DID call flow

Now let's move on to the DIDs scheme realization in your system.

Prior to creating the DIDs in your system, make sure you have at least two active clients - an originator (Voxbone) and a terminator (Client A).

Helpful Tip

In your clients settings, to indicate the type of your clients, create each one of them an account with the respective origination or termination settings enabled.

Moving to the process of creating and assigning DID numbers, it can be divided into several steps:

  1. Go to the Retail > DID Management > Operators List tab.
    1. Create one or more operators (DID providers). For this, click the New Operator button and proceed with filling in the form.

      Screenshot: Adding a new DID operator

  2. Open the DID Management section.
    1.  Add one or more DID numbers with or without tags. When adding, set the In Stock status to be able to assign DIDs further on. 
      Note: You can also use the Import DIDs button to add new DIDs. 

      Screenshot: Adding new DIDs

  3. Go to the Retail > Packages section. 
    1. Create a new package that will include allowed DIDs quantity and tags specified in DIDs settings (if applicable) in the DID Limits section.

      Screenshot: Creating a new DID package

  4. Assign a respective package to Client A that will hold a DID in the Client Packages section using the Assign Package button.

    Screenshot: Adding a Package to a Client


  5. Open the Clients tab.

    1. Click on a client you want to assign a DID to, and open their settings. 
    2. Go to the DIDs tab, and add one or more DID numbers using the Add DID button. 
      Note: DIDs could be only assigned to accounts.

      Screenshot: Assigning a DID number

  6. In the Routing Plans section, add a new routing plan with the DID type rule and the Full DID Code

    Screenshot: Adding a new routing rule

    Note

    Starting from JeraSoft Billing version 3.20.0, all you need to do is set the Type of the rule to be DID. The system will do everything else automatically.

  7. Add this routing plan to Voxbone (who is the operator of DID numbers) in the clients' settings.
  8. In the Rates Tables section, create the respective rate tables for both Voxbone and Client A. If you wish to pay Voxbone for the incoming calls, the origination rate table will hold negative rates; if you wish to charge Voxbone for the incoming calls, the origination rate table will hold positive rates; if you wish to charge nothing from Voxbone for the incoming calls, the origination rate table will hold free (zero) rates for the DID destination. Whereas the termination rate table will be with the negative rates so that Client A will pay you for the incoming calls. 
              Note: the termination rate table should have a full DID number in the Code field for this scheme to operate correctly. 
  9. Run the DR manager in the Task Scheduler section (or remotely, using Terminal) to apply all the changes.
  10. Then, add both rate tables to the respective clients in the system using their clients' settings.

If you configured these steps right, in the Routing Analysis section of your billing system, you will be able to simulate a call between the parties to ensure effective assigning of a DID number.

Screenshot: Routing Analysis

Helpful Tip

Please note that this functionality is very switch dependent, and additional development or testing may be required. Contact JeraSoft Support team for help, if you have any doubts or questions.

While a call flow with Client A as a terminating client is configured a little complicated, when originating calls, the system sees it as any other regular orig client. Thus, the call flow to the term Vendor will look like this:

Chart: Orig DID call flow