Frequently asked questions
MiRTA PBX: common questions
Who is MiRTA PBX for?
MSPs, ITSPs and VoIP providers running multiple customer phone systems. MiRTA PBX is self-hosted, Asterisk-based software; tenants share infrastructure with logical configuration and access boundaries. Architecture and responsibilities.
What can we brand?
Brand the web interface with hostname-based themes, logos, page titles, login text and supported templates. Branding scope.
Can we keep our SIP trunks and numbers?
Yes. Supply your own carrier and numbering arrangements, and validate interoperability and routing in the pilot. MiRTA PBX does not require a bundled trunk service.
How is MiRTA PBX licensed?
€200 per licensed server per month, with no license caps on tenants, extensions, channels, DIDs, voicemail or core features. Actual workload capacity depends on the deployment. Pricing and exclusions.
Can we use one server, a cluster or virtual infrastructure?
Yes. Size physical or virtual infrastructure for the voice workload. Multiple nodes require a shared database and planned failure handling; active-call continuity is not guaranteed. Deployment choices.
Can customers administer their own tenants?
User profiles and tenant assignments restrict web administrators to permitted functions and resources. These accounts are separate from SIP extension credentials. Delegated access reference.
Are provisioning and reporting APIs available?
Yes. Use the configuration and reporting APIs to provision tenants and connect your existing systems. Tenant-scoped or global keys control access; reporting endpoints are read-only. API reference.
What support and operations are included?
Installation, MiRTA PBX software and Asterisk integration support, maintenance, updates, upgrades and bug fixes are included. OS support, monitoring and backups are separately scoped. Support boundaries.
How can we use AI?
Use a virtual receptionist for caller questions and routing, plus transcription, summaries and sentiment analysis for recorded calls. Configure services and tenant options first. Talk with AI.
Can we migrate gradually?
Plan a staged pilot around your trunks, numbers, integrations and call flows. Migration steps depend on your existing system. Review your pilot.
Plan your evaluation
Discuss questions specific to your service and pilot.