Meeting ends on its own
# support
f
Hi. Is there any way to prevent meeting end by itself? After not sending messages or talking for a while I get: Meeting ended in error: Meeting has ended Call has stopped Any fixes for this? Or at least how can I unpause the dialog? Start/stop creates a new one
?
z
Can u send me the Call ID?
f
Every call ID
When you don't speak or send messages it disconnects after 15-20 seconds - I need to disable it
n
assistant.silenceTimeoutSeconds
f
Thanks, is there a way to use vapi_assistant_id to create assistant and just add some values from CreateAssistantDTO? Or I need to copy everything over from Vapi dashboard to create assistant object which satisfies CreateAssistantDTO and then I can do silencetimeouseconds etc.? @nikhil
Don't think it's possible, can't find anything related to assistant key in CreateAssistantDTO
Pasting my message from #1211486158232617032
Hi. I managed to fix the timeout issues with setting "silenceTimeoutSeconds" while creating new assistant from scratch. However my app is built with client-side code and I don't like the idea that they can see my prompt, firstMessage etc. Now I have issue - I can either pass "assistant_id_key" to assistant and it works but I can't set silenceTimeoutSeconds or responseDelaySeconds or I can set everything and let client see all assistant params and data. Can you add the missing options from CreateAssistantDTO to Vapi dashboard?
s
I am facing the same issue and it seems that "silenceTimeoutSeconds" doesn't work because my calls are being cut every 30 seconds even after changing it to 360 seconds. You can check my assistant configuration using this assistant ID d6163864-c4c7-4772-899c-b79a9059105a // @nikhil
f
@Sahil how are you adding the "silencetimeoutseconds" to existing assistant with ID?
i could either build assistant all by myself with the "silencetimeoutseconds" or use Assistant ID key but then i couldnt modify anything
s
Basically, I sent the HTTP Request with the silencetimeoutseconds parameter and I am not adding it to the existing assistant.
f
I don't think it can work
If you already created assistant you can't mutate it
s
I used my previous assistant configurations to create a new assistant via the
/assistant
endpoint. Therefore, it should work.
n
Hey that's a great point and yes we definitely don't support that flow. You could create 10 assistants with different values and use of them of the client as needed. Not ideal but will work
@Sahil could you send a callId?
s
I found the solution. Anyways thanks @nikhil