7 things people get wrong about VoIP calls

This one has been wrong for at least ten years, but it sticks around because it was true in the early days.

A traditional landline or cell call uses the G.711 codec, which captures audio from about 300 to 3,400 Hz. That is enough to understand speech, but it is narrow, and it is why phone voices have that slightly muffled, flat quality you have learned to associate with 'phone call sound.'

Modern VoIP uses the Opus codec, which captures roughly 20 to 20,000 Hz, essentially the full range of human hearing. A browser-to-browser VoIP call on a decent connection sounds noticeably richer and more natural than a traditional phone call.

The 'VoIP sounds bad' reputation comes from early VoIP over slow connections, and from the packet loss and jitter that show up when a call degrades. That is a connection-quality problem, not a VoIP problem. A bad call on bad internet sounds worse than a landline. A good VoIP call on good internet sounds better.

Accurate in 2005, not in 2026.

Early VoIP struggled on the asymmetric connections of the dial-up era, where upstream bandwidth was tiny and latency was high. Those conditions made real-time audio genuinely hard.

Modern broadband, even a typical 50 Mbps home connection, has far more capacity than a voice call needs. A single VoIP call uses roughly 100 kbps in each direction. On a 100 Mbps connection that is a fraction of one percent of what is available.

Dropped VoIP calls today are almost always caused by Wi-Fi instability, not a lack of bandwidth. A wired Ethernet connection removes most dropout problems.

This is true of some calling tools, WhatsApp to WhatsApp, FaceTime to FaceTime, but not of VoIP generally, and not of browser-based calling.

When you generate a FreeCallMe call link, you share a URL. The other person clicks it, and their browser opens the call room. No app, no account, no shared platform. WebRTC, built into every major browser since around 2012, handles the rest.

For calls to real phone numbers through the FreeCallMe dialer, the recipient just needs a phone. They do not know or care that you called from a browser.

The both-people-need-the-same-app limitation applies to closed-network apps. It does not apply to browser VoIP or to calls that terminate on a real phone number.

This confuses older, unencrypted VoIP setups with modern browser calling.

WebRTC requires DTLS-SRTP encryption for all media. It is not optional and it is not a setting, it is baked into the specification. A WebRTC call cannot be placed without it, and your voice travels encrypted between your browser and the other person's.

For calls through SIP infrastructure to real phone numbers, TLS encrypts the signaling and SRTP encrypts the media where the carrier supports it.

What VoIP does not protect: metadata (who you called, when, for how long) and the last stretch of a call into a traditional landline, which runs over infrastructure older than encryption. But the call content, what you actually say, is encrypted in any compliant WebRTC or modern SIP setup.

You need a microphone and internet access. That is it.

The myth comes from early office VoIP, which needed SIP desk phones, adapters, and on-premise servers. For a home user or a browser call, none of that applies. Your laptop's built-in microphone and the browser you already have are enough.

If you want better quality, and for important calls it is worth it, a $20 USB headset makes a real difference over a laptop's built-in mic. But it is not required.

Partly true, and widely misunderstood.

VoIP works from anywhere with internet access. A browser call between two people in different countries works the same as a call between two people in the same city. The audio travels over the internet regardless of geography.

Where it gets more complicated is calling to phone numbers in certain countries. Some carriers, particularly in India and parts of the Middle East and Southeast Asia, aggressively filter inbound international VoIP calls. That is not a VoIP failure, it is a carrier policy that treats international VoIP as potential spam.

The FreeCallMe dialer reaches more than 220 countries, with the rate for each shown before you dial. A handful of destinations are simply harder to complete because of that carrier-side filtering, not because the technology cannot reach them.

VoIP became mainstream consumer technology around 2003, when Skype launched. WhatsApp voice calling, FaceTime, Google Meet, Discord voice channels: every one of these is VoIP, and together they have billions of users with no business context at all.

The 'VoIP is a business thing' association comes from the industry that grew up selling VoIP as a replacement for office PBX systems. That is one application, not the whole story.

A student sharing a link so a study group can talk without everyone installing Zoom. A relative abroad getting a call on their normal mobile from a browser. A freelancer calling a client without handing over a personal number. These are all VoIP, and none of them need an IT department.