Getting Started with Telnyx
SIP Signaling Addresses
Telnyx SIP Regions
Telnyx SIP proxies are available in the following regions:
| Region | FQDN | IP Address 1 | IP Address 2 |
|---|---|---|---|
| US | sip.telnyx.com | 192.76.120.10 | 64.16.250.10 |
| Europe | sip.telnyx.eu | 185.246.41.140 | 185.246.41.141 |
| Australia | sip.telnyx.com.au | 103.115.244.145 | 103.115.244.146 |
| Canada | sip.telnyx.ca | 192.76.120.31 | 64.16.250.13 |
| Asia (Beta) | sip.telnyx.asia | 103.115.244.158 | 103.115.244.159 |
SIP Regions affect only the signaling path. To control where media is anchored, see AnchorSite™ below.
Outbound Calls
You can configure your SIP server or device to send calls to any SIP region listed above. Use the FQDN or IP addresses depending on your device's requirements.
The FQDNs for each region support DNS record types A, SRV, and NAPTR. DNS A records resolve to IP address 1. SRV and NAPTR records provide round-robin routing across both IPs and advertise available transport protocols and ports.
⚠️ Outbound calls from the same IP address or SIP username are limited to 20 calls per second. Telnyx reserves the right to adjust this limit.
Inbound Calls
Telnyx delivers inbound calls to your SIP infrastructure using one of two methods:
If your device uses SIP registration, register to any SIP region listed above.
For IP or FQDN authentication, select your inbound SIP region in the Inbound section of your Connection in Mission Control. If no SIP Region is explicitly configured, Telnyx selects it based on your AnchorSite™ setting. This determines which proxy IPs deliver calls to your infrastructure.
⚠️ If you use an ACL or firewall, allow-list all IP addresses for your selected SIP Region.
Transport Protocols
Telnyx supports the following transport protocols for SIP signaling:
| Transport Protocol | Port |
|---|---|
| UDP | 5060 |
| TCP | 5060 |
| TLS | 5061 |
JSON API
The signaling addresses, transport protocols, and media CIDRs listed on this page are also available as a machine-readable JSON file:
https://sip.telnyx.com/voice.json
Use this endpoint to programmatically keep your firewall rules, SIP configuration, or monitoring tools in sync with the latest Telnyx network information.
AnchorSite™
The AnchorSite™ setting controls which Telnyx Point of Presence (PoP) handles the media for your calls. Configure it per Connection on the Connections page.
Latency (default)
Telnyx proactively pings your connection using ICMP ping messages to measure round-trip times from all available sites. The PoP with the lowest latency is automatically selected.
⚠️ Allow the Telnyx media IP addresses listed in this article on your firewall so ICMP pings can reach your endpoint.
Manual
If you know which PoP best serves your setup, you can anchor your media to a specific site. This is recommended when your media IP is in a different region than your signaling IP (latency detection is based on signaling IP) or when ICMP is not supported.
Regardless of which option you choose, Telnyx will always re-route to the next closest available site in the event of an outage or maintenance event.
When using Credential Connections, include your SIP authentication username in the Contact header of the first INVITE during digest authentication. If unsupported, pass it in a custom header instead: X-Telnyx-Username: <username>.
More details here: AnchorSite™ guide
Media
The RTP port range used by Telnyx is 16384 to 32768 (UDP).
Telnyx uses the following media IP addresses for RTP streams.
⚠️ If you use an ACL or firewall, allow-list these addresses:
Subnets (containing all media IPs)
36.255.198.128/25
50.114.136.128/25
50.114.144.0/21
64.16.226.0/24
64.16.227.0/24
64.16.228.0/24
64.16.229.0/24
64.16.230.0/24
64.16.248.0/24
64.16.249.0/24
103.115.244.128/25
185.246.41.128/25Codecs
Telnyx supports the following audio and video codecs:
- G.711U (PCMU)
- G.711A (PCMA)
- G.729
- G.722 (wideband)
- Opus (wideband)
- AMR‑WB (wideband, HD Voice)
- H.264 (video)
- VP8 (video)
Telnyx uses a 20 ms packetization interval (ptime=20) for RTP media.
Setting Up Mission Control
Regional Note: The examples in this guide use sip.telnyx.com (US region) throughout. You can substitute this with the FQDN for any preferred region from the SIP Regions table — all ports and transport protocols are identical across regions.
Initial setup
- Log in to Telnyx Mission Control.
- Create a Connection for your SIP device. Choose from the following authentication types:
- Credentials (username and password) — inbound and outbound
- IP address — inbound and outbound
- FQDN (inbound) + Credentials (outbound)
- FQDN (inbound) + IP address (outbound)
Making outbound calls
- Create an Outbound Profile and assign your Connection to it.
- Configure your SIP device to send calls to
sip:sip.telnyx.com:5060(UDP or TCP) orsip:sip.telnyx.com:5061(TLS) - Destination numbers in +E.164 format are supported by default. You can configure regional settings on your Connection to allow local dialing formats.
Receiving inbound calls
- Purchase a number and assign it to your Connection.
- If you chose Credentials authentication, register your SIP device with your username and password to
sip:sip.telnyx.com:5060(UDP or TCP) orsip:sip.telnyx.com:5061(TLS) before receiving calls. - With IP Authentication, Telnyx delivers calls from one of your inbound SIP Region's IP addresses (see table above) using UDP by default. To use TCP or TLS, edit the SIP Transport Protocol option for Inbound Calls on the Connections page.
- You can enter multiple IP addresses with different priorities. Telnyx attempts each address in priority order, respecting the No Ringback Timeout setting.
- With FQDN Connections, Telnyx routes calls to the resolved FQDN records (SRV records supported).
Encryption
Telnyx supports TLS versions v1.2 and v1.3 for encrypted signaling, and SRTP for encrypted media.
For outbound calls, you can configure your device to use TLS and SRTP and make calls without further configuration on the Telnyx portal.
For inbound calls, you can enable TLS with SRTP in the Connections page.
Media Handling
Telnyx auto-detects your media IP address by monitoring early RTP packets. If the actual IP:port differs from what was negotiated in SDP, Telnyx adjusts automatically. Disable this via Disable RTP Auto Adjust under Expert Options on the Numbers page.
To accept RTP from any source for the entire call, enable Accept any RTP packets under Expert Options on the Numbers page.
FAX
Telnyx supports fax over G.711 or T.38.
For inbound fax, Telnyx expects a T.38 re-INVITE from the customer by default. If no re-INVITE is received, the call continues with G.711. Disable this via the T.38 option on the Numbers page.
For outbound fax, choose a fax mode using the T.38 Re-invite Initiated By options in the Outbound tab on the Connections page:
- Telnyx Telnyx sends a T.38 re-INVITE after detecting a fax tone
- Customer Telnyx expects a T.38 re-INVITE from the customer
- DisabledTelnyx won't send a T.38 re-INVITE and will reject any received
STUN
Telnyx provides STUN service using the following addresses:
stun.telnyx.com:3478TURN
Telnyx provides TURN service using the following address:
turn.telnyx.com:3478Request TURN credentials by emailing support@telnyx.com.
SIP Over WebSockets
SIP over WebSockets enables real-time voice calls directly from the browser, with no plugins required. The browser handles audio and media natively, while SIP signaling is carried over a WebSocket connection.
Use a third-party SIP JavaScript library (such as SIP.js or JsSIP) to connect directly to Telnyx's SIP WebSocket endpoints, using the same SIP regions listed above.
Example for US SIP region:
wss://sip.telnyx.com:7443 (encrypted)For more development flexibility, consider the Telnyx WebRTC Voice SDK — Telnyx's own library that abstracts SIP entirely, handling connection management, authentication, and call control through a higher-level API.