Skip to main content

PhoneServer Providers

The PhoneServer Providers panel displays the synchronization status with the PhoneServer. This helps you monitor provider health and troubleshoot connectivity issues.

Accessing PhoneServer Providers​

The PhoneServer Providers panel is its own top-level page. In the sidebar's Global section, open Phone Server (requires the Provider Manager role).

PhoneServer Providers

The page has three panels — Phone Server Providers (per-provider sync status), PhoneServer Connection Health, and Recent Sync Events (All Providers) — plus a Resync all button in the top-right that re-syncs every STT and TTS provider at once.

PhoneServer Connection Health​

The PhoneServer Connection Health table shows all PhoneServers that have ever connected to the platform.

PhoneServer Connection Health

Health Check Monitoring​

  • Disconnected PhoneServers appear in the platform health check at /api/health
  • This allows monitoring of connection issues across all registered PhoneServers

Cleaning Up Connections​

If a PhoneServer should no longer communicate with the platform (e.g., it was only used for a demo), you can remove it from health checks by clicking the delete button. This prevents it from appearing in the health check results.

Understanding the Provider Table​

The table displays all STT and TTS providers with their sync status:

ColumnDescription
TitleProvider name with an icon indicating STT (microphone) or TTS (speaker)
TypeSTT for Speech-to-Text, TTS for Text-to-Speech
StatusCurrent synchronization status
Last SyncTimestamp of the last successful sync, or "Never" if not synced
ErrorError message if sync failed

Sync Status Values​

StatusBadge ColorMeaning
SYNCEDGreenProvider is successfully synchronized with PhoneServer
PENDINGGraySync is in progress or queued
FAILEDRedSync failed - check error message
DIRTYYellowConfiguration changed, needs resync

Filtering Providers​

Use the filter buttons in the top right to view:

  • All - All STT and TTS providers
  • STT - Only Speech-to-Text providers
  • TTS - Only Text-to-Speech providers

Sync Process​

Automatic Sync​

Providers are automatically synchronized when:

  1. A new provider is created
  2. An existing provider is updated
  3. A provider is enabled for a bot under Bot → Providers
  4. PhoneServer reconnects after disconnection
  5. Phone channel configuration changes

Each of these triggers a full sync: every enabled STT and TTS provider of the tenant is re-sent to the PhoneServer along with all phone channel configurations, not only the provider you changed. Providers that are not enabled for any bot are skipped — the PhoneServer only ever receives providers that a bot actually uses.

Synchronization requires a connected PhoneServer. While no PhoneServer is connected, syncs are not queued: a changed provider is left as DIRTY ("Needs Sync") instead. The next time a PhoneServer connects, it receives a full sync automatically and those providers return to SYNCED.

Manual Resync​

To manually trigger a resync, click Resync all in the top-right of the page. This re-syncs every enabled STT and TTS provider at once. Re-saving a provider under Provider Management has the same effect.

Tip: Use Resync all when a provider shows "FAILED" status after fixing the underlying issue.

Note: Resync all fails with an error if no PhoneServer is connected. Check the PhoneServer Connection Health table first.


Troubleshooting Sync Issues​

Provider Shows "FAILED"​

Common causes:

  • Invalid API credentials - Verify your API key is correct
  • Network connectivity - Check if the provider's API is reachable
  • Configuration error - Review provider settings
  • Service outage - Check provider status page

Steps to resolve:

  1. Check the Error column for details
  2. Navigate to Provider Management and edit the provider
  3. Verify and update credentials if needed
  4. Save the provider — saving already triggers a resync
  5. If the status does not change, click Resync all

Provider Stuck on "PENDING"​

PENDING means the provider was sent to the PhoneServer but no acknowledgement came back. This may indicate:

  • The PhoneServer disconnected mid-sync
  • High server load
  • Network latency

Steps to resolve:

  1. Wait a few moments for sync to complete
  2. Refresh the page
  3. Check the PhoneServer connection status in the PhoneServer Connection Health table
  4. If still pending, click Resync all

"Never" in Last Sync Column​

The provider has never been successfully synced. This typically means:

  • Provider was just created
  • Provider is not enabled for any bot, so it is never sent to the PhoneServer
  • All sync attempts have failed
  • PhoneServer has never connected

Steps to resolve:

  1. Verify PhoneServer is connected (check the PhoneServer Connection Health table)
  2. Verify the provider is enabled for at least one bot under Bot → Providers
  3. Review provider configuration
  4. Click Resync all to trigger a new sync attempt

Provider Keeps Returning to "FAILED"​

If a provider fails again after every resync:

  • There may be a persistent configuration issue
  • The provider credentials may be invalid
  • The external service may be unavailable

Steps to resolve:

  1. Verify the external service is operational
  2. Double-check all provider credentials
  3. Test the provider in the external service's own console
  4. After fixing, reset by editing and saving the provider

Connection Status​

The PhoneServer connection status is shown in the Phone Channel header:

StatusMeaning
ConnectedPhoneServer is connected and can process calls
DisconnectedNo connection to PhoneServer
ErrorConnection error occurred

If the PhoneServer is disconnected:

  • Provider syncs are skipped and run again automatically once it reconnects
  • Phone calls cannot be processed
  • Contact your administrator

Provider Error Messages​

Common error messages and their meanings:

ErrorMeaningSolution
STT processing failedSTT service rejected the configurationCheck API key and language settings
Error while receiving TTS responseTTS service returned an errorVerify credentials and voice settings
Connection timeoutCould not reach the providerCheck network connectivity
Invalid credentialsAPI key is incorrect or expiredUpdate API credentials
Unsupported languageLanguage code not supportedCheck provider's supported languages

Best Practices​

Multiple Providers​

  • Configure backup providers of the same type
  • If one provider fails, switch to backup in phone channel settings
  • Different providers have different strengths (quality vs. latency vs. cost)

After Configuration Changes​

  • Always verify sync status after changing provider settings
  • Wait for "SYNCED" status before testing phone functionality
  • If sync fails, check error details before troubleshooting further