This section provides real-world examples of how to use Number Lists to manage inbound call filtering. You’ll learn how to add numbers and set rules to allow or block calls based on specific criteria.
With Number Lists, you can:
Block unwanted calls from specific prefixes or numbers.
Allow calls from specific prefixes or numbers, while blocking all other calls.
Load Balance your traffic based on the incoming CLI.
Choose one of the following examples:
1. Block Calls from a Specific Prefix
Learn how to create a number list, which blocks calls from a specific prefix.
After setting up your Number List, make sure to assign it to an Inbound SIP Trunk so the call filtering rules take effect. For more details, see the Assign a Number List to a SIP Trunk guide.
Scenario: A global service provider needs to route incoming calls based on the caller’s country code (CLI prefix), while using a single DID number.
Solution: To manage this, the provider assigns specific number lists to trunks within a trunk group. The system uses the CLI prefix to match the call to the correct number list and selects the appropriate trunk for routing.
For example:
Calls from the United States (prefix 1) are routed to a US-based trunk.
Calls from the United Kingdom (prefix 44) are routed to a UK-based trunk.
This setup enables efficient load balancing and region-specific routing while maintaining a single DID.
Calls with prefix 1 (US) are routed to US SIP Trunk.
Calls with prefix 44 (UK) are routed to UK SIP Trunk.
All other calls are rejected by default.
This setup allows a single DID number to intelligently route incoming traffic to country-specific trunks, improving routing efficiency and regional control.
Tip
Scale the trunk group to include as many trunks and number lists as needed to achieve traffic load balancing in expected countries or regions.
Learn how to create, configure, and manage Number Lists to filter inbound calls by allowing or rejecting specific numbers or prefixes linked to SIP trunks.