Log in to the Telnyx Mission Control Portal and navigate to SIP Trunking > SIP Connections; create a new SIP Connection, choosing either IP-based authentication (add your PBX source IP) or credential-based authentication (set a username and generate a credential).
Configure the connection's inbound settings: set the SIP URI subdomain (e.g., yourcompany.sip.telnyx.com) which your PBX will register to or use as a destination; enable the codecs your PBX supports (Telnyx supports G.711, G.722, Opus, and others).
Create an Outbound Voice Profile under Voice > Outbound: set a name, choose the traffic type (Conversational, Metered, etc.), and add the SIP Connection(s) that will use this profile for outbound calls.
Assign phone numbers to the SIP Connection via the Numbers section so that inbound PSTN calls to those numbers are delivered to your PBX via the connection.
Test inbound and outbound calling; for outbound, your PBX dials Telnyx's SIP termination address (provided in the portal) and includes the calling number in the From header matching a number on your account.
Use the Telnyx API (POST /sip_connections and POST /outbound_voice_profiles) to manage connections programmatically with YOUR_API_KEY in the Authorization header for CI/CD automation.
Known gotchas
IP authentication requires that your PBX has a fixed public IP; if the IP changes without updating the SIP Connection, inbound and outbound calls will fail with 403 Forbidden.
Telnyx routes outbound calls based on the Outbound Voice Profile's traffic type and associated numbers; ensure the calling number (From header) matches a number on your account or calls may be rejected by downstream carriers.
Telnyx's SIP trunking does not support SIP REGISTER on IP-authenticated connections; use credential-based authentication if your PBX requires registration.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp