VoIP: Asterisk server or hardware SIP PBX?

Before you choose: what "IP telephony" actually is

VoIP replaces the traditional analog wiring with IP packets traveling over your data network. Three key pieces:

• SIP (Session Initiation Protocol) — opens, closes, and routes calls. Open standard, basically universal.
• RTP (Real-time Transport Protocol) — carries the audio (and video) once the call is established.
• Codec — how that audio is compressed. The common ones: G.711 (HD-voice quality, 87 kbps), G.729 (compressed, 31 kbps, licensed), Opus (open source, high quality, adaptive).

The "PBX" (Private Branch Exchange) is the central system that orchestrates everything: extensions, IVR ("press 1 for sales..."), queues, recording, voicemail, transfers, CRM integration. In the analog world it was a mandatory metal box in the rack; in IP it can be a Linux server, a dedicated appliance, or a cloud service.

The three possible paths

1. Asterisk server (or derivatives with UI: FreePBX, Issabel, Wazo)

Asterisk is the most widely used open-source PBX engine in the world, originally written by Mark Spencer in 1999. On top of pure Asterisk, distributions with web UI are built:

• FreePBX — the most popular, maintained by Sangoma. Huge community, paid and free modules.
• Issabel — successor of the extinct Elastix, popular in Latin America.
• Wazo — more modern, better UI, native Microsoft Teams integration.
• FusionPBX — built on FreeSWITCH (alternative to Asterisk), multi-tenant.

It runs on a Linux server (physical or VM): 2 vCPU, 4 GB RAM, 40 GB SSD comfortably handles 50 extensions. It connects to the outside world via a SIP trunk contracted from a provider (Twilio, Voxbeam, Skyetel, Bandwidth, or local ISPs).

2. Hardware SIP PBX (dedicated appliance)

Physical equipment designed specifically as an IP phone system. You connect, configure, and forget. The common ones:

• Yealink SIP-T46U / W90 series — good price/quality, modern UI.
• Grandstream UCM 6300 / 6304 / 6308 — most popular in Latin American SMBs. Supports 50 to 3000 users depending on model.
• Cisco Business Edition / UCM — large enterprise, expensive closed ecosystem.
• Avaya IP Office — traditional corporate, expensive and complex.
• Panasonic KX-NS — hybrid (accepts analog + IP), popular in hotels.
• Snom / Mitel / Audiocodes — more niche.

3. Cloud PBX (managed service)

You install nothing. The PBX lives at the provider and your IP phones or softphones connect over the internet. Examples:

• 3CX Hosted — the most popular. Can also be self-hosted free up to 10 users.
• RingCentral, Vonage, 8x8 — strong in the US, present in LatAm.
• Zoom Phone, Microsoft Teams Phone — integrated with existing collaboration platforms.
• Net2Phone, Dialpad, Vozelia — variants.

4. Hybrid: keep your existing analog PBX with an ATA / FXO gateway

If you already have an analog PBX deployed (Panasonic KX-TES824, KX-TDA, Siemens HiPath, Avaya Partner, Alcatel, NEC, etc.) that's still working, you don't necessarily have to throw it out to migrate to SIP. An ATA (Analog Telephone Adapter) or an FXO/FXS gateway bridges the analog and IP worlds. Two variants:

• FXO gateway (the old PBX keeps its trunk lines, but those lines actually ride on SIP behind the scenes). The PBX thinks it's connected to traditional phone lines; the gateway converts them to SIP trunk. Common equipment: Grandstream GXW4501 / GXW4502 / GXW4504, Cisco SPA8800, Audiocodes MP-114, Sangoma Vega.
• FXS ATA (keep individual analog phones on an IP PBX). The ATA converts SIP to a phone line so you can plug in traditional phones, fax machines, or door intercoms. Common equipment: Grandstream HT801 / HT802 / HT812 / HT814 / HT818, Cisco SPA112 / SPA122, Linksys PAP2T (legacy).

For companies with large legacy analog phone fleets, there are high-density FXS gateways: Grandstream GXW4216 / GXW4224 / GXW4232 / GXW4248 (16 to 48 analog ports to SIP).

This is the option companies most often underestimate: you don't always have to replace everything. If the analog PBX still works fine and you only want to lower line cost (going out via SIP trunk instead of traditional PSTN) or add remote capabilities (IP extensions coexisting with analog ones), a USD 150–600 gateway saves you a full USD 3,000–10,000 migration.

Side-by-side comparison

Real-world costs

Comparison for a typical company with 20 extensions, 4 concurrent external calls, basic CRM integration and call recording:

The ranges depend on provider, brand and implementation hours. The gap between self-hosted and cloud per-user is brutal: past 10–15 extensions, self-hosted typically pays back in 6–12 months vs cloud per-user.

When each path fits

Asterisk/FreePBX on your own server

Fits when:

• You have 15+ extensions and a technician (in-house or external) who knows Linux.
• You need custom integrations with CRM, ERP, notarial or industrial systems — Asterisk has APIs (AMI, ARI, AGI) for everything.
• You care about privacy: recordings stay on your server, not at a third party.
• You have complex flows: multi-level IVR, predictive dialing, WhatsApp Business API integration.
• You want to avoid lock-in: the day you change SIP provider or support, you lose nothing.

