Toll fraud is one of the most expensive ways a phone system can fail. Attackers get into a PBX or SIP account and route calls to costly international or premium-rate numbers, often over a weekend or holiday, and the bill can arrive weeks later. The good news is that most compromises exploit a handful of avoidable mistakes, so a short list of controls goes a long way. This guide explains how attacks happen and gives a hardening checklist you can apply to 3CX, Yeastar, FreePBX and most other systems.

What toll fraud is and who pays

The usual scheme is international revenue share fraud (IRSF): criminals lease high-cost numbers, then pump calls to them through a hacked system and collect a share of the charges. 3CX describes the pattern as calls placed in bulk to international destinations, often overnight or when offices are closed. Stolen SIP credentials are also resold as cheap calling routes.

The UK's National Cyber Security Centre describes these attacks as prolonged, with expensive numbers dialed hundreds or thousands of times, and makes the point every owner should hear: your provider may detect and warn you of fraud, but as the business owner you will be expected to pay the bill.

How attackers get in

Entry pointHow it's abusedMain control
SIP registrationScanners find an open SIP port and guess extension passwordsLong random passwords, IP restrictions, automatic blocking
Admin web interfaceDefault or weak admin password on a console reachable from the internetIP-restricted console, MFA, no default accounts
Desk phonesDefault web passwords; SIP credentials read from the phone or its provisioningChange phone admin passwords, secure provisioning
SIP trunk accountCredentials taken from a config file, backup or the provider portalIP-based trunk authentication, MFA on the provider portal
Voicemail, IVR and forwardingA guessed voicemail PIN or an IVR option that gives a dial tone or forwards to an outside numberNo outbound dialing from IVR or voicemail, limits on external forwarding
Anonymous SIPUnauthenticated calls land somewhere that can dial outDisable anonymous inbound SIP and SIP guests
Unpatched softwareKnown vulnerabilities in the PBX or phone firmwareRegular updates

Fraud isn't the only SIP attack. Registration floods can overload a PBX, scanners can make phones ring with odd caller IDs in the middle of the night, and unencrypted calls can be intercepted on networks you don't control. The same controls reduce all three, and the NCSC also recommends TLS for signaling and SRTP for media.

The hardening checklist

1. Credentials and access

  • Use long, random SIP passwords. 3CX generates random SIP credentials and voicemail PINs for each new extension and warns about weak ones; keep the generated values instead of replacing them with something memorable. Never use the extension number as the password.
  • Protect the admin console with multi-factor authentication and restrict it to office and VPN IP addresses.
  • Change default passwords on phones, gateways and the PBX itself, and give each administrator a personal account.
  • Remove unused extensions and accounts for people who have left. The NCSC recommends auditing accounts regularly for exactly this reason.

2. Network exposure

  • Don't expose SIP to the whole internet. Allow SIP and RTP only from your SIP provider's IP addresses, and ask the provider for IP-based authentication if it offers it. The NCSC advises locking inbound and outbound PBX traffic down to trusted IPs.
  • Connect remote users without open SIP ports: through the vendor's tunnel, an SBC (session border controller) or a VPN. In 3CX, the extension option "Block remote non-tunnel connections" is on by default; leave it on unless a remote desk phone truly needs direct SIP. Setup options are in VoIP for remote teams.
  • Geo-block access from countries where you have no staff or providers, using the PBX's country filter or your firewall's geo-IP rules.
  • Turn off anonymous inbound SIP calls and SIP guests on Asterisk-based systems, as Sangoma's FreePBX security checklist recommends.
  • Put an on-premise PBX on its own VLAN or subnet, separated from office PCs.

Moving SIP off port 5060 cuts down automated scanning noise, but treat it as housekeeping, not protection. Port forwarding and NAT are covered in our guide to one-way audio and dropped calls.

3. Automatic blocking

  • Ban addresses after repeated failed logins. On FreePBX, enable Intrusion Detection (based on fail2ban); 3CX and Yeastar have built-in anti-hacking and auto-defense rules.
  • Join the vendor's shared blocklist where one exists, such as the 3CX Global IP Blacklist or the Yeastar Global Anti-hacking IP Blocklist, which drop traffic from addresses reported by other systems.
  • Allow-list your own offices and providers so a typo from a known site doesn't lock you out.

