In Twilio Console, go to Elastic SIP Trunking and create a new trunk; give it a friendly name and note the automatically generated SID.
Under the Termination tab, assign a termination SIP URI subdomain (e.g., yourcompany.pstn.twilio.com) — this is the address your PBX dials to send calls out to the PSTN through Twilio.
Add IP Access Control Lists or Credential Lists to authenticate your PBX; Twilio Elastic SIP Trunks do not support SIP REGISTER, so you must add your PBX's source IP(s) as trusted peers in the Access Control List.
Under the Origination tab, add your PBX's SIP URI as an origination URI so that Twilio delivers inbound PSTN calls to your PBX; set the priority and weight for failover across multiple URIs.
Associate phone numbers or a Twilio-hosted CNAM/E.164 number with the trunk under the Numbers tab, or use the trunk SID in a BYOC number configuration.
Twilio Elastic SIP Trunks support G.711 (PCMU/PCMA) natively; if your PBX offers additional codecs such as G.729, ensure your SBC or PBX is configured to prioritize PCMU to avoid transcoding or codec mismatch errors.
Known gotchas
SIP REGISTER is not supported on Twilio Elastic SIP Trunks; authentication is IP-based via Access Control Lists — ensure your PBX has a static IP or update the ACL when IP changes.
Origination URI failover requires the primary URI to return a SIP error (5xx or timeout) before Twilio tries the next; configure your PBX health checks accordingly.
E.164 format is required for called-party numbers on the termination side; sending numbers in national format (without country code) results in a 4xx SIP response.
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