Skip to content

Security

Ten Security Checks for Every Internet-Facing VICIdial Server

A practical security checklist for VICIdial and Asterisk servers — SIP exposure, credentials, toll-fraud limits, patching, backups and monitoring.

Author
JH Dialer Engineering Team
Published
Reading time
2 min read
On this page
  1. 1. Is SIP open to the whole internet?
  2. 2. Are admin pages restricted?
  3. 3. Are all credentials unique and strong?
  4. 4. Is SSH key-only?
  5. 5. Is brute-force blocking enabled?
  6. 6. Are international destinations restricted?
  7. 7. Is there a spend or call-rate alarm?
  8. 8. Is the system patched?
  9. 9. Are backups off the server — and tested?
  10. 10. Is someone watching?

A VICIdial server on a public IP address is a target from the moment it goes online. Automated scanners look for open SIP ports and web admin pages, then try common credentials. The goal is usually toll fraud — placing expensive international calls on your account.

Here are the checks we run on every system we install or take over.

1. Is SIP open to the whole internet?

Restrict SIP (and RTP where possible) to your carriers’ IP addresses and known agent networks. If agents work from changing home IPs, use WebRTC over HTTPS or a VPN rather than opening SIP globally.

2. Are admin pages restricted?

Limit the VICIdial admin interface to office IPs or a VPN. There is rarely a reason for it to be reachable from anywhere.

3. Are all credentials unique and strong?

Change every default password: admin users, phone registrations, database, API users. SIP secrets should be long and random.

4. Is SSH key-only?

Disable password login for SSH and restrict it by IP.

5. Is brute-force blocking enabled?

Tools such as fail2ban block IPs after repeated failures on SSH, SIP and web logins.

6. Are international destinations restricted?

If you only call two countries, your dialplan should only allow those. Block premium-rate ranges. This single control limits the damage of any compromise.

7. Is there a spend or call-rate alarm?

Ask your carrier for spend limits and alerts. Monitor for unusual call volume to unexpected destinations.

8. Is the system patched?

Apply operating system and application updates on a schedule, tested first where possible.

9. Are backups off the server — and tested?

A backup stored on the same disk as the database is not a backup. Copy backups elsewhere, encrypt them, and restore one periodically to prove it works.

10. Is someone watching?

Disk space, service status and failed-login spikes should alert a person who will act.


If you’d like us to run these checks on your system, see backup & security or technical support.

Frequently asked questions

How quickly do attackers find a new SIP server?

Public IP ranges are scanned continuously, so a new server with open SIP ports typically starts receiving probes soon after it goes online. Treat hardening as part of installation, not a later task.

Tell us how your call center runs. We’ll design the dialer around it.

Share your agent count, campaigns and CRM. You’ll get a technical recommendation and a written quotation — no obligation.