What Is VoIP? A Plain-English Guide for Business in 2026

What Is VoIP?

VoIP stands for Voice over Internet Protocol. In plain English: it's a technology that lets you make and receive phone calls using your internet connection instead of traditional copper telephone lines. Instead of your voice traveling as an electrical signal over a dedicated phone circuit, VoIP converts your voice into digital data packets and sends them over the same IP network your emails and web pages use.

The term has been around since the mid-1990s, but VoIP didn't become a viable enterprise option until broadband internet became widespread. By 2026, VoIP is the standard for business telephony. Traditional analog landlines are the exception, not the rule—used mainly where internet service is unreliable or in applications (like elevator phones or alarm systems) where analog POTS lines are still required by code.

When most businesses say "VoIP," they usually mean one of two things: a hosted UCaaS platform (RingCentral, Zoom Phone, Microsoft Teams Phone) where a cloud provider manages everything, or a SIP trunk that replaces traditional phone lines while connecting to an existing on-premise PBX. Both are VoIP—they just put the control plane in different places.

The practical upshot for a business owner: VoIP means no more per-minute long-distance charges, no more "lines" to provision, no more waiting for a technician to add an extension, and a phone system that travels with your employees wherever they have internet access.

How VoIP Works (Technical Overview)

You don't need to understand VoIP internals to use it, but knowing the basics helps when you're troubleshooting call quality or evaluating vendor proposals. Here's what's actually happening when you place a VoIP call.

The Call Setup: SIP

SIP (Session Initiation Protocol) is the signaling language that VoIP systems use to set up, manage, and tear down calls. Think of it as the dialing mechanism. When you pick up a VoIP phone and dial a number, SIP sends a message across the network that says, in effect, "I want to start a call between these two endpoints." The far end responds, they negotiate the call parameters (including which audio codec to use), and the call is established. When you hang up, SIP sends a BYE message and the session closes.

SIP runs on port 5060 (unencrypted) or 5061 (TLS-encrypted). Most enterprise VoIP deployments today use encrypted SIP to prevent eavesdropping. If your vendor proposal doesn't mention TLS for SIP signaling, ask about it—especially for industries with compliance requirements like healthcare or finance.

The Audio Path: RTP and Codecs

Once SIP establishes the call, the actual audio travels over RTP (Real-Time Transport Protocol)—a separate data stream from the SIP signaling. RTP is UDP-based, which means it doesn't guarantee delivery or ordering of packets. For file transfers, lost packets cause corruption. For voice, a tiny fraction of lost packets usually goes unnoticed; the codec compensates. This is by design—speed matters more than perfection for real-time audio.

The audio codec determines how your voice is compressed before transmission and decompressed at the far end. The two codecs you'll see most often in business VoIP:

• G.711 — the "uncompressed" standard. Uses 64 kbps per call. Produces excellent, natural-sounding audio because it does minimal compression. Requires more bandwidth but is the default for calls where quality is paramount. Used on most LAN calls and over high-bandwidth connections.
• G.729 — a compressed codec that uses only 8 kbps per call. Dramatically reduces bandwidth requirements—useful for remote workers on limited connections or for SIP trunks where you're paying per channel. The trade-off: some audio artifacts under high compression, and it requires a license (though most VoIP hardware includes it).

Newer codecs like Opus and G.722 (HD Voice) are increasingly common. Opus is used by WebRTC-based platforms (browser-based calling, Microsoft Teams). G.722 provides wideband audio (7 kHz vs. the 3.4 kHz of G.711) for noticeably clearer calls when both endpoints support it.

The Quality Factors: Latency, Jitter, and Packet Loss

Three network metrics determine call quality on a VoIP system:

• Latency (one-way delay): The time it takes audio to travel from your mouth to the listener's ear. Under 150ms is the ITU-T standard for good quality. Above 300ms, conversations become uncomfortable because you're talking over each other. Latency is mostly determined by the physical distance to your VoIP provider's servers and the number of network hops between you.
• Jitter: Variation in the delay between packets. Even if your average latency is 50ms, if some packets arrive in 20ms and others in 120ms, the audio sounds choppy and broken. VoIP phones and software use a "jitter buffer" to smooth out these variations—but a jitter buffer that's too large adds latency, and one that's too small lets variation through as audio distortion. Target jitter under 30ms for reliable call quality.
• Packet loss: The percentage of audio packets that never arrive. Most codecs can mask packet loss under 1–2% without the listener noticing. Above 3–5%, calls start to sound clipped and garbled. Packet loss above 10% makes calls unusable. Packet loss is usually caused by network congestion or a misconfigured router.

