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

# Telnyx SIP Connection: console steps for Wixzel Voice

> Connect a Telnyx SIP Connection to Wixzel Voice for AI phone calls: IP authentication, the platform IP under Outbound, an inbound region and a transport.

Agents you build on Wixzel Voice place and answer phone calls over a SIP trunk
you bring, and a Telnyx SIP Connection is one of the carriers that works with
it. Telnyx bills you for the trunk and the minutes at your own rates; the voice
engine is billed per second of actual usage from your Wixzel Voice balance. This
page covers where Telnyx keeps each setting. The steps that are the same for
every carrier, and the troubleshooting list, are on [SIP trunks](/sip-trunks).

<Info>
  Allowlist **`95.216.218.102`** for outbound calls, and send inbound calls to
  **`sip:95.216.218.102:5090`**. Every trunk returns both as `platform_ip` and
  `origination_uri`, so read them from `GET /v1/sip-trunks` rather than trusting
  this page to stay current.
</Info>

## How do I connect a Telnyx SIP Connection to Wixzel Voice?

Both directions go through one Telnyx **SIP Connection**.

<Steps>
  <Step title="Create an IP-authenticated SIP Connection">
    **Mission Control → SIP Connections**, then set the connection type to
    **IP authentication** rather than credentials or FQDN registration.
  </Step>

  <Step title="Add the platform IP under Outbound">
    Add **`95.216.218.102`** as an authorised address. Telnyx lets you list
    several with priorities and tries them in order.
  </Step>

  <Step title="Pick an inbound SIP region">
    Telnyx asks for one explicitly for IP and FQDN authentication. Left unset it
    is derived from your AnchorSite, which is rarely what you meant.
  </Step>

  <Step title="Set the transport to match your trunk">
    Telnyx delivers over **UDP** by default. If your Wixzel Voice trunk sets
    `transport` to `tcp` or `tls`, change the SIP Transport Protocol on the
    connection to match, or the two ends will not agree.
  </Step>

  <Step title="Point the number at the connection">
    Assign your numbers to this connection so inbound calls reach it, then give
    the number an `inbound_agent_id` in Wixzel Voice so there is an agent to
    answer.
  </Step>
</Steps>

Telnyx expects the leading `+`, so leave `send_plus` at its default.

## What if a Telnyx call does not connect?

Work through [When a call does not connect](/sip-trunks#when-a-call-does-not-connect),
and start with Telnyx's own call logs: they show whether the call reached
Telnyx at all and how Telnyx cleared it.

## Related

* [SIP trunks](/sip-trunks): the allowlist, the inbound address and the
  troubleshooting list that apply to every carrier.
* [Quickstart](/quickstart): connect the trunk, register a number, create an
  agent and place a first call.
* [Telnyx SIP trunk setup](https://voice.wixzel.com/integrations/telnyx):
  the short version on the Wixzel Voice site, with what a minute costs on each
  voice engine.