Skip to main content
Connic
Connectors

Telnyx Voice

An existing Telnyx phone number connects incoming callers to a Connic voice agent.

Last updated
Sync Mode
Telnyx Voice keeps the call open while the agent listens and responds. Each connector links to exactly one deployed agent with voice_config.

How it works

Connic creates a dedicated Telnyx Call Control application, assigns the selected number to it, and streams audio in both directions. Only incoming calls are supported.

The number and account remain in Telnyx. Model credentials, prompts, tools, and voice settings belong to the Connic project and agent. See Voice agents for supported realtime models and current limitations.

Setup

  1. Deploy a voice agent

    Configure a supported realtime model and voice_config on an LLM agent. Save the model provider credentials in the project and deploy the agent to the target environment.

  2. Save the Telnyx connection

    Add Telnyx Voice from the connector marketplace. Save the Telnyx API key and the account's base64-encoded Ed25519 public key. Reuse this saved connection for other numbers or Telnyx Messaging.

  3. Select the number

    Choose an existing active number from the connected Telnyx account. Clear call forwarding, technical prefixes, and destination rewrites that would bypass the agent or change the receiving number. A number already assigned to another Connic Voice application must first be released by that connector.

  4. Save the connector and link exactly one deployed voice agent. Connic creates the Call Control application and configures incoming calls automatically. Call the number and inspect the resulting run for the transcript, tool calls, timings, and errors.

Saving replaces incoming-call routing
The selected number is assigned to Connic's Call Control application. Its previous application assignment is not saved or restored when this connector is removed.

Settings and credentials

SettingValue
Telnyx connectionThe saved account credentials, also available to Telnyx Messaging connectors.
API keyA Telnyx API key with access to the account's phone numbers and Call Control applications.
Public keyThe same account's base64-encoded Ed25519 public key for verifying Telnyx webhook signatures.
Phone numberAn existing active number selected from the connected account.

Connic uses the API key to validate the account, list numbers, and configure the call application. The public key verifies incoming events; it is separate from the API key. Obtain both in the Telnyx portal. Credentials for the voice model are configured separately in the Connic project.

During a call

The agent receives the caller's speech and streams spoken responses back through Telnyx. When the caller interrupts, queued playback can be cleared. The agent's voice settings control whether it can end the conversation; a completed call is hung up through Telnyx.

Text messaging uses a separate Telnyx Messaging connector. Voice setup changes the number's call application assignment.

Changes and removal

Edit the saved Telnyx connection to rotate credentials. Edit the Voice connector to switch the number or saved connection. On removal, Connic clears only the call routing it still owns. It does not restore an earlier provider assignment. Manual changes made in Telnyx after setup are preserved.

Connic removes its unused Call Control application after the connector change is saved, provided the application still belongs to this connector and has no assigned numbers.

Troubleshooting

  • If account validation fails, check the API key's access and copy the public key from the same Telnyx account.
  • If a call is rejected, confirm the connector is enabled and linked to exactly one deployed voice agent.
  • If removal cannot clear the number's Connic application assignment, detach that application from the number in Telnyx and retry removal. Changes made manually in Telnyx are preserved.
  • Use Connic run errors together with Telnyx call logs to investigate failures. Telnyx documents the underlying media streaming protocol.