UCaaS troubleshooting is the process of diagnosing and resolving problems with cloud-based unified communications: poor call quality, dropped calls, registration failures, one-way audio, softphone connectivity, and inbound/outbound routing failures. Most UCaaS problems are not in the cloud provider's infrastructure — they occur in the network path between the user and the cloud, in device/app configuration, or in DNS/routing.
Diagnosing scope before diving in
Start with scope questions before any technical investigation.
| Question | One user affected | Everyone affected |
|---|---|---|
| What it suggests | Device/app/local network | Infrastructure, provider, or broad config |
| First check | Device settings, headset, local router | Provider status page, trunk registration, network path |
Inbound vs outbound direction also matters: inbound only = likely DID routing, SIP registration, or number config; outbound only = likely SIP trunk auth, routing rules, or carrier issue; both = SIP registration or broader connectivity.
Initial diagnostic checklist
- Check provider status page — rule out known outage before investigating.
- Confirm SIP registration status — is the trunk or softphone registered?
- Run a test call in both directions — characterize the symptom exactly (one-way audio? drops after 30s? can't connect at all?).
- Check network: run speed test, ping test to the cloud SBC, check for packet loss.
- Verify DNS resolves the SBC FQDN correctly.
- Check QoS settings — is VoIP traffic prioritized on the network?
- Check firewall rules — are required SIP and RTP ports open?
- Check headset/device — swap hardware to isolate.
Poor call quality (choppy audio, echo, robotic voice)
Causes: packet loss, jitter, high latency, codec mismatch, incorrect jitter buffer settings.
- Packet loss >1% noticeably degrades call quality; >3% makes calls unusable.
- Jitter >30ms without jitter buffer compensation causes choppy audio.
- Echo: usually acoustic feedback from headset/speaker, or acoustic echo cancellation disabled.
- Robotic/metallic voice: often G.729 codec at network congestion, or excessive jitter buffer delay.
See VoIP call quality for a full diagnostic treatment.
One-way audio
One party can hear the other but not vice versa. Most common cause: NAT/firewall issue — RTP media path blocked or asymmetric.
- Check: is SIP ALG enabled on the router? Disable it — SIP ALG breaks NAT traversal for VoIP.
- Check: are UDP ports for RTP (typically 10000–20000) open outbound and inbound?
- Check: does your SIP trunk provider require a specific local IP in the SDP?
See one-way audio in VoIP for a dedicated guide.
Calls failing to connect
No ringback, fast busy, or call immediately rejected. Check SIP response codes:
- 403 Forbidden: auth failure.
- 404 Not Found: DID routing problem.
- 503 Service Unavailable: provider or trunk down.
Outbound: verify SIP trunk credentials, outbound caller ID settings, any call blocking rules. Inbound: verify DID is provisioned, DID routes to correct endpoint/queue, SIP registration is current.
UCaaS softphone / app problems
- Can't log in: verify credentials, check SSO configuration, check MFA.
- Calls ring but can't answer: check audio permissions (microphone access), check headset selection.
- App crashes on call: check software version, try reinstalling, check OS audio driver conflicts.
- Poor quality on app but good on hardware phone: check computer network (VPN split-tunneling for VoIP, QoS on WiFi).
See softphone apps for device-specific guidance.
Registration failures
- SIP 401/407: authentication challenge — usually wrong credentials or IP ACL mismatch.
- SIP 403: auth rejected — wrong username/password or IP not whitelisted.
- SIP 503: provider endpoint unavailable.
- Registration timeout: network firewall closing UDP session before SIP keepalive — shorten SIP registration interval or use TCP SIP transport.
See SIP trunk registration failure for a step-by-step fix guide.
Dropped calls
- Drops at 30–32 seconds: classic symptom of SIP response packet not reaching caller (SIP BYE or ACK blocked by NAT); fix NAT traversal.
- Drops after 3–4 minutes: SIP session timer (RFC 4028) — one side is not sending re-INVITEs; check both sides support the same session timer behavior.
- Random drops: RTP timeout — media stream interrupted (packet loss event, congestion, NAT binding expired); check network stability and RTP timeout setting.
Remote worker / home office problems
- Home router: usually the culprit (SIP ALG, NAT issues, low-priority WiFi).
- VPN: if VoIP goes through VPN, check VPN server congestion and whether split-tunneling is configured to send VoIP direct.
- WiFi vs wired: VoIP over WiFi is sensitive to interference and channel congestion — recommend wired for critical users.
See VoIP redundancy for remote site failover design.
Collecting evidence for escalation
When escalating to your provider, include:
- Exact symptom description (one-way? drops? can't connect?).
- Direction (inbound/outbound/both).
- Scope (one user/one site/all users).
- Time of first occurrence and whether it is persistent or intermittent.
- SIP response codes from CDR.
- Call IDs (Call-ID header) from affected calls.
- Network test results (ping, traceroute, speed test to SBC IP).
- SIP capture if available (pcap file or HEP/Homer data).
- Any recent changes (new equipment, config change, ISP change, software update).
- Provider status page screenshot at time of incident.
