The Question Behind the Question
When someone asks whether their handsets are compatible, they are rarely asking a protocol question. They are asking whether the decision they are contemplating is going to look expensive and slightly foolish to whoever signs off on it.
That is a completely reasonable thing to be worried about, and it deserves a straight answer rather than a marketing one. So here is the straight answer, and then the detail that qualifies it.
A desk phone is not a subscription. It is a piece of network equipment that speaks a published protocol, and it will speak that protocol to whoever you point it at.
The premise most hardware anxiety rests on, and why it is wrong
Session Initiation Protocol was published as an open standard and no company owns it. Every serious handset manufacturer implements it, because a phone that only worked with one platform would be unsellable. That is why the phones on your desks are almost certainly not the obstacle you think they are — and why any provider implying otherwise is describing their hardware margin rather than the technology.
The Short Answer and Its Conditions
Yes, in most cases, with three conditions that are worth stating clearly up front rather than discovering later.
- Calling works. Features need checking. The protocol standardises registration, ringing, answering, hold, transfer and audio. It does not standardise the wall of busy lamp keys showing who is free, shared line appearance across a reception pod, one-touch call park, presence or directory name lookup. Those are vendor implementations. Some are textbook, some are idiosyncratic. Checking one handset of each model settles it in about ten minutes.
- The device has to be current enough to be secure. This is the real cut line, and it is not about age. A handset that cannot negotiate TLS 1.2 for signalling and SRTP for audio is sending its registration credentials across your network in the clear, which is a problem irrespective of how nicely it rings.
- Somebody may need to unlock it. If the phones came from your current provider, they may be pinned to that provider's provisioning account. This is the one condition that can genuinely cost you time, and it is covered in full below.
What the answer means in practice
For a typical Australian business with a few dozen handsets bought in the last five years, the realistic outcome is that nearly everything on the desks is reused, a handful of oddities are replaced, and the analogue things on the walls get their own short conversation. Not a skip bin. Not a full refresh quote.
What Is Actually on Australian Desks
This list is assembled from what turns up during real migrations in Australian offices rather than from a manufacturer catalogue. It is deliberately specific, because “most SIP phones work” is not an answer anyone can act on.
| Brand | Models we see constantly | Worth knowing |
|---|---|---|
| Yealink | T31G and T31P at the entry level, T33G, then T43U, T46U and T48U through the middle, and T53W, T54W, T57W, T58W Pro and T87W at the top. EXP43 and EXP50 expansion modules | The most common brand in the country by a distance. Clean standards behaviour, mature provisioning, easy to work with |
| Fanvil | X3U, X4U, X5U, X6U, X7A and X7C on the desk. X210 and X210i for reception and paging consoles. V62, V64, V66 and V66 Pro. Android touch models A320, A32i and A330 | Unbeatable on price per programmable key. The X210 carries 106 and the V66 up to 116, which matters if one person watches the whole building |
| Grandstream | GRP2601, GRP2612 and GRP2612W, GRP2613, GRP2614, GRP2615, GRP2616, GRP2624, GRP2634, GRP2636, GRP2650 and GRP2670 | The default fleet phone for a lot of Australian managed service providers, so it turns up in inherited estates constantly |
| Snom | D717, D735, D785, D812, D815, D862 and D865 | Less common here than in Europe. Standards-clean and generally trouble-free when it does appear |
| Poly (Polycom) | VVX 150, 250, 350 and 450. Edge E100, E220, E320, E350, E450 and E550 | Usually inherited from an earlier enterprise rollout. Check the firmware generation before assuming anything |
| Cisco | 6821, 6841, 6851 and 6861. 7811, 7821, 7841 and 7861. 8811, 8841, 8851, 8861 and 8865 | Only on multiplatform (MPP) firmware. On the enterprise call manager load they will not work with any cloud platform. Conversion is documented and routine, but it is a real step |
| Htek, Gigaset, AudioCodes, Sangoma | Htek UC902, UC912, UC924 and UC926. Gigaset Maxwell. AudioCodes 400HD. Sangoma P310, P320, P325, P330 and P370 | All standards-based and all fine. The Sangoma P-series in particular is better hardware than its market share suggests |
Treat the list as a starting point
Manufacturers revise hardware inside a single model name, ship regional variants and occasionally change behaviour in a firmware build. The only test that settles it is registering one of your actual phones, which takes minutes and which we will do with you before you commit to anything. A model missing from this list is not a refusal — it means we have not seen enough of them in Australian offices to say something useful about it.
Cordless, Conference and the Warehouse
Desk phones are the easy part. The devices that actually delay migrations are the ones that were installed once and never thought about again.
DECT cordless
Yealink W73P, W78P and W79P, the rugged W59R, and the multi-cell W70B, W80 and W90 systems. Gigaset N670 and N870. Snom M300, M700 and M900. Fanvil W710D and W610D. Single-cell is plug-and-go; multi-cell is a radio planning exercise that changing platform neither fixes nor breaks.
Conference phones
Yealink CP925, CP935W and CP965. Poly Trio 8300, 8500, 8800 and C60. Grandstream GAC series. Usually the oldest device in the building and the most likely to have fallen out of firmware support without anyone noticing.
Overhead paging
Algo 8180, 8186, 8301 and 8373. CyberData SIP speakers and paging adapters. Worth deciding early whether you need multicast paging or SIP paging, because they behave differently and the wiring assumptions differ.
Door and gate intercoms
2N IP Verso, Force and Solo. Akuvox R20, E12 and X915. Fanvil i10, i16V and i18S. Doorbird. All register as SIP endpoints; the relay that actually releases the strike plate is configured on the intercom itself, not on the phone platform.
The Things Bolted to Your Walls
Analogue equipment is where a straightforward migration turns into an interesting one, and it is almost always because nobody walked the building before cutover.
The general answer is an analogue telephone adapter. In Australia the Grandstream HT series is the usual choice — HT801 and HT802 for one or two devices, HT812, HT814 and HT818 for more — with AudioCodes, Patton and Yeastar as alternatives. One FXS port equals one analogue device, so count the ports before ordering rather than after.
Four things that need a decision, not an adapter
A monitored alarm panel that dials out over an analogue line can fail silently behind an adapter, and you find out on the night it matters. It belongs on an IP or 4G reporting module. A lift emergency phone carries a legal obligation and must be physically tested in the lift by someone who has read the maintenance contract. An EFTPOS terminal should be verified with your acquirer rather than assumed, and most current terminals prefer IP or mobile anyway. A fax machine gets its own paragraph below.
On fax: T.38 is supported and is a genuine improvement on pushing modem tones through a voice codec. It remains a best-effort protocol carrying a 1980s handshake across a packet network. If faxing still matters to your business — and in parts of health and conveyancing it does — the dependable answer in 2026 is fax-to-email. We will support the machine on an adapter if you want it. We will also tell you which of the two options generates fewer support calls, because you are entitled to know that before you choose.
The Lock That Turns a Weekend Into a Fortnight
Of everything in this article, this is the item that most often surprises people who otherwise know what they are doing.
Every major manufacturer runs a redirection service. Yealink calls it RPS; Grandstream and Cisco use EDOS-style device provisioning; Poly has ZTP. The purpose is entirely legitimate. A brand-new phone, plugged in for the first time, asks the manufacturer's server who it belongs to, gets pointed at the right provider's provisioning system, and configures itself with nobody touching it. That is what makes genuine zero-touch deployment possible.
And here is the consequence
Whoever registered that handset in the redirection service decides where it points, and a factory reset does not clear it. Reset the phone and it simply asks again — and gets sent straight back to the same provider. Releasing it takes them about sixty seconds. Persuading them to spend those sixty seconds during an unhappy departure can take considerably longer.
- Ask the question before you ever buy handsets from a provider. In writing: if we leave, will you release these devices from your provisioning account? A provider who will not answer that plainly has just told you something useful about the rest of the relationship.
- Work out who actually owns the phones. Purchased outright, or supplied as part of the service? The original invoice usually settles it, and the two positions are legally very different.
- Request the release early. Week one of the migration, while the relationship is still cordial — not on cutover Friday when it definitely is not.
- Have the fallback ready. If release is refused, most handsets can be manually configured to override the redirection. It is more work per device and it is a perfectly serviceable plan B for phones you own outright.
Since it is a fair question to put to us as well: handsets bought from VOCPhone belong to you. If you leave, we release them. We would rather earn the renewal than hold your hardware.
What Does Not Survive the Move
Five things go, whichever platform you move to. None is a reason to stay. All are reasons to spend an hour on an inventory before cutover week instead of during it.
| What you lose | Why | What to do about it |
|---|---|---|
| Programmed key layouts | Every DSS, BLF and speed dial key comes from the old provisioning template | Rebuilt on the new platform. On auto-provisioned models that is one template, not forty phones |
| Handset phonebooks | Contacts saved locally live on the device in a proprietary format | Export what you can, then move to a shared cloud directory every device reads — which is where they should have been |
| Vendor screen apps | XML browser applications and widgets were written against the old platform | Note them, then almost certainly do not miss them. Occasionally someone does, so ask first |
| Call recordings and voicemail | They live on the old platform, not on the handset | Export before the account closes. This is the most common regret in a switch and it is unrecoverable |
| Branded firmware behaviour | A Teams-branded or provider-branded load makes the phone that product, not a generic SIP phone | Usually re-flashable to a standard load. Test one handset before assuming the fleet follows |
When a Working Phone Is Still a Liability
The usual reason given for a hardware refresh is that the phones are old. On its own that is a weak argument — a well-built handset from 2019 can be entirely fine in 2026, and plenty are still going. The question that actually matters is narrower and much easier to answer.
Is the firmware still maintained?
A model the manufacturer has stopped patching accumulates published vulnerabilities that anyone can look up. Look for a release inside roughly the last eighteen months, or a model still listed as current.
Does TLS 1.2 or better actually negotiate?
Not whether the option exists in a settings menu — whether a real registration completes over it. Without it, credentials and call signalling cross your network in plain text.
Does SRTP negotiate on real calls?
Encrypting the signalling but not the media protects the envelope and leaves the letter open. Verify it on an actual call rather than in a configuration page.
Has the admin password been changed?
Default web interface credentials on IP phones remain one of the oldest routes into toll fraud in Australia. Unique passwords, and management reachable only from inside your own network.
The rule that follows
Replace a handset that cannot negotiate current transport security, no matter how well it makes calls. Keep one that can, no matter how dated it looks. That single test will produce a better and cheaper refresh plan than any conversation organised around how tired the plastic looks — and it is close to the reverse of how most of those conversations actually run.
The Afternoon Audit
Do this before anyone quotes you anything. One person, one afternoon, and you arrive at every subsequent conversation holding facts rather than estimates.
- Walk the floor with a notepad. Make, model and location of every device with a handset or a speaker. Include the boardroom, the warehouse, the kitchen, the workshop and the one in the storeroom nobody has used since 2022.
- Write down the MAC addresses. They are on the label underneath and in the phone's status menu. This is the single piece of information that makes zero-touch provisioning possible on the other side.
- Note the firmware version per model. One reading per model is enough. You are checking maintenance status, not building an asset register.
- Follow the analogue cables. Fax, EFTPOS, lift phone, alarm panel, gate intercom, paging horn, door strike. This step is more social than technical — ask whoever has worked there longest, because they know where things are buried.
- Find out who owns the hardware. Dig out the original invoice. Purchased outright and supplied-with-service are very different starting positions.
- Email your current provider about release. Ask for written confirmation that devices will be released from their provisioning account. Do it now, not later.
Then send us the list
Give us that inventory and we will come back line by line: what registers immediately, what auto-provisions, what needs an hour of manual configuration, and what genuinely should be replaced. That assessment is free and it is specific to your building, which makes it worth considerably more than any general compatibility claim on a web page, this one included.
The Question Almost Nobody Asks
Having spent an entire article on reusing handsets, it would be dishonest to skip the possibility that you need fewer of them than you think.
Most businesses bought a desk phone per employee because that was the only way an employee could be on the phone system. That has not been true for years. Calls, video, SMS, chat and contacts all run in the desktop and mobile apps, on hardware your staff already carry, with the business number on the outbound caller ID rather than a personal mobile.
| Who | Desk phone? | Why |
|---|---|---|
| Reception, or whoever answers for the building | Yes | High call volume, constant transfers, and a wall of keys showing who is free is genuinely faster than a mouse |
| Anyone on the phone for most of the day | Yes | Handset ergonomics and audio quality matter when it is four hours a day, not four calls |
| Shared spaces — workshop, warehouse, kitchen, boardroom | Yes | A shared device that belongs to a place rather than a person. Often cordless |
| Office staff who take a handful of calls a day | Probably not | The desktop app with a decent USB or Bluetooth headset is better, cheaper and travels home with them |
| Field staff, sales, anyone mobile | No | The mobile app is the whole point. A desk phone for someone who is never at their desk is expensive furniture |
The counter-argument, stated fairly
If you are buying from scratch, buying one model for most desks is genuinely easier to run — one firmware policy, one template, one set of quirks, one support conversation. That argument applies to new purchases. It is not a reason to write off thirty working handsets you have already paid for, and when it gets used that way it is an argument about hardware margin dressed up as an argument about simplicity.
The short version
Your phones speak an open protocol and will almost certainly work. Check three things and you have your answer: is the firmware still maintained, does the device negotiate TLS and SRTP, and will your current provider release it from their provisioning account. Everything after that is configuration, and configuration is our job rather than yours.
Related: how zero-touch provisioning works for the mechanics, what actually goes wrong when switching providers for the wider migration, and troubleshooting VoIP and SIP problems for when a registration refuses to come up.
Frequently Asked Questions
Can I keep my existing IP handsets if I move to VOCPhone?
In most cases yes, and the reason is that Session Initiation Protocol is a published open standard rather than anyone's private system. Every serious handset manufacturer implements it because a phone that only worked with one platform would be unsellable, so current-generation Yealink, Fanvil, Grandstream, Snom, Poly, Cisco on multiplatform firmware, Htek, Gigaset, AudioCodes and Sangoma devices will register and carry calls. In Australian offices the models that turn up most often are the Yealink T31G, T33G, T43U, T46U, T48U, T53W, T54W, T57W and T87W, the Fanvil X3U, X4U, X5U, X7A, X7C, X210 and V66, and the Grandstream GRP2601 through GRP2670 range. Three conditions apply. Calling is standardised but features are not, so busy lamp keys, shared lines, call park and directory lookups need a ten-minute check per model. The device must be current enough to negotiate TLS 1.2 and SRTP. And if the phones came from your current provider they may be pinned to that provider's provisioning account and will need releasing. Send us the make, model and count and we will tell you exactly where each one lands.
What is a provisioning lock, and how do I get my handsets released?
Every major manufacturer runs a redirection service — Yealink calls it RPS, Grandstream and Cisco use EDOS-style device provisioning, Poly has ZTP. A brand new phone plugged in for the first time asks the manufacturer's server who it belongs to, is pointed at the correct provider's provisioning system, and configures itself with nobody touching it. That is what makes true zero-touch deployment possible, and it is a good thing. The consequence is that whoever registered the handset in that redirection service controls where it points, and a factory reset does not clear it: the phone simply asks again and is sent straight back. Releasing a device takes the current provider about sixty seconds, but persuading them to spend those sixty seconds during an unhappy departure can take much longer, which is why you should request it in writing in week one of a migration rather than on cutover Friday. If release is refused, most handsets can be manually configured to override the redirection, which is more work per device but a perfectly workable fallback for phones you own outright. Handsets bought from VOCPhone are yours and we release them.
Will my fax machine, EFTPOS terminal, alarm panel or lift phone still work?
Each of those needs its own decision rather than one blanket answer. Ordinary analogue devices sit behind an analogue telephone adapter, and in Australia the Grandstream HT range is the usual choice — HT801 and HT802 for one or two devices, HT812, HT814 and HT818 where you need more — with AudioCodes, Patton and Yeastar as alternatives. One FXS port equals one analogue device, so count ports before ordering. Four things deserve more care than an adapter. A monitored alarm panel dialling out over an analogue line can fail silently behind an adapter and you discover it on the night it matters, so it belongs on an IP or 4G reporting module. A lift emergency phone carries a legal obligation and should be physically tested in the lift by someone who has read the maintenance contract. An EFTPOS terminal should be verified with your acquirer, and most current terminals prefer an IP or mobile path anyway. Fax over T.38 is supported and is a real improvement on pushing modem tones through a voice codec, but it remains best-effort, and if faxing genuinely matters the dependable 2026 answer is fax-to-email.
How do I decide whether to keep or replace an old desk phone?
Decide on firmware and transport security rather than on age, because age on its own is a weak signal. A well-built handset from 2019 can be completely fine in 2026 and many still are. Ask four questions of each model. Is the firmware still maintained, meaning a release inside roughly the last eighteen months or a model still listed as current, since an unpatched device accumulates published vulnerabilities anyone can look up? Does TLS 1.2 or better actually negotiate on a real registration, not merely appear as an option in a settings menu, because without it credentials and signalling cross the network in plain text? Does SRTP negotiate on real calls, since encrypting the signalling but not the media protects the envelope and leaves the letter open? And has the web interface admin password been changed from the default, given that default credentials on IP phones remain one of the oldest routes into toll fraud in Australia? The rule that follows is short: replace a handset that cannot negotiate current transport security regardless of how well it makes calls, and keep one that can regardless of how dated it looks.
What will I lose when I move my handsets to a new phone platform?
Five things, none of which should stop you, all of which are reasons to inventory beforehand. Programmed DSS, busy lamp and speed dial key layouts come from the old provisioning template and get rebuilt on the new platform, though on auto-provisioned models that is a single template change rather than touching forty phones. Contacts saved locally on individual handsets live on the device in a proprietary format, so export what you can and then move to a shared cloud directory every device reads, which is where they belonged anyway. Vendor XML screen applications and widgets were written against the old platform and will not follow, and are rarely missed. Call recordings and voicemail live on the old platform rather than on the handset and must be exported before the account closes — this is the single most common regret in a switch and it is unrecoverable afterwards. Finally, a phone carrying a Teams-branded or provider-branded firmware load behaves as that product rather than as a generic SIP phone; it can usually be re-flashed to a standard load, so test one before assuming the whole fleet will follow.
Do cordless DECT, conference phones, door intercoms and paging speakers work too?
Yes, and they are usually the parts that delay a migration precisely because nobody thinks about them until cutover week. For DECT cordless, the Yealink W73P, W78P, W79P and rugged W59R work, as do the multi-cell W70B, W80 and W90 systems, along with Gigaset N670 and N870, Snom M300, M700 and M900, and Fanvil W710D and W610D. Single-cell installations are effectively plug-and-go; multi-cell is a radio planning exercise that changing platform neither fixes nor breaks. Conference phones including the Yealink CP925, CP935W and CP965, the Poly Trio range and the Grandstream GAC series register normally, though they are frequently the oldest device in the building and the most likely to have quietly fallen out of firmware support. Door and gate intercoms from 2N, Akuvox, Fanvil and Doorbird register as ordinary SIP endpoints, with the relay that releases the strike plate configured on the intercom rather than on the phone platform. Overhead paging from Algo and CyberData works, but decide early whether you need multicast paging or SIP paging, because they behave differently and assume different wiring.
Do I actually need a desk phone for every employee?
Almost certainly not, and it is worth asking before you spend anything on hardware at all. Most businesses bought one handset per person because that was once the only way for someone to be on the phone system, and that has not been true for years — calls, video, SMS, chat and contacts all run in the desktop and mobile apps on hardware your staff already own, with the business number on outbound caller ID rather than a personal mobile. A reasonable split looks like this. Reception, or whoever answers for the whole building, should have a real handset, because high volume with constant transfers and a wall of keys showing who is free is genuinely faster than a mouse. Anyone on calls for most of the day should have one, since ergonomics and audio quality matter at four hours a day rather than four calls. Shared spaces such as a workshop, warehouse, kitchen or boardroom need a device that belongs to the place rather than a person, often cordless. Office staff taking a handful of calls a day are better served by the desktop app and a decent headset, and field and sales staff need the mobile app, not furniture on a desk they never sit at.
