📁
Master DNL Class4 Version 5
  • Introduction
  • Support
  • First Time Setup
    • Create Vendor
    • Create Routing
      • Routing Plan
      • Static Route
      • Dynamic Route
    • Create Client
    • Call Simulation
    • Check CDR
    • Check Report
    • Check PCAP
    • Setup ANI Rotation
    • Set Min Call Duration
    • Block Calls by DNC
  • Maintainence
    • Update US LERG in Switch
    • How to manage PCAP cleaning
    • How to manage CDR cleaning
      • Using dnl_backup_tool
      • Using dnl_cloud_tool
  • Troubleshoot
    • Getting "Missing table" error during invoice generation
    • Switch can't process more than 30K ports
    • How many calls are client sending
    • Call Failure
    • Enforce Valid DNIS Length
    • Enforce E164 Format for Vendor Trunk
    • Configure VoIP Switch in UI
    • SIP Switch is Down
    • Validate Auto-Invoice Rule
  • Installation
    • Installation with RPM
Powered by GitBook
On this page

Was this helpful?

  1. First Time Setup
  2. Create Routing

Static Route

PreviousRouting PlanNextDynamic Route

Last updated 4 years ago

Was this helpful?

Introduction

Static Route is how you define actually how vendor trunk is to be selected. Within Static Route, you can order the vendor trunks by:

  • Top Down Routing

  • Round Robin Routing

  • Percentage Routing

Top Down Routing means Class 4 will always select the route from top to bottom of the vendor trunk list. Round Robin means Class 4 will balance traffic sent all vendor trunk evenly. Percentage routing let's you define % of traffic being sent to each vendor trunk.

Here is how you create static routing:

Step 1: Click on Routing > Static Routing

Step 2: View all existing static routing

Step 3: Add new static routing

You can click on "Create New" and then create a new static routing:

If you are terminating US traffic, you should route by LRN number instead.

Step 4: Add new static routing entry

When you click inside the name of the static route, you get to see the list of routing entry:

You can have different set of vendor trunks defined for different DNIS routing code. You can have different routing strategy for different DNIS prefix or you can leave it blank.