Destination Blocking: Stop Expensive International Calls | NetViaVoice
🛡️ Toll Fraud Prevention · Call Cost Control · 2026

Destination Blocking:
Expensive Blocked International Calls

How to configure destination blocking on your SIP trunk and PBX system to prevent unauthorized international calls, eliminate toll fraud, and take full control of your telecom costs.

By NetViaVoice Security Team  ·  Updated 2026  ·  ⏱ 10 min read

📋 Article Summary

Unexpected international call charges are one of the most damaging — and most preventable — telecom surprises a business can face. Whether caused by employee misuse, misconfigured systems, or sophisticated toll fraud attacks, uncontrolled international calling can cost businesses thousands of dollars overnight. This guide covers every layer of destination blocking: what it is, which destinations are highest risk, how to implement blocking in Asterisk, FreePBX, 3CX, and at the SIP trunk provider level, how to create whitelist-based calling policies, and how to build a complete call cost control framework that protects your business 24/7.

🚫 What Is Destination Blocking and Why Does It Matter?

Destination blocking is a configuration-level rule applied to your VoIP phone system, PBX, or SIP trunk that prevents calls from being placed to specific phone number prefixes, countries, or number ranges. When a user dials a restricted number, the call is rejected before it ever connects — producing a busy tone or a configurable announcement explaining the restriction.

In the context of business telecommunications, destination blocking is the primary defense against two distinct threats: internal cost creep (employees making expensive personal international calls on company lines) and external toll fraud (hackers compromising your SIP credentials and using your account to make thousands of calls to premium-rate numbers at your expense).

The business case for destination blocking is overwhelming. International calls — particularly to satellite phones, certain Caribbean and Pacific island nations, and premium-rate number ranges — can cost $1.00–$9.00 per minute or more. A single compromised SIP account making calls over a weekend can accumulate bills of $5,000–$50,000 before anyone notices Monday morning. Destination blocking stops this at the source, regardless of how the call was initiated or by whom.

$38BAnnual global cost of telecom fraud according to CFCA
$9.00Per-minute rate to some satellite/premium destinations
72hrsTypical window before toll fraud is detected without monitoring
100%of destination-blocked numbers cannot be dialed regardless of method

Stop Expensive Calls Before They Happen

NetViaVoice configures destination blocking, call caps, and fraud detection on your SIP trunk — protecting your business around the clock.

💸 The Real Cost of Unblocked International Calls

Understanding the financial exposure from unblocked international destinations is essential context for any destination blocking policy. Not all international calls are equally expensive — the variation is dramatic, and the most expensive destinations are often those targeted by toll fraud schemes.

💰 International Call Rate Ranges by Destination Type
US, Canada, UK (low-cost)$0.001–$0.01/min
Western Europe, Australia$0.01–$0.05/min
Africa, Middle East (mobile)$0.05–$0.25/min
Pacific Islands, Caribbean (certain)$0.25–$2.00/min
Satellite phones (Iridium, Inmarsat)$3.00–$9.00/min
Premium-rate numbers (IRSF targets)$1.00–$9.00/min
* Rates are indicative. Actual rates vary by carrier and change frequently. IRSF = International Revenue Share Fraud.
🔓

Compromised SIP Credentials

Attacker brute-forces weak SIP password. Dials premium-rate numbers all weekend undetected.

$8,000–$50,000 loss
👤

Employee Personal Calls

Staff member calls family in high-rate country. Billed to company without awareness.

$200–$2,000/month
🤖

Misconfigured IVR

IVR allows callers to dial out internationally through an unguarded dialthrough vulnerability.

$1,000–$20,000 loss
🚨
Toll Fraud Happens Fast IRSF (International Revenue Share Fraud) attacks are automated. Scripts try thousands of SIP credential combinations per hour. Once in, they immediately call premium-rate numbers in destination countries where fraudsters earn revenue sharing. A successful attack can run up thousands of dollars in charges within 3–4 hours — often overnight or over weekends when no one is watching.

⚠️ Highest-Risk Destinations to Block Immediately

Not every international destination needs to be blocked — but certain prefixes and country codes are so consistently associated with toll fraud and premium-rate exploitation that they should be blocked by default for any US business that doesn't have a specific operational need to call them.

