Common Business VoIP Issues, Causes and Fixes: The NZ IT Troubleshooting Guide
Common VoIP Issues, Causes and Troubleshooting Solutions in NZ
Business Voice over Internet Protocol (VoIP) systems allow organisations to make and receive telephone calls over internet connections rather than relying exclusively on traditional telephone infrastructure. However, call quality, reliability and availability depend on network performance, firewall configuration, internet connectivity and power resilience.
For New Zealand businesses using cloud-based phone systems such as 3CX, common problems include choppy audio, call delays, dropped calls, one-way audio, phone registration failures and service interruptions during power or fibre outages.
This guide explains how to diagnose common business VoIP issues, identify their underlying causes and implement practical fixes. It also outlines how network readiness assessments, Quality of Service (QoS), firewall configuration, mobile failover and business continuity planning can help organisations maintain reliable communications.
Business VoIP Troubleshooting: Explained in 60 Seconds
Most business VoIP problems fall into four categories: network performance, firewall configuration, endpoint or device issues, and service availability.
Choppy or robotic audio is commonly associated with network jitter, packet loss, congestion or wireless interference.
Delayed conversations can indicate excessive network latency, routing inefficiencies or congestion.
One-way audio and dropped calls may result from firewall settings, Network Address Translation (NAT), SIP ALG interference or incorrect session configuration.
Phones that cannot register may have connectivity, authentication, DNS, firewall or provisioning issues.
Calls interrupted by power or fibre outages require an appropriate continuity plan, such as mobile call forwarding, cellular connectivity or battery backup.
Businesses can reduce these risks by assessing their network before deployment, prioritising voice traffic where supported, using suitable network equipment, validating firewall configurations and testing failover arrangements.
Sharp New Zealand provides business communications solutions, including 3CX phone systems and associated network services, to help organisations plan and support reliable workplace communications.
Diagnosing Business VoIP Quality and Network Performance
How does business VoIP work?
Business VoIP converts voice into digital data packets that travel across IP networks. The receiving device reconstructs those packets into audible speech, allowing calls to take place over a business network, broadband connection or mobile data service.
Unlike email or file transfers, voice communication is sensitive to delays and variations in packet delivery. A file can often tolerate retransmission and additional delivery time, whereas a delayed voice packet may arrive too late to be useful during a live conversation.
A reliable VoIP deployment therefore requires more than sufficient internet download speed. It needs consistent connectivity, appropriate upload capacity, low packet loss, controlled latency and suitable configuration across the network.
Why network readiness matters for New Zealand businesses
Many organisations use their internet connections for Microsoft 365, cloud backups, video conferencing, business applications, remote access and telephone calls simultaneously. If these services compete for limited bandwidth, real-time voice traffic may experience congestion.
Other potential problems include poorly configured routers, unsuitable Wi-Fi coverage, outdated firewall firmware, incorrect DNS settings and insufficient backup connectivity.
Before introducing a cloud phone system or troubleshooting persistent call quality issues, IT teams should assess:
Available upload and download bandwidth during peak business hours.
Latency, jitter and packet loss between the office and the phone service.
Router, firewall and switch compatibility.
Wired and wireless network performance.
Power supply and fibre connectivity dependencies.
Remote-worker connectivity and mobile failover arrangements.
Firewall rules, device provisioning and security requirements.
A network readiness assessment can identify these issues before they affect staff, customers or business-critical calls.
Issue 1: Choppy Audio, Jitter and Latency
Choppy, distorted or robotic audio is one of the most common business VoIP complaints. It can make conversations difficult to understand and reduce the professionalism of customer interactions.
What is VoIP jitter?
Jitter is the variation in the time it takes voice packets to arrive at their destination. When packets arrive inconsistently, the receiving device may struggle to reconstruct smooth audio.
Common symptoms include:
Robotic or broken-up speech.
Audio that briefly cuts in and out.
Words or syllables disappearing during conversations.
Call quality deteriorating when the office network is busy.
As a practical starting point, aim for jitter below 30 milliseconds, while recognising that the appropriate threshold depends on the phone platform, codec, jitter buffer and service provider requirements.
What is VoIP latency?
Latency is the time taken for data to travel between endpoints. Excessive delay creates an unnatural conversation because participants may begin speaking before the other person has finished.
Symptoms can include:
Noticeable delays between speaking and hearing a response.
Participants talking over one another.
Slow conversational turn-taking.
Longer delays for calls involving remote sites or additional network routing.
A commonly used planning target is one-way network latency below approximately 150 milliseconds. This is not the same as round-trip latency, which measures the journey in both directions. Lower latency is generally preferable, particularly for interactive business calls.
What is packet loss?
Packet loss occurs when voice packets fail to reach their destination. Lost packets may result in missing words, distorted speech or brief periods of silence.
For planning purposes, aim for packet loss below 1%, with lower levels preferable for consistently clear audio. Some services may specify stricter limits.
Common causes of poor VoIP call quality
1. Network congestion
Large file transfers, cloud backups, software updates and video meetings can compete with voice traffic, particularly on connections with limited upload capacity.
2. Inadequate Quality of Service configuration
Without suitable traffic management, network equipment may not prioritise real-time voice packets when congestion occurs.
3. Wi-Fi interference
Wireless interference, weak signal strength, channel congestion and roaming between access points can interrupt voice packets.
4. Unreliable network equipment
Overloaded routers, faulty Ethernet cables, outdated firmware and poorly configured switches can affect voice performance.
5. Internet service issues
Congestion or packet loss beyond the local network may originate from the internet service provider or the route to the hosted phone platform.
How to improve VoIP call quality
Implement Quality of Service (QoS). Configure supported network equipment to prioritise voice traffic during congestion. Correct QoS configuration may involve traffic classification, DSCP markings, queue management and appropriate bandwidth allocation. Do not assume that every SIP port or packet should automatically receive priority; follow the phone platform and network equipment documentation.
Use wired connections for desk phones. Connect IP phones to suitable Ethernet switches using reliable cabling. Power over Ethernet (PoE) can supply compatible phones with power through the same cable used for network connectivity.
Optimise Wi-Fi for softphones. Where wireless use is necessary, assess signal strength, channel interference, access point capacity and roaming behaviour. A well-designed 5 GHz or newer Wi-Fi deployment may help, but changing frequency bands alone will not fix congestion or poor coverage.
Test during peak usage. Measure network performance while employees are using their usual business applications. An idle network test may not reveal congestion that appears during the working day.
Investigate the source of packet loss. Compare tests across the local network, internet connection and relevant service endpoints to determine whether the issue is local or external.
Issue 2: One-Way Audio, Dropped Calls and SIP ALG Conflicts
One-way audio occurs when one participant can hear the other, but the reverse audio path fails. Other symptoms include calls that disconnect unexpectedly, phones that fail to register or calls that work internally but fail externally.
Firewall and NAT configuration are possible causes, although these symptoms can also originate from routing, media negotiation, endpoint settings or the phone service itself.
What is SIP ALG?
SIP Application Layer Gateway (SIP ALG) is a router or firewall feature designed to inspect and modify Session Initiation Protocol (SIP) traffic to help it operate through NAT.
SIP establishes and manages call sessions, while voice media commonly travels through separate Real-time Transport Protocol (RTP) streams.
Some SIP ALG implementations modify signalling information in ways that conflict with a particular VoIP platform's connection method. This can result in failed call setup, one-way audio or unexpected disconnections.
However, SIP ALG is not universally harmful. Whether it should be disabled depends on the phone platform, firewall vendor and network design.
Common symptoms of firewall or NAT problems
One participant can hear the other, but not vice versa.
Calls connect successfully but disconnect after a short period.
Incoming calls fail while outgoing calls work.
IP phones repeatedly lose registration.
Remote offices experience problems that do not affect the main office.
Calls fail when users connect through a particular router or firewall.
A disconnection at approximately 30 to 32 seconds can be a useful diagnostic clue in some SIP configurations, but it is not definitive proof of a firewall problem.
How to troubleshoot SIP ALG and firewall configuration
Step 1: Confirm the scope of the issue.
Establish whether the problem affects all phones, a single extension, one location, external calls only or a particular internet connection. This helps narrow the possible causes.
Step 2: Review the firewall configuration.
Check the firewall vendor's documentation and the phone platform's current network requirements. If SIP ALG is known to conflict with the deployment, disable it in accordance with the supported configuration.
Step 3: Validate NAT and firewall rules.
Confirm that required signalling and media traffic can travel between the relevant endpoints. Avoid opening unnecessary ports or exposing phone-system interfaces directly to the internet.
Step 4: Check the supported remote-office connection method.
For 3CX deployments, a Session Border Controller (SBC) may be appropriate for connecting supported remote phones to a central or hosted PBX. The SBC provides a managed connection method designed for the platform's requirements.
An SBC does not eliminate every firewall or network issue, and it should not be described as bypassing all inspection or security controls. Follow the current 3CX configuration and security guidance for the chosen deployment.
Step 5: Review logs and repeat the test.
Inspect firewall logs, phone-system events and call details where available. Repeat inbound and outbound calls after each controlled configuration change.
Why port requirements should be checked rather than assumed
VoIP systems use different ports and transport protocols depending on their configuration. SIP signalling, RTP media, SBC connections, provisioning and other services may have separate requirements.
For example, port 5060 is commonly associated with SIP, while 5061 is commonly associated with SIP over TLS in applicable configurations. Port 5090 is used by the 3CX SBC in supported configurations.
These are not universal instructions to forward every port to every phone. The correct configuration depends on the 3CX version, deployment architecture, firewall and provider requirements.
Issue 3: Echo, Headset Problems and Poor Audio at the Endpoint
Not every VoIP problem originates in the internet connection. Audio equipment and endpoint configuration can also cause poor call quality.
Why does a VoIP call echo?
Echo occurs when audio from a speaker or headset microphone is picked up and transmitted back to the other participant. It can also arise from acoustic feedback, analogue interfaces or endpoint processing problems.
Common causes include:
Using a speakerphone at high volume.
Microphone gain set too high.
Poorly positioned microphones.
Incompatible or faulty headsets.
Incorrect acoustic echo cancellation settings.
Problems with analogue telephone adapters or gateways.
How to reduce echo
Test the call with a known-good headset.
Reduce speaker volume and adjust microphone sensitivity.
Check headset firmware, drivers and compatibility.
Test a different phone or softphone to determine whether the issue follows the device.
If the issue persists across devices, investigate the phone platform, analogue equipment and network path.
If only one employee experiences echo, start with their headset, device settings and local environment. If multiple users report the same issue, investigate shared equipment and the wider phone service.
Issue 4: IP Phones Not Registering or Losing Connectivity
An IP phone must connect to the relevant phone service and authenticate successfully before it can operate as intended. Registration problems can prevent users from making or receiving calls.
Common causes of registration failure
Incorrect extension credentials or provisioning details.
DNS resolution failures.
Internet connectivity interruptions.
Firewall rules blocking required traffic.
Incorrect date and time settings affecting certificate validation.
Expired certificates or authentication problems.
Unsupported firmware or configuration changes.
DHCP or VLAN configuration errors.
Recommended troubleshooting process
Check basic connectivity. Confirm that the phone has a valid IP address, gateway and DNS configuration.
Verify provisioning and authentication. Review the extension configuration and provisioning process using the approved management interface. Do not share passwords or authentication tokens in support tickets or public troubleshooting discussions.
Check DNS and time synchronisation. Incorrect DNS resolution or system time can prevent devices from reaching the expected service or validating certificates.
Review firewall and VLAN settings. Confirm that the phone's network segment permits the traffic required by the deployment.
Check platform status and logs. Determine whether the problem affects a single device, a site or the wider hosted service.
If multiple phones lose registration simultaneously, prioritise investigation of shared dependencies such as internet connectivity, DNS, firewall changes and service availability.
Issue 5: Power Cuts, Fibre Outages and Business Continuity
Cloud phone systems can improve resilience by separating the hosted PBX from the physical office. However, cloud hosting does not make every part of the phone service immune to local outages.
In New Zealand, a fibre connection's optical network terminal (ONT), router, network switches, access points and desk phones may all depend on local electricity. A cloud PBX may remain operational during an office power cut while employees lose access to it.
Similarly, a fibre outage can disconnect the office from the hosted phone platform even when the office still has power.
How do cloud phone systems behave during a local power outage?
A cloud-hosted PBX can continue operating in its hosting environment if the service and its supporting infrastructure remain available. Calls may still be routed according to the configured call flows, but employees cannot use unpowered office equipment or an unavailable internet connection.
Whether incoming calls can be redirected depends on the system configuration, available carrier services and the destination's connectivity.
Business continuity strategies for VoIP
1. Configure mobile call handling.
Where supported, configure call forwarding, ring groups or other routing rules to direct incoming calls to nominated mobile numbers during an outage.
2. Use mobile softphones where appropriate.
A supported 3CX mobile application can allow staff to make or receive calls through an available internet connection. Cellular data may provide an alternative to office broadband, subject to mobile coverage, service configuration and device battery life.
3. Install an appropriately sized UPS.
An Uninterruptible Power Supply can keep selected network equipment operating during a power interruption. Depending on the design, this may include the fibre ONT, router, switches and essential phones.
Runtime varies with battery capacity, equipment power consumption, battery condition and load. Do not assume a UPS will provide two to four hours of service without calculating and testing the expected runtime.
4. Assess backup internet connectivity.
A compatible 4G or 5G router may provide a backup path if the primary fibre connection fails. Confirm that failover is configured and that the phone service can use the alternate connection.
5. Document and test the recovery plan.
Record the people responsible for activating the plan, the destination numbers for forwarded calls, the required network equipment and the process for restoring normal service.
VoIP outage readiness checklist
Before relying on a cloud phone system for business-critical communications, confirm that:
Incoming calls have a documented alternative routing destination.
Staff know how to use the approved mobile calling method.
The backup mobile or internet connection has been tested.
Critical network equipment has suitable battery backup where required.
Contact centre, reception and emergency communication requirements have been considered.
Recovery procedures are documented and periodically tested.
A continuity plan should reflect the organisation's operating hours, customer service commitments, physical locations and risk tolerance.
VoIP Troubleshooting Quick Reference Matrix
Use this table to identify likely causes and the first actions to investigate. Symptoms can have multiple causes, so confirm the underlying issue before making production network changes.
| Symptom | Possible root cause | Recommended first action |
| Choppy or garbled audio | Jitter, packet loss, congestion or Wi-Fi interference | Measure network quality during peak use; inspect QoS and local connectivity |
| Delayed conversations | High latency, inefficient routing or congestion | Measure one-way latency where possible and investigate the network path |
| One-way audio | NAT, firewall, media routing or endpoint configuration | Review firewall logs, media paths and supported NAT settings |
| Calls dropping after approximately 30 seconds | SIP signalling, firewall state, NAT or session-handling issue | Check SIP traces and firewall logs; verify the call's disconnection reason |
| Echo during calls | Acoustic feedback, headset or microphone configuration | Test a known-good headset and adjust audio settings |
| Incoming calls fail | Call routing, provider, registration or firewall issue | Test outbound calls and review inbound routing and provider status |
| IP phones fail to register | Authentication, DNS, provisioning, firewall or connectivity issue | Check device IP configuration, registration status and logs |
| Phones stop working during a power cut | ONT, router, switch or phone has lost power | Test UPS coverage and confirm mobile call routing |
| Office phones fail during a fibre outage | Primary internet connection unavailable | Test backup connectivity and alternative call handling |
| Remote users experience poor calls | Home Wi-Fi, ISP routing, VPN or device issues | Compare a wired test, local network results and the approved remote-access configuration |
How Much Internet Bandwidth Does Business VoIP Need?
The bandwidth required by a business phone system depends on the audio codec, packetisation interval, transport overhead and number of concurrent calls.
A useful preliminary estimate is approximately 100 Kbps of upload bandwidth and 100 Kbps of download bandwidth per active call. This is a planning estimate, not a universal guarantee or a complete network capacity calculation.
For example, 20 simultaneous calls could require approximately 2 Mbps in each direction for voice traffic under this simplified assumption. Additional capacity is needed for other business applications, network overhead, traffic bursts and resilience.
Businesses should size their internet connections for concurrent calls during peak demand rather than simply counting registered extensions.
A suitable assessment considers:
The maximum number of simultaneous calls.
Available upload and download capacity.
Other applications competing for bandwidth.
Whether QoS is supported and correctly configured.
Performance during peak usage.
The availability of a secondary connection if the primary service fails.
A faster broadband plan may help where bandwidth is the bottleneck, but it will not automatically resolve poor Wi-Fi coverage, firewall misconfiguration, excessive routing latency or faulty equipment.
How to Test Network Readiness Before Switching to VoIP
A pre-deployment network readiness assessment helps determine whether an organisation's existing infrastructure can support its proposed phone system.
Rather than relying on a single speed test, IT teams should assess the network under realistic operating conditions.
Step 1: Establish a baseline
Record current download and upload speeds, latency, packet loss and jitter. Repeat measurements at different times, including periods of high business activity.
Step 2: Test the local network
Check Ethernet connections, switch performance, Wi-Fi coverage, VLAN configuration and the condition of routers and access points.
Where possible, compare a wired endpoint with a wireless endpoint to identify whether the problem is local to Wi-Fi.
Step 3: Confirm firewall and platform compatibility
Review the current requirements for the chosen phone system, including supported ports, transport protocols, DNS, security controls and remote-office connectivity.
For 3CX deployments, use the documentation appropriate to the specific version and architecture.
Step 4: Assess concurrent-call capacity
Estimate expected peak simultaneous calls and calculate bandwidth requirements using the selected codec and the service provider's guidance. Include other business traffic and appropriate capacity headroom.
Step 5: Test real call scenarios
Make inbound and outbound calls, test calls between locations, assess headset and mobile-app performance, and check call quality during normal business activity.
Step 6: Validate resilience
Where continuity is important, test the procedures for internet failure, office power loss, mobile failover and recovery. A backup connection that has never been tested should not be treated as a proven continuity solution.
Step 7: Document findings and corrective actions
Create a record of identified issues, their priority, recommended changes, responsible owners and retest results. This provides a baseline for ongoing service management.
Sharp NZ can help businesses evaluate their business communications requirements and determine whether their network, phone configuration and support arrangements are suitable for a planned deployment.
Choosing a Business VoIP Solution and Support Partner in NZ
Selecting a business phone system involves more than comparing call features or monthly prices. Organisations should evaluate network readiness, deployment architecture, ongoing support, security, integration requirements and business continuity.
A practical assessment should include:
Call quality: How are latency, jitter and packet loss measured and investigated?
Network readiness: Can the provider assess the existing LAN, WAN, firewall and Wi-Fi environment?
Deployment model: Is a cloud-hosted PBX, on-premises system or hybrid configuration most appropriate?
Security: How are authentication, encryption, access controls and software updates managed?
Resilience: What happens if the office loses power, fibre connectivity or access to a critical network component?
Support: Who is responsible for diagnosing issues across the phone platform, internet connection and local network?
Scalability: Can the solution accommodate new users, additional sites and changing call volumes?
Ongoing management: Are monitoring, maintenance and configuration reviews available?
How Sharp NZ supports business communications
Sharp New Zealand offers business communications solutions, including 3CX phone systems and related network services. By considering the phone platform alongside the network and support environment, businesses can plan a solution that better aligns with their operational requirements.
Sharp's approach is to make technology easy by helping organisations understand their requirements, identify potential technical issues and select an appropriate solution for their workplace.
Businesses considering a new phone system or experiencing persistent VoIP issues can explore Sharp's Business Phone Systems offering or review Sharp Managed WAN and Router Security to understand the available connectivity and network services.
Frequently Asked Questions About Business VoIP Issues
Why is my business VoIP phone call choppy?
Choppy VoIP audio is commonly caused by jitter, packet loss, network congestion or wireless interference. Measure network performance during peak usage, check the local connection and review QoS settings where supported. If the issue persists, investigate the internet connection and phone service path.
What is the recommended jitter level for business VoIP?
A practical planning target is below 30 milliseconds of jitter. The appropriate threshold depends on the phone platform, codec, jitter buffer and service provider requirements. Lower and more consistent jitter generally supports better call quality.
What latency is acceptable for business VoIP?
A commonly used target is below approximately 150 milliseconds of one-way network latency. Round-trip latency measures both directions and should not be confused with one-way latency. The full end-to-end delay also depends on endpoint processing, codecs and other parts of the call path.
How much bandwidth does each VoIP call need?
Approximately 100 Kbps in each direction per active call is a useful preliminary planning estimate for many business VoIP scenarios. Actual requirements vary with the codec, packetisation, transport overhead and configuration. Businesses should calculate capacity using the phone platform's specifications and expected concurrent calls.
Why can I hear the caller but they cannot hear me?
One-way audio can result from firewall or NAT problems, blocked media traffic, incorrect routing, endpoint configuration or service issues. Review the firewall and call logs, confirm the supported network configuration and test whether the problem affects multiple devices.
Should SIP ALG be disabled for 3CX?
SIP ALG can interfere with some 3CX deployments by modifying SIP signalling. However, the correct setting depends on the firewall, phone system version and network design. Check the current 3CX and firewall documentation before changing the setting, and validate the result with controlled call tests.
Why do some VoIP calls disconnect after 30 or 32 seconds?
A repeatable disconnection after approximately 30 to 32 seconds can indicate a SIP signalling, NAT or firewall session-handling issue. It is a diagnostic clue rather than a definitive diagnosis. Review SIP traces and firewall logs to establish why the call is being terminated.
Will a cloud phone system keep working during a power cut?
A cloud-hosted PBX can remain operational in its hosting environment during a local office power cut, but office phones and network equipment may stop working. Continuity depends on power backup, internet availability, mobile access and call-routing configuration.
Can I use a 3CX mobile app during an office internet outage?
A supported 3CX mobile application may continue to provide calling through an available cellular data connection, provided the service, account configuration and mobile network remain operational. Incoming call handling may also require appropriate routing configuration. Test the arrangement before relying on it during an outage.
How can I test whether my network is ready for VoIP?
Measure latency, jitter, packet loss and bandwidth under realistic business conditions. Check the LAN, Wi-Fi, firewall and remote-office connections, then test actual inbound and outbound calls. Confirm that the network supports the phone platform's current requirements and document any corrective actions.
Does faster internet always fix VoIP problems?
No. Faster internet may improve performance when insufficient bandwidth is the cause, but it will not necessarily fix packet loss, poor Wi-Fi, incorrect firewall settings, excessive routing latency or faulty endpoint equipment. Diagnose the actual bottleneck before upgrading the connection.
What should a New Zealand business include in its VoIP outage plan?
An outage plan should cover mobile call routing, alternative internet connectivity where appropriate, battery backup for critical network equipment, staff communication procedures and documented recovery steps. The plan should be tested periodically and tailored to the organisation's operational requirements.
Final Recommendations: Building a More Reliable Business Phone System
Reliable business VoIP depends on the combined performance of the phone platform, local network, internet connection, firewall configuration, endpoint devices and continuity arrangements.
New Zealand organisations can reduce the risk of poor call quality and service interruptions by:
Measuring jitter, latency and packet loss during peak business usage.
Prioritising voice traffic through appropriate QoS configuration.
Using reliable wired connections for desk phones where practical.
Reviewing SIP ALG, NAT and firewall behaviour against the supported phone-system configuration.
Investigating headset, device registration and DNS issues as well as network faults.
Preparing mobile call-routing and backup connectivity arrangements.
Testing the network and documenting results before deployment and during ongoing support reviews.
For organisations planning a new deployment or investigating recurring call quality issues, a structured network assessment provides a practical starting point.
Explore Sharp NZ Business Phone Systems to learn more about Sharp's business communications solutions, including 3CX, or visit Sharp Managed WAN and Router Security to explore related network services.
Make technology easy with Sharp NZ.
Kimberley Holden is Brand & Communications Manager at Sharp New Zealand, where she leads strategic marketing, brand development, and customer communications across Sharp’s portfolio of consumer products and workplace technology solutions, including print, visual solutions, visitor management, voice and data, and software. She brings a strong focus on clear messaging, customer engagement, and delivering consistent brand experiences across complex technology environments.