VoIP & Business Communications

VoIP Call Quality Problems? 8 Network Issues Your IT Provider Should Have Fixed Already

NSN Management · Tulsa

A Tulsa accounting firm spent three weeks blaming their VoIP provider for choppy calls and dropped connections—only to discover their own network switch had been throttling voice traffic the entire time. The provider's service was fine. The problem was a network configuration issue that a proactive IT team would have caught before the first call ever went through.

If your business relies on VoIP phone systems and you're experiencing poor call quality, the fault almost certainly lies with your network—not your VoIP carrier. Most IT providers treat voice calls like any other application, but voice traffic is uniquely sensitive to conditions that barely affect email or web browsing.

Why Your VoIP Calls Sound Worse Than Your Old Landline

VoIP call quality suffers because voice traffic is extremely sensitive to packet loss, jitter, and latency—network conditions that don't noticeably affect email or file downloads. A 200-millisecond delay is barely perceptible when loading a website but makes two-way conversation nearly impossible because human brains struggle to process overlapping speech.

Why Network Issues Affect Voice Differently Than Data

Traditional data applications use TCP, which retransmits lost packets automatically. VoIP uses UDP, which sacrifices reliability for speed—dropped voice packets are gone forever. When your network loses 1% of packets, a file download might slow down slightly. That same 1% packet loss turns a phone call into a choppy, unintelligible mess.

Poor call quality is almost never the VoIP provider's fault. It's a network configuration problem your IT provider should have addressed during deployment. The eight issues below are all preventable—and all represent failures of reactive IT support.

Issue #1: Your Network Switch Doesn't Prioritize Voice Traffic (No QoS Configuration)

Network switches treat all traffic equally by default, meaning a large file backup can starve voice packets of bandwidth and cause choppy calls. Quality of Service (QoS) configuration tells managed switches to prioritize voice packets over file transfers, video streams, and general data traffic—ensuring calls remain clear even when the network is busy.

What Quality of Service (QoS) Does

QoS uses 802.1p or DSCP tagging to mark voice packets as high-priority. When a network switch sees a tagged voice packet and a tagged file transfer packet competing for the same bandwidth, the switch forwards the voice packet first. The file transfer waits a few milliseconds—imperceptible to the user—while the phone call remains crystal clear.

Real-World Scenario: Backups Kill Calls

Picture this: someone starts a large file backup to cloud storage at 10 a.m. Suddenly every active call goes choppy. Users complain. The IT provider blames the internet connection. The real problem? Voice packets and backup data are competing equally for bandwidth because no one configured QoS on the managed switch.

A proactive IT provider configures QoS tagging before the VoIP phone system goes live. Break-fix providers never touch switch configs unless something breaks—and by then, your team has already spent weeks frustrated by unusable phones.

Issue #2: Insufficient or Unmonitored Bandwidth

Each VoIP call requires approximately 100 kilobits per second of bandwidth including protocol overhead, so a 10-person office making simultaneous calls needs at least 1 Mbps of dedicated upload capacity. Many businesses have asymmetric internet connections where upload bandwidth becomes the bottleneck, causing call quality to degrade the moment multiple users are on the phone simultaneously.

Upload Bandwidth: The Hidden Bottleneck

Most business internet connections are asymmetric—offering far more download capacity than upload. A typical plan might deliver 100 Mbps download and only 10 Mbps upload. When three employees make calls (300 kbps total), send emails with attachments (2 Mbps), and sync files to the cloud (4 Mbps), upload capacity is maxed out. Voice packets get delayed, and calls turn choppy.

Proactive vs. Reactive Bandwidth Management

Proactive Managed IT Provider	Break-Fix IT Provider
Conducts bandwidth assessment before VoIP deployment	Assumes 'you have internet, so VoIP will work'
Monitors upload and download usage trends monthly	Only checks bandwidth after users complain
Right-sizes connection based on concurrent call projections	Recommends upgrades reactively after problems appear
Configures QoS to reserve bandwidth for voice traffic	Never modifies traffic shaping settings

A proactive provider calculates how many simultaneous calls your office makes during peak hours, multiplies by 100 kbps, and ensures your upload connection can handle that load plus routine data traffic. Reactive providers wait until your receptionist calls them screaming about dropped calls before they even think about bandwidth.

