Q4
09/12/2026, 7:46 AMAI Evy
09/12/2026, 7:46 AMAI Evy
09/12/2026, 7:46 AMAI Evy
09/12/2026, 7:46 AMAI Evy
09/12/2026, 7:46 AMfrom and P-Asserted-Identity headers to the user's number
- Cold transfer uses SIP REFER; supporting caller ID override is up to the telephony provider
- Retell Twilio numbers support showing the user's number on both warm and cold transfer; Retell Telnyx numbers support it only via cold transfer (SIP REFER)
- If caller ID override isn't supported, the transfer fails
There's a documented FAQ entry on this exact symptom: "The transfer destination sees the wrong caller ID. What's wrong?" — Showing the caller's number requires caller ID override support from your telephony provider. If override isn't supported, the transfer fails. The suggested fix is to switch Displayed Caller ID to Retell Agent's Number or use a supported number .
Separately, in a Discord forum thread, a community member reported the same error message intermittently on warm transfers and was advised to switch Displayed Caller ID to "Retell Agent's Number" instead of "User's Number," though the root cause wasn't confirmed in that thread [(2) ]() . Another Discord message describes the same error occurring on a warm transfer using SIP trunking (Twilio) while trying to keep the user's number as caller ID [(3) ](AI Evy
09/12/2026, 7:47 AM