In the Telnyx Mission Control Portal (or via the API at api.telnyx.com/v2/), create a SIP Connection for inbound traffic; choose credential-based authentication (username/password) or IP-based authentication and note the SIP proxy endpoint sip.telnyx.com.
Create an Outbound Voice Profile and assign the SIP Connection to it; set the outbound destination (PSTN or SIP peer) and configure concurrent call limits, traffic type (business-phone, BYOC, etc.), and codec preferences.
Assign purchased Telnyx phone numbers to the SIP Connection for inbound routing; configure the inbound webhook URL to receive call events.
In your PBX or SBC, set the SIP registrar/proxy to sip.telnyx.com (or a regional edge PoP); configure credentials matching those set in the Connection.
Test with an inbound and outbound call; verify SIP signalling reaches Telnyx, RTP media flows correctly, and call events are received at your webhook.
Known gotchas
Credential authentication requires periodic SIP re-registration; configure your SBC keep-alive OPTIONS pings to match your provider's session expiry to avoid silent registration drops.
Telnyx enforces E.164 format for dialled numbers on outbound calls; local-format or national-format numbers will be rejected.
Outbound Voice Profile concurrent call caps are enforced strictly — exceeding them returns 503; set appropriate limits before load testing.
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