Issue #3: Outdated Firmware on Routers and Switches

Routers and switches running firmware from 2019 or earlier often contain bugs that cause intermittent packet loss or fail to honor QoS tags correctly, degrading VoIP call quality. Managed IT providers maintain firmware update schedules as part of routine maintenance, while break-fix providers only update networking devices when they completely fail or after users report persistent problems.

Known Firmware Bugs That Break VoIP

Certain Cisco RV-series small business routers shipped between 2018 and 2020 contained a firmware bug that caused SIP packet drops during high traffic periods. The router would appear to function normally—websites loaded, emails sent—but VoIP calls experienced random one-second audio gaps every few minutes. Cisco released a patch in mid-2020. Businesses whose IT providers never applied that patch continued experiencing problems for years.

Why Break-Fix Providers Avoid Firmware Updates

Firmware updates carry a small risk of causing configuration changes or temporary outages. Break-fix IT providers avoid that risk by simply never updating firmware unless a device fails completely. They don't maintain update schedules. They don't track vendor security bulletins. They assume 'if it's not broken, don't touch it.'

Managed IT providers treat firmware updates like oil changes—routine maintenance that prevents catastrophic failures. They test updates in non-production environments, schedule them during low-traffic windows, and document every change. When a VoIP-killing bug is patched, their clients never experience the problem because the firmware was already up to date.

Issue #4: Network Congestion from Unmanaged Devices (BYOD, Guest Wi-Fi)

Smartphones streaming video, guest tablets downloading updates, and personal laptops all consume bandwidth on the same network as VoIP phones unless VLANs and traffic shaping are configured to separate them. When unmanaged devices share the same network segment as business phones, their data-heavy activities can starve voice traffic and cause call quality to collapse during busy periods.

The Guest Wi-Fi Problem

A medical office in Tulsa configured guest Wi-Fi for patients in the waiting room. The IT provider set it up on the same network segment as the office VoIP phones. Every afternoon, when the waiting room filled up, multiple patients streamed video on their phones. The front desk phone became unusable—calls dropped mid-sentence, audio cut in and out, and the receptionist couldn't schedule appointments.

How Proactive IT Providers Segment Traffic

• Voice VLAN: Dedicated network segment for VoIP phones with strict QoS priority and monitored bandwidth
• Employee VLAN: Separate segment for staff computers and tablets with moderate QoS priority
• Guest VLAN: Isolated segment for visitor devices with no QoS priority and bandwidth throttling to prevent saturation
• IoT VLAN: Quarantined segment for smart devices, printers, and security cameras that don't need access to sensitive resources

A proactive IT provider segments voice traffic onto a dedicated VLAN during initial setup. Break-fix providers plug everything into the same switch and hope for the best. When call quality suffers, they blame the phones or the carrier—never their own failure to configure basic network segmentation.

Issue #5: Jitter and Packet Loss from Failing Ethernet Cabling

Damaged Cat5e cables, kinked patch cords, or cables run parallel to electrical conduit introduce electromagnetic interference that causes jitter and packet loss even though VoIP phones show link lights and appear connected. Physical layer problems create intermittent audio dropouts that break-fix providers dismiss as 'probably the internet,' while proactive providers test and certify cabling before deployment.

What Jitter Does to Voice Calls

Voice packets should arrive at steady intervals—one every 20 milliseconds. When cabling is damaged or poorly installed, packets arrive erratically: three packets at once, then nothing for 100 milliseconds, then two more. The VoIP phone's jitter buffer tries to smooth this out, but if jitter exceeds 30-40 milliseconds, audio becomes garbled or drops entirely.

Cabling Problems That Break VoIP

• Kinked patch cords: Cables bent at sharp angles near connectors develop intermittent connectivity that shows normal link lights but drops packets
• Cables near electrical conduit: Running data cables parallel to power lines for more than a few feet introduces electromagnetic interference
• Damaged Cat5e shielding: Cables crushed by furniture or pinched in cable trays lose shielding effectiveness and become susceptible to crosstalk
• Exceeding cable length limits: Cat5e and Cat6 cables lose signal integrity beyond 100 meters, causing errors that affect time-sensitive voice traffic

A proactive provider tests and certifies cabling with professional tools before installing phones. Reactive providers assume 'if it's plugged in, it's fine.' When users complain about choppy calls, the reactive provider blames the VoIP carrier and wastes weeks troubleshooting the wrong layer of the stack.

