Clear answers before deployment.
Product, commercial and operational decisions in plain language.
Product
Is RelayPBX only a PBX?
No. The same control plane covers business PBX, contact-center and service-provider operating models. Features and limits depend on the edition.
Can one installation host several customers?
Yes in Service Provider and selected Enterprise configurations. Tenant isolation is enforced in APIs, data access and file operations.
Does configuration require a FreeSWITCH restart?
Most routing and directory configuration is delivered dynamically. Changes are activated without restarting live services.
Deployment & licensing
Can I run it on my own server?
Yes. Community and commercial editions support self-hosted deployment. A managed cloud option follows the same product model.
What happens if the license server is unavailable?
Live calls do not depend on the licensing service. The PBX verifies a signed local license and uses a grace period for control-plane outages.
Will there be an ISO image?
Yes, after the Linux installer and upgrade path are proven. VM images come first so the same first-run workflow can mature without maintaining an operating-system fork too early.
Operations & support
How are updates made safe?
Each release requires a preflight, encrypted backup, versioned database migration, health verification and an application rollback path.
Can support inspect SIP and SDP details?
Call history connects the logical flow to debug data. Packet capture can be enabled with retention and access controls when deeper protocol inspection is required.
What support options are planned?
Community uses public documentation and community channels. Paid plans add ticketing, response targets and optional 24/7 escalation.
Need an answer for your environment?
Bring your topology, constraints and target call flow.