having isues if i pass callerId: {{customer.number}} for a transfer tool its crashing anyideas? it used to work on cold transger and I Think arthur pushed an update but it broke both warm and cold transfer for us, would appreciate your help!

Looks like the recent update to Vapi might be causing issues with dynamic callerId during transfers especially if the number isn’t resolving properly. It used to work, so probably something changed in how warm/cold transfers handle it. I’ve seen crashes happen when the number is null or not in the right format. Quick question: does it still fail if you try a static number, and what does the log show for customer.number? @AiTitus :)

yep!

Give me a minute

cool let me know you update and I can test 🙂 . When did they tighten validation was this recent?

You welcome 🤗

so @Obed even if we are using the VAPI # (on twilio) lets say #5555551212 and we initiate a transfer in VAPI and want to use the caller id instead of #7777771212 (not on twilio) it cant work unless that number is on Twilio? In the past this did work so just wondering if the logic is off or something?

Yeah Twilio tightened Caller ID validation, so transfers now only work if the Caller ID is a Twilio-owned or verified number; it used to be looser, but that’s no longer allowed.

do you have a specific post or doc that says when they did that just trying to let management know 🙂

There isn’t one clear announcement post. Twilio rolled it out gradually via policy updates and support responses, mainly tied to stricter Caller ID / spoofing enforcement, so most teams found out when it started failing in practice.

today i set callerID to our Agent (on twilio) (on our dev instance) and the warm transfer worked with the callerID, last week this did not work and broke last monday. Any ideas why it would work today but notlast week?

Twilio can silently reset or fail Caller ID settings if the number isn’t fully verified or temporarily flagged. Once it re-verifies, things magically work again.