Network Requirements for VoIP

Before deploying VoIP, verify your network meets these thresholds:

Bandwidth: Allow 85–100 kbps per concurrent call (G.711). For a 30-person office where 20 might be on calls simultaneously, reserve at least 2 Mbps dedicated to voice traffic. Don't rely on total bandwidth—measure dedicated available capacity.

Latency: One-way delay should be under 150ms. Run a ping to your VoIP provider's closest data center. If you're seeing 80–100ms consistently, that's fine. Above 150ms, call quality degrades.

Jitter: Under 30ms. Run a jitter test using tools like PingPlotter or your VoIP vendor's pre-deployment test tool.

Packet loss: Under 1%. Anything above 3% will produce audible call quality problems.

QoS (Quality of Service): Configure your router and switches to prioritize VoIP traffic (DSCP EF / CS3 marking) over general internet traffic. Without QoS, a large file download or video upload can degrade call quality for everyone in the office simultaneously.

Types of VoIP Services

VoIP is a technology, not a product. It's deployed in several fundamentally different ways, each with different cost structures, control levels, and IT requirements.

Hosted UCaaS (Cloud Phone Systems)

The most common choice for businesses today. A third-party provider—RingCentral, Zoom Phone, Microsoft Teams Phone, 8x8, Vonage—hosts the entire phone system in their cloud. You provision users through a web admin console, download a softphone app, plug in IP phones if you want desk phones, and you're live.

You don't own or manage any server infrastructure. The provider handles redundancy, patching, compliance, and capacity. Cost is per seat per month. This model is called UCaaS (Unified Communications as a Service) because most platforms bundle in video conferencing, team messaging, and presence alongside the phone system.

Hosted UCaaS is the right choice for most businesses under 500 seats, for organizations with remote or distributed workforces, and for any company that doesn't want to maintain telecom infrastructure in-house.

SIP Trunking

SIP trunking is VoIP in a more targeted form. Instead of replacing your entire phone system with a cloud platform, you replace only your physical phone lines (the connection between your building and the public telephone network) with a SIP trunk—essentially a VoIP connection from a carrier to your existing PBX or IP PBX.

Your PBX (Cisco, Avaya, Mitel, or an open-source system like FreePBX) stays on-premise. The SIP trunk just handles the "last mile" between your PBX and the outside world. This is common in larger enterprises that have invested heavily in on-premise PBX infrastructure and aren't ready for a full migration, or in organizations with complex call routing requirements that are easier to manage on-premise.

SIP trunks are sold in "channels"—each channel supports one concurrent call. A 20-channel SIP trunk can handle 20 simultaneous calls. Carriers typically charge $15–$25 per channel per month, making SIP trunking very cost-effective for high call volume organizations.

On-Premise IP PBX

An IP PBX is a traditional Private Branch Exchange that speaks IP natively instead of requiring analog or digital phone lines. Cisco Unified Communications Manager (CUCM), Avaya Aura, and open-source solutions like FreePBX/Asterisk and 3CX are common examples.

An on-premise IP PBX gives your IT team maximum control over call routing, features, integrations, and data sovereignty. The trade-off: significant upfront hardware and software costs ($25,000–$150,000+ depending on scale), ongoing maintenance, licensing renewals, and the need for in-house or contracted VoIP expertise. Most businesses are moving away from this model, but it remains relevant in highly regulated industries (healthcare, government), large enterprises with custom requirements, or organizations with unreliable internet that need local call processing to continue during outages.

Hybrid Deployments

Many enterprises run hybrid architectures: a cloud UCaaS platform for most employees, with an on-premise component for specific functions (legacy integrations, analog device support, contact center, or compliance recording). Hybrid deployments are common during migration periods—keeping an existing PBX alive while gradually moving users to cloud seats.

Key Business Benefits of VoIP

Cost Savings: 30–50% vs. Traditional Landlines

The cost case for VoIP is compelling. Traditional PSTN landlines (especially T1/PRI circuits used for business) run $400–$1,200 per month for a 23-channel PRI, plus per-minute long-distance charges. A comparable hosted VoIP solution with unlimited calling typically costs $15–$25 per seat per month. For a 50-person office that was paying $800/month for a PRI plus long-distance overage, moving to hosted VoIP often cuts the voice bill by 40–60%.

The savings compound when you factor in eliminated hardware maintenance, no PBX refresh cycles (typically $50,000–$100,000 every 7–10 years), and reduced IT labor for system administration.

Geographic Flexibility and Remote Work

VoIP phone numbers are software constructs, not tied to a physical address. An employee in Portland and a remote worker in Austin both get extensions on the same system, reachable at the same number, with the same features. Adding a new remote employee means clicking "add user" in the admin console, not scheduling a technician visit.