Destination / PrefixCountry / TypeTypical RateFraud RiskAction
+881, +882, +883Satellite phones (Iridium, Inmarsat)$3–$9/minExtremeBlock for all users
+900 (US premium)US Premium Rate Services$1–$5/minExtremeBlock for all users
+1-900US 900 premium numbers$1–$10/minExtremeBlock for all users
+357 99xCyprus premium mobile$1–$3/minExtremeBlock unless Cyprus needed
+676, +677, +678Tonga, Solomon Islands, Vanuatu$0.50–$2/minExtremeBlock for all users
+1-268, +1-473, +1-767Caribbean NANP (Antigua, Grenada)$0.25–$1/minHighBlock unless Caribbean ops
+232, +234, +255Sierra Leone, Nigeria, Tanzania$0.10–$0.50/minHighBlock unless Africa ops needed
+0900 (international premium)Various premium service codes$1–$5/minHighBlock globally
+86 (China)China mainland$0.02–$0.10/minMediumBlock unless China ops
+7 (Russia)Russia$0.05–$0.20/minMediumBlock unless Russia needed

🔧 6 Methods to Block International Calls

📋

Dialplan Prefix Blocking

Block calls at the PBX dialplan level by rejecting any dialed number matching a specific prefix pattern. Most flexible and granular method — works in Asterisk, FreePBX, and most IP-PBX platforms.

🌍

Country Code Blocking

Block all calls to specific country codes (e.g., deny all calls starting with +234 for Nigeria). Maintained as a list in your PBX or SIP trunk portal — easy to manage and update.

👤

Per-User / Extension Policies

Set different calling permissions per extension. Reception desk: domestic only. Sales team: North America + Europe. CEO: unrestricted. Granular control without blanket blocking.

💰

Call Spend Caps

Set maximum daily or monthly spend limits per extension or account. When the cap is reached, outbound calls are blocked automatically until reset. Complements destination blocking.

⏰

Time-of-Day Blocking

Block all international calls outside business hours (evenings, weekends). Since most fraud happens when no one is monitoring, after-hours blocking eliminates a major attack window.

✅

Whitelist-Only Mode

Block everything by default — only allow calling to explicitly approved country codes or number ranges. Zero-trust calling policy — the most secure approach for high-risk businesses.

⚙️ Destination Blocking in Asterisk & FreePBX

In Asterisk, destination blocking is implemented in the dialplan — in extensions.conf — by matching called number patterns and sending blocked calls to a Hangup() or Busy() application before they reach the outbound trunk context. Here's how to implement it:

// extensions.conf — International Destination Blocking
; ─── Context: outbound-restrictions ─────────────────────────
[outbound-restrictions]

; BLOCK: Satellite phones (+881, +882, +883)
exten=>_011881.,1,Playback(this-call-cannot-completed)
same=>n,Hangup(21)
exten=>_011882.,1,Playback(this-call-cannot-completed)
same=>n,Hangup(21)

; BLOCK: US 900 premium numbers
exten=>_1900.,1,Playback(blocked-number)
same=>n,Hangup(21)
exten=>_900.,1,Playback(blocked-number)
same=>n,Hangup(21)

; BLOCK: Specific high-fraud countries (Nigeria +234, etc.)
exten=>_011234.,1,Playback(call-not-permitted)
same=>n,Hangup(21)
exten=>_011676.,1,Playback(call-not-permitted)
same=>n,Hangup(21)

; BLOCK: ALL international (everything starting with 011)
; Use this for maximum protection — allow only domestic
exten=>_011.,1,NoOp(International call blocked: ${EXTEN})
same=>n,Playback(international-calls-not-permitted)
same=>n,Hangup(21)

; ALLOW: Everything else (domestic US/Canada)
include=>outbound-allowed
    

FreePBX GUI Method — Outbound Route Restrictions

📍 FreePBX Destination Blocking Navigation

  • Connectivity → Outbound Routes → [Route Name] → Dial Patterns tab: Add patterns that should be BLOCKED and point them to a Termination/Reject destination instead of a trunk
  • Admin → User Management → User Groups → Calling Permissions: Restrict international calling per user group — accounts, reception, sales, executives
  • Admin → Call Barring: FreePBX Pro feature for easy country-level blocking via checkbox interface
  • Applications → Blacklist: Add specific international numbers that should never be dialed — works on both inbound and outbound
  • For time-based blocking: Admin → Time Conditions — create "After Hours" condition that routes outbound international to a blocked context

🖥️ Blocking in 3CX and Cloud PBX Systems

PlatformBlocking Feature LocationBlocking CapabilityGranularity
3CX PBXAdmin Console → Users → Call PermissionsInternational on/off per extension group; country-level via outbound rulesHigh
3CX (Outbound Rules)Admin → Outbound Rules → Prefix filterBlock by dialed prefix — e.g., block all 011 callsHigh
Hosted PBX (generic)Admin Portal → Call Controls → Outbound RestrictionsCountry toggle or prefix deny listMedium
Microsoft Teams (Direct Routing)Teams Admin Center → Voice → Calling PoliciesPer-user calling policy; restrict to domestic onlyHigh
Grandstream UCMPBX → Outbound Routes → Outbound BlacklistPrefix-based blocking with scheduling supportMedium
Cisco CUCMCall Routing → Route Pattern → Block patternPattern-based blocking per partition and CSSVery High

