what are the common issues that lets agent to disconnect from the room after 1-2 sec of joining I checked for any conflicting audio capture and found VoiceProcessorWrapper and AudioRecorder exist but aren’t started in this flow; iOS AppDelegate.swift doesn’t set audio session. From your new log, the server is still initiating “disconnect from room” a few seconds after ActiveSpeakers fires, not due to our code path. To narrow root cause fast, can we try these targeted A/B tests? I won’t change code further without your go-ahead: • Disable agent dispatch for a test: comment out dispatchAgent in AgentCallService and connect/speak. If it stays connected, the issue is triggered by remote audio/renegotiation. • Route toggle test: remove setSpeakerphoneOn(true) (or set it to false) and retry. Some iOS devices drop when forced to speaker at capture start. • Longer mic delay: increase the post-connect delay to 1000 ms before setMicrophoneEnabled(true). • AutoSubscribe off: connect with { autoSubscribe: false }, then, after 1 s, manually subscribe to the agent’s audio when it appears. This reduces early renegotiation churn. • Identity isolation test: add a per-connection random suffix (instead of per-service) for participantIdentity to rule out any identity race across back-to-back joins. Two clarifications that will help choose which to do first: • Are any other voice screens (e.g., LiveKitVoiceChatScreen or anything using AudioRecorder) mounted when AgentCallScreen is active? • Device/route used during repro (model, iOS version, speaker/earpiece/Bluetooth)? If you want me to proceed, say which two tests you prefer first (e.g., “disable agent dispatch” + “route toggle”), and I’ll implement them and add enhanced disconnect logging so we can capture the exact reason from RoomEvent.Disconnected.

Thanks for reaching out, Sumiya. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.