In Vodia Networks' upcoming version 60 build, a new feature allows users to log in with their Google accounts seamlessly. This is made possible through a JavaScript library from Google, providing a secure and convenient login experience. The process involves obtaining a token from Google, and users can benefit from features like two-factor authentication. Setting up this feature requires configuring the domain on the Google API site and integrating a Client ID into the PBX web interface. Scheduled for release in version 60.2, this enhancement simplifies user logins.
A cool feature we had on our wish list for a long time will be in our next version 60 build: Login with your Google account.
The way this works is the web front end pulls a JavaScript library from a Google server that handles the details for the Google login; once the login is done, Google provides a token the PBX backend can use to pull the email address of the logged-in account and set up a user session, just as if the user had logged in with his or her username and the password.
Google has done a lot to make the login convenient and secure, providing two-factor authentication and email notifications as part of Google G Suite service. There is nothing the end user needs to do to make this work.
The email address in the user account must match the email account in the Google account; if a user has multiple email addresses, one match will be sufficient. It makes no difference if it’s a free Gmail account or a paid Google business account.
The domain for this feature must be set up on the Google side: for this you have to log in to the Google API site and create credentials for the domain. It isn’t possible to use wildcard domain names, so every domain name that can be used for the login must be listed; if you are using a secure connection you should only enter the https address; if you are using multiple domain names, they must be listed separately. There is a wizard at https://developers.google.com/identity/sign-in/web/sign-in you can use to set this up:
After picking a name for your login, you need complete some minimal configuration. The PBX uses "Web browser" as configuration; the URL must match the URL that you use for logging in:
The final screen shows you the Client ID you need to copy into the PBX web interface. A typical client ID has the form xxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.apps.googleusercontent.com.
Copy the Client ID into the domain settings, "Google sign in client ID." Hit the save button.
The next time someone visits the login page, there will be a small login field under the login submit button to trigger the login process; right now this service is only available for user accounts.
System and domain administrators still need to use their username and password credentials as before. Fortunately, most browsers today support storing those credentials, so repeated logins shouldn’t be too inconvenient.
This will be generally available for 60.2 builds. We have already included it in some 60.1 test builds.
JavaScript IVR transforms the way businesses handle incoming calls by enabling fully customizable, intelligent phone menu systems. Unlike static IVR setups with limited, pre-defined options, JavaScript IVR allows you to create dynamic call flows that adapt in real time based on caller input, business data, or even external API integrations. This means you can route calls more efficiently, automate complex processes, and offer highly personalized experiences to your customers. Whether you want to check customer records before transferring a call, adjust menu options based on time of day, or integrate with CRM systems for instant data access, JavaScript IVR gives you the flexibility and control to make it happen - all while improving efficiency and enhancing caller satisfaction.
Vodia support is now easier to access through the Vodia Help Center on Jira, giving partners and customers a centralized platform to submit technical support tickets, ask sales or licensing questions, and suggest new features. With a valid license key, users can open detailed requests and track their status in one place. The portal also brings together Vodia documentation, the PBX API, and the Vodia forum, making it the go-to resource for everything Vodia. Whether you're troubleshooting, planning an upgrade, or just need guidance, the Help Center is designed to streamline your experience and connect you with the right support faster.
At ChannelCon 2025 in Nashville, Vodia Sales Engineer Eric Altman engaged with MSPs and IT professionals to explore how AI is shaping the future of managed services. He emphasized that ChannelCon remains a valuable space for building strong vendor-partner relationships, especially as AI continues to dominate industry conversations. Altman noted how Vodia is helping MSPs unlock greater flexibility by combining powerful PBX features with AI-driven capabilities like dynamic call analytics, customized call flows, and automated performance reporting. He also highlighted Vodia’s recent launch of prepaid cloud instances on AWS, DigitalOcean, and Microsoft Azure, designed to streamline deployment for MSPs without infrastructure or licensing delays.