Hello 👋 I'm using Vonage phone numbers (not Twilio). SCENARIO in 2 steps: 1) Call with id** 0ab8c522-b205-4f60-bcec-a2eee0e355f9** from a customer (number +32 492 85 85 50) to an assistant (Vonage number +32 460 20 83 04 linked to assistant id 51c8b632-0108-4e75-a5a8-0ec185c3af75). This assistant is supposed to transfer the call to another number (Vonage number +32 460 22 50 67, linked to another assistant with id cd37ff71-f729-4466-bec9-77dbe95daeb7), with following transferCall function : "model": { "model": "gpt-4o", "tools": [ { "type": "endCall" }, { "type": "transferCall", "destinations": [ { "type": "number", "number": "+32460225067", "message": "je vous transfère à l'assistante virtuelle personnelle du docteur Riquet", "callerId": "{{customer.number}}", "description": "assistante virtuelle personnelle du docteur Julie Riquet" }, ... } 2) The call is effectively transferred to the number (new call with id fa2512b5-d49f-4f7a-ad34-fe47e34e8ec2), but the call has the {{phoneNumber.number}} as callerId instead of {{customer.number}}. So you will see in the call log of this second call that the customer number is +32 460 20 83 04, which is the Vonage assistant's number that transferred the call, instead of +32 492 85 85 50 which is the customer's number. EXPECTED BEHAVIOUR : I expected to have +32 492 85 85 50 as customer.number. I initially tried to not add the property "callerId" on the transferCall tool destinations, as the documentation says that by default it would give the customer number. However, because I had the phoneNumber.number, I tried to force it by adding the callerId property on each destination, but it still fails to give me the right number.

Based on the information available, there appears to be an issue with Vonage numbers and the callerId parameter. Try purchasing a number directly from Twilio and importing it into Vapi as a potential solution:

json
{
  "type": "transferCall",
  "destinations": [
    {
      "type": "number",
      "number": "+32460225067",
      "callerId": "{{customer.number}}",
      "numberE164CheckEnabled": false
    }
  ]
}

If the issue persists, contact Vapi support with your call IDs for further investigation. Sources: - [Discord Channel](https://discord.com/channels/1211482211119796234/1338285744090906756) - [Discord Channel](https://discord.com/channels/1211482211119796234/1339690911675977838)

By default, we have caller ID feature only for Twilio. If he requires it for Vonage, you’ll have to raise a feature request..

Oh 😓 Added it there : https://vapi.canny.io/feature-requests/p/support-transfercall-tools-callerid-param-for-vonage-numbers

Thanks for sharing, noted.

@Shubham Bajaj @Kings_big💫 my feature request above has disappeared 👆 ? It doesn't seem to have been solved 😬

Hey Jeebs, I wanted to let you know that we're managing a high volume of support requests at the moment, so our response time might be a bit slower than usual. I truly appreciate your understanding and will get back to you as soon as possible!  Thanks again for your patience!

Hello Kyle. Thanks for your reply ; this sounds like this is never going to happen 😬 Will try to see whether other vonage users have the issue.

Hi, First off, we want to sincerely apologize for the delay in getting back to you. We understand how frustrating it is to wait - especially when you're counting on us - and we owe you a clear explanation of what’s been happening and how we’re addressing it. Over the past few weeks, we've seen a significant increase in support requests. While this reflects exciting growth, it has also stretched our small team and exposed some real challenges in scaling our support operations. To improve your experience, we’ve taken a step back to reassess our approach. Here’s what we’re implementing: - Smarter Support Through Automation: We’re investing in our AI support systems to help you resolve issues more efficiently. Soon, our support bot will offer expanded capabilities, making it easier to access accurate, instant help—particularly for common or repetitive queries. - Expanding the Support Team: To meet growing demand, we’re adding 2–3 new team members focused on managing support volume and improving response times. - Prioritized SLAs for High-Usage Accounts: We’re introducing service level improvements for users who are growing with us: - Accounts with usage over 1,000 minutes/month will receive prioritized support. - For all general inquiries, we’re establishing a standardized 48-hour response time. We’re confident these steps will lead to faster, more reliable support and help us better serve you as you grow with us. Also, in case you still need help with this ongoing ticket, do let us know, and we will help you get this resolved as soon as possible. Thank you for your continued patience and for being part of our journey. Warm regards, Vapi Team

That's amazing since I have more than 1000 minutes a month. How will you differentiate?

We will mark your account type in our system by verifying information on the backend.