📁
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. Troubleshoot

Enforce Valid DNIS Length

PreviousCall FailureNextEnforce E164 Format for Vendor Trunk

Last updated 4 years ago

Was this helpful?

In this article, I am going to show you how to block calls that have valid length for the DNIS and ANI.

Here is how a normal basic routing plan looks. It basically just route all calls according to the vendor trunks defined in the dynamic route specified.

However, you can set it so that this rule is applied with the length of ANI and DNIS meets the valid size.

You can do this by clicking "Edit" on this rule:

You can use ANI/DNIS Prefix, Min Length, and Max Length to specify traffic you don't like. For those traffic, you can send them to a different Dynamic or Static Route that either always return 503 or route to a miss call vendors like some of our clients are doing.