🌐 SIP Trunk Provider-Level Blocking

The most robust destination blocking strategy includes controls at the SIP trunk provider level — not just at the PBX. Provider-level blocking is enforced on our infrastructure before calls even leave the network, meaning it cannot be bypassed by dialplan errors, misconfigured call forwarding, or compromised PBX credentials.

🛡️ What NetViaVoice Provides at the Provider Level

  • Country-level destination blocking: We block entire country codes from your account — calls to blocked countries never traverse our network
  • Prefix-level blocking: Block specific prefixes (e.g., all +881 satellite calls) across your entire SIP trunk account
  • Real-time spend monitoring: Set daily and monthly spending thresholds — we alert you and optionally auto-block when limits are approached
  • After-hours international block: Automatically block all international calling outside your configured business hours
  • IRSF protection list: We maintain an actively updated blacklist of known IRSF (International Revenue Share Fraud) number ranges — blocked automatically
  • Velocity limits: Block accounts that make more than a set number of international calls per hour — stops automated fraud scripts
  • Instant block on demand: Call or portal-request to block any destination immediately — takes effect in under 60 seconds
✅
Defense in Depth: Layer Your Blocking The most secure approach is blocking at BOTH the PBX level AND the SIP trunk provider level. Even if an attacker bypasses your PBX (e.g., by exploiting a misconfigured call forwarding rule), provider-level blocking on your NetViaVoice SIP trunk prevents the call from completing. Two layers of protection are always better than one.

✅ Whitelist Strategy: Allow Only What You Need

The most secure and recommendable approach for businesses that don't need broad international calling is a whitelist-based policy — block all international by default, then specifically enable only the country codes your business actually calls. This "deny by default, allow by exception" approach eliminates the entire category of unexpected international charges.

Business TypeRecommended DefaultWhitelist To EnableBlock Everything Else
Local retail / service businessDomestic US onlyNothing — block all internationalAll international
US + Canada operationsNANP only+1 prefix (includes Canada)All non-NANP
US + UK / Europe clientsDomestic + approved countries+44, +33, +49, +31 etc.All other countries
Real estate (see our SIP for Real Estate guide)Domestic + client countriesCountries where international buyers originateAll other high-risk
Contact center (outbound)Campaign-specific countriesOnly countries in active campaign listAll non-campaign countries
Global enterpriseAll enabled with monitoringAll countries (with per-user policies)High-risk premium numbers only
// Asterisk — Whitelist Approach (Block All International, Allow Specific)
; Priority: Most specific patterns first, general block last

[outbound-international]

; ALLOW: UK (+44)
exten=>_01144.,1,Dial(SIP/trunk/${EXTEN})
exten=>_+44.,1,Dial(SIP/trunk/${EXTEN})

; ALLOW: Germany (+49)
exten=>_01149.,1,Dial(SIP/trunk/${EXTEN})

; ALLOW: Canada (already in NANP +1)
; No special rule needed — handled in domestic context

; BLOCK: Everything else international (catch-all)
exten=>_011.,1,Playback(international-not-authorized)
same=>n,Hangup(21)

exten=>_+.,1,Playback(international-not-authorized)
same=>n,Hangup(21)
    

📊 Real-Time Monitoring & Auto-Block Alerts

Destination blocking is a static defense — it prevents calls to known high-risk destinations. But sophisticated fraud attacks evolve, and new premium-rate destinations are constantly being exploited. Real-time monitoring adds a dynamic layer that catches unusual calling patterns before significant charges accumulate.

📡 Monitoring Controls That Complement Destination Blocking

  • Call volume velocity alerts: Alert (and optionally auto-block) when more than X outbound calls are placed per hour — abnormal for most businesses
  • Spend threshold alerts: Email or SMS alert when daily outbound spending exceeds a set amount (e.g., $50/day for a typical SMB)
  • After-hours call alerts: Instant notification any time an outbound call is placed outside business hours
  • New destination alerts: Flag when a call is placed to a country code your account has never called before
  • Failed authentication alerts: Monitor SIP registration failures — high failure rates indicate a brute-force attack in progress
  • Call duration anomaly: Flag calls with abnormally long duration to unusual destinations — a hallmark of IRSF fraud
  • Auto-suspend: Automatically suspend outbound calling and notify admin if fraud threshold is crossed — stops damage in minutes not hours

