Several calls ended with vapifault-transport-never-connected reason today. Call Ids: 2c98594c-8629-4ec5-81b4-fe3418b28211 f4056f60-d76c-42af-accb-6a3d3d57223c 0bedec13-1eb3-4378-9889-f4d4cbe1ec0d What the meaning of vapifault-transport-never-connected ?

@marem The

vapifault-transport-never-connected

error indicates that the calls attempted through the Voice API (VAPI) were unable to establish a connection. This could be due to a variety of reasons such as network issues, misconfiguration, or problems with the underlying transport mechanism that VAPI uses to set up the call. To resolve this issue, you should check the following: 1. Network connectivity: Ensure that there are no issues with the network that could prevent a successful connection. 2. Configuration settings: Verify that all the necessary configuration settings for making calls are correct. 3. Service status: Check if there are any known issues or maintenance activities that might be affecting the VAPI service. If after checking these points the problem persists, it would be best to reach out to support for a more detailed investigation into the specific call IDs you've provided.

I checked on our side, but we had no issues in our logs or infrastructure @User

@marem The error

vapifault-transport-never-connected

indicates that the system was unable to establish the necessary WebSocket connection to manage a live call session. - This time it was because of A worker process failed to connect within the expected time, leading to a timeout (ETIMEDOUT). Can happen to a call or two, when there is a burst of traffic.