IP PHONES & HANDSETS

How to choose
an IP phone.

The useful differences are in the way a phone works with your platform, your network and the person at the desk.

A DEVICE IS ONLY PART OF THE DECISION

The platform.
The person.
The working day.

Start with those three.
Then compare the specification.

IN SIMPLE TERMS

A business phone
on your IP network.

An IP phone connects to a communications service over a data network. A SIP desk phone uses SIP signalling to arrange calls with a compatible platform; the audio travels separately. It needs power, connectivity, an account and a supported configuration.

Some businesses use a mix of desk phones and softphones. A cordless handset is a different form factor, while a Wi-Fi-enabled desk phone may simply remove the Ethernet cable. Choose the equipment around the role.

Read the VoIP architecture guide

FIT THE WORKING DAY

Different desks.
Different priorities.

These are ways to think about use, not product rankings. People in the same business may need different devices.

01

Everyday office

An entry-level handset can suit routine calling when the display, transfer controls and required headset connection are easy to use.

02

Professional / manager

More frequent calls may justify clearer call handling, extra function keys and a display that makes several conversations easier to manage.

03

Reception

Prioritise transfers, visible colleague status, headset control and enough programmable keys. An expansion module may help if the platform supports it.

04

Executive / touchscreen

A larger screen can make directories and call control easier to navigate. Check whether the interface helps the user’s actual work before prioritising screen size.

READ THE SPECIFICATION WITH PURPOSE

What to look for.
And why it matters.

01

Power and the network connection

Power over Ethernet (PoE) lets a compatible switch or injector power a phone through its network cable. Check the device’s required PoE standard, the switch’s total power budget and any extra demand from accessories. A PoE logo is not a guarantee that your switch can power every desk.

Ethernet pass-through lets some phones share a network outlet with a computer. Check the speed of both ports and the network design: a slower phone port can constrain the attached computer. If the office needs continuity during a power cut, include the switch, router and upstream connection in the plan.

02

Wi-Fi and cordless are different choices

A Wi-Fi-enabled desk phone uses a wireless network connection but normally still needs local power. It is not necessarily a cordless handset. Verify built-in Wi-Fi versus a supported adapter, coverage and how voice behaves under load.

A DECT handset normally connects through a compatible base station; multi-cell deployments need coverage and roaming planning. A portable Wi-Fi phone has a different radio and network design. Choose around where people walk and work, rather than treating all wireless devices as interchangeable.

03

Accounts, lines and function keys

A SIP account is a configured identity for registration with a service. A ‘line’ on a phone specification may refer to an account, a line appearance or a programmable key; it does not automatically mean another public number or more carrier call capacity. Confirm the manufacturer’s terminology and the platform’s limits.

Busy Lamp Field (BLF) keys can show another extension’s status and may support pickup or transfer when the platform permits it. Expansion modules add more physical keys, but need compatible firmware, provisioning and power. Test the receptionist’s daily workflow, not only the number of buttons.

04

Headsets and Bluetooth

Check the actual connection: USB, a telephone headset socket, Bluetooth or a supported adapter. A headset that carries audio may still lack answer/end-call control. Electronic Hook Switch (EHS) support can require a specific cable, adapter and phone configuration.

Bluetooth may connect a headset or another supported device, depending on the model. Range, pairing behavior and supported profiles matter. For busy desks, test mute, ringing, call control and switching between computer and phone with the intended headset.

05

Display and audio quality

A colour display or touchscreen should make caller information, directories and transfers easier to use. Check contrast, text size, physical controls and accessibility with the person using it. A touch interface is a preference to evaluate, not a performance grade.

Codecs such as G.711 and G.722 describe audio formats. The usable codec depends on the endpoint, platform and other call legs. Microphones, speakerphone echo control, headset fit and network conditions also affect clarity. Listen to real calls in the intended room; ‘HD’ branding alone is not a quality test.

06

Provisioning and day-to-day management

Provisioning delivers settings such as the account, server, directory and key layout. Platform-supported templates can make replacement phones consistent and reduce individual setup work. Check whether the device can be enrolled into your service and whether an existing provider lock or provisioning assignment must be released.

Keep administration credentials and provisioning access protected. Plan how updates are tested, how a failed change is reversed and how a device is securely reset or retired. A cheap replacement can become expensive if every change requires a desk visit.

07

Firmware, support and platform fit

Firmware is the phone’s operating software. The correct platform edition and supported version can matter as much as the model name. Native Teams phones and generic SIP phones are not equivalent; Microsoft’s SIP Gateway has its own eligible devices and limitations.

End-of-sale means new sales are ending; end-of-life and support milestones describe different stages that each manufacturer defines. Check security-update coverage, replacement availability and the platform’s support list. A legacy handset that still registers may lack supported provisioning or fixes for future problems.

BEFORE A LARGER ROLLOUT

Try one in
the real setting.

Use the intended platform, network and accessories for a small acceptance test. Give a receptionist, a frequent caller and an everyday user time with the device.

  • Make and receive calls; check transfers, caller ID and voicemail.
  • Try the headset, mute, call-control buttons and any BLF keys.
  • Check audio in a busy period and in the actual room.
  • Confirm provisioning, supported firmware and the replacement process.
  • Ask who supports the complete setup when something fails.
Understand supported, certified and compatible

CONTINUE YOUR RESEARCH

The device and
the wider system.

Manufacturer & platform documentation

Optional further reading from the organisations behind the technology, including standards bodies. Platform examples describe that platform’s implementation.

YOUR BUSINESS COMES FIRST

Start with the system,
not the phone.

Bring your people, platform and calling needs into one conversation. Clear requirements make the equipment decision easier.

Prepare a brief to download and discuss with your supplier.