@Derky It sounds like you've encountered an issue with call forwarding when receiving inbound calls on your Twilio number. Since outbound calls are working correctly, this suggests that the issue is specific to the inbound call flow. Here are a few steps you can take to troubleshoot the issue: 1. **Check Configuration**: Verify that the inbound call configuration matches the outbound call configuration since the latter is working correctly. 2. **Review Logs**: Look closely at the call logs for inbound calls to see if there are any discrepancies or errors that stand out compared to the outbound call logs. 3. **Examine the Forwarding Number**: Ensure that the

forwardingPhoneNumber

attribute in your Create Assistant API setup is either omitted, set to null, or an empty string ('') for inbound calls, as per the context provided. 4. **Test with Different Numbers**: Try forwarding to a different phone number to see if the issue persists. This can help determine if the problem is with a specific forwarding number or the forwarding process in general. 5. **Check Twilio's Documentation**: Review Twilio's documentation on call forwarding to ensure that all the necessary steps and configurations are correctly implemented. 6. **Contact Twilio Support**: If you've gone through all the above steps and the issue still isn't resolved, reaching out to Twilio's support team may provide additional insights. If you need further assistance or if you'd like me to perform any specific checks or configurations, please let me know!

You can continue this conversation by mentioning me in the message.

In the Twilio logs I see that outbound calls get handled by the US region, inbound by the Ireland region. I can't seem to find where I can change it in Twilio. (I only need a Dutch (Netherlands) inbound calls and forward calls also to NL only.

Do let @Derky me know if you require further help.

@Shubham Bajaj I'm a little step further. Twilio says I need to use the Ireland region auth and API-keys. In VAPI I cannot use an API-key as far as I can see, I can only provide an Account SID and Account Token. When I try to use the Account Token for the Ireland region I get an authentication error, when I use the US region the phone number is succesfully imported. I've asked Twilio if they could see why I'm getting an authentication error but they are referring to VAPI. Is there anything you can see in the logs when I got the authentication error or do you have to configure something specific to make Twilio (Ireland region) Auth Tokens work when importing a phone number?

@Shubham Bajaj I've got a response from Twilio, apparently when initiating a call the region needs to be specified. This is what a Technical Support Engineer from Twilio just responded: We are showing this number is successfully routed to the IE1 region. Please note, when submitting an API call the region must also be declared in the endpoint (domain name). If you don't specify a target region for a request, the request will be handled in the default US1 Region. I can not be positive what API call Vasi is making when you attempt to 'import' a number, my guess is they are adding the voice URL to your phone number. This process would use the following API call: POST https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers/{Sid}.json In order to run this request in the Ireland region, the call would need to show as: POST https://api.dublin.ie1.twilio.com/2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers/{Sid}.json For more information, about Region requirements, please check out this doc: https://www.twilio.com/docs/global-infrastructure/create-an-outbound-call-via-rest-api-in-a-non-us-twilio-region I hope this helps. Please let me know if you have any more questions.

Hey @Derky an feature requested, and once we are done with it I will let you know.