Configure hosted voice with Mirta PBX

MSPControl integrates with Mirta PBX to manage customer PBX tenants from a hosting space. The current implementation supports one Mirta PBX service connection per selected service context; it is not a generic multi-provider PBX connector.

Manage Mirta PBX tenantsCreate or import tenants, link organizations and users, and review Teams and extension status.

Before you begin

You need:

• a Mirta PBX server URL;
• an API key that can access the required Mirta PBX operations;
• a server registered in MSPControl where the Mirta PBX service can be configured;
• a hosting plan with the PBX resource group and a non-zero PBX tenants quota;
• peer-role access to the PBX tenants screen.

Protect the Mirta PBX API key

The API key is used for provider-level tenant and extension operations. Keep it out of tickets and documentation, and rotate it if it is exposed.

Configure the provider

1. In the MSPControl server settings, add the Mirta PBX service.
2. Enter the Mirta PBX Server URL and API key.
3. Select Test Connection and confirm that the connection succeeds.
4. Save the service settings.
5. Add the PBX resource group to the applicable hosting plan.
6. Allocate a non-zero PBX tenants quota.
7. Open a customer hosting space and confirm that Voice > PBX Tenants appears.

Why the Voice menu is missing

The Voice menu is added only when all of these conditions are true:

1. A hosting space is selected.
2. The selected account is not an Administrator account.
3. The hosting plan contains the PBX resource group.
4. The hosting plan has a PBX tenants quota.
5. The current peer role can view the PBX tenants screen.

The menu builder evaluates the resource group and quota independently, so adding the provider service without adding the quota does not expose the customer menu.

What MSPControl manages

The current Mirta PBX integration includes:

• PBX tenant creation, update, import, disablement and deletion;
• tenant limits such as extensions, channels, queues, IVRs, DIDs and related PBX resources;
• links between a PBX tenant and an MSPControl hosted organization;
• links between Mirta extensions and MSPControl users;
• extension status for linked, unlinked and detected misconfigured extensions;
• Microsoft Teams application linking and compliance status;
• validation and setup actions for PSTN gateway, PSTN usage, voice route and voice routing policy objects.

Version support still needs an approved matrix

The source confirms the implemented Mirta PBX workflows, but it does not define a public Mirta PBX version range. Test the integration with the version used in your environment before production deployment.

Troubleshooting

Symptom	What to check
Voice is missing for one customer	Confirm the selected hosting plan contains the PBX resource group and PBX tenants quota.
Voice is missing for one technician	Confirm that technician’s peer role can view PBX tenants.
Voice is missing for every customer	Confirm that the Mirta PBX service is configured and assigned through the applicable hosting plans.
Tenant or extension data cannot be loaded	Run Test Connection, then verify the server URL, API key and network access from the MSPControl server.
Extension counts are incomplete	The edit page uses live Mirta calls for unlinked and misconfigured counts. Restore provider connectivity and refresh the page.