Skip to main content
Use the Voice dashboard to monitor managed PMA-Voice compatible instances after setup. The dashboard shows instance state, region, endpoint, port, latest heartbeat and connected client count when the instance reports it.

Dashboard tabs

TabUse it for
InstancesReview active Voice instances and open instance details.
RegionsCheck regional availability before creating or moving service capacity.

Instance details

Open an instance to review:
  • Instance status.
  • Region.
  • Endpoint hostname and port.
  • Registered server ID.
  • Last heartbeat.
  • Connected clients when available.
  • Generated PMA-Voice server.cfg settings.
Copy the setup block from the instance detail page whenever you need to reconfigure PMA-Voice.

Status reference

StatusMeaning
ProvisioningFiveMesh is preparing the managed Voice instance.
OnlineThe instance is available and can be used by the server.
RestartingA restart has been requested and is still in progress.
ErrorThe instance needs attention or support review.
DeletingThe instance is being removed.
DeletedThe instance was removed and no longer serves the registered server.

Restart an instance

1

Open the instance

In Voice, open the instance detail page.
2

Request restart

Click Restart.
3

Wait for status to recover

Watch the status and heartbeat before changing PMA-Voice settings again.
Restart is unavailable while an instance is provisioning, deleting or already deleted.

Delete an instance

Delete a Voice instance only when the registered server should stop using managed Voice infrastructure. Deleting the instance frees the plan slot. It does not remove the registered server from FiveMesh.
You cannot delete an instance while provisioning is still in progress. Wait for provisioning to finish, then delete the instance if it is no longer needed.

Heartbeat and clients

The dashboard uses heartbeat data to show whether the Voice agent is reporting and how many clients are connected. If the heartbeat is missing or stale:
  • Confirm the instance is online.
  • Confirm the server is using the latest endpoint and port from the detail page.
  • Restart the instance if the action is available.
  • Open a Discord ticket with the workspace, registered server ID, instance ID and region.