This has become a baseline requirement for modern businesses. Post-2020, any phone system that can't support remote workers out of the box is a liability, not an asset.

Scalability Without Lead Time

Traditional phone systems required capacity planning—you had to buy trunk capacity before you needed it. With VoIP, adding users, phone numbers, or call capacity happens in minutes through software. Spinning up a new office location doesn't require a new telco circuit—you provision it in the admin console and ship IP phones to the new address.

Features That Used to Require Expensive Add-Ons

Features that once required expensive PBX modules—voicemail-to-email transcription, call recording, automated attendants, call analytics, CRM integration—are typically included in standard hosted VoIP plans or available as modest add-ons. A $25/seat/month UCaaS plan includes more functionality than a $100,000 on-premise PBX installed a decade ago.

Integration With Business Tools

Modern VoIP platforms integrate natively with Salesforce, HubSpot, Microsoft Teams, Slack, ServiceNow, and hundreds of other business applications. Screen pops (automatically opening a CRM record when a known customer calls), click-to-dial from within a CRM, and post-call activity logging are standard features. These integrations were theoretically possible with legacy PBX systems but required custom development. With hosted UCaaS, they're pre-built.

Limitations and What Can Go Wrong

VoIP is the right choice for most businesses—but not unconditionally. Understanding the limitations before you commit prevents expensive surprises.

Internet Dependency

This is the fundamental trade-off of VoIP: you've moved your phone system onto your internet connection, which means an internet outage also takes down your phones. Traditional PSTN landlines work during power and internet outages (the phone network carries its own power). VoIP does not.

Mitigations: a secondary internet circuit from a different carrier (common in most businesses already), automatic call forwarding to mobile numbers when the primary connection fails, and hosted UCaaS platforms that let you configure failover routing in the admin console. For critical operations, maintain at least one analog POTS line or cellular backup for emergencies.

Power Outages

IP phones require power. During a power outage, IP phones go dark unless they're on a UPS (uninterruptible power supply). Your router and switches also need power—a single battery backup that keeps your core network equipment alive is a worthwhile investment for any business that depends on phone availability.

Call Quality Is Network-Dependent

VoIP call quality is only as good as your network. On a properly configured network with QoS, VoIP sounds as good or better than a landline. On a congested or misconfigured network, it sounds terrible—choppy, echoing, one-sided audio, dropped calls. The root cause is almost always network configuration, not the VoIP platform. Before blaming your VoIP provider, run a network quality test.

E911 Registration Requirements

Traditional 911 automatically reports your location because landlines are tied to a physical address. With VoIP, your number is location-independent—which is great for remote work but complicates emergency calling. Hosted VoIP providers require you to register a physical address for each number (E911), and most states have regulations requiring businesses to keep E911 records current. For businesses with multiple locations or frequent moves, E911 management is an ongoing administrative task, not a one-time setup.

Warning: Don't neglect E911 registration. If an employee calls 911 from a VoIP number with an outdated or missing E911 address, emergency responders may go to the wrong location. When you provision VoIP lines, E911 registration for every number is not optional—it's a legal requirement and a safety obligation.

Fax Machines and Analog Devices

Standard analog fax machines don't work reliably over VoIP connections because fax uses a tone-based signaling protocol (T.30) that's sensitive to the latency and packet loss that VoIP networks introduce. Solutions: use a cloud fax service (eFax, RightFax), use the T.38 fax-over-IP standard if your VoIP equipment supports it, or keep a dedicated analog line for fax. Similarly, elevator emergency phones, alarm systems, and some door access systems may require analog lines—check before cutting all POTS circuits.

How Much Does Business VoIP Cost?

VoIP pricing varies significantly depending on the deployment model and the features you need. Here's a realistic breakdown.

Hosted UCaaS Pricing

The dominant model for businesses today. Pricing is per seat per month:

The prices above are list prices. ITG Group regularly negotiates 15–30% below list for clients, especially on multi-year agreements or larger seat counts. Always ask for a telecom broker or advisor to run the negotiation—carriers expect it and build margin into list pricing.

What's Not Included in the Per-Seat Price

Watch for these costs that appear on invoices but aren't always in the initial quote:

• Number porting fees: $0–$25 per number ported. Some carriers waive this; others don't. Ask upfront.
• E911 registration: $1–$3 per number per month in some states.
• IP desk phones: $80–$300 per phone hardware cost, not included in software pricing. Many businesses use softphones only (laptop/mobile app) to eliminate this cost.
• International calling: Unlimited calling plans cover the US and Canada. International per-minute rates apply beyond that and vary widely by country.
• Implementation / professional services: Simple setups may be self-service. Multi-site deployments, custom integrations, or contact center configurations often require paid professional services.

