WebSocket Service Failing - All Outbound Calls Failing with "Twilio Connection Failed
All outbound calls are failing immediately with "Twilio Connection Failed" status. The issue appears to be with VAPI's WebSocket infrastructure, not configuration.
What's Happening:
API call succeeds - call created with status "queued"
Twilio initiates call successfully
VAPI's WebSocket service fails to accept Twilio's stream connection
Twilio receives SIP 500 error and terminates call (0 seconds duration)
VAPI dashboard shows "Twilio Connection Failed" with NO WebSocket logs
Evidence of Infrastructure Issue:
WebSocket logs are completely empty (no connection established at all)
Consistent SIP 500 errors across multiple call attempts
Same failure pattern on different call IDs
API and Twilio initiation work fine - failure is at WebSocket transport layer
Technical Details:
Failed Call IDs:
e1013eb3-0fc5-4a94-b3a0-7d4b92273023
48184c19-2a76-451f-82ee-d85b7785bf98
Assistant ID: 60241850-4871-4ce5-8162-7813b230b1c3
Phone Number: +19783062142 → +263783966561
Timestamps: 2025-09-19 around 13:31 UTC and 13:59 UTC
WebSocket Endpoint Failing: wss://phone-call-websocket.aws-us-west-2-backend-production1.vapi.ai/
What's Happening:
Evidence of Infrastructure Issue:
WebSocket logs are completely empty (no connection established at all)
Consistent SIP 500 errors across multiple call attempts
Same failure pattern on different call IDs
API and Twilio initiation work fine - failure is at WebSocket transport layer
Technical Details:
Failed Call IDs:
e1013eb3-0fc5-4a94-b3a0-7d4b92273023
48184c19-2a76-451f-82ee-d85b7785bf98
Assistant ID: 60241850-4871-4ce5-8162-7813b230b1c3
Phone Number: +19783062142 → +263783966561
Timestamps: 2025-09-19 around 13:31 UTC and 13:59 UTC
WebSocket Endpoint Failing: wss://phone-call-websocket.aws-us-west-2-backend-production1.vapi.ai/

