DEV Community

IT And Office
IT And Office

Posted on

Used IP phones for your PBX: Aastra, Avaya & more

If you run Asterisk, FreePBX, FusionPBX, 3CX, or a lab Kamailio box, the desk phone is the part everyone underspends attention on and overspends money on. New SIP handsets are absurdly marked up for what is essentially a small ARM board with a speakerphone. The used market is full of perfectly good enterprise phones pulled from office refreshes for a fraction of the price - but only some of them will register cleanly against a standard SIP PBX, and the rest will waste a weekend. Here's how to tell them apart before you buy.

The single most important question: native SIP or vendor protocol?

Enterprise desk phones ship in two flavors, and they can look physically identical:

  • Native SIP firmware - the phone speaks standard SIP/RTP and will register against Asterisk, FreePBX, 3CX, or any RFC-compliant PBX.
  • Vendor call-control firmware - the phone speaks a proprietary protocol and only works with that vendor's call server.

The traps to know:

  • Cisco 7900 series (7940/7960/7941/7961/7942/7962) - these shipped with SCCP (Skinny) firmware for CallManager. They can run third-party SIP firmware, but flashing it is fiddly, needs a TFTP server, specific firmware-file naming, and the load names differ per model. The 7941/7961 and later need a signed SIP load. Doable in a lab, annoying at scale.
  • Cisco 8800 / 7800 series - much easier, they have a proper multiplatform (MPP) SIP firmware track. Make sure the listing says "MPP" or you'll be doing a migration.
  • Avaya 96x1 (9608/9611/9621/9641) - ship as H.323 by default for Avaya Aura. There is an official SIP firmware load, but you have to convert them, and provisioning expects an Avaya-style 46xxsettings.txt file.
  • Avaya 1600 series - H.323 only in practice, skip for a standard SIP PBX.
  • Mitel / Aastra (6700i, 6800i, 6900 series) - this is the easy path. The 6730i/6731i/6735i/6737i/6739i and the newer 6863i/6865i/6867i/6869i run native SIP out of the box, provision over HTTP/TFTP with a simple config file, and register against Asterisk/FreePBX with zero drama. The older Aastra 480i/9133i also speak SIP. This is why these turn up constantly in homelab and small-PBX setups.
  • Polycom SoundPoint IP / VVX - native SIP (the "UC Software" builds). Older SoundPoint IP 331/335/450/550/650 are dirt cheap used and work fine; VVX 300/400/500 are the sweet spot for features. Watch for VVX units locked to Skype for Business ("Lync base profile") - you can flip them back to "Generic" but confirm the seller hasn't left them on an SfB-only build.
  • Grandstream / Yealink / Snom - basically always native SIP, minimal surprises. Yealink T2x/T4x and Snom 3xx/7xx are excellent used buys.
  • Polycom / Cisco "for Teams/Zoom" SKUs - some later units are firmware-locked to a cloud platform. Read the model suffix carefully.

What to check before you pay

PoE class and power. Almost every enterprise phone is 802.3af (PoE Class 2-3). Colour touchscreen models with a sidecar/expansion module can push into 802.3at territory. If you're powering from a used switch, confirm the switch's per-port and total PoE budget covers the fleet. Phones without PoE need the barrel-jack PSU, which is the first accessory sellers lose - check it's included or budget for it.

Handset, cord, and stand. The commonly missing parts on used phones are the stand/foot, the handset curly cord, and the PSU. A phone with no stand is still usable but looks it. Bulk pallet listings often mean mixed conditions - ask.

Firmware version and provisioning lock. Ask what firmware it's on and whether it's been factory reset. A phone still pointed at a previous owner's provisioning server (redirection service like Cisco EDOS / Polycom ZTP / RPS) can keep pulling a config you don't control. For Polycom, check it's not tied to Polycom ZTP; for Cisco MPP, check it's not enrolled in a cloud provisioning profile. A full factory reset (often a key combo at boot) usually clears it, but confirm.

Physical wear. Rubber keypad wear and shiny spots are cosmetic. The things that actually fail: speakerphone rattle, dead backlight, cracked screen on touchscreen models, and Ethernet PHY on the PC-passthrough port (many phones have a 2nd port for daisy-chaining a computer - test both).

Gigabit vs 100M passthrough. Older phones (Aastra 67xxi, SoundPoint IP, Cisco 794x) have 10/100 switch ports. If the phone sits inline between the wall and a workstation, that caps the desktop at 100 Mbps. For gigabit desks you want 6800/6900-series, VVX, Yealink T4x, or Cisco 8800.

Provisioning quickly once they arrive

  • Set up a provisioning file per MAC (Aastra <mac>.cfg, Polycom <mac>-phone.cfg + <mac>.cfg, Yealink <mac>.cfg) on an HTTP server, and point DHCP option 66 (or option 160 for Polycom) at it.
  • Keep a base/common config for shared settings (NTP, timezone, codec order - G.711 for LAN, add G.722 for HD audio, G.729 only if you're bandwidth-constrained), and a per-phone file for the SIP credentials and line keys.
  • Lock the admin password in the config - plenty of used phones arrive with the default still set.
  • For a homelab, a tftpd-hpa or a two-line python -m http.server in the provisioning directory is enough to get going.

If you'd rather start from handsets that are already native SIP and factory-reset rather than gambling on an auction lot that might be H.323 or SCCP, resellers like IT and Office carry tested Aastra/Mitel SIP phones pulled from European office fleets, which sidesteps the whole firmware-conversion problem.

Over to you

What's registered against your PBX right now - are you running a matched fleet, or a graveyard of whatever showed up cheap? And has anyone here actually had a good experience converting Cisco 7900s to third-party SIP firmware, or is that a trap best left alone in 2026?

Top comments (0)