What do I need to use VoIP?

Using VoIP comes down to three essentials, plus a few things a business will want on top of them. Voice over Internet Protocol carries your calls as data packets across an internet connection instead of over a dedicated copper phone line, so the phone company's wire is replaced by your broadband link and a provider that connects your calls to everyone else.[1] The three essentials are a stable internet connection, an account with a VoIP provider, and at least one endpoint that can send and receive the audio.[1] Everything else, from Power over Ethernet to call-prioritizing switches, exists to make those three work reliably once more than one person is on the phone.

A home user can often start with equipment already on hand. Most homes have a modem and router, or a combined gateway, which is all the network hardware a single line needs, and a smartphone app or an inexpensive adapter turns an existing phone into a VoIP endpoint.[6] VoIP is also forgiving on speed, since a single call needs less than half a megabit per second of download capacity, which nearly every modern broadband plan clears with room to spare.[6]

Where a business setup differs

A business has to plan for many calls at once and for the reliability people expect from a phone. That means sizing bandwidth for concurrent calls, giving voice traffic priority on the network so a large file transfer cannot degrade a call, and often powering desk phones through the network cable rather than a wall outlet.[2][7] United States providers of interconnected VoIP also have to route your 911 calls to the right emergency center, which requires you to register the physical address where each phone is used.[8] The sections below take each requirement in turn, starting with the connection everything else depends on.

A single VoIP call needs little capacity, but it needs that capacity to arrive on time and in order, which is why connection quality matters more than a big download number. Each concurrent call on the common G.711 codec uses about 100 kbps in each direction once packet overhead is counted, and a more compressed codec such as G.729 drops that to roughly 31 kbps at some cost to clarity.[3][4] Microsoft rates a single audio stream at about 58 kbps up and down for good quality on its own platform, which lands in the same range.[2] To size a connection for more than one line, multiply your peak number of simultaneous calls by roughly 100 kbps and add headroom for spikes and retransmissions.[3]

Three quality measures decide whether those packets become clean audio. Latency, the one-way delay, should stay under 150 milliseconds so conversation feels natural, jitter, the variation in packet timing, should stay below 30 milliseconds, and packet loss should sit under about half a percent.[3] A connection can post a high speed-test result and still deliver poor calls if it spikes in latency or drops packets under load, so a wired connection and an internet plan with steady performance beat raw bandwidth for voice. Most modern broadband clears the download requirement easily, since a single call runs on well under half a megabit per second.[6]

A VoIP call reaches an ordinary phone number only through a provider that bridges your internet connection to the public telephone network, so an account with one is not optional.[1] There are two common ways to buy that connection. A hosted, or cloud, VoIP plan puts the call-handling system on the provider's own infrastructure and bills per user or per line, which is why most small and midsize offices choose it, as there is no phone system to run on site.[1] A SIP trunk is the alternative for an organization that already operates its own phone system, or PBX, and wants to keep it, because the trunk supplies the outside connectivity that carries the PBX's calls over the internet.[1]

Whichever you choose, the provider is what gives you working phone numbers and dial tone, the calling features people expect such as voicemail and an auto-attendant, and the routing that connects your calls to everyone else.[1] In the United States the provider also carries the legal duty to route your 911 calls, which is one reason running every piece of a phone system yourself is rare outside large enterprises.[8] For most buyers the decision is less about capability and more about how much of the system you want to operate yourself.

You make VoIP calls on one of three kinds of endpoint, and plenty of setups mix them by role.[1] An IP desk phone is the closest match to a traditional office phone, since it speaks the Session Initiation Protocol, plugs into the network with an Ethernet cable, and needs no computer to work.[1] A softphone is an application that turns a laptop or smartphone into a phone, which is why remote and hybrid teams often skip desk hardware and use the provider's desktop and mobile apps instead.[1][6]

The third option keeps a phone you already own. An analog telephone adapter, or ATA, sits between a standard analog handset or fax machine and your internet connection, converting the analog signal into digital voice packets and speaking SIP to the provider.[5] A typical ATA offers an RJ-11 FXS port for the phone on one side and an Ethernet port for the network on the other, so an old cordless phone or a fax line can keep working without replacement.[5] Home setups sometimes use a base-station adapter that plays the same role.[6]

