Phone Compatibility
Bring the phones you already use.
Thirdlane provisions and operates the major desk-phone vendors out of the box, with full template and firmware coverage for current models. Zero-touch provisioning via Yealink RPS, Snom SRAPS, and Fanvil’s redirect service — phones find your platform on first boot, no per-device touching.
Supported vendors
Yealink
Full template + firmware coverage. Yealink Management Cloud Service (YMCS v2) integration via Open API. Remote Provisioning Server (RPS) support for zero-touch out-of-the-box deployment.
Snom
Templates and firmware for current Snom models. Secure Redirection and Provisioning Service (SRAPS) support for ZTP without exposing the provisioning endpoint.
Fanvil
Templates and firmware coverage. Remote Auto Provisioning supported for ZTP via Fanvil’s redirect service.
Polycom
Templates with span (line-key count) support across small-footprint and high-density models.
Grandstream
Provisioning templates and firmware management for current Grandstream models.
Cisco
Multi-platform Cisco phone support, including CUCM-feature-compatible provisioning for migrations off Cisco Unified Communications Manager.
Other SIP devices
Standards-compliant SIP phones and softphones can register against Thirdlane regardless of provisioning support — phones outside this list still work; they just register manually.
Provisioning capabilities
Phone Models management
Browse, filter, clone, and inline-edit phone templates. Full CRUD for custom models so you can support phones beyond the shipped library.
Per-model protocols
HTTP, HTTPS, FTP, FTPS, TFTP. Configurable globally and per model. Protocol-aware template variables so the same template adapts to whichever transport you use.
Custom template variables
Define global name/value pairs in Provisioning Settings; reference them from any phone template. Useful for environment-specific URLs, tenant identifiers, and feature flags.
ZTP redirection
Yealink RPS, Snom SRAPS, and Fanvil Remote Auto Provisioning so the phone finds Thirdlane on first boot — no per-device manual setup.
External Provisioning mode
Direct phones to download configs from a customer-managed DMS instead of Thirdlane’s built-in provisioning. Useful for service providers who centralize provisioning across multiple platforms.
S3 File Transport
Automatic upload of generated provisioning files to S3-compatible storage after each device is provisioned. Pairs with cloud DMS deployments.
Custom Script Transport
Run user-defined post-provisioning scripts with file paths and context variables — for hooks into your own audit, monitoring, or asset-management systems.
Hot Desking
Designated phones aren’t bound to a single user. Anyone with valid credentials can sign in and associate the phone with their extension for the session.
Practical patterns
- New deployment, new phones — buy phones with the vendor’s ZTP service. Pre-stage MAC addresses in Thirdlane, ship the phones direct to the user, plug in to provision.
- Migration from another platform — point the phones’ redirect URL at Thirdlane via RPS / SRAPS / FAP. Mass-cutover without on-site visits.
- Heterogeneous fleet — Yealink in HQ, Polycom in conference rooms, Grandstream in remote sites? One platform provisions all of them with consistent dial-plan and feature config.
- Service-provider model — multiple end-customer tenants, each with their own phone fleet. Per-model templates apply across tenants; per-tenant variables customize CLI, dial plan, and SIP servers.
- External DMS integration — if you operate a centralized DMS across multiple platforms, switch Thirdlane to External Provisioning mode and let your DMS serve the configs.
Phone not on the list?
Standards-compliant SIP phones and softphones register against Thirdlane regardless of whether we ship templates for them — you just lose ZTP on the unsupported model. The Phone Models management screen lets you clone an existing template and adapt it to a new device.
For volume deployments of a phone we don’t currently template, talk to us — adding template support for major models is straightforward.
Walk through provisioning.
We’ll show you ZTP for Yealink, Snom, and Fanvil; per-model templates; and the provisioning protocols that fit your network and security policies.