Agent is not answering or finishing call
# support
e
I have tried to connect my agent or the phone number with the server URL for the inbound agent and I created a workflow on n8n and I double check everything from the web through the HTTPand the web of response and I check everything 2×3×10 times corrected every error which possibly was in the JSON but it’s still not working. Every time I’m calling the number of this inbound agent it’s ringing one time and then it’s instantly kind of closing the call and there is no call appearing in the call logs .
v
You can continue this conversation by mentioning me in the message.
@Exideus_Systems I'm sorry to hear you're experiencing issues with connecting your agent to the phone number for inbound calling. It sounds like you've been very thorough in checking your workflow and JSON configuration. Since the call is being disconnected without appearing in the call logs, it could be an issue with the phone number provisioning or the way the agent is set up to handle inbound calls. Here are a few steps you can take to troubleshoot the issue: 1. **Check Phone Number Provisioning**: Ensure that the phone number has been correctly provisioned and is active. Verify that it is correctly configured to forward calls to your server URL. 2. **Review Server Configuration**: Make sure that your server is running and is configured to accept incoming HTTP requests. Check for any firewalls or security settings that might be blocking the incoming calls. 3. **Inspect Agent Configuration**: Review the agent's configuration to ensure it's set up to handle inbound calls. Make sure that the workflow you've created is active and properly linked to the phone number. 4. **Test Server Endpoint**: You can try to simulate an inbound call by sending a test HTTP request to your server URL to see if it's responding as expected. 5. **Check with Service Provider**: If everything on your end seems correct, it might be worth reaching out to your telephony service provider to ensure there are no issues on their end. 6. **Review Logs**: If possible, check the server logs for any errors or messages that could indicate what's going wrong when the call is received. If you've already checked all of these and the issue persists, it might be necessary to get in touch with the support team for your telephony service or the n8n workflow automation tool for more detailed assistance. They may be able to provide insights based on system logs or known issues. Would you like me to assist you with anything specific, such as reviewing configuration details or contacting support?
e
Its bot working im working in this since 8 hours and i checked it on twilio but there i see the call logs and everything call is 0 seconds and its not working
v
@Exideus_Systems I understand how frustrating this can be, especially after investing so much time into it. Since you're seeing the call logs in Twilio with a duration of 0 seconds, it suggests that the call is reaching Twilio but not successfully connecting to your server or the workflow isn't handling the call correctly. Here are a few more specific steps you can take: 1. **Twilio Webhook Configuration**: Double-check that the webhook URL configured in Twilio for incoming calls is correct and points to the right endpoint in your n8n workflow. 2. **HTTP Response**: Ensure that your server is returning a valid TwiML response when Twilio sends the webhook request. If Twilio doesn't receive a proper TwiML response, it may terminate the call immediately. 3. **Error Messages**: Look for any error messages in the Twilio call logs. Twilio logs should provide an error code or message that can give clues as to why the call is failing. 4. **Twilio Debugger**: Use the Twilio Debugger to get more detailed information about the errors. The Debugger can be found in the Twilio Console and can provide insights into what's going wrong. 5. **Network Issues**: Verify that there are no network issues between Twilio and your server. This includes checking that your server's firewall is not blocking incoming connections from Twilio's IP addresses. 6. **TwiML Bins or Studio Flows**: As a temporary measure, you might want to try using Twilio's TwiML Bins or Studio Flows to ensure that the basic call handling works before routing calls through your n8n workflow. If you've already tried these steps without success, it may be time to reach out to Twilio's support team for assistance. They can provide more detailed help and potentially identify issues from their side. Would you like me to guide you on how to access the Twilio Debugger or provide any other assistance?
s
Hey @Exideus_Systems can you share the phone number id?
e
For sure ad1d44d5-0bd7-4025-833c-e5bae8548c47 I was talking ajd trying to solve it woth 3 devs yesterday and we couldnt. Inside of Twilio, everything is OK there’s no error and there I can see the call logs which are zero seconds because of what I was describing that the call is ringing one time and then hanging up. We reviewed and tested the JSON and everything was OK. So I really don’t know why this is happening and would be very very happy to get this solved by today.
s
Hey @Exideus_Systems can you trying removing your number from Vapi and then adding it again, It will work most likely vapi url from twilio number webhook is missing.
e
No its not i checked it and its not missing it is in twilio
s
@Exideus_Systems when calls fails because of the incorrect connection setup we send debugging artifacts to your server url. What you can do is: 1. Add server url to the phone number 2. Make a call 3. Check the Vapi sent debugging artifcats After this you will get to know what is missing, and we won't get to know actually is missing so you have to check debugging artifacts. In case this doesn't works for you your still blocked, shoot me a message we will connect and resolve it.
TIP
tag me in general channel to revert back to you fastest.
2 Views