Call dropped
# support
m
Call id 1e202595-ef47-40b7-8686-ce64aee9b51c TWilio error: Error 31921Stream - WebSocket - Close Error (Closed without handshake)
v
@Mamata Kondapally I understand you're experiencing an issue with a Twilio call that closed without a handshake, resulting in error 31921. This error typically indicates a problem with the WebSocket connection used for streaming. To assist you further, could you please provide more details about the context in which this error occurred? For example, were you trying to initiate a call, or was this during an ongoing call? Any additional information would be helpful in diagnosing the issue.
You can continue this conversation by mentioning me in the message.
m
It was during ongoing call. I had another call drop as well.
@Vapi
v
@Mamata Kondapally I'm sorry to hear that you experienced another call drop. Call drops can be caused by various issues, such as network connectivity problems, configuration errors, or issues with the Twilio service itself. To help you resolve this, I would need to know more about your setup. Could you please provide the following information? 1. The code snippet you're using to handle the WebSocket connection. 2. Any relevant logs that show the behavior leading up to the call drop. 3. The configuration of your Twilio application, especially any parameters related to timeout or connection handling. With this information, I can give you more specific advice on how to prevent these call drops from happening in the future. If you're unable to share these details here, I recommend reaching out to Twilio's support team directly for further assistance.
m
@Vapi we dont have any websockets on our end. We are using Vapi Server URL.
v
@Mamata Kondapally Thank you for clarifying that you're using Vapi's Server URL feature. Since you're not handling WebSockets directly, the issue might be related to the interaction between Twilio and Vapi's services. Here are a few steps you can take to troubleshoot and potentially resolve the issue: 1. **Check Server URL Configuration**: Ensure that the Server URL configured in Vapi is correct and that the endpoint is capable of handling requests from Twilio. 2. **Review Server Logs**: Look at the logs on your server to see if there are any errors or warnings that could indicate what went wrong during the call. 3. **Network Stability**: Verify that your server has a stable internet connection and that there are no network issues that could be causing the WebSocket to close prematurely. 4. **Twilio Service Status**: Check Twilio's status page to see if there are any ongoing issues with their service that could be affecting your calls. 5. **Contact Support**: If the above steps don't reveal any issues, it may be best to reach out to Vapi support with the call ID and error details so they can investigate further. If you would like, I can assist you in closing this support ticket if you feel the issue has been resolved or if you plan to reach out to Vapi support for further assistance. Would you like me to proceed with that?
m
@Vapi I would like to connect with support.
v
@Mamata Kondapally Please ask support for more info on this.
m
@Vapi how do I connect with support?
v
@Mamata Kondapally To connect with support, you can typically follow these steps: 1. **Support Portal**: Visit the official support portal of the service you're using (in this case, Vapi or Twilio). There, you can find options to submit a support ticket or contact customer service. 2. **Email**: You can send an email to the support email address provided by the service. Make sure to include all relevant details such as the call ID, error message, and a description of the issue. 3. **Phone**: Some services offer phone support. You can call their support number during business hours for direct assistance. 4. **Live Chat**: If available, use the live chat feature on the service's website for real-time assistance from a support agent. 5. **Community Forums**: Post your issue in community forums or discussion boards. Other users or support staff may be able to help you. 6. **Documentation**: Review the service's documentation or FAQs, which might have information related to your issue. If you need the specific contact details for Vapi support, please let me know, and I will provide them if available.
s
@Mamata Kondapally is it happening frequently for you? if yes then please share the other call ids, because it looks like it happened by one of the chance for this specific call.
m
We had 2 calls that dropped.
s
please share the call id.
m
I dont have the Vapi call ID. I can share the twilio callsid
Vapi call id: 91d3217d-5fcf-4f9b-b5ff-51406f2ad1e2 TwilioCallId: CAf3180768a6ed684059f928a41df61e02
@Shubham Bajaj
Twilio error: Error 31921Stream - WebSocket - Close Error (Closed without handshake)
s
@Mamata Kondapally this is on our due to recent changes. It happens rarely when capacity limit is reached or something like that.
Ideally it won't be happening again for you repeatedly but if happens do let me know.
m
Thanks @Shubham Bajaj
@Shubham Bajaj We have back channelling disabled and I still find the bot saying random words. Is the backchanneling=false in our call api request being honored?
s
yes it is being honored, you can create a new ticket for this.
7 Views