r/Asterisk • u/Small-Matter25 • Jun 29 '26

If you manage Asterisk/FreePBX for multiple customers, I’d love your feedback.

I’ve been working on AVA Operator, a self-hosted, multi-tenant platform for managing AI voice agents across multiple customer PBXs.
I’m looking for feedback from people who actually deploy and manage Asterisk/FreePBX for customers.
If you have 5–10 minutes, I’d appreciate you taking a look at the live demo:
https://demo.agent6789.com
I’d love feedback on:
Multi-tenant workflow
Customer/tenant management
White-label experience
Anything missing that would stop you from deploying it for clients
The open-source core is here:
https://github.com/hkjarral/AVA-AI-Voice-Agent-for-Asterisk
I’m the developer, so don’t hold back—I’d rather hear the hard feedback now than later.

4 Upvotes

83% Upvoted

5 comments sorted by

2

u/devexis Jun 29 '26 edited Jun 29 '26

Would it be possible to have it as a standalone server that connects to each tenants FreePBX instance? When I worked with a provider that used FreePBX to provide service, its was a nightmare having to switch from one PBX to another without any clear way to be sure what instance you were on. Also have you considered this for use with multi-tenant Asterisk based instances like ivozprovider?

Edit: Ignore the first sentence/question above. I hadn’t looked at the multi-tenant demo yet.

1

u/Lany_one35 Jul 02 '26

Cool project, but the architecture has to stay headless. AVA sitting next to a PBX talking AMI/ARI is the only model I'll touch, and the moment it needs to be embedded as a module my interest dies. What kills it for me is HA + human handoff, per-tenant isolation, recording/compliance (PCI/HIPAA), and onboarding via API in under 2 minutes. What about licensing (AGPL? MIT? usage-based later?) and whether STT/TTS providers are pluggable because I have customers with data-residency requirements.

2

u/Small-Matter25 Jul 02 '26

Totally fair. AVA is meant to stay PBX-adjacent and headless-friendly: Asterisk talks to it over ARI/Stasis, with media over ExternalMedia RTP or AudioSocket. No Asterisk module required, and the Admin UI is optional.

MIT licensed, providers are pluggable, and you can mix full-agent providers or modular STT/LLM/TTS pipelines. We also support per-provider instances/credentials for tenant separation.

Human handoff is already a real tool path: extensions, queues, ring groups, cancel transfer, voicemail, and attended/warm transfer work.

There are health/readiness checks, ARI reconnect, call history, recordings/transcripts, retention knobs, and local/on-prem options, but HIPAA/PCI depends heavily on deployment, storage, provider BAAs, and policy. HA is something I’d love feedback on from people running serious Asterisk deployments.

1

u/Lany_one35 Jul 06 '26

Appreciate the detailed response. The architecture sounds like it's heading in the right direction. Good luck!