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

The Vodia PBX and SAML Integration

Vodia PBX now supports SAML integration, offering a secure and standards-based method for enterprise users to access their phone system through single sign-on. SAML, or Security Assertion Markup Language, allows employees to authenticate in one system and access other systems without managing multiple passwords, improving both security and user experience. By exchanging digitally signed SAML Assertions between Identity Providers and Service Providers, Vodia ensures seamless authentication across internal and external applications. With this integration, IT teams can simplify user management, reduce login complexity, and maintain strong security controls for business communications.

September 2, 2025

Rethinking Communication in Education: Vodia Smart School

Digital communication is now woven into daily school life, from classroom platforms to how parents and teachers connect. Vodia Smart School takes this further with a VoIP-powered system that provides fast, secure, and documented communication for consent forms, sick notes, and routine notifications. In urgent situations, it enables automated alerts to staff, parents, and first responders, ensuring rapid responses when time is critical. Fully GDPR-compliant and offering features such as caller ID masking, MS Teams integration, and control of bells, announcements, and school systems, Smart School gives schools a modern, reliable alternative to legacy systems while improving both safety and everyday operations.

August 28, 2025

Vodia Now Integrates with Microsoft Teams Presence

Vodia PBX now supports Microsoft Teams Presence, building on its Teams Direct Routing certification and Dynamics 365 integration. Using Graph API from version 69.5.13, a user’s Vodia extension is automatically set to Do Not Disturb when they are on a Teams call. Presence status such as Available, Away, Busy, In a Meeting, or Presenting is matched via the Teams user’s principal username or email, allowing VoIP phones and web portals to show real-time status across devices. This integration connects Teams with a full-featured SIP-compliant PBX, enabling organizations to unify communications, streamline workflows, and support both cloud and on-premise telephony solutions.

August 25, 2025