Platform compatibility · 3CX

3CX-compatible SIP phones — a buyer's checklist

Q: What details does a handset need to register as an extension?

The server address, the SIP port (default 5060), the username — normally the extension number — the authentication password and the display name, with registration switched on. The platform documentation states the same fields from the platform side, and the phone side is configured over the phone web interface or pushed by auto provisioning. Signalling runs over UDP or TCP, with TLS where encryption is required.

Q: Which codec and DTMF settings should we use?

DTMF must match on both sides: In-band, RFC2833 or SIP INFO, and RFC2833 is the documented standard method. For codecs, G.711 gives the widest compatibility, G.722 and Opus give wideband audio, and G.729 is the documented choice where bandwidth is tight — the platform documentation recommends G.729 for IP telephony, and G.711 is the fallback everywhere else. The catalogue publishes G.711U/A, G.722, G.729A/B, G.726, iLBC and Opus across the ranges.

Q: Can an analog phone, a fax machine or a door station sit on the same system?

Yes, in the same dial plan. The GA10 puts one analog telephone on the network with 2 SIP lines and one FXS port, and the OM series carries analog ports by card — up to 4 on the OM20G, 12 on the OM50G, 48 on the OM80E and 96 on the OM200G. Fax runs as T.38 or G.711 pass-through. Door and indoor stations register as standard SIP endpoints with relays for door release, and the PA3 and PA2S gateways put an existing speaker line or paging zone on the same system.

3CX runs a phone system on standard SIP, so the useful question is not which badge a handset carries but which protocol and feature requirements it satisfies: registration, multiple accounts, DTMF handling, transport, encryption, codecs, programmable keys and provisioning. This page sets out those requirements, names the models in the catalogue that publish them, and states plainly where the platform's own published device list takes over. NEXVIA supplies and integrates the equipment; the platform side of a 3CX deployment is configured by whoever runs the 3CX installation.

The checklist a 3CX deployment asks of a handset: SIP registration, multiple accounts, DTMF method, transport, TLS and SRTP, codecs, key field and provisioning
Published line counts across the catalogue run from 2 SIP lines on the X301 group to 20 on the X7, X7C, X210 and the V Series screen models
DTMF is selectable as In-band, RFC2833 or SIP INFO on the GA10 and the desk-phone datasheets — the method has to match the platform setting
Codecs published across the range: G.711U/A, G.722, G.729A/B, G.726, iLBC and Opus
Provisioning facts we can document: auto provisioning over DHCP option 66, TR069/TR104/TR106 and SIP PnP, with central device management named in the manufacturer material
No model on this site is described as 3CX-certified, and no model is claimed to be on the 3CX supported-device list — that list belongs to the platform and is confirmed per firmware

Request a Quote Open the system planner

NEXVIA X6U business IP phone with a 4.3-inch main screen and two side DSS key screens

The short answer

A 3CX phone system is built on standard SIP, so compatibility is a requirement list, not a badge. The handset has to register as a SIP extension — server address, username, password and display name — with the platform side listening on the usual port 5060 and signalling accepted over UDP or TCP. It has to offer a DTMF method that matches the platform setting: In-band, RFC2833 or SIP INFO. It should carry the codecs the platform offers — G.711 for compatibility, G.722 and Opus for wideband, G.729 where bandwidth is tight — and it should support TLS signalling and SRTP media where the deployment requires encryption.

The second half of the checklist is capacity and keys. Published line counts in this catalogue run from 2 SIP lines (X301 group, and the 2-line H Series handsets) to 4 (X303 group), 6 (X3U), 12 (X4U), 16 (X5U) and 20 on the X7, X7C, X210 and the V Series screen phones — enough accounts for an extension plus a second line or a shared appearance. For busy-lamp and speed-dial work the published key fields go up to 116 on-screen DSS keys on the A Series and V Series phones, 106 on the X210 and X210i and 60 on the X6U, with 3 to 5 LED line keys on the XU models.

The honest limit: 3CX publishes its own supported-device list, and it changes with platform and firmware versions. We do not hold that list and this site does not repeat it. What we do is confirm the current position with you at quotation time: send the platform version, the extension count, the role the phone is meant to fill and the features you need, and the answer comes back as a model list checked against the product documentation current at that moment — not as a certification claim.

Capability matrix — what the platform actually uses

