Editorial

Automatic Provisioning in the Cloud Age

Published on:

December 14, 2012

The addition of the snom 710 to the 700-series has significantly enhanced deployment flexibility, especially with our version 5.0.3 improvements. One key change is the automatic device button profile assignment, which eliminates manual configuration and saves time by allowing the PBX to pick the right profile when provisioning devices. This simplifies deployments and ensures phone features are fully utilized. The update also customizes hard key provisioning per device, improving functionality. And the new PBX discovery method using snom XML RPC server streamlines setup, especially for hosted PBX and private cloud users, saving time on troubleshooting and device resets.

The availability of the snom 710 was a game changer for the 700-series. Now customers have a range of devices that make it possible to roll out systems into small and large offices. The snom 710 was added to the supported devices in version 5 from the beginning, but version 5.0.3 includes important improvements that make it really easy to roll out these devices.

First of all, snom ONE always offered buttons configuration. The new version makes it a lot easier to deploy phones by using default device button profiles; with these profiles, the PBX automatically picks the right device profile when generating the provisioning data for the devices. In other words, when plugging devices in, the administrator doesn't have to manually assign profiles to users any more: They are automatically picked by the system depending on the device type. For most of the devices in the domain, this is a reasonable setup and usually only a small part of the device requires manual modifications. Not only is this a big time saver, but in many installations the phones' features are untapped because there is no time to set up the buttons correctly.

While we were on it, we also looked at the other hard keys on the devices. In the previous versions, all snom phones were treated equally, but they are not equal. The new version provisions the hard keys depending on the device so, for example, the menu button on the 720 and 760 uses the XML content generated from the PBX.

We also looked at the PBX discovery mechanism. In addition to manual configuration, DHCP option 66, and multicast provisioning, we added a new mechanism that uses the snom XML RPC server to discover the PBX. This new method was primarily designed for hosted PBX operators; in "private cloud" installations, however, it also makes a lot of sense to use this. When the administrator assigns the MAC to an extension, now the PBX publishes that MAC to the central redirection server, so when the phone boots up, it takes the PBX address from there. This works from any location where the phone has access to the public Internet. It also works when the customer factory-resets the device; this means the standard support procedure will ask the in-house or external customer to reset the device and reboot.

This is a big time saver compared to manual setup, where the support staff has to babysit users through the procedure of setting the device up every time something goes wrong. Time is money these days.

Latest Articles

View All

A PBX That Lets You Build It Your Way

Every business handles calls differently, and its phone system should support those differences. Vodia PBX gives businesses and service providers the flexibility to shape call flows, configure individual tenants and extensions, and build a branded experience for their customers. Queues, ring groups, schedules, forwarding, and AI agents can work together around each team’s requirements, while the REST API connects the phone system with wider business workflows.

November 11, 2026

The Vodia PBX Now Supports Grok

Vodia PBX now supports xAI’s Grok, giving partners another option for building AI voice agents for their customers. Using Grok’s speech-to-speech API, a Vodia Voice Agent can greet callers, ask who they’d like to speak with and transfer them to the appropriate extension. For example, a caller can simply say they’d like to speak with sales and be connected to the sales team. The article walks through what you need to connect Vodia PBX to Grok and includes a sample call transfer script you can adapt to your own call flow.

November 5, 2026

Vodia PBX 70.7: Built for the way your customers work

Vodia PBX 70.7 brings practical improvements to hotel operations, call quality troubleshooting, outbound dialing, and device provisioning. A new Hotel Front Desk template puts room status, wake-up calls, and guest services in one place, while additional call quality metrics help teams investigate audio issues. Updates to the User Web Portal, reporting schedules, hardware support, and integrations give MSPs, resellers, and service providers more tools to manage deployments and support their customers’ everyday communications.

November 2, 2026