> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Telnyx

> Map Telnyx SIP Connections, number assignments, and Outbound Voice Profiles into a future telephony deployment review.

Prepare Telnyx routing as a SIP integration candidate. There is no Telnyx-specific Threetone phone import or released Telnyx adapter. A saved generic SIP record does not connect these systems.

## Identify the provider objects

Telnyx uses a SIP Connection for authentication and incoming routing, assigns numbers to a connection, and uses an Outbound Voice Profile for outbound policy. Review [Telnyx's SIP getting-started guide](https://developers.telnyx.com/docs/voice/sip-trunking/get-started) with the carrier account owner.

| Object | Information to collect |
| - | - |
| SIP Connection | Identifier, authentication method, routing destination, and relevant network settings. |
| Phone number | Exact number and assigned connection. |
| Outbound Voice Profile | Linked connection, permitted destinations, and account-owner-approved spending controls. |

## Prepare the mapping

<Steps>
  <Step title="Trace inbound routing">Follow the number to its assigned connection and current destination. Document what will happen to callers during a failed or rolled-back deployment.</Step>
  <Step title="Trace outbound routing">Confirm that the intended connection is associated with the correct Outbound Voice Profile. A working inbound route does not establish outbound authorization.</Step>
  <Step title="Review the SIP candidate">Map the carrier destination, authentication, source restrictions, transport, and media requirements to the [SIP reference](/agents-platform/deploy/telephony/sip-reference). Keep the Telnyx API key separate from trunk credentials.</Step>
  <Step title="Require runtime readiness">Before changing number routing, verify a supported Threetone ingress, credential handoff, and executable agent version. Prepare independent inbound and outbound acceptance cases.</Step>
</Steps>

## Failure handling

If incoming calls take the wrong route, inspect the number-to-connection assignment first. If only outbound calls fail, review profile linkage, destination policy, and provider error details. If signaling succeeds but audio fails, examine negotiated media and network access before changing application prompts.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does importing a SIP record create a Telnyx Connection?" id="telnyx-faq-connection">No. Threetone import stores configuration and does not create provider resources.</Accordion>
  <Accordion title="Can I use a Telnyx number through the current Twilio outbound path?" id="telnyx-faq-outbound">No. That service requires Twilio fulfillment. A generic SIP import does not satisfy the provider requirement.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.