Twilio Error 32011: Trunk Not Found Elastic SIP Trunking: Causes and How to Fix It

Twilio error 32011 is specific to Elastic SIP Trunking and means that the SIP INVITE or REGISTER request arriving at Twilio's SIP infrastructure cannot be matched to any existing SIP trunk in your account. This is a trunk lookup failure: the combination of the Request-URI domain, the From header, and the SIP credentials in the request do not resolve to a configured trunk. The error results in a SIP 404 Not Found response being returned to your PBX.

What Causes This Error

Configuring your on-premise PBX or SIP gateway to send calls to a SIP trunk FQDN that does not match the termination URI provisioned for your Elastic SIP Trunk is the most common cause: the trunk FQDN is in the format yourtrunk.pstn.twilio.com and must match exactly what your PBX is targeting. A SIP trunk that was deleted from the Twilio Console under Elastic SIP Trunking while still referenced by the PBX configuration produces 32011 for every outbound call attempt, since the trunk no longer exists in Twilio's routing database. Typographical errors in the PBX trunk configuration, such as a missing hyphen in the subdomain or an incorrect TLD (for example, .twilio.net instead of .twilio.com), prevent Twilio from matching the incoming INVITE to any trunk. Using a different Twilio account's trunk FQDN in your PBX, which can happen during a migration from one Twilio account to another when the PBX configuration is not updated, results in 32011 because the trunk belongs to a different account than the one receiving the request.

How to Fix It Step by Step

Log into the Twilio Console and navigate to Elastic SIP Trunking, then Trunks to confirm your trunk exists and is in an active state: note the exact Termination SIP URI shown on the trunk's General Settings page. Compare this URI character by character against what your PBX is configured to use as the outbound SIP trunk endpoint: even a single character difference causes 32011. Update your PBX's SIP trunk configuration to use the exact Termination SIP URI from the Console, ensuring the format matches yourtrunkname.pstn.twilio.com with HTTPS or UDP transport as configured on the trunk. After updating the PBX configuration, make a test call and verify the Twilio Debugger under Monitor, then Debugger shows the SIP INVITE being received and matched to the correct trunk.

How to Prevent It from Recurring

Document your Elastic SIP Trunk Termination URI in your team's infrastructure runbook and require that any PBX configuration change involving the SIP trunk endpoint be verified against this documented value before deployment, preventing typos from reaching production. Set up Twilio Console Alerts under Monitor, then Alerts for 32011 errors so your team is immediately notified when the error appears, rather than discovering the issue through dropped calls or user complaints. Implement a SIP OPTIONS health check from your PBX to the trunk FQDN at a 60-second interval: a non-200 response to the OPTIONS indicates the trunk is unreachable or misconfigured and triggers an alert before calls fail. When deleting or modifying Elastic SIP Trunks in the Console, check the list of all systems that reference the trunk FQDN (PBX, SBC, TwiML applications) and update all of them atomically before the change is committed, preventing a scenario where a trunk deletion breaks a system that was not updated.

When to Call a Specialist

If the trunk exists in the Console and the PBX is targeting the correct FQDN but 32011 errors persist, there may be a DNS resolution inconsistency where the PBX is resolving the trunk FQDN to an IP address in a different Twilio region than the region where the account's trunk is provisioned, causing the SIP INVITE to arrive at a Twilio regional cluster that does not have visibility into your trunk. A specialist can capture SIP INVITE packets from the PBX, trace the DNS resolution of the trunk FQDN, and identify if the resolved IP belongs to the correct Twilio region. You should also escalate if you are migrating trunks between Twilio accounts as part of a business acquisition or restructuring, as trunk migration requires specific sequencing and credential updates that a specialist can manage to avoid 32011 downtime during the transition.

Conclusion

Error 32011 is an Elastic SIP Trunk lookup failure caused by a URI mismatch or deleted trunk, and it is fixed by verifying the Termination URI in the Console and updating the PBX configuration to match exactly. If this error is blocking your production system, contact our team and we will diagnose and fix it within the hour.