Capability	Models in the catalogue	What it means when the phone registers
Colour-screen desk phones with DSS keys	X6U, X5U, X5U-R, X4U, X3U / X3U Pro and the V Series models	Multiple SIP accounts with programmable line and DSS keys for presence and speed dialling; 30 to 60 DSS keys on the XU models and up to 116 on the V67 and V66; dual Gigabit ports with integrated PoE on the XU family
Android touch-screen phones	X7A, A320, A320i, A330i, A308i	Touch screens from 7 inches to 10.1 inches on Android 9.0 or Android 14, with third-party application installation stated for some models; whether a client application is deployed on them is a platform-side decision, and this catalogue treats them first as standards-based SIP phones
Entry and headset-first desk phones	X301, X301P, X301G, X301W, X303, X303P, X303G, X303W and the X2P	2 and 4 SIP lines on a 6-way audio conference for back offices and service desks; the X2P adds RJ9 and 3.5 mm headset ports, LED mute, hold and auto-answer keys and a pedal-switch option for positions that work on a headset all day
Wireless handsets for staff who move	W610D with the W710D and W710H bases; W610W, W611W, W620W	DECT bases publishing up to 30 handsets per base and 300 per system, with SRTP/SIPS/TLS and 16 simultaneous calls per base; portable Wi-Fi handsets with up to 16 DSS keys and a configurable push-to-talk key documented for quick dial, intercom and multicast
Room and service handsets	H Series — H6W, H5/H5W, H4/H4W, H3/H3W, H2U, H1, H602/H602W, H601/H601W, H603W, H1-2 Wire	2 SIP lines with 2 to 10 programmable service keys and customisable faceplates; the Wi-Fi 6 and cordless variants cover rooms that have power but no data outlet, and the 2-wire models reuse an existing pair
Analog telephones, door stations and paging	GA10; A12/A12V, i16S, i11S, i10S, i67; PA3, PA2S; A212, A201	The GA10 puts one analog telephone on the network with 2 SIP lines and 1 FXS port; door stations and indoor stations register as standard SIP endpoints with relays for door release; the paging gateways and SIP speakers carry announcements on the same extension plan
Consoles and conferencing	A320i, A330i, A308i, X210i; CA600, CA400, CA200; CS20, CS40	Paging and answer consoles with goose-neck microphones, speaker output up to 92 dB and up to 116 DSS keys, plus conference terminals and speakerphones that register on the same SIP system for meeting rooms

The rows below are capabilities and published figures, not certifications: no model on this page is described as certified for any platform, and no supported-device list published by a platform vendor is reproduced here.

Other platform compatibility pages

Microsoft Teams phones

Two routes to a Microsoft Teams phone position: a native device from Microsoft's own published list, or a standards-based SIP phone joined at a documented SIP interface.

Zoom Phone desk phones

What a desk phone has to support to register to Zoom Phone — and how the platform's own compatible-device list is checked at quotation time instead of copied into a table.

What a 3CX deployment uses from the handset

Every row below is a requirement that appears in a 3CX design conversation, followed by what this catalogue publishes for it. The third column says where the answer is confirmed; nothing in it is a claim about the platform.

Requirement list for a SIP handset on a 3CX phone system, against the published figures of this catalogue

Requirement	What the phone has to do	What this catalogue publishes
SIP registration	Register as a standard SIP extension with the server address, username, password and display name	Standard SIP registration across the desk, hotel, wireless, intercom and gateway ranges; the OM platform registers extensions on port 5060 by default and signalling runs over UDP or TCP, with TLS available
Accounts and lines	One account per extension, plus a second account where a desk watches another number	Published counts: 2 SIP lines (X301 group, X2P, H Series), 4 (X303 group), 6 (X3U / X3U Pro), 12 (X4U), 16 (X5U), 20 (X7, X7C, X210 and the V Series screen models; the X7A is printed with 20 in the solution brochure)
DTMF handling	Match the platform setting: In-band, RFC2833 or SIP INFO	The GA10 publishes In-band, RFC2833 and SIP INFO; the desk-phone and gateway datasheets print the same selectable methods, and the platform side documents RFC2833 as the standard method
Transport and encryption	SIP over UDP or TCP, with TLS signalling and SRTP media where encryption is required	UDP (default), TCP or UDP&TCP; TLS and SRTP options documented on the platform side, and SRTP/SIPS/TLS published for the DECT bases in the wireless range
Codecs	Carry the codec set the platform offers, with a narrowband fallback	G.711U/A, G.722, G.729A/B, G.726, iLBC and Opus appear across the desk phones, the GA10 and the wireless handsets; the platform documentation recommends G.729 for IP telephony where bandwidth is limited
Programmable keys and presence	Line keys, busy-lamp fields, park and pickup keys, speed dials	Up to 116 on-screen DSS keys (A Series, V67, V66), 106 (X210, X210i), 60 (X6U), 30 (X5U, X4U) and 3 to 5 LED line keys on the XU models
Provisioning	Configuration pushed from the platform or a device manager, per firmware	Auto provisioning over DHCP option 66, TR069/TR104/TR106 and SIP PnP; the manufacturer material also names its distributed provisioning and device-management services
Headsets and desk accessories	Call-centre or office headsets, including wireless models	EHS wireless headset support published across the desk range; USB and Bluetooth headsets, EHS and USB Bluetooth adapters and the WF20 USB Wi-Fi adapter are listed in the accessories

