Enterprise

Multi-PBX Management

Multi-PBX management lets you connect and manage multiple FusionPBX instances from a single CrystalQore installation. This is an Enterprise tier feature, ideal for organizations with distributed phone systems, multiple offices, or hosted deployments serving many customers with separate PBX servers.

Overview

With Multi-PBX:

• Multiple FusionPBX servers — Connect several PBX instances to one CrystalQore
• Tenant-to-instance assignment — Each tenant is assigned to a specific PBX instance
• Centralized monitoring — View connection status for all instances in one place
• Cross-instance user management — Manage users across tenants and PBX instances from the Superadmin panel

Why Multi-PBX?

Assigning Tenants to PBX Instances

When you create or edit a tenant, you assign it to a PBX instance:

1. Navigate to Admin → Tenants
2. Create or edit a tenant
3. Select the PBX instance from the dropdown
4. Save

Users in that tenant will use the assigned PBX for:

• Extensions and dial plan
• Call routing and CDR
• Presence (BLF)
• Click2Dial and call handling

Centralized Monitoring

The PBX instance management page shows all connected instances and their status:

Identify failing connections quickly and address them before users are affected.

Cross-Instance User Management

From the Superadmin panel you can:

• View users across all tenants and PBX instances
• Create users in any tenant (and thus any PBX)
• Sync users from any connected PBX instance
• Filter by tenant or PBX instance

This gives you a single pane of glass for user management regardless of which PBX they use.

Sync and Multi-PBX

When running FusionPBX Sync:

• Sync is performed per PBX instance
• You choose which instance(s) to sync
• Users and extensions from each instance are imported or updated
• Tenant mapping is determined by domain or explicit configuration

Best Practices

• Name instances clearly — "HQ", "West Coast", "Customer Acme" — for easy identification
• Monitor regularly — Check connection status; set up alerts if supported
• Document tenant-to-instance mapping — Keep a record for troubleshooting
• Plan for failover — Know how to reassign tenants if an instance goes down

Related Documentation