SIP Trunking Pricing

If you're keeping an on-premise PBX and just replacing your phone lines with a SIP trunk, pricing looks different: $15–$25 per concurrent channel per month, plus per-minute rates for calls (or unlimited calling bundles). A 10-channel SIP trunk with unlimited US/Canada calling runs $150–$250/month, substantially less than a PRI circuit at the same capacity.

On-Premise IP PBX Total Cost of Ownership

On-premise systems have a different cost structure: significant CapEx upfront ($25,000–$150,000 depending on scale), annual maintenance contracts (typically 15–20% of initial cost per year), hardware refresh every 5–7 years, and internal IT labor or contracted support. For a 100-seat on-premise deployment, the 5-year TCO often runs $200,000–$400,000 when fully loaded. Comparable hosted UCaaS over the same period: $120,000–$180,000. The math favors cloud for most organizations.

VoIP vs. Traditional Landline

The comparison between VoIP and traditional PSTN landlines isn't really a close competition for most businesses in 2026—but understanding the differences helps clarify what you're trading when you make the switch.

Traditional landlines still make sense in a narrow set of scenarios: locations with unreliable or no broadband, applications where analog device compatibility is non-negotiable (certain alarm or fire suppression systems), or in areas where carriers have already announced POTS sunset timelines that require analog-to-IP migration anyway. The major US carriers (AT&T, Verizon, Lumen) have been sunsetting PSTN infrastructure for years. In many markets, "keeping your landline" is no longer an option—carriers are discontinuing service on legacy copper.

How to Choose a VoIP Provider

The right VoIP solution depends on your organization's size, technical maturity, geographic footprint, and how much control you want over the system. Here's how to work through the decision.

Start With Your Use Case

Most businesses fit into one of three buckets:

• Simple replacement: You have a traditional phone system or aging PBX and want a modern cloud phone system without a lot of complexity. You want to provision numbers, set up voicemail, configure a basic auto-attendant, and let employees use a softphone app. Hosted UCaaS (any of the major platforms) is the answer.
• Complex requirements: You have a large contact center, compliance recording requirements, complex call routing across multiple sites, or deep integration needs with custom applications. Evaluate UCaaS platforms with mature contact center offerings (8x8, RingCentral, Genesys Cloud) or consider whether an on-premise or hybrid approach better serves your needs.
• Existing PBX investment: You've spent significantly on a Cisco or Avaya PBX that isn't end-of-life. SIP trunking gives you cost savings on the carrier side without forcing a full platform migration. You can migrate to full cloud when the PBX refresh cycle comes.

Evaluate Network Readiness Before Evaluating Vendors

Many businesses choose a VoIP platform before verifying their network can support it. This creates deployment problems that aren't the vendor's fault. Before issuing an RFP or signing a contract, run a network assessment: test latency, jitter, and packet loss to your shortlisted vendor's data centers. Verify your router supports QoS configuration. Confirm your internet circuit has adequate headroom for your expected concurrent call volume.

Questions to Ask Every VoIP Vendor

• What is the uptime SLA, and how is it measured? (Five-nines is 99.999%; most offer 99.9%—know the difference.)
• What is your process for number porting, and what are the fees?
• Are there seat minimums, and how is downscaling handled mid-contract?
• What are the international calling rates to the countries my team calls regularly?
• Is E911 registration managed by your platform or do I register separately?
• What does your onboarding and implementation support include at this price tier?
• What are the auto-renewal terms and termination notice requirements?
• What redundancy do you have for your calling infrastructure? (Active-active data centers? Failover regions?)

Don't Overlook Contract Terms

VoIP platforms are sold as software subscriptions, which means the contract terms matter as much as the technical capabilities. Watch for auto-renewal provisions (typically 60 days' written notice required to cancel), early termination fees on 24- or 36-month contracts, seat minimums that require payment even if headcount drops, and per-minute overages on calling plans marketed as "unlimited" (many have fair-use caps). A 12-month initial term is the right choice for a first deployment—it gives you enough time to validate the platform without overcommitting.

ITG Group's role in VoIP procurement: As an independent telecom advisory firm, we compare VoIP providers on your behalf, validate that the network requirements are met before cutover, negotiate contract terms, and manage the transition. Our clients typically pay 15–30% less than list price and avoid the contract gotchas that catch most first-time buyers. The service costs you nothing—carriers pay advisory fees, not you.

Frequently Asked Questions