Business Phone System Not Working? A Troubleshooting Checklist

When a business phone system stops working, isolate the failure to one of five layers — power, network, the PBX itself, SIP registration/trunks, or the phones — and you can usually fix it or give support the exact fault in minutes instead of hours. Most outages are not the PBX; they are the network or a single device.

Definition: Phone-system troubleshooting is the process of isolating why calling fails — no dial tone, no incoming calls, one-way audio, or total outage — by testing each layer from the wall to the cloud.

Layer 1: Power and Internet

• Are the PBX, switches, and gateways powered, with no tripped PoE?
• Is the internet up? A VoIP-only outage (calls fail, email works) points to the SIP trunk or provider
• Did a recent power cut leave a device unplugged or in safe mode? Reboot in order: modem → router → switches → PBX → phones

Layer 2: The Network and VLAN/QoS

VoIP is sensitive to latency and jitter. Check:

• Voice VLAN configured, and phones actually on it
• QoS marking (DSCP/802.1p) present end-to-end
• MTU/jumbo frames not fragmenting SIP or RTP
• Firewall not blocking SIP (5060) or RTP (dynamic UDP) ports

Layer 3: SIP Registration and Trunks

Layer 4: The Phones

• Phone shows "no service"? It failed to register — check credentials and reachability to the PBX
• One phone dead, others fine? Likely the handset or its port, not the system
• Phantom calls or all phones rebooting? A bad firmware push or DHCP option

Layer 5: The PBX Core

If nothing registers and the admin page is unreachable, the PBX itself is the suspect: check CPU/memory, disk full, or a failed service. A configured backup and a survivable edge gateway turn a core failure from a company-wide outage into a local one.

A 10-Minute Isolation Routine

1. Call between two internal extensions — if that fails, the problem is local (PBX/network/phones)
2. Call an external number — if that fails but internal works, it is the trunk or provider
3. Check one phone vs. all — isolates handset vs. system
4. Check the voice VLAN and firewall rules
5. Reboot in the correct order and re-test

How Newrock Reduces Outages

Newrock's OM-series IP-PBX with edge gateways keeps local calling alive if the WAN or core fails, and UMS central management surfaces device health and alerts before a fault becomes an outage. Built-in diagnostics make the five-layer check faster for your IT team.

FAQ

Why do my VoIP calls have no audio but the call connects?

Classic one-way or no audio points to NAT or firewall blocking the RTP media path; check STUN/NAT settings and open the RTP UDP range on the firewall.

Internal calls work but external don't — what's wrong?

The PBX and phones are fine; the fault is the SIP trunk or provider. Check trunk registration and the carrier portal for the affected DIDs.

How do I stop outages from taking down the whole company?

Add a survivable edge gateway so branch or floor calling continues if the central link fails, and keep a recent PBX config backup.

Should I reboot the PBX first when phones die?

Not first. Test internal calls and a single phone to isolate the layer, then reboot in order: modem, router, switches, PBX, phones.

Bottom line: a methodical five-layer check — power, network, PBX, SIP/trunk, phones — turns panic into a precise fix, and resilient architecture turns a system fault into a minor local one.