Issue #6: ISP-Level Issues Your IT Provider Should Be Monitoring

Some internet service providers deprioritize or block VoIP traffic—particularly SIP signaling over UDP port 5060—or have peering issues with VoIP carriers that cause one-way audio and registration failures. Proactive managed IT providers run SIP ALG checks, monitor for asymmetric routing, and coordinate with ISPs to resolve these issues; break-fix providers tell you to 'call your internet company' and wash their hands of the problem.

The One-Way Audio Problem

A Tulsa business experienced one-way audio on every outbound call: the person they called could hear them perfectly, but they heard nothing in return. The VoIP provider confirmed their servers were sending audio. The business owner spent $2,000 replacing phones and reconfiguring the system. The actual problem? Their ISP was blocking inbound SIP traffic on UDP port 5060 as an anti-spam measure.

ISP Issues Proactive Providers Catch Early

• SIP ALG interference at ISP level: Some ISPs enable Application Layer Gateway features on their own equipment that corrupt SIP headers
• Asymmetric routing: Outbound voice packets take one network path while inbound packets take another, causing timing mismatches
• Port blocking: ISPs block common VoIP ports to reduce spam calls or preserve their own phone service revenue
• Peering issues: Poor connectivity between the ISP and the VoIP carrier's network introduces latency or packet loss that doesn't affect general web traffic

A proactive managed IT provider coordinates with your ISP during VoIP deployment. They verify port availability, disable ISP-level SIP ALG, test for asymmetric routing, and document any carrier-specific configuration requirements. Break-fix providers hand you a phone and a support number, then blame the carrier when problems appear.

Issue #7: Firewall or Router Misconfiguration (SIP ALG Problems)

Many business routers include a feature called SIP Application Layer Gateway that attempts to assist VoIP traffic by rewriting SIP packet headers, but this feature often causes registration failures, one-way audio, and dropped calls by corrupting the very packets it's meant to help. SIP ALG should almost always be disabled on business routers when using modern VoIP systems—a simple checkbox setting that knowledgeable IT providers handle during initial firewall configuration.

SIP ALG intercepts SIP traffic passing through the router and modifies the IP addresses and port numbers embedded in SIP message headers. In theory, this helps devices behind NAT communicate with external SIP servers. In practice, most modern VoIP systems already handle NAT traversal correctly, and SIP ALG interference breaks working configurations.

When SIP ALG rewrites packet headers, it often creates mismatches between the connection information in SIP headers and the actual packet routing information. The VoIP server receives registration requests with incorrect contact information, sends responses to the wrong address, or drops packets it considers malformed. The result: phones that won't register, calls that connect but immediately disconnect, or audio that flows in only one direction.

How Proactive IT Providers Address Router Configuration

During network assessments, competent IT providers document every router and firewall in the voice path. They log into each device and verify SIP ALG status before deploying phones. If SIP ALG is enabled, they disable it and test call quality. They also configure proper port forwarding for SIP and RTP traffic, set up Quality of Service rules to prioritize voice packets, and document all changes in network configuration records.

Break-fix providers skip these steps because they're not billable until something breaks. When call quality issues surface weeks after deployment, they charge you troubleshooting time to discover problems they should have prevented.

Issue #8: Lack of Monitoring and No Performance Baseline

Without continuous monitoring and performance baselines, IT providers have no way to detect degrading network conditions before they affect call quality, forcing them into reactive troubleshooting mode instead of preventing problems altogether. Proactive IT providers deploy monitoring tools that track jitter, latency, packet loss, and bandwidth utilization continuously, alerting them to issues before users experience call quality problems.

Every network has performance variations throughout the day. Bandwidth utilization peaks during certain hours, latency spikes occasionally, and jitter fluctuates based on network load. These variations only become problems when you don't measure them and establish what's normal for your environment.

Break-fix IT providers deploy VoIP systems without baseline measurements. They have no record of your network's latency before VoIP implementation, no graphs showing typical jitter patterns, and no alerts configured to detect degrading performance. When users complain about call quality, these providers run speed tests and check for obvious problems, but they can't tell you whether current performance represents unusual degradation or typical network behavior.

Monitoring Tools Proactive Providers Deploy

