Twilio Error: Account not allowed to call +1_____
# support
g
Copy code
400 - "{\"message\":\"Couldn't Create Twilio Call. Twilio Error: Account not allowed to call +1123214343\",\"error\":\"Bad Request\",\"statusCode\":400}"
no idea why, geo permissions are enabled. Have called these numbers before, they are zoom numbers as that is how I test my AI caller.
v
@GeneralKugelBlitz It seems like there might be an issue with your Twilio account settings or permissions. Even though you've mentioned that geo permissions are enabled and you have called these numbers before, there could be a few reasons why this error is occurring now: 1. **Twilio Account Restrictions**: Your Twilio account might have some restrictions that are preventing calls to certain numbers. 2. **Geo Permissions Update**: There might have been changes or updates to geo permissions that you are not aware of. 3. **Twilio Service Issues**: There could be a temporary issue with Twilio's service that is affecting your ability to make calls. 4. **Billing or Account Status**: Ensure that your account is in good standing and that there are no billing issues that could affect your service. To resolve this, I recommend checking your Twilio account's voice settings to ensure that nothing has changed with your geo permissions. Also, review any recent updates or alerts from Twilio that might affect calling capabilities. If everything seems to be in order on your end, it would be best to reach out to Twilio support for further assistance. They can provide more detailed information on why your account is not allowed to make calls to the specified number. Would you like me to guide you on how to check your Twilio account settings or assist you with anything else?
You can continue this conversation by mentioning me in the message.
s
@GeneralKugelBlitz If a phone number is purchased from Vapi, you cannot enable geo-permissions and make calls. Instead, you need to purchase a number from Twilio and enable the geo-permissions as required.
Do let me know how can I help your further.
Because of no response closing this ticket!!
10 Views