Twilio phone number connected to assistant but num...
# support
h
Hey, I connected a twilio number with an inbound assistant but the line is blocked anytime I call. Any idea what the issue could be?
v
message has been deleted
@HugoTavuk Hello! It sounds like you might be experiencing an issue with the voicemail detection settings for your inbound assistant. If the line is getting blocked, it could be that the voicemail detection is incorrectly identifying your calls as voicemail and not allowing them to connect to the assistant. To help you better, I can guide you through checking and configuring your voicemail detection settings. The
squad.members.assistantOverrides.voicemailDetection
object is where you can set these configurations, and since you're using Twilio, you'll need to ensure that the
provider
is set to
twilio
. Would you like to proceed with checking or updating your voicemail detection settings? If so, could you provide me with the current settings, or let me know if you need assistance accessing them?
You can continue this conversation by mentioning me in the message.
h
To add some more detail: I am using the webapp to create the assistant. I have added the phone number via the dashboard.
I would appreciate your help
Hey @Vapi , the issue has nothing to do with voice mail. I have bought a phone number at twilio. Then I connected the twilio phone number to the assistant. The mode of the assistant is Twilio. I am using the Dashboard. The problem is that the number is busy any time I call. In the twilio dashboard the number is displayed as Webhook to POST: https://api.vapi.ai/twilio/inbound_call. Any idea whay to do?
Hey @Vapi I am still struggeling here and would appreciate your help.
v
@HugoTavuk I'm here to help! If your Twilio number is consistently busy when you try to call it, there are a few potential issues we can look into: 1. **Twilio Configuration**: Ensure that your Twilio number is correctly configured to work with the VAPI. The webhook URL you provided seems correct, but you should also check if the HTTP method is set to POST and that no other configuration is overriding this webhook. 2. **Twilio Account Status**: Verify that your Twilio account is in good standing, with no billing or usage issues that might be affecting your service. 3. **Network Issues**: Sometimes, network problems can cause calls to fail. Check if there are any known issues on Twilio's status page or with your own network provider. 4. **Concurrent Calls Limit**: If you have a high volume of incoming calls, you might be hitting a concurrent call limit. Check your Twilio usage records to see if this might be the case. 5. **Error Logs**: Look at the Twilio logs for any errors or messages that could indicate what's going wrong. This can provide clues as to why the calls are not going through. 6. **VAPI Configuration**: Double-check the VAPI settings in the webapp dashboard to ensure everything is set up correctly. If you've gone through these steps and the issue persists, it might be best to reach out to Twilio's support for a more in-depth investigation. They can provide specific insights into your account and the interactions with the VAPI. Would you like to go through any of these steps together, or do you need further assistance with something specific?
h
@Vapi 1. Seems to be configured correctly. 2. No issue. 3. No isssue. 4. Not an issue. 5. No error logs because no calls detected. 6. One thing I am wondering: I set Mode to Twilio and publish the agent. After page reload the mode is back to web again. Any idea why that is?
v
@HugoTavuk It's quite peculiar that the mode reverts back to 'web' after you set it to 'Twilio' and publish the agent. This behavior suggests there might be an issue with saving the configuration on the VAPI dashboard. Here are a few steps you can take to troubleshoot this problem: 1. **Browser Issues**: Sometimes, browser cache or extensions can interfere with web applications. Try clearing your browser cache, disabling extensions, or using a different browser to see if the issue persists. 2. **Save Confirmation**: After changing the mode to 'Twilio' and publishing the agent, ensure that you receive a confirmation message indicating that the changes have been saved successfully. 3. **Support Inquiry**: If the problem continues, it might be a bug or a system issue on the VAPI's end. In this case, reaching out to VAPI support with detailed information about the issue, including the steps you've taken and the behavior you're observing, would be the next best step. 4. **Documentation Review**: Review the VAPI documentation to ensure there are no additional steps or configurations that you might have missed when setting the mode to 'Twilio'. If you'd like, I can assist you in reaching out to support with the necessary details to get this issue resolved. Would you like me to initiate that process for you?
s
@HugoTavuk can you share the phone number id?
h
Hey @Shubham Bajaj we can close the thread as this is a dubplicate to: https://discord.com/channels/1211482211119796234/1313400817017159742
The issue was with Twilio - thanks for the help anyways.
@Vapi this issue is resolved
v
@HugoTavuk Sweet. Have a great day!
4 Views