• VoIP-specific monitoring: Tools that generate synthetic call traffic to test voice quality continuously, even when real calls aren't happening
• Network performance monitoring: Systems that track latency, jitter, and packet loss across all network segments, with VoIP-specific thresholds
• Bandwidth utilization tracking: Tools that identify when circuits approach capacity, allowing proactive upgrades before congestion affects voice quality
• PBX system monitoring: Platform-specific monitoring that tracks registration failures, call failures, and quality metrics reported by the VoIP system itself
• Alerting systems: Automated notifications when performance metrics exceed thresholds, allowing IT providers to investigate before users notice problems

These monitoring systems generate baseline data during the first weeks after deployment. The IT provider reviews metrics weekly, establishes normal ranges for each performance indicator, and configures alerts based on your specific network behavior. When performance degrades, the monitoring system detects the change immediately and alerts the IT team—often before a single call is affected.

With baseline data and continuous monitoring, IT providers diagnose problems quickly by comparing current metrics to historical norms. They can definitively state whether latency has increased, identify when degradation began, and correlate timing with network changes or external factors. This evidence-based approach resolves issues in hours rather than days.

The True Cost of Reactive IT Support for VoIP

Break-fix IT providers charge less upfront because they don't invest time in network assessments, QoS configuration, or monitoring deployment. This appears cost-effective until call quality problems emerge. Then you pay for:

• Emergency troubleshooting at premium hourly rates when calls drop during business hours
• Repeated site visits to "investigate" issues that baseline testing would have identified before deployment
• Lost productivity when staff can't communicate reliably with clients or colleagues
• Damaged client relationships when poor call quality makes your business appear unprofessional
• Replacement equipment purchases when the provider misdiagnoses network problems as hardware failures
• ISP circuit upgrades you didn't need because the provider couldn't identify the real bottleneck

The financial impact extends beyond direct IT costs. A manufacturing client switched from a break-fix provider to proactive management after experiencing intermittent call quality problems for eight months. The break-fix provider had made five on-site visits, replaced two phones, upgraded the Internet circuit unnecessarily, and still hadn't resolved the issue. The problem? A single Ethernet cable in the server room with a damaged connector was introducing intermittent packet loss—something basic network monitoring would have flagged immediately.

That client paid $8,400 in troubleshooting fees, $3,200 for unnecessary circuit upgrades, and lost an estimated $15,000 in staff productivity over eight months. The actual fix cost $40 and fifteen minutes of labor.

Questions to Ask Your IT Provider About VoIP Readiness

Before deploying VoIP or if you're experiencing call quality issues with your current system, ask your IT provider these specific questions:

1. "What is our current network latency, jitter, and packet loss to our VoIP provider's data center?" They should provide specific measurements, not vague assurances that "everything looks fine."
2. "What QoS configuration have you implemented on our routers and switches?" They should describe specific DSCP markings, traffic prioritization rules, and bandwidth reservations.
3. "How are you monitoring our VoIP call quality continuously?" They should name specific monitoring tools and explain what metrics they track.
4. "Is SIP ALG enabled on any of our network devices?" The answer should be a definitive "no" with documentation showing they've verified this on every device.
5. "What is our documented performance baseline for VoIP metrics?" They should show you graphs or reports proving they've established normal ranges for your network.
6. "What happens when your monitoring detects degrading call quality?" They should describe their alerting system and typical response procedures.

If your IT provider can't answer these questions with specific technical details, they're operating in break-fix mode—reacting to problems rather than preventing them. Your VoIP call quality will eventually suffer, and you'll pay troubleshooting fees to fix issues that proper planning would have prevented.

Moving from Reactive to Proactive VoIP Support

Transitioning to proactive IT management doesn't require replacing your entire VoIP system. A competent managed service provider will:

1. Conduct a comprehensive network assessment that documents current performance metrics, identifies configuration issues, and establishes baselines
2. Implement proper QoS configuration across all network devices in the voice path without disrupting existing services
3. Deploy monitoring tools that track VoIP-specific metrics continuously and alert the IT team when thresholds are exceeded
4. Document all network equipment and create configuration standards that prevent future issues
5. Create a documented response plan for VoIP issues so problems are resolved quickly using proven procedures rather than trial-and-error troubleshooting
6. Schedule regular network reviews to verify configurations remain optimal as your business grows and technology evolves

