On Twilio Elastic SIP Trunking termination, if no caller ID number is in the INVITE From field, Twilio uses Remote-Party-ID or P-Asserted-Identity instead.
Checked 2026-10-02
If a Caller ID Number is not specified in the SIP INVITE's From Field, then the Remote-Party-ID or the P-Asserted-Identity will be used.
- Vendor
- Twilio
- Product
- Elastic SIP Trunking
- Subsystem
- Termination caller ID
- 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 · Allowed Caller ID Numbers in Termination calls
Cite this note
APA
WarmTransfer. (2026, October 2). SIP identity headers: P-Asserted-Identity and Diversion and History-Info: source note sip-identity-headers-twilio-pai-rpid-fallback. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-identity-headers-twilio-pai-rpid-fallback
BibTeX
@misc{warmtransfer-claim-sip-identity-headers-twilio-pai-rpid-fallback,
title = {SIP identity headers: P-Asserted-Identity and Diversion and History-Info: source note sip-identity-headers-twilio-pai-rpid-fallback},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-identity-headers-twilio-pai-rpid-fallback},
note = {Source note sip-identity-headers-twilio-pai-rpid-fallback, checked 2026-10-02}
}