Why calls go missing

Many "broken" phone systems are just set up wrong.

When calls ring the wrong desk, go to voicemail at lunchtime or never reach a team, the hardware is usually fine. Something in the call's path is set up in a way nobody expected: a number matched to an old destination, a time profile that thinks it's a bank holiday, a hunt group that still lists someone who left last year.

Every business phone system, from an Avaya IP Office in a ten-person office to a Cisco cluster across several sites, makes the same handful of decisions for every call. If you know which decision went wrong, you know where to look. That's what this hub is for: matching what you hear to the exact setting that causes it, before anyone changes anything.

We write for the person who looks after the phones alongside their real job, office managers, IT generalists and practice managers, and we keep the deep reference material for engineers further down every page.

Six stages. Six kinds of fault.

Match the symptom to the stage before changing anything. Each stage has its own guide, a diagram of the call, and a first check that's safe to do.

01

Line

No calls at all, an engaged tone for callers, or one number that's gone dead.

First check: do outgoing calls work? If not, talk to your carrier before touching the system.

Read the guide →
02

Incoming route

Calls land on the wrong person or team, or a direct number rings reception.

First check: note the exact number dialled, then find the route that matches it.

Read the guide →
03

Time profile

Out-of-hours handling switches on at lunch, stays on in the morning, or misses a bank holiday.

First check: write down when it happens and compare it with the profile's hours.

Read the guide →
04

Hunt group

Some team phones never ring, or calls always go to the same person first.

First check: compare the group's members and ring pattern with who actually rang.

Read the guide →
05

User

Calls vanish into Do Not Disturb, a forward to an old mobile, or a logged-out handset.

First check: look at the user's DND and forwarding status, not their phone.

Read the guide →
06

Voicemail

Callers hit voicemail too soon, never get it, or hear the wrong greeting.

First check: check the no-answer time and which mailbox the call falls back to.

Read the guide →

Built for the systems UK offices still run.

We go deepest on Avaya IP Office, with a smaller set of guides for Mitel, Cisco and NEC.

Guides live

Avaya IP Office

Still one of the most common small-business systems in the UK. Guides cover incoming call routes, hunt groups, time profiles and night service, SIP lines and handsets, plus what its support status means for you.

Open the Avaya IP Office guides →
Guides live

Mitel MiVoice

Phones not ringing, MiVoice Office 250 status, and manuals, and how to plan around the system's support status.

Open the Mitel MiVoice guides →
Guides live

Cisco CUCM

Phones that won't register, and finding your model's guide.

Open the Cisco CUCM guides →
Guides live

NEC UNIVERGE

SV9100 phones not ringing, and desk phone basics.

Open the NEC UNIVERGE guides →

How to use the hub.

Three steps, whatever the system. You only need to read as far as your problem goes.

1

Describe what callers hear

Start from the symptom, not the setting. "Reception's phone rings for the sales line" is more useful than "the router is wrong". The search above and every guide begin there.

2

Find the stage

Each guide names the stage most likely to cause that symptom, shows the call's route on an animated diagram, and explains the setting in plain English.

3

Check safely, then decide

Follow read-only checks in order. If the fix needs a configuration change you're not sure about, stop there: you'll know exactly what to tell your maintainer, or you can ask us.

Common questions.

Is it safe to follow these guides on a live system?

Every guide starts with read-only checks: looking, noting and test-calling, not changing. Where a fix needs a configuration change, we say so clearly, explain what it affects, and suggest you take a backup or ask your maintainer first.

Do I need engineer access to my phone system?

Not for most first checks. Many faults can be narrowed down by making a test call and noting what happens. Some later steps need administrator access to the system's management tool, and the guide tells you when you've reached that point.

My system is old. Should I just replace it?

Not automatically. An older system that's configured well can keep running for years, and replacing it brings its own costs and risks. Our decision guide and replacement assessment walk through support status, parts, lines and your team's needs, and compares staying put fairly with moving to options such as 3CX or Teams Phone.

What does the ISDN and analogue switch-off mean for my phones?

UK providers are retiring traditional ISDN and analogue lines in favour of internet-based calling. If your system still uses those lines, it will need a SIP or other IP connection before your provider switches yours off. Check your own provider's dates; our ISDN guide explains what changes and which devices still need attention.

How are the guides checked?

Against the makers' own documents and notices, with the sources listed on each guide. Each page shows when it was last checked. Menus and defaults vary by software release, so confirm them on your own system before changing anything.

Are you linked to Avaya, Mitel, Cisco or NEC?

No. We're independent and not affiliated with any manufacturer. Product names are used only to describe the systems the guides cover.

Interactive

Follow a call through your phone system

Press a stage, or let it play. Each one shows what happens, how it goes wrong and the first safe check.

See it happen

Follow a call through all six stages

Press a step to jump to it. Save the GIF to share it.

Free to share. Print, pin or post.

Three one-page guides for whoever looks after your phones. Each is a 1000×1500 image, sized for Pinterest and easy to print. Click one to open the page it comes from.

Infographic: the six stages of a business call (line, incoming route, time profile, hunt group, user, voicemail) with the symptom and first safe check for each.
The 6 places a business call can breakFrom: Phone fault reviewSave PNG
Infographic: a three-question decision tree for keeping, upgrading or replacing a business phone system.
Keep, upgrade or replace? The 60-second decision treeFrom: Replacement assessmentSave PNG
Infographic: five steps for handing phone-system support to a new supplier without a gap in cover.
Switching phone support: the 5-step handover checklistFrom: Support plansSave PNG
Optional next step

Found the stage, not the fix?

Send what you've found. We read it and reply with the likely cause and your options: repair, upgrade or replace.

Request a fault review →