The list we do not publish — and what we do instead

3CX publishes its own supported-device list, and it moves: a model can be listed for one release and not the next, and a listed model can depend on a firmware version. We hold no list of that kind, and this site does not repeat, extend or reinterpret one. That is why no page here calls a phone 3CX-certified or puts it on a supported-device list.

The sequence that does work for a project is short: check the platform's own published list for the exact release you run, then send us the platform version, the number of extensions, the role each phone has to fill and the features you need. We answer with the models whose published specifications meet the requirement list on this page and confirm the current position on the quotation.

Platform release and firmware version decide which devices are listed — the list is checked against the version you actually run
Roles the platform defines itself — a router-phone role, for example — are defined and listed by the platform; if a project depends on one, tell us and we will match the requirement against the current documentation
The manufacturer also updates firmware over time, so the position is confirmed at quotation time rather than assumed from a page written earlier
Send the extension count and the features (park, pickup, busy lamp, recording, queue positions) and the model shortlist is narrowed in one reply

This is a deliberate limit, not an omission: a compatibility table filled in from impression is worse than no table. Ask us and the current facts are confirmed in writing.

If the phone system is part of the project too

NEXVIA supplies and integrates IP PBX systems as well as the handsets, so a 3CX-adjacent project can be a phone-only supply or a complete design. The OM series runs from 24 to 1000 SIP trunks across five models, with analog ports from none to ninety-six and local or remote recording.

On platform compatibility the product manual is the source, and we quote it rather than extend it: the OM series is documented as compatible with a variety of business platforms and terminals such as CallManager, Broadsoft, Skype for Business, Huawei IMS and Asterisk. That sentence belongs to the manual; it is not a list we add to, and it says nothing about any other platform.

24 to 1000 SIP trunks across the OM series; up to 120 concurrent calls on a single trunk on the OM20G and OM200G and up to 200 on the OM1000-UC
Analog ports by card: up to 4 (OM20G), 12 (OM50G), 48 (OM80E) and 96 (OM200G), with no analog ports on the OM1000-UC
DTMF as RFC2833, in-band or SIP INFO; codecs G.711, G.729A, G.722 and G.722.2 on the platform side
Auto provisioning over DHCP option 66 and TR069, with recording in G.711 and G.729 and fax as T.38 or G.711 pass-through
Ring groups with sequential, rotating or simultaneous distribution and up to 40 members; queues of up to 20 waiting calls

The compatibility sentence above is quoted from the OM series administrator manual. It names those platforms and no others, and it is printed here exactly because that is what the documentation says.

What the model list looks like per position

A typical small deployment asks for one phone per desk, one for the operator or reception and one for a door or a warehouse. The published figures make the shortlist straightforward: 2-line entry phones for back-office and service positions, 4-line phones where a second line is watched, 6 to 20-line phones where busy-lamp fields matter, DECT or Wi-Fi handsets for staff who move between rooms, and gateways where an analog phone, a speaker line or an un-cabled room has to stay in service.

Reception and operator: X6U or X210 with 60 to 106 DSS keys, or an A Series console where paging is part of the job
Desks: X301 group for 2 lines, X303 group for 4, X3U for 6 and X4U or X5U where a second screen for keys is wanted
Call-centre positions: X2P with RJ9 and 3.5 mm headset ports and a pedal-switch option; EHS adapters for wireless headsets
Mobile staff: W610D DECT with a W710D or W710H base, or the W611W and W620W Wi-Fi handsets
Door, gate and service positions: the i16S, i11S, i10S and i67 families, registered as SIP extensions with relay-controlled door release