The transition typically takes 2-4 weeks and involves minimal disruption. The investment pays for itself through eliminated troubleshooting costs, improved productivity (no more dropped calls during important conversations), and better customer experiences.

The Real Cost of "Good Enough" VoIP Support

Many businesses tolerate mediocre VoIP call quality because they've normalized the problems. "It's good enough most of the time" becomes the accepted standard. But this acceptance carries hidden costs:

• Lost sales opportunities when prospects experience poor call quality and question your professionalism
• Frustrated employees who waste time repeating themselves or calling back after dropped connections
• Damaged client relationships when important conversations are interrupted by audio problems
• Recurring troubleshooting expenses as technicians repeatedly address symptoms without fixing underlying causes
• Opportunity cost of management time spent dealing with communication problems instead of strategic initiatives

A manufacturing company in Ohio calculated that their "occasional" VoIP problems were costing them approximately $3,200 monthly in wasted staff time, repeated troubleshooting charges, and one documented lost contract where the prospect cited communication difficulties as a concern. After implementing proper network configuration and monitoring, these costs disappeared entirely.

What Proactive VoIP Management Actually Looks Like

When your IT provider manages VoIP proactively, you'll notice several differences in how problems are handled—or rather, how they're prevented:

Before you experience issues: Your IT team receives alerts that jitter has increased from 8ms to 15ms on your primary internet connection. They investigate, discover a configuration change by your ISP, adjust QoS settings accordingly, and document the change. You never notice because call quality never degraded.

During expansion: Before you add new office locations, your IT provider analyzes bandwidth requirements, configures QoS on new equipment before deployment, and verifies call quality between locations during testing. Your first calls work perfectly because the network was prepared.

Regular optimization: Quarterly network reviews identify that your voice traffic has grown 30% over six months. Your IT team proactively increases bandwidth reservation and adjusts prioritization before congestion occurs.

Vendor coordination: When your VoIP provider pushes a system update, your IT team coordinates the change, monitors performance afterward, and verifies that all network configurations remain optimal for the new version.

This is the difference between reactive troubleshooting and proactive management. One approach keeps you constantly behind problems; the other prevents them from occurring.

Taking Action: Evaluating Your Current VoIP Support

If you recognize your situation in this article, start with an honest assessment of your current IT support:

1. Document your VoIP problems. Keep a log for two weeks noting every call quality issue, dropped call, or audio problem. Note the time, people involved, and symptoms.
2. Request your network documentation. Ask your IT provider for QoS configurations, network diagrams showing voice traffic paths, and monitoring reports for VoIP metrics.
3. Review your support tickets. Look at how many VoIP-related tickets you've opened in the past year and calculate the time spent on these issues.
4. Ask the critical questions. Use the questions from earlier in this article to gauge whether your IT provider is managing proactively or reactively.
5. Calculate the true cost. Consider not just direct troubleshooting expenses but also staff time, lost productivity, and potential business impact.

If this assessment reveals gaps in your current support, you have two options: work with your existing provider to implement proper VoIP management (if they have the expertise), or find a managed service provider who specializes in proactive network management.

Why These Problems Persist in IT Support

Understanding why VoIP call quality issues remain so common helps explain why they might exist in your environment:

Break-fix business models: Some IT providers still operate on break-fix billing, where they're paid to fix problems rather than prevent them. There's little financial incentive to implement configurations that eliminate billable troubleshooting.

Generalist technicians: VoIP requires specific networking knowledge that general IT support may lack. Understanding real-time protocol requirements, QoS implementation, and voice-specific monitoring isn't part of basic IT training.

Complexity avoidance: Proper VoIP configuration requires careful planning and testing. Some providers avoid this complexity, opting for "plug and play" installations that work initially but fail as networks evolve.

Invisible problems: Unlike a server crash or internet outage, degraded VoIP quality often manifests as "occasional" issues that don't trigger urgent responses. Problems persist because they're not quite bad enough to demand immediate attention.

Vendor finger-pointing: When issues occur, it's easy to blame the VoIP provider, internet service provider, or phone hardware rather than accepting responsibility for network configuration.

These systemic issues mean that finding IT support capable of truly proactive VoIP management requires asking the right questions and verifying technical capabilities rather than accepting general assurances.

Frequently Asked Questions