Softphone users usually add a headset with a microphone for hands-free calling and cleaner audio, while desk-phone users get that built in. The practical choice tends to follow the person, because a contact-center agent or a fax line has different needs than a field salesperson who lives in a mobile app.

The setup that keeps calls clear gives voice packets priority on the network and reliable power to the phones. Quality of Service, or QoS, is a setting on your router or switch that tags voice as high-priority traffic so a large upload or a video stream cannot starve a call of bandwidth, and applying it across every segment of a managed network is the standard recommendation rather than a nice-to-have.[2] Without it, calls tend to break up exactly when the network gets busy.

Power over Ethernet for desk phones

Power over Ethernet sends both data and electricity down the same cable, so a desk phone draws power from the switch and needs no wall adapter or nearby outlet. The original 802.3af standard supplies up to 15.4 watts from the switch port, of which about 12.95 watts reaches the phone after cable loss, while 802.3at, marketed as PoE+, raises the budget to 25.5 watts for phones with color screens or expansion modules.[7] A small site can run on a modem and router, or a single gateway, but a PoE switch is what makes a row of desk phones practical.[6]

Keeping calls up in an outage

Because the phones and the network now run on your electricity rather than the phone company's, a battery backup on the modem, router, and switch keeps calls alive through a short power cut.[8] When a business moves to hosted VoIP, providers typically assess whether the local and wide-area network and the Wi-Fi can carry the added voice traffic with proper QoS, and may recommend new phones or a network upgrade before cutover.[9][1]

Yes, and 911 for VoIP works differently from a landline, so it needs deliberate setup. Under United States rules for interconnected VoIP, your provider must transmit each 911 call along with a callback number and your registered physical location to the correct emergency call center, and it has to obtain that location from you before service starts.[8] Because a VoIP phone can be carried anywhere there is internet, the address on file does not update itself. Your provider must give you a way to change your Registered Location when the phone moves, and it is on you to keep it current so responders reach the right building.[8]

Providers are also required to tell you in plain language that 911 may be unavailable during a power outage, a broadband failure, or if you relocate the equipment, and to obtain your acknowledgement that you understand those limits.[8] That advisory is the reason a battery backup and a charged mobile phone matter as fallbacks. Fixed services increasingly deliver an automated dispatchable location with each call, but where that is not technically feasible, the registered-address model is what stands between a caller and a misrouted emergency response.[8] None of this is an optional add-on, because it is a federal requirement that applies to the service itself.

Moving voice onto the internet shifts a few responsibilities onto you, and each one is worth planning for before cutover.

Power and internet become your responsibility

A landline draws power from the phone company and usually keeps working in an outage, while VoIP runs on your electricity and your internet, so both the phones and the connection go down when either fails.[8] A UPS on the network gear and a mobile phone as backup cover most of that gap.

Call quality tracks your network, not the plan

Because the audio travels over the public internet and your local network, jitter or packet loss anywhere along the path shows up as choppy or robotic sound, and the fix is usually QoS and enough bandwidth rather than a different provider.[3][2]

911 needs active upkeep

The registered-address model means a phone carried to a new location can send responders to the old one until someone updates it, so a portable phone is convenient but adds a small compliance chore.[8]

Older hardware may not survive the switch

Moving an office to hosted VoIP can require new phones or a network upgrade, so budgeting only for the monthly service and not the readiness work is a common miss.[9][1]

A few things people expect to buy turn out to be optional or unnecessary. You do not need a traditional phone line, because VoIP replaces it, and many businesses port their existing numbers over and cancel the copper.[1] You do not need a computer left running, since IP phones and ATAs register with the provider on their own and a softphone only has to be open when you want to make a call.[5] You also do not need an unusually fast connection, because a single call fits in well under a megabit and quality depends far more on latency and jitter than on headline download speed.[6][3] The one thing you cannot skip is the 911 registration, which is a regulatory requirement rather than an optional add-on.[8]