call stream failed for multiple calls please refer to the screenshots! https://cdn.discordapp.com/attachments/1348948430151745557/1348948430499876885/image.png?ex=67d151a0&is=67d00020&hm=d37644754ee45360b7979a3f93ae91ae292105d7583b0fb3d8d99ace953c6b7e& https://cdn.discordapp.com/attachments/1348948430151745557/1348948430960984065/image.png?ex=67d151a0&is=67d00020&hm=8abaa2b3339c43c92cf10338f203d8a09685c61be7b649fe66ebf3217bcfe4fa& https://cdn.discordapp.com/attachments/1348948430151745557/1348948431410036787/image.png?ex=67d151a0&is=67d00020&hm=5a186a4fd0a9a7084efec8207e4b5ce959433d11f924f270c1a45162131e7235&

Hi there! I can see you're experiencing WebSocket handshake errors with your Twilio integration. This is typically happening because the server is returning an HTTP code other than 101 (which is required for successful WebSocket upgrades). Based on the error details, here are some common causes and solutions: ### Common Causes 1. Network Configuration Issues - Firewalls or proxies might be blocking WebSocket connections 2. Incorrect WebSocket URL - The endpoint might be incorrect or not properly configured 3. Server-Side Problems - Your server might not be properly configured to support WebSocket protocol ### Troubleshooting Steps 1. Verify WebSocket Support - Ensure your server has WebSocket protocol enabled as mentioned in the error message - Check that the path in your TwiML URL actually supports WebSocket connections 2. Server Configuration - Make sure your server is properly set up to handle bidirectional audio streaming - Verify you have separate WebSocket clients for "transport" and "listen" endpoints if using Vapi

javascript
   const setupCallBridge = async (callId, twilioWs) => {
     const vapiTransport = new WebSocket(`wss://api.vapi.ai/call/${callId}/transport`);
     await new Promise(resolve => vapiTransport.once('open', resolve));
     
     const vapiListen = new WebSocket(`wss://api.vapi.ai/call/${callId}/listen`);
     // Handle bidirectional audio
   };

3. Error Handling - Implement robust error handling in your WebSocket

.onerror

events - Add logging to capture detailed information about connection failures 4. Network Testing - Try connecting from a different network to rule out local network issues - Use WebSocket testing tools to verify if connections can be established externally

this happened when 7 concurrent calls has been placed to same assistant out them 3 got failed !!

@jennifer twilio has reported to us

customer-did-not-answer

and if I look into the calls twilio didn't connected in time. I am keeping this ticket open to look it again later for fair consideration.