Frequently asked questions

Which models are described on this site as 3CX-certified?

None. No model on this site is called 3CX-certified and no model is claimed to be on the 3CX supported-device list. 3CX publishes that list itself and it changes with releases and firmware; what this page publishes is the protocol and feature requirement list a phone has to satisfy, plus the manufacturer figures that show where each family stands. The current position is confirmed with you at quotation time.

How do I check whether a specific phone works with our 3CX release?

Two steps. First, look up the device in 3CX's own published list for the release you run — that list is authoritative for the platform side. Second, send us the release, the extension count, the role each phone fills and the features you need (park, pickup, busy lamp, recording, queue positions); we reply with the models whose published specifications meet those requirements and confirm them on the quotation.

What details does a handset need to register as an extension?

The server address, the SIP port (default 5060), the username — normally the extension number — the authentication password and the display name, with registration switched on. The platform documentation states the same fields from the platform side, and the phone side is configured over the phone web interface or pushed by auto provisioning. Signalling runs over UDP or TCP, with TLS where encryption is required.

Which codec and DTMF settings should we use?

DTMF must match on both sides: In-band, RFC2833 or SIP INFO, and RFC2833 is the documented standard method. For codecs, G.711 gives the widest compatibility, G.722 and Opus give wideband audio, and G.729 is the documented choice where bandwidth is tight — the platform documentation recommends G.729 for IP telephony, and G.711 is the fallback everywhere else. The catalogue publishes G.711U/A, G.722, G.729A/B, G.726, iLBC and Opus across the ranges.

Can an analog phone, a fax machine or a door station sit on the same system?

Yes, in the same dial plan. The GA10 puts one analog telephone on the network with 2 SIP lines and one FXS port, and the OM series carries analog ports by card — up to 4 on the OM20G, 12 on the OM50G, 48 on the OM80E and 96 on the OM200G. Fax runs as T.38 or G.711 pass-through. Door and indoor stations register as standard SIP endpoints with relays for door release, and the PA3 and PA2S gateways put an existing speaker line or paging zone on the same system.

Does NEXVIA supply the phone system as well as the handsets?

Yes. NEXVIA is a system integrator: we design the system, supply the equipment, commission it on site and support it afterwards. The handsets can be supplied as extensions on an existing platform, or the whole system can be designed around an IP PBX from 24 to 1000 SIP trunks, with the analog ports, the wireless handsets, the door stations and the paging sized to the site. The equipment is manufactured by NEXVIA in our own plant and supplied under the NEXVIA brand.

Are prices, lead times or platform licences published here?

No. Commercial terms are not published on this site — every project is quoted per site, model mix and quantity, and platform licensing is handled by whoever runs the platform. Send the site type, the extension count, the areas to cover and your platform release, and the reply comes back with a configuration and a quotation.

Relationship and trademark notice

NEXVIA manufactures its own range of IP telephony equipment — PBX systems, SIP phones, hotel handsets, nurse call, intercom and public address — and integrates it for the site: design, manufacture, supply, commissioning and after-sales support.

This page describes the protocol and feature requirements a telephone has to satisfy to register on a third-party platform. It does not claim platform certification, and it does not reproduce any platform vendor's supported-device list; the current position is confirmed against that vendor's own published documentation at quotation time.

All product and platform names on this page — including 3CX, Microsoft Teams and Zoom — are trademarks or registered trademarks of their respective owners. NEXVIA is not affiliated with, endorsed by or sponsored by those vendors, and their names are used only to describe the interoperability requirements of a standards-based SIP telephone.

3cx compatible phones · 3cx supported phones · 3cx phones · 3cx router phones · 3cx desk phone

Page author: NEXVIA EngineeringPublished:2026-09-29Last updated:2026-10-13

Covers: 3cx compatible phones · 3cx supported phones · 3cx phones · 3cx router phones · 3cx desk phone

Equipment on this page is supplied and integrated by NEXVIA; platform names are used to describe interoperability requirements only.

Explore Products

Planning an IP telephony project?

Send us the site type, the number of extensions or rooms and the areas to cover — we will come back with a configuration and quotation.