lively-terabyte-73999
03/18/2026, 4:23 AMtall-airline-16756
03/18/2026, 4:23 AMtall-airline-16756
03/18/2026, 4:23 AMsip_number or otherwise specifying the ANI for transfers, make sure that exact number is whitelisted/verified by the provider.
1. Confirm caller ID passthrough is allowed
◦ Some providers block arbitrary caller IDs unless caller ID passthrough/spoofing is explicitly allowed on the trunk. Confirm your trunk/settings permit presenting that Caller ID.
1. Check provider rules for outbound numbers
◦ Some providers restrict which numbers can be used as caller ID (for example, must belong to your account, be purchased from them, or be explicitly validated). Make sure you meet those requirements.
1. If you need a workaround
◦ Use a provider-verified number as the transfer caller ID.
◦ Configure the transfer request to present a number that your SIP provider accepts (for example, a number provisioned in that provider account).
What I can help with next
• If you tell me the SIP provider you’re using (e.g., Twilio, Telnyx) and which Caller ID you attempted to present, I can give more specific steps for that provider (where to verify numbers or enable passthrough).
• If you’d like, share the transfer request fields you used (redact sensitive tokens) so I can confirm which field contains the caller ID and whether it looks correct.
Reference
• For more detail on how LiveKit interacts with SIP transfers and caller ID handling, see: Preserving Caller ID During SIP Transfers in LiveKit Agents: https://kb.livekit.io/articles/8118805435-preserving-caller-id-during-sip-transfers-in-livekit-agents
Would you like to share the provider and the caller ID you tried to use so I can guide you through the exact verification steps?
Sources: Preserving Caller ID During SIP Transfers in LiveKit Agents, with interactive elements