Skip to main content

How to use origin-based rates (OBR)

This article covers the full OBR workflow: setting up Origin Decks, importing OBR rate files, day-to-day rate management, and the call flow rules that govern how OBR rates are applied.

Video walkthrough

A step-by-step tutorial of the full OBR workflow is available on the JeraSoft YouTube channel.

Origins and Origin Decks

What is an Origin Deck?

An Origin Deck is a collection of Origins. Each Origin holds one or more number prefixes (codes) that identify where a call is coming from. An Origin Deck is assigned to a Rate Table to enable origin-based rate matching for that table.

Origin Decks are located under Configuration → Origin Decks.

origin decks location

note

The same prefix (code) can appear in multiple Origins simultaneously — this is intentional and supported by the system.

For example, code 49 may be included into origins "AUT - GRPA", "BEL - EEA", "CYP - EEA" and so on, where each origin is used depending on the destination.

Linking an Origin Deck to a Rate Table

  1. Go to Configuration → Origin Decks and create your needed deck. You can populate it manually or through the rates import process.
  2. Once your Origin Deck is ready, assign it to a Rate Table. The system will now apply origin-based rate matching for all calls processed using this rate table.

Importing OBR rate files

The import process for Origin Decks works the same way as for Code Decks, using the Update Deck option in Advanced Import Settings.

Supported file formats

Origin data can be present in your rate file in two ways:

  • InlineOrigins are included as an additional column in the main rates sheet, alongside destinations and prices.
  • Separate sheetOrigins are placed on a dedicated sheet within the same file.

Both formats are handled identically during import.

Import steps

  1. Go to Rates → Rate Tables and open the target Rate Table.
  2. Click the import icon.
  3. Select and upload your prepared rate file.
  4. Map the required fields on the import screen.
  5. Open Advanced Import Settings and enable the Update Deck option to import origins.
  6. Complete the import.
tip

After import, filter the Rate Table rates list by Origin Name to verify that all OBR rates were imported correctly before going live.

For a demo upload, please check out the video tutorial above.

Day-to-Day OBR management

All standard rate management tasks in the system support Rates with defined Origins:

  1. Assigning an Origin Deck

    Assign an Origin Deck to a Rate Table to enable origin-based rate matching for that table (see Setting Up OBR in Your Rate Table above).

  2. Adding rates manually

    When adding a rate manually inside a Rate Table, you will see an Origin field. Select an Origin from the assigned Origin Deck to create an origin-specific rate for that destination.

  3. Filtering by Origin

    In the rates list, use the Origin Name filter to quickly view or verify rates for a specific origin.

  4. Exporting rates with OBR data

    When exporting a Rate Table, you can include separate sheets for OBR rates and Origins in the export file. This is useful when sharing rate files with partners.

  5. Notifying customers about OBR changes

    The Rates Notification tab in Reseller settings supports adding separate OBR and Origins sheets to rate notification emails. Configure this in Management → Resellers → Rates Notifications.

  6. Reporting on OBR traffic

    The following reports support filtering and grouping by Origin Name: Summary Report, Orig-Term Report, and xDRs List Report.

Testing OBR with rates simulation

Use the Simulate tab inside a Rate Table to verify that your origin-based rates are matching correctly before going live.

  1. Go to Rates → Rate Tables and open the target Rate Table.
  2. Click the Simulate tab.
  3. Set the Src Party ID field to a source number that matches one of your defined Origins.
  4. Run the simulation. If a matching OBR rate is found, it will be shown in the results. If no OBR rate matches, the system falls back to regular rates without a defined Origin.
tip

Testing with different source numbers — including numbers that match multiple Origins — is a good way to confirm your prefix coverage before enabling OBR in production.