Every business phone system eventually gets replaced. The desk phones usually don’t. That mismatch is where a quiet, rarely-discussed form of vendor lock-in lives — in the provisioning of the very phones you paid for.
If you run communications for customers — whether you’re a small MSP with a handful of accounts or a large operator with thousands of seats — here’s a question worth asking before you commit to any platform: when it’s time to move, do your phones come with you, or do they belong to your PBX vendor?
How zero-touch provisioning actually works
Modern IP phones (Yealink, Snom, Poly, Fanvil, Grandstream) support “zero-touch” provisioning through a manufacturer redirection service — Yealink’s is called RPS (Redirection and Provisioning Service). The concept is simple:
- Each phone, on first boot, contacts the manufacturer’s redirection service.
- The service looks up the phone’s MAC address and returns a provisioning URL.
- The phone fetches its configuration from that URL and sets itself up.
The catch: a given MAC address can belong to only one account in that redirection service at a time. So the real question is — whose account is it?
Two models: who holds the account
Provider-owned (you’re in control). Platforms built to serve MSPs — from a single office to nationwide operators — let you connect your own manufacturer accounts and bind your customers’ phones to your provisioning server. You can add devices, re-point them, and remove them when a customer leaves. Thirdlane is built this way, and it’s the model providers should expect from any platform designed for their business.
Vendor-brokered (the vendor is in control). Here the PBX vendor uses its own manufacturer accounts and registers your customers’ phones under them. It’s marketed as convenience — “no account setup required” — and for a single small deployment that’s a fair trade. But the price is control over hardware you own.
Where this bites: leaving 3CX
3CX’s publicly documented approach is a clear example of the vendor-brokered model. Rather than letting a provider use their own manufacturer account, 3CX registers phones under 3CX-controlled accounts on its own cloud — and by design, you can’t attach your own account to it. The practical consequences show up when you try to leave:
- The redirection entries for phones you own sit inside 3CX’s account, not yours.
- You can’t remove those entries yourself.
- They only clear automatically a couple of weeks after you stop managing the extension — and that countdown restarts whenever the extension is edited.
Yeastar follows a similar vendor-brokered pattern through its own cloud service. See our detailed comparisons for the specifics: Thirdlane vs 3CX and Thirdlane vs Yeastar.
None of this is unlawful, and the convenience is real for the smallest deployments. But for an MSP with hundreds or thousands of endpoints, it means your fleet’s “home address” is held by the very platform you’re trying to migrate away from.
Why ownership matters — at any size
- Portability. Migrate in, and out, on your schedule — not on someone else’s timer.
- Control. Add, re-point, and remove devices yourself, without filing tickets with a vendor or the manufacturer.
- Resilience. Your provisioning doesn’t hinge on another company’s cloud, accounts, or policy changes.
- Ownership of the relationship. No third party sitting between you and your own hardware and customers.
A checklist before you choose a platform
- Can I connect my own manufacturer provisioning account (Yealink, Snom, Poly…)?
- Can I add and, importantly, remove device entries myself?
- If I leave, what exactly happens to my phones — and how long does it take?
- Is provisioning tied to the vendor’s cloud, or to infrastructure I control?
The Thirdlane approach
We don’t lock your phones to us. You bring your own provisioning accounts, you keep control of your devices, and if you ever leave, your phones are yours to redirect — no waiting period, no tickets, no permission required. That’s not a feature we bolted on; it’s a consequence of a simple principle that matters to MSPs of every size: your customers and your hardware belong to you.
Moving off 3CX or Yeastar? We help MSPs migrate whole systems — users, IVRs, ring groups, greetings, and more — onto a single Thirdlane platform. Explore our migration paths or talk to us.