✅ Complete Destination Blocking Checklist

  • All satellite phone prefixes blocked (+881, +882, +883) at PBX and provider level
  • All premium-rate number ranges blocked (+900, +0900, country-specific premium prefixes)
  • High-fraud country codes blocked by default (review list with your provider)
  • Caribbean NANP numbers assessed and restricted if not operationally needed
  • Whitelist strategy implemented — only explicitly approved countries allowed
  • Per-extension calling permissions configured (reception: domestic only; management: approved international)
  • After-hours international blocking enabled — no international calls outside business hours
  • Daily spending cap set at SIP trunk provider level with auto-suspend
  • Real-time spend alert configured — email/SMS when threshold reached
  • Failed SIP registration alert active — notifies on brute-force attempts
  • Velocity limit configured — block account exceeding X calls/hour
  • SIP credentials using strong password (16+ chars, mixed case, symbols, numbers)
  • IP whitelist on SIP trunk — only your office IP can register and make calls
  • Provider-level IRSF protection list active on your SIP trunk account
  • Test all blocking rules — verify blocked destinations return busy/announcement
  • Documented blocking policy reviewed and approved by management
  • Staff informed of calling policy — employees understand which destinations are restricted

Lock Down Your SIP Trunk — Block Expensive Calls Now

NetViaVoice configures destination blocking, fraud monitoring, and call caps for your SIP account — protecting your business from unexpected charges and toll fraud attacks.

Available Mon–Sat  ·  US: +1 201 979 3825  ·  Int'l: +92 333 5908806
❓ Frequently Asked Questions
1 How do I block all international calls on my VoIP system?
Blocking all international calls requires changes at both the PBX dialplan level and ideally at your SIP trunk provider level. In Asterisk/FreePBX, add a dialplan rule that matches any number beginning with 011 (the international dialing prefix from the US) and routes it to Hangup(21) with a "not permitted" announcement. In FreePBX GUI, go to Connectivity → Outbound Routes and either delete the international route entirely or restrict it to specific extensions. In 3CX, set call permissions to "Domestic Only" for all user groups under Admin → User Management. Additionally, contact your SIP trunk provider (NetViaVoice: +1 201 979 3825) to apply provider-level blocking as a second layer of protection. This dual-layer approach ensures international calls cannot be placed even if your PBX configuration has a gap.
2 What is IRSF toll fraud and which destinations does it typically target?
IRSF (International Revenue Share Fraud) is a scheme where fraudsters compromise a VoIP account (typically through stolen SIP credentials), then place high volumes of calls to premium-rate numbers in destinations where they earn a revenue share from the receiving carrier. Fraudsters typically target satellite phone numbers (+881, +882, +883), certain Caribbean island numbers (+1-268, +1-473, +1-649), Pacific island nations (Tonga +676, Vanuatu +678, Solomon Islands +677), and premium-rate services in Eastern Europe and parts of Africa. These attacks are automated and can generate thousands of dollars in charges within hours. Destination blocking of these high-risk prefixes, combined with provider-level IRSF protection and strong SIP credential policies, is the primary defense. See our related articles on VoIP security configuration for complementary protection measures.
3 Can I block international calls only outside business hours?
Yes — time-based destination blocking is a highly effective fraud prevention strategy because most toll fraud attacks occur overnight and on weekends when no one is monitoring the phone system. In Asterisk/FreePBX, this is implemented using Time Conditions: create a time group defining your business hours, then use that time group in your outbound route — international calls outside the time group route to a blocked/hangup context rather than the trunk. In 3CX, time-based rules can be applied through the Advanced Call Flow settings. At the SIP trunk provider level, NetViaVoice can apply after-hours international blocking directly on your account. The combination of 24/7 domestic calling with after-hours international blocking is an excellent balance between security and operational flexibility.
4 Will destination blocking affect our legitimate international business calls?
Only if you block destinations your business actually calls — which is exactly why a whitelist strategy is preferable to a generic "block all international" approach. The recommended process is: (1) Pull a report of all international destinations your business has called in the last 6–12 months. (2) Identify which of these are legitimate business needs. (3) Create a whitelist of approved country codes. (4) Block everything else. This ensures legitimate calls to your actual business partners and clients are unaffected while eliminating exposure to high-risk destinations you've never needed. NetViaVoice can pull a destination usage report from your SIP trunk account to inform this analysis. For businesses needing specific DID numbers in multiple countries, see our DID number ordering guide — inbound DIDs don't require outbound calling to those countries.
5 What's the difference between destination blocking and call routing restrictions?
Destination blocking is a security and cost control feature that prevents specific numbers from being dialed at all — regardless of routing configuration. Call routing restrictions (covered in our routing guide) determine which trunk or path an allowed call uses. Think of it as: destination blocking answers "can this call be made at all?", while call routing answers "if this call is allowed, which way does it go?" They are complementary controls — blocking prevents unwanted calls from ever reaching the routing engine, while routing optimizes legitimate calls for cost and quality. Both should be configured for a comprehensive telecom cost control strategy. Destination blocking is implemented in the dialplan before any routing decisions; routing rules only apply to calls that pass the blocking filter.