The Vodia PBX integrates with the Google Translate API to transcribe voicemail recordings into text; this text is then included in voicemail notification emails. To enable this feature, you’ll need a Google Cloud account, along with an active Voice API subscription key - this can be created under “APIs & Services” in the Google Cloud Console. This API key, which should be restricted for security, is entered into the Vodia PBX system to activate transcription capabilities. For multi-tenant setups, voicemail transcription can be managed per domain or disabled for specific extensions, offering flexible control over API usage.
Google offers a powerful API for converting speech into text. The Vodia PBX is currently using this feature to convert voicemail recordings into text format; it includes that text in the voicemail notification, which is typically sent to the user by email. This API must be enabled in the Google Cloud Console.
After you have set up an account with Google Cloud, make sure you provide your credit card information so you can enable the Voice API. You will also have to create a project that holds the API key. You can do this in “APIs & Services” in the Dashboard area.
Activating Google Cloud Subscription Key
After you have created a project, you need to navigate to the “Credentials” area, where you can create new credentials for your project. You need to create a new API Key.
You should then restrict the key by some means (e.g., by limiting it to your server IP address) so nobody else can use that key unless it's used from that IP address.
Enable Voicemail Transcription in Vodia PBX
After you have set up your account on the Google console, copy the API Key into the PBX in admin mode, General/Settings/Notifications. There you can also determine if domains should have the feature enabled or not, unless you set it explicitly in the domain settings.
Multi-Tenant Scenario
In some cases, you would want to disable the Google API per extension. To disable, go the main page of your domain page and click on the edit button, scroll down to "Enable voicemail to text API" and switch it to off.
Vodia’s 2025 marked a year of pragmatic AI adoption, unprecedented platform robustness, and laying the foundation for the next phase of the PBX. With version 69 reaching exceptional stability, focus has shifted to version 70, which introduces a redesigned admin interface and major architectural improvements in scalability, resilience, and flexibility. Alongside steady expansion of integrations and partner tooling, the roadmap for 2026 emphasizes refined user experiences, modernized apps, and continued investment in reliability over hype.
Delaying PBX upgrades may feel safe in the short term, but real-world dependencies like security standards, app compatibility, and vendor APIs eventually force reactive upgrades at the worst possible time. Staying reasonably current with Vodia PBX versions, rather than clinging to outdated releases or jumping on every new preview, helps maintain security, compatibility, and performance while avoiding emergency upgrades, especially as newer features and OS requirements become unavoidable.
The New York City Department of Education has issued a Request for Expression of Interest signaling its intent to modernize district-wide communications by moving away from legacy landline PBX systems. Serving 1.1 million students across 1,800 schools, the proposed transition to a cloud-based VoIP platform focuses on resiliency, scalability, multilingual capabilities, hybrid deployment options, and integration with Microsoft Teams for more than 150,000 staff members.
.svg)