4. Restrict what can be dialed

  • International dialing off by default. Allow only the countries you call, and only for the people who call them. 3CX allows just your installation country when first installed; Yeastar combines an allowed-country list with a per-extension international permission.
  • Block premium-rate and high-cost prefixes you never need.
  • In the US and Canada, watch the +1 zone. The North American Numbering Plan includes Caribbean countries that are dialed like domestic long distance, so a country filter alone won't catch them. Block those area codes in your outbound rules unless you call them.
  • Write strict outbound rules by prefix, number length and user group, rather than one rule that lets anyone dial anything.
  • Restrict calls out of hours, and require a PIN for international routes if only a few people use them.
  • Limit forwarding and transfers to external numbers, and never let an IVR give callers an outside line. Our guide to IVR design best practices covers safe menu options.
  • Check the international prefix setting. 3CX notes that its country blocking relies on the correct international dialing code; a wrong value can silently disable the safety net.

5. Cap the damage

  • Limit concurrent calls per trunk to your real peak, so a compromised account can't open dozens of channels.
  • Limit call rates and durations per extension. Yeastar's outbound call security guide covers frequency, concurrency and duration limits; its default frequency rule allows each extension up to 5 outbound calls per second, so tighten it to suit your users.
  • Ask your SIP provider for a spending cap or prepaid balance, fraud alerts, and barring of destinations you never call. Match its country restrictions to your PBX settings so there are two layers. See SIP trunking explained for what to ask a provider.

6. Patch, monitor and review

  • Keep the PBX, phone firmware and the server's operating system updated.
  • Turn on email alerts for blocked IPs, failed logins and system changes.
  • Review call records weekly. The NCSC lists warning signs: repeated short calls, many hung-up incoming calls, sudden use of freephone or high-cost destinations, long calls and changes in after-hours calling.
  • Back up the configuration and keep logs where an attacker can't delete them.

Where to find these controls

Feature names at the time of writing (November 2026); menus vary by version, so check your vendor's documentation.

Control3CXYeastar P-SeriesFreePBX
Block brute-force attemptsAnti-hacking, Global IP BlacklistAuto Defense, Global Anti-hacking IP BlocklistIntrusion Detection (fail2ban), Firewall
Limit international destinationsAllowed Country CodesAllowed Country Codes, per-extension international permissionOutbound route dial patterns
Restrict access by IP or countryConsole restrictionsStatic Defense rules, Allowed Country IPsFirewall zones and trusted networks
Remote users without open SIPTunnel in 3CX apps, 3CX SBCRemote Access ServiceVPN, or Firewall Responsive mode if untrusted clients must connect
Cap the damageOutbound rules per group and prefixCall frequency, concurrent call and duration limitsMaximum channels per trunk

If you've been hit

  1. Stop the calls: disable outbound routes or the affected trunk, and ask your provider to bar international calls on the account immediately.
  2. Preserve evidence before you change anything else: call records, PBX logs and a support bundle. 3CX advises gathering logs first so forensic information is kept.
  3. Find the entry point: which extension or trunk placed the calls, and whether new extensions, forwarding rules, admin accounts or outbound rules appeared.
  4. Reset every credential: SIP passwords, admin accounts, voicemail PINs and the provider portal.
  5. Close the gap, patch, then re-enable calling in stages while you watch the call records.
  6. Report it to your provider in writing and to the police or national fraud reporting service, such as Action Fraud in the UK.

A hosted PBX shifts patching and server security to the provider, but passwords, dialing permissions and the bill usually stay with you. The NCSC suggests checking your contract for who is responsible if a misconfiguration is exploited. For security beyond the phone system, see our cybersecurity checklist for small businesses, and the business VoIP phone system guide for how security fits into the overall setup.

How BtoBSkills can help

Through our VoIP support and configuration service, we can review and tighten your trunks, outbound rules, extensions and remote access on 3CX, Yeastar, FreePBX and other Asterisk-based systems. For a wider look at your network and systems, our cybersecurity consultation assesses your current security posture and identifies vulnerabilities. Request a quote for either.