When calls on a new hosted phone system sound choppy, the provider usually gets the blame. Sometimes that is fair. Often, though, the problem sits closer to home: a congested broadband line, an overloaded router or patchy Wi-Fi.

Hosted VoIP sends your calls over the same network as your email, cloud software and video meetings. That works well when the network is ready for it, and badly when it is not. A few hours of testing before you switch can save weeks of frustration afterwards. This guide explains what to measure, how to do it, and what to fix.

Why the Network Matters So Much

With a traditional ISDN line, voice had its own dedicated path. With hosted telephony, voice travels as small packets of data across your internet connection, competing with everything else.

If those packets arrive late, out of order or not at all, callers hear delays, robotic voices or gaps. The cloud PBX can be perfectly healthy while your office network is the weak link.

That is why a good migration starts with your premises rather than the provider's brochure.

The Four Measurements That Matter

You do not need to become a network engineer, but it helps to understand four terms.

Bandwidth

This is how much data your connection can carry. For voice, upload speed is often the limiting factor, because many business broadband services offer far less upload than download. Each call travels in both directions, so both matter.

Latency

The time a packet takes to travel from your office to the provider and back. High latency causes awkward pauses and people talking over each other.

Jitter

Variation in that delay. Packets that arrive at uneven intervals make audio sound broken, even if the average delay is low.

Packet loss

The proportion of packets that never arrive. Even small amounts can cause dropouts in speech.

Industry guidance commonly suggests keeping latency modest, jitter low and packet loss close to zero for good voice quality. Providers differ on exact thresholds, so ask yours what it recommends rather than relying on a single figure.

How to Test Your Network: A Simple Routine

You can gather useful evidence with free tools and a bit of patience.

1. Run speed tests at different times. Test first thing in the morning, mid-day and late afternoon, on several days. A single test at 7am tells you little about peak hours.
2. Check upload speed separately. Note the upload figure, and compare it with the number of simultaneous calls you expect at your busiest time.
3. Measure jitter and packet loss. Many online tools and some routers report these. Your provider may also supply a test tool or a trial service.
4. Test over a wired connection first. Plug a laptop directly into the router to remove Wi-Fi from the picture. Then repeat on Wi-Fi in the places where staff will actually use softphones.
5. Test under load. Run a typical busy scenario, such as video calls, large uploads and cloud backups, while making test calls.
6. Record the results. A simple table of time, test type and result gives you something concrete to share with providers.

If you can, ask for a short trial on a few lines before moving the whole business. It is the most realistic test available.

Sizing Your Bandwidth Sensibly

As a rough rule of thumb, an uncompressed voice call uses around 100 kbps in each direction once overhead is included. Compressed codecs use less, sometimes with a small trade-off in quality.

Multiply by your peak number of simultaneous calls, then leave generous headroom for everything else on the line. A 20-person office rarely has 20 calls at once, but a sales team or reception desk can spike unexpectedly.

The bigger risk is competition for bandwidth. A single large file upload can swamp a modest line unless voice is prioritised. So the question is not only "is there enough capacity?" but also "does voice get first call on it?"

Router and Network Fixes That Make a Difference

Prioritise voice traffic

Quality of service (QoS) settings tell your router to treat voice packets as more important than downloads and updates. Many business routers support this, though basic ISP-supplied ones may not.

Check your router and firewall

Older routers can struggle with high volumes of small packets, and some firewalls interfere with voice traffic. Your provider should tell you which settings to check, and may recommend or supply a compatible router.

Use wired connections where you can

Desk phones and fixed workstations are more reliable on cable than on Wi-Fi. Save Wi-Fi for laptops and mobile devices.

Improve Wi-Fi where softphones are used

Coverage gaps, crowded channels and too many devices on one access point cause breakup during calls. A quick survey of where staff work, and where signal drops, often reveals simple fixes such as moving or adding an access point.

Separate voice from the rest where practical

Some businesses use a separate network segment for phones. This is not essential for a small office, but it can help in larger or busier environments.

Plan for power and backup

Voice depends on your router and switches staying on. A small UPS can cover short power cuts, and a 4G or 5G failover router can protect against a broadband failure.

A Realistic Example

Consider a 22-person architecture practice moving to hosted VoIP. Everything looks fine on paper: the broadband is quick and the plan is generous.

Before switching, the office manager runs speed tests at three times a day for a week. Download speeds are consistently good, but upload drops noticeably in the late afternoon, when the team uploads large drawings to cloud storage. A wired test call during one of these uploads sounds choppy.

Two fixes follow. The router's QoS settings are adjusted to prioritise voice, and large uploads are scheduled for the evening. A trial of five lines then runs for a fortnight, with no complaints.

Had the practice skipped testing, the problem would have appeared on day one, in front of clients.

What to Ask Your Provider

Network readiness should be a two-way conversation. Ask:

• What bandwidth and connection quality do you recommend for our size?
• Which routers and firewalls do you support or recommend?
• Can we run a trial or pilot on a small number of users?
• What tools do you offer to diagnose call quality problems?
• Who is responsible if the issue turns out to be on our side, and will you help investigate?
• Do you support failover, such as automatic call redirection to mobiles, if our connection drops?

A provider such as Wavetel Business, which works with UK organisations on VoIP and business communications, should be willing to discuss your network in practical terms before you commit, rather than just quoting the licence price.

Frequently Asked Questions

How much bandwidth do I need for hosted VoIP?

As a rough guide, allow around 100 kbps per simultaneous call in each direction, then add headroom for other traffic. Upload speed is often the constraint, so check it as well as download.

Why do my VoIP calls sound choppy?

Common causes include congested bandwidth, high jitter, packet loss, weak Wi-Fi or router settings that do not prioritise voice. Testing on a wired connection helps narrow it down.

Do I need a separate internet line for phones?

Not always. Many small offices run voice on their main connection with QoS enabled. A separate or backup line is worth considering where call reliability is critical.

Can I use Wi-Fi for VoIP calls?

Yes, particularly for softphone apps, but quality depends on coverage and congestion. Desk phones and fixed workstations are usually more reliable when wired.

Should I test before or after signing a contract?

Before, if possible. Ask for a trial, or at least run your own tests and share the results with the provider, so any network issues are known in advance.

Conclusion

Most hosted VoIP quality problems trace back to the network, not the phone system. Bandwidth, latency, jitter and packet loss decide how calls sound, and your router and Wi-Fi decide whether voice gets the priority it needs.

Your practical next step: run speed and quality tests at different times of day for a week, note your upload figures, and check how your router handles voice priority. Then ask providers for a small trial. A little testing now is far cheaper than fixing call quality after everyone has switched.