Audio messages and conferences ready for international use
MaxiPBX is evolving into a complete communications platform: multilingual audio message generation, prompt studio, male/female voices, background music, LiveKit conferences and multi-server architecture.
Google Text-to-Speech and 60 languages
The TTS engine aims for broad linguistic coverage, with a Bring Your Own Key logic to let each client manage their own supplier keys.
- Google Cloud Text-to-Speech configuration via JSON service account or API key
- Testing credentials before saving and listing available voices
- Credentials encrypted at rest and never displayed again
- Database compatible with MaxiPBX's 60-language ecosystem
Audio studio for prompts, IVR and announcements
Audio generation must become a business tool, not just a text field.
- Source text by language and context of use
- Choice of voice, gender, language and variants based on provider
- Preparation of background music, preview and final rendering
- Organization of audio files by tenant and by usage
LiveKit video conferencing
Video conferencing relies on LiveKit to avoid reinventing the real-time core, with architecture designed for multiple servers.
- Distribution of meetings across multiple LiveKit servers
- Ability to deploy a dedicated conference server at a demanding client's site
- Possible separation between mobile push, TTS and video to reduce risks
- Architecture ready for international scaling
Generic or branded messages
Audio and video content must be able to serve the MaxiPBX brand or partner brands.
- Generic prompts without logo for multi-brand use
- Branded content according to partner profile
- Wiki and tutorials eventually managed from the ControlPlane
- Translations and voices consistent with the client's language
Frequently asked questions
Why Google TTS rather than a single AI voice provider?
Google offers very broad linguistic coverage, which aligns better with the 60-language objective. The model is designed to allow adding other providers if needed.
Do AI keys belong to MaxiPBX or the client?
The planned model is Bring Your Own Key: the client or partner can enter their own key within their scope, with encryption at rest.
Must LiveKit necessarily run at MaxiPBX?
No. For clients who want to host the conference themselves, a dedicated LiveKit server can be deployed on their VM and connected to the ecosystem.
Ready to streamline your voice messages and video conferencing?
We can define with you the languages, voices, branding rules and conference architecture that suits you.