Tech

Administrators

Published on:

January 29, 2013

With snom ONE expanding into the cloud, the need for multiple administrators became evident. The new system now includes three distinct roles: the "super administrator," who retains full control over the PBX; the "system administrator," who shares many privileges but cannot alter super administrator accounts; and the "domain administrator," who manages specific domains without impacting account licenses. This new structure eliminates the need for sacrificing accounts for administrative purposes and clarifies roles. Additionally, the "login as" option has been removed, making it clear which role each user holds within the system.

With snom ONE moving more and more into the cloud, we needed to address an old problem. There are usually several persons taking care about the system. Giving them all the same username and password is a bad idea, just like giving everyone the master key for the building. As employees join and leave companies, they must have their own credentials for logging into the system.

So we finally added multiple administrators. There are now three levels:

The “super administrator” is what we know from before. This person has full control over the PBX, including managing other administrators. When upgrading to 5.0.4, this account will stay the same.

The “system administrator” is similar to the super administrator, but cannot create, change or delete the super administrator or other system administrator accounts. There can be many system administrators, each one of them with their own password.

The “domain administrator” is similar to what was previously known as domain administrator permission of an extension. Those domain administrators can be set up in the domain properties by the system or super administrators, and each domain can have multiple domain administrators.

The point here is that the domain administrators don’t count against and account licenses. This was a problem with the previous concept, as usually one account had to be sacrificed for administration purposes. Also, the system administrators don’t count against the license.

This also explains why the “login as” selection box has disappeared from the login screen. Now it is well defined what role each account has.

Derniers articles

Voir tous

Integrating OpenAI's Realtime API with Vodia PBX: Webinar Recording Now Available

In our recent webinar, "Integrate OpenAI’s Realtime API with Vodia PBX," we explored how integrating AI with your communication systems can revolutionize the way your business operates. From automating repetitive tasks to improving workflow efficiency, the webinar covered how the collaboration between Vodia PBX and OpenAI’s Realtime API can streamline operations, enhance collaboration - especially for Microsoft Teams users - and provide intelligent automation to stay ahead in a competitive landscape. If you missed the live session or want to revisit the insights, the recording is now available for you to access.

December 18, 2024

Unlock the Power of OpenAI’s Realtime API with Vodia PBX: Join Our Exclusive Webinar!

Join our exclusive webinar to explore how Vodia PBX seamlessly integrates with OpenAI’s Realtime API, unlocking powerful new capabilities for your communication systems. This session will showcase how AI-driven features can streamline workflows, improve operational efficiency and elevate the PBX experience for both general users and those on Microsoft Teams. Whether you’re looking to stay ahead of the competition or leverage the latest AI trends, this webinar offers practical knowledge and actionable strategies. Register now to secure your spot and take the first step toward transforming your telecom infrastructure with AI innovation!

December 4, 2024

Connecting to OpenAI Realtime API

This document details the beta version of the Vodia PBX that connects to the OpenAI realtime API, enabling users to interact with a chatbot via telephone. The backend JavaScript code facilitates the connection, handling audio input and output, and the WebSocket connection to the OpenAI API. The setup requires a Vodia PBX version 69.5.3 or higher, an API key, and a license with an IVR node. The demo can be accessed by editing the ivrnode.js template and creating an IVR node in the tenant. The system supports various VoIP devices and offers good voice quality. Future improvements include voice activity detection and the ability to take actions based on OpenAI responses.

November 26, 2024