Vapi is the Voice AI platform for developers.

Vapi AI

All of a sudden the calls are ending because silenced timeouts but the AI didn't even start off with it's firstMessage. 

This is a web-call where the video and the mic permissions of the user has to be enabled in order to talk with the AI. 

The call is getting started but the AI is not starting off with the firstMessage and neither the user's input is reaching the AI

here is a callId - 4085da10-7f6d-4bd4-8cdd-ac1aec67d37c

Ensure your browser grants mic access, set firstMessageMode to "assistant-initiated", increase silenceTimeoutSeconds, and test in browsers like Chrome instead of Brave to avoid permission issues.

and I just tried now <@1006897684965244938>

it works when I remove assistantOverrides and only have agent id into .start()

it was working till yesterday with no problem but now it isn't

and now if I am trying to add assistantOverrides to .start() with just the variableValues then the variableValues are not getting mapped to the assistant's system prompt

the Vapi assistant is now conversational tho

this is all I am doing on client side

const assistantOverrides: AssistantOverrides = {
  variableValues: variableValues,
};


    const startedCall = await vapiInstance.current.start(VAPI_AGENT_ID,assistantOverrides);

please check out this callId - cc529398-b555-44ca-b885-3aadf1f2429c

in the API logs I can only see assistantId being passed

this is when I was overriding bunch of parameters but for some reason the Vapi AI assistant was not at all talking

there is a stark difference (request body) in the API logs of calling the assistant at the dashboard compared to when I call from my web app

here is a callId when I tried to call from dashboard - 21553b8b-4ee6-4fd7-bf2f-796a5acf50e4

here is another recent callId called from my web app - 10d4cfd5-5cce-4873-992c-036b6af00d69

<@&1231325148079194222> any lead on this guys ?

<@750982101515501568> I will take a look at your ticket, after some time.

<@750982101515501568> an you increase your assistant **customerJoinTimeoutSeconds** to 30-40?

```sh
curl --request PATCH \
  --url 'https://api.vapi.ai/assistant/YOUR_ASSISTANT_ID' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "customerJoinTimeoutSeconds": 30
  }
```

**customerJoinTimeoutSeconds** (default 15s) is how long we wait for the user to join the web-call before ending it.

<@750982101515501568>  This parameter specifically extends the window for connection establishment, which is critical for users with connectivity challenges. It's not just about the SDK timeout, it's about keeping the call session alive on our servers while the connection is forming.

Ohh I see. I will try adding this param to the code and let you know. Thank you so much <@865531204849500190>

it worked ! Thanks again <@865531204849500190>