31920 - Stream - WebSocket - Handshake Error
# support
k
My assistant started off the day making outbound calls fine. I changed nothing and then halfway through the day about half the numbers started show customer did not answer in vapi. When i checked twilio it shows this error "31920 - Stream - WebSocket - Handshake Error". Not sure what happened it was just working. Can anyone help with this?
v
Suggestion: Since this error is often linked to SIP or webhook configuration issues, please review any recent changes to your SIP trunk or webhook settings in both Vapi and Twilio. If nothing has changed, try restarting your SIP endpoints and check network connectivity between Twilio and your WebSocket server. If the issue persists, consider reaching out to Vapi or Twilio support with your call logs and error details for further investigation. Reference: Known intermittent issues discussed in [Vapi Discord Support](https://discord.com/channels/1211482211119796234/1372358449761091584). Source: - [Vapi outbound call not triggering (Discord)](https://discord.com/channels/1211482211119796234/1341449578100031488)
s
@Kizzz I came here to post this as well, came out of nowwhere, causing a pretty big distruption lol
r
+ 1 facing the same issue
s
@Kings_big💫 @Shubham Bajaj @Vapi
k
Send your call ID
s
1b0288c7-62bb-4d82-8627-fe30c8a219f5 33f66861-3a1a-4b40-ba1f-06ea5f66e11c bd732a89-e9ed-4582-856b-d494aff06278 @Kings_big💫
k
Looking into it
c
Hey Slavi Savanovic, Twilio been unable to connect with us on these calls. Could you please inquire about this issue with them? You can obtain the Twilio call IDs by making a GET/call request using Vapi's call ID. Please let me know the outcome.
r
@Shubham Bajaj i'm facing the issue with VAPI numbers as well. Here is a call id for reference: 0fb4a88c-4181-4ef6-bcf9-70c4ab520b7a
s
Hey @Raj @Kizzz @SlaviSavanovic The issue has been resolved. It was a temporary glitch that lasted for few minutes. You can try again and let me know how it goes.
r
i'm still seeing the same errors: 3a92d2e6-c691-410f-ac09-c3289f8dc755 and 4a23c80c-1373-4798-b03b-e672d5683d6b
c
Hey Raj, if this issue is still persisting for you, I suggest you contact your telephony provider. Review your telephony logs and then compose an email detailing the issue. Once you receive their response, please let me know what they have to say.
k
Mine is working better now
k
Glad it resolved
2 Views