I am creating an assistant using Vonage for the phone number, Vapi for the assistant and a make.com scenario for the instructions. I want the make.com scenario to provide dynamic variables based on the phone number that is forwarding calls to the Vonage phone number. How can I identify this phone number in the make.com scenario? Right now I only see the number of the person calling, and the Vonage phone number.

@Max431993 To identify the phone number that is forwarding calls to your Vonage phone number within your make.com scenario, you will need to ensure that the forwarding service is passing along the original caller ID information. This is sometimes referred to as "Caller ID Passthrough" or "Diverted Call Information." Here are the steps you can take: 1. **Check with Your Forwarding Service**: Verify with the service that is forwarding calls to your Vonage number that they support passing the original caller ID information. 2. **Configure Your Forwarding Settings**: If supported, you may need to configure your forwarding settings to include the original caller ID information. 3. **Capture the Information in Vonage**: Once the forwarding service sends the original caller ID, Vonage should be able to capture this information. You may need to check Vonage's documentation or support to find out how to access this data. 4. **Pass Information to make.com**: When setting up your make.com scenario, you will need to ensure that the data from Vonage (which should now include the original caller ID) is being passed to make.com. This may involve configuring webhooks or API calls between Vonage and make.com. 5. **Use Dynamic Variables**: In your make.com scenario, you can use dynamic variables to capture and utilize the original caller ID information. You will need to map the correct field from the incoming data to your dynamic variable. If you have already set up your system and are not seeing the original caller ID, it's possible that the forwarding service is not configured correctly to pass this information, or Vonage may not be capturing it. In this case, you may need to reach out to the support teams of your forwarding service and Vonage for further assistance. Remember to test your setup thoroughly to ensure that the original caller ID is being captured and used as expected in your make.com scenario.

Hey @Max431993 allow me sometime to find something according to your current tech stack. Incase you required it urgently then the solution is to use SIP.

Thanks Shubam, I´ll looked into SIP but at this point it seems a bit much to implement the whole SIP rerouting. Is it possible to add this to the API?

Yeah give me sometime to check what's the possible workaround.

Hi Shubham, do you have an update on this? Or a rough timeline maybe?

Hey @Max431993 checked with the team, as of now we have workaround for the twilio telephony but Vonage if not wrong doesn't provides call forwaded from in their request body because this it cannot be made availabile to you. In case you find any docs related to ti from Vonage side where they pass the call forwared from in the request body, we will be happy to implement a solution for it.

Twilio is also fine for now, could you share how the Twilio workaround works? The only problem there is that they don´t have Spanish phone numbers and half of my clients are from Spain. I´ll just use custom numbers for the Spanish customers

https://github.com/VapiAI/advanced-concepts-phone-call-provider-bypass Setup a server with twilio to accept phone calls and then pass then over to Vapi with forwarded from as assistant metadata. You need to get metadata from twilio request body and then forward to Vapi.

Thanks! I´ll work on that and report here how I integrated it

@Max431993 can you share your code for the following " have tried your suggested solution but it did not work out as I hoped."?