This is using the Web SDK for the following scenario: I am starting a conversation successfully without microphone permission by passing in overrides to 'dailyCallConfig' and 'dailyCallObject' when instantiating a new Vapi instance. This allows me to start a call successfully without microphone permission. However, after 10 seconds the room is ended with the following error which I believe propagates from Daily:

{
  "action": "error",
  "errorMsg": "Meeting has ended",
  "error": {
    "type": "no-room",
    "msg": "Exiting meeting because room was deleted"
  },
  "callClientId": "17387830296490.3572555603910488"
}

This happens even though I am sending messages from the client within those first 10 seconds, i.e.

vapiRef.current.send({
        type: "add-message",
        message: {
          role: "user",
          content: userMessage,
        },
      });

If I request and accept microphone permissions at any point within those first 10 seconds (even if the call started without permission) I am able to continue the call - if permission is not accepted within those 10 seconds the call/room is destroyed, with the client message:

{
  "type": "status-update",
  "status": "ended",
  "endedReason": "customer-did-not-give-microphone-permission"
}

Keep in mind my Call Timeout settings are beyond 10 seconds, per photo attached. What I am trying to achieve is the ability to disable the "customer-did-not-give-microphone-permission" logic so that the call can continue even without microphone permission. My use case is to begin the call as 1-way, and allow the user to interact with the assistant through text, and then opt-in to voice later on in the conversation if they desire. https://cdn.discordapp.com/attachments/1336782522859913226/1336782523132412035/image.png?ex=67a50f3d&is=67a3bdbd&hm=563a21b6ed427909055550ea2f427a92453e2fec1824bba141d570ead0d6d675&

Hey @LBThree To help track down this issue, could you share: - The call ID This would really help me figure out what went wrong!

hey @Shubham Bajaj, appreciate you taking a look! callId=

f63a7e0e-3e49-4cfe-97b1-7a6a31feb07a

This is a fresh example but it's reproducible every time based on my configuration and use case