Hey everyone, I'm hitting a wall with Vapi web calls and wondering if anyone else has seen this: Setup: Using transient assistants via /call/web API Call creates successfully (201), Daily room opens 3 peers join: Guest (me), Vapi Speaker, Vapi Listener Within 5-10 seconds: "Meeting has ended" / "room was deleted" What I've tried: Added endCallFunctionEnabled: false and silenceTimeoutSeconds: 600 to assistant payload Verified mic permissions granted in Daily UI Confirmed origin is whitelisted for public key Same assistant works fine from Vapi dashboard preview The error: Daily shows "You were removed from the call" and console shows {type: 'ejected', msg: 'Meeting has ended', error: {...}, callClientId: '...'} Daily support confirmed the rooms are being deleted by Vapi's backend, not by Daily infrastructure or expiry settings. Questions: Has anyone else hit this "immediate room deletion" issue with web calls? Are there account-level timeout settings I'm missing? Do the endCallFunctionEnabled / silenceTimeoutSeconds params actually work for transient assistants? Should I be using base assistants instead of transient for web calls? Already contacted Vapi support but curious if this is a known issue with a workaround. Thanks! https://cdn.discordapp.com/attachments/1423411727290208316/1423411727663628339/Screenshot_2025-10-02_at_21.48.52.png?ex=68e036f9&is=68dee579&hm=ec67e3524607cd2c63133b8131dd3cfcd87e4fabd507e704d887fd7e743d23ad& https://cdn.discordapp.com/attachments/1423411727290208316/1423411728166686881/Screenshot_2025-10-02_at_21.48.31.png?ex=68e036f9&is=68dee579&hm=229bd873ea7144b32cbee4f441507b180451416f4abfad92df492754d4da2ecf&

Thanks for sharing the details! To help narrow this down: Have you tried explicitly setting the

customerJoinTimeoutSeconds

parameter (e.g.,

customerJoinTimeoutSeconds: 30

) in your transient assistant payload when creating the web call? This parameter specifically controls how long users have to join before the call is auto-terminated, and is supported for both transient and permanent assistants ([see documentation](https://docs.vapi.ai/calls/customer-join-timeout)). If you have already set this, could you share the relevant part of your assistant configuration (with sensitive info redacted)? Source: - [Customer join timeout documentation](https://docs.vapi.ai/calls/customer-join-timeout)

Message marked as helpful by @Jonathan! 🎉

Following up on my previous post - thanks to the community help, I've resolved the timeout issue with customerJoinTimeoutSeconds: 60. The Daily room now stays open for the full duration, all 3 peers join successfully (Guest, Vapi Speaker, Vapi Listener), and mic permissions are granted. Current problem: Zero audio from the assistant. The room works, I can speak (my mic shows activity), but the assistant never speaks - no greeting, no response to my input. What's confirmed: The exact same base assistant works perfectly when tested in Vapi dashboard Tested with Vapi's native voices (not 11labs) - same issue Happens across multiple devices and browsers Room stays connected for 60 seconds before timing out Using unmodified webCallUrl from API response (no custom parameters) Vapi Speaker peer is present in the room but shows no audio activity API call: javascriptPOST https://api.vapi.ai/call/web { "assistantId": "e66c1ef5-2f56-4530-a17e-8e644a7aa7f7", "assistantOverrides": { "customerJoinTimeoutSeconds": 60, "endCallFunctionEnabled": false, "silenceTimeoutSeconds": 600 } } Returns 201, then redirecting to data.webCallUrl as-is. Daily console shows: Meeting ended due to ejection: Meeting has ended {type: 'ejected', msg: 'Meeting has ended', error: {...}} Questions: Since the assistant works in dashboard but not via API, what could cause audio to not route to the Daily room? Are there assistant configuration settings that block web calls specifically? Could this be a Daily room provisioning issue on Vapi's backend? Is there a way to debug why Vapi Speaker peer isn't transmitting audio? This is the last blocker before going live. Any insights appreciated!

Hey, Could you provide the call ID where you experienced this issue? We want to review the logs to identify the cause.