The short answer
Each symptom points somewhere different. Choppy or robotic audio usually means the connection is busy or the Wi-Fi is weak. One-way audio usually means a router or firewall is blocking the return path. A call that always drops at the same number of seconds is a timer or a device answering. Write down the time, the number and how long the call lasted, every time.
Decode the symptom
Find the line that sounds most like your problem. The middle column is where a technician will look first. The last column is what you can safely check or record yourself.
- You hearChoppy, robotic or breaking-up audioUsually points toPackets arriving late or not at all: a busy connection, weak Wi-Fi, or another device uploading.You canNote the time, whether it was on Wi-Fi or a cable, and what else was happening (backups, video calls, large uploads).
- You hearOne-way audio: one side cannot hearUsually points toA router or firewall letting audio out but not back in. Common with shared-building internet or a second router.You canNote which side could not hear, and whether it happens on every call or only some. Try the same call on the mobile app on mobile data.
- You hearCalls drop at the same number of secondsUsually points toA timer, not the internet. A session timer, a device answering, or a transfer rule firing.You canTime three dropped calls with a stopwatch. If they all end within a few seconds of each other, say so. That one detail saves hours.
- You hearCalls drop at randomUsually points toConnection dropouts, a failing handset or cable, or Wi-Fi roaming between access points.You canCheck whether it follows the person (one handset or app) or the place (one area or everyone).
- You hearEcho or talking over each otherUsually points toDelay on the path, or a speakerphone and headset feeding back.You canTry a wired headset on the same call path. Note whether it is your echo or the caller’s.
- You hearOutbound calls fail or say the number is unavailableUsually points toThe carrier rejecting the call, a barring rule, or a number format problem.You canWrite down the exact number dialled and the exact message or tone. Try one landline and one mobile number.
Why voice is fussy
A phone call uses very little internet, but it cannot wait. A web page that loads half a second late still loads. A word that arrives half a second late is gone. That is why calls can break up on a connection that looks fast on a speed test.
- 58–76 kbpsRough audio use of one call each way, per Microsoft’s Teams phone estimates. A call is small.Source: Microsoft Learn
- 150 msThe one-way delay the ITU recommends staying under for most conversations to feel natural.Source: ITU-T G.114
- 1 busy uploadis often enough to break calls. Backups, cloud sync and cameras fill the upload side first.See the bandwidth calculator guide
So the fix is rarely “buy a faster plan”. It is usually finding what else is using the connection at the same moment, or what is blocking the audio’s return path.
Safe checks you can do
None of these change settings. They narrow down where the problem lives, which is most of the work.
One person, or everyone?
YouAsk two colleagues whether they have the same problem today. One handset or app points at that device. Everyone points at the connection or the phone service.
Cable or Wi-Fi?
YouIf the bad calls are on a softphone over Wi-Fi, make a test call from a computer plugged in with a cable, or standing next to the access point. If that is clean, the Wi-Fi is the suspect. See Slow internet? A 10-minute test that shows where the problem is.
Make a long test call
YouRing a mobile from the office phone and stay on for at least two minutes. Short test calls hide drops that happen at 30 or 40 seconds.
Check the clock
YouDoes it happen at the same time each day? Lunchtime, when the backup runs, or when everyone joins a video meeting? Time patterns point at something sharing the connection.
Check for a wider outage
YouIf calls and internet are both bad, follow Business internet down? Safe first checks before anything else.
Leave the router alone
Your adminRestarting or resetting a router can wipe the settings the phones depend on, and calls can stop until the port forwarding is rebuilt. Ask first.
What a technician checks next
Your log decides where they start. These are the usual suspects behind the symptoms above.
- Network
Double NAT and CGNAT
When the connection sits behind a second router or a carrier-grade NAT (the modem’s internet address is in the shared 100.64.0.0/10 range instead of a true public address), audio can flow one way only. The fix is usually a public or static IP or a router change.
- Router
SIP ALG and port forwarding
Some routers “help” with phone traffic and break it instead. Port forwards can end up on the wrong interface after a modem swap.
- Capacity
Upload and priority
Whether something fills the upload at call times, and whether voice is given priority over everything else.
- Devices
Handsets and timers
Firmware, cabling, a cordless handset set to answer automatically, or a group timer moving the call.
- Carrier
The call trace
Signalling logs show whether the carrier rejected or ended the call. That is why the exact time and number matter.
Write it up so it gets fixed
- Hard to act on
“The phones have been dropping out all week, it’s really bad, please fix ASAP.”
- Easy to act on
“Three inbound calls to the main number dropped today at 9:42, 11:15 and 2:03, each at about 40 seconds. Reception desk phone, cabled. Other staff fine. Outbound calls OK.”
Send the log through your normal support route. Never include passwords or sign-in codes. See How to raise an IT support request without sharing secrets.
Sources and further reading
- ITU-T G.114: One-way transmission time
- RFC 6598: Shared address space for carrier-grade NAT (100.64.0.0/10)
- Microsoft Learn: QoS on Teams phones (audio bandwidth estimates)
- Microsoft Learn: Prepare your organisation’s network for Teams (bandwidth requirements)
Checked 12 November 2026. Product menus and provider rules change; check the linked source if something looks different.