Twilio Elastic SIP Trunking rejects termination calls not using E.164 format with SIP 400 Bad Request, not 404 or 484.
Checked 2026-10-02
- Vendor
- Twilio
- Product
- Twilio Elastic SIP Trunking
- Subsystem
- Termination
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- Elastic SIP Trunking — Twilio · tier 2 current vendor documentation · Termination settings section (E.164 note)
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting SIP 404 Not Found and 484 Address Incomplete call failures: source note sip-404-484-troubleshooting-twilio-non-e164-400. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-twilio-non-e164-400
BibTeX
@misc{warmtransfer-claim-sip-404-484-troubleshooting-twilio-non-e164-400,
title = {Troubleshooting SIP 404 Not Found and 484 Address Incomplete call failures: source note sip-404-484-troubleshooting-twilio-non-e164-400},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-twilio-non-e164-400},
note = {Source note sip-404-484-troubleshooting-twilio-non-e164-400, checked 2026-10-02}
}