Trying to implement a "put call on hold" feature. Using add-message works well, but the assistant insists on acknowledging the demand, which find a bit annoying. So I looked into options to effectively turn the volume to zero or mute the assistant, and came across the type: 'control', control: 'mute-assistant' messages. Muting works well, but unmuting doesn't. Stumbled upon this GH issue that seems to indicate a regression here https://github.com/VapiAI/client-sdk-web/issues/16 Is mute/unmute supposed to work? Thanks for your help!

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What SDK you're using

Thx for the response ! Just did a couple attempts: ac25efd0-0c26-4caa-aad9-b0133c0b3dc0 fc804ba3-051a-4664-896f-75694343f570 "@User-ai/web": "^2.2.2", Thx for your help!

Hello Jerome, checking with the engineering team on this. Should have an answer for you shortly.

Correct. Mute-assistant does what it’s supposed to do, unmute, seemingly not

Can you share the call ID where you have triggered the unmute assistant inbound message? This will help me figure out what could have been going wrong for you.

@Shubham Bajaj I believe it was done in the 2 call ids above

🔵 15:55:46:737 Live Call Manager Control Message Received... {"type": "control", "control": "mute-assistant"} So here is what happening is Using VAPI web SDK, you are trying to send the unmute assistant control event but that's not being triggered. Eventually, your assistant is not getting unmuted. A quick solution for you to unblock is you can use live call control to send the unmute events for now. I'll suggest you create an issue over GitHub saying the unmute system the unmute event using VAPI.send method doesn't work and the steps to reproduce it. This will help the team to see what could have been going on for you then eventually build a fix for it.