Doesn't fit when:

• You're a 3–5 extension micro-business — overkill.
• You have nobody to administer it and the only option is expensive external support.

Hardware SIP PBX (Grandstream UCM, Yealink, etc.)

Fits when:

• You want a "closed-box" solution, easy to maintain by a generalist technician.
• You have 10–100 extensions, standard flows (IVR, queue, voicemail, transfer) with no weird integrations.
• Direct manufacturer support (Grandstream, Cisco, etc.) gives you peace of mind.
• There are constraints to running an extra server (no rack space, no staff).

Doesn't fit when:

• You need customizations the firmware doesn't allow.
• You're very small (4–6 ext) — the hardware doesn't pay back.

Cloud PBX (3CX hosted, RingCentral, Zoom Phone, Teams Phone)

Fits when:

• 100% remote or geographically distributed team.
• Micro-business (1–10 people) that doesn't want to administer anything.
• You already pay Microsoft 365 E5 / Teams Phone or Zoom Business — adding telephony is marginal.
• You need to scale quickly without reimplementing anything.

Doesn't fit when:

• Your internet is unstable or has frequent outages (common in some industrial zones in Latin America).
• You have 30+ users and the per-user model ends up costing 4–10× more than self-hosted.
• Recordings have legal requirements to stay on national territory or on your own system.

Hybrid with ATA / FXO gateway (keep your existing analog PBX)

Fits when:

• You have a recent or not-yet-amortized analog PBX (Panasonic KX-TDA/TES, Avaya Partner, NEC, etc.) that still works well.
• You want to lower monthly cost by going out via SIP trunk instead of traditional PSTN.
• You have a fleet of analog phones, fax machines, door intercoms, or alarm lines you don't want to replace.
• Phased migration: SIP trunk today, replace the PBX later when it dies or you outgrow it.

Doesn't fit when:

• The analog PBX is very old, with no spares or support, and you'll have to replace it in 1–2 years anyway.
• You need modern features (digital recording, sophisticated IVR, CRM integration) the analog PBX can't support.
• Expected growth exceeds the current PBX's capacity.

Use cases by scenario

Micro-business (3–8 people)

Cloud PBX or 3CX self-hosted on a small VM. Buying a hardware PBX or running pure Asterisk doesn't pay off. If you're already on Teams or Zoom, adding the phone module is the cleanest option.

SMB (15–60 people), single site

Asterisk/FreePBX in a VM or Grandstream UCM6304. The decision hinges on whether you have a trusted Linux tech. If you do, FreePBX wins (more flexible and cheaper). If not, the hardware PBX with vendor support lowers operational risk.

Mid-size (60–200 people), call center

FreePBX/Issabel with call-center modules (queues, predictive dialer, wallboards) or Asterisk + VICIdial for heavier contact-center loads. Cloud per-user at this volume is financially unsustainable.

Multi-site (several cities)

Centralized FreePBX in a datacenter, with IP phones at each site registering over VPN (WireGuard or IPSec) or SIP-TLS over internet. Alternative: 3CX hosted if the sites are small and simplicity matters more.

Vertical-specific

• Hospitality: Panasonic KX-NS or Grandstream UCM with PMS module. Integration with check-in/out and billing.
• Hospital / clinic: FreePBX with auditable call recording and number masking for medical confidentiality.
• Port / industrial plant: PBX with dust/humidity-resistant phones (IP54+) and radio links to remote sites. Asterisk + rugged phones like Yealink WH63 / Cisco 8821.
• Notary / legal: FreePBX with mandatory call recording and routing by service type.

What decides success or failure: the network, not the PBX

Most failed VoIP deployments are not about the PBX — it's because the data network wasn't ready.

Common (and expensive) mistakes

• Weak SIP passwords: the most common attack is automated scans testing credentials to place fraudulent international calls. I've seen USD 8,000 bills over a weekend. Use long passwords, geo-IP block, configure fail2ban.
• Misconfigured NAT: if your PBX is behind NAT and you don't set externip or use STUN, calls connect but no audio passes. The classic "one side can hear, the other can't."
• Incompatible codecs: forcing G.729 without a license or hardware gives robotic audio. Start with G.711, drop to G.729 only if you have bandwidth issues.
• Mixing voice/data on a cheap switch: broadcasts and poor QoS degrade voice quality.
• No fallback plan if internet drops: if your business depends on the phone, consider dual-ISP failover or a gateway with analog backup line (FXO).
• Forgetting legal compliance: in many countries, call recording requires user notification ("this call will be recorded"). Regulated sectors (legal, financial, health) have minimum retention.

My honest recommendation

Need to deploy or migrate your IP telephony?

I've spent years deploying and maintaining Asterisk/FreePBX/Issabel and hardware PBXs (Grandstream, Yealink, Cisco) in notarial, marine-port, hospitality, construction and industrial sectors in Cartagena and the rest of Colombia. If you need to evaluate your case, size the right SIP trunk, integrate with your CRM/ERP, or audit an implementation that isn't working — message me on WhatsApp and let's talk.

Related articles

Networking Access points and business WiFi Internet Residential vs dedicated internet Infrastructure On-premise vs cloud