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.

Selected server

Choose the registered server in the sidebar, then open Voice. The page displays the instance for that server. Region selection appears during activation; V2 does not use the old all-instances and regions tabs.

Instance details

Open the server’s Voice page 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

Restart an instance

1

Open the instance

Select the server in the sidebar, then open Voice.
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.

Retry provisioning

If the endpoint and port are missing after a failed provisioning attempt, use Retry provisioning when offered. Wait for connection details before applying the PMA-Voice configuration. Contact support if retry fails.

Delete an instance

Delete a Voice instance only when the registered server should stop using managed Voice infrastructure. Remove or replace the external Voice settings in server.cfg before stopping the service. 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.