twilio
Bitrate is 0 and ICE fails silently for participant even though tracks publishing succeeded
Hi, we have an issue where an ICE error happens according to Twilio support and bitrate is 0 but no msg is transmitted to the frontend. In the frontend it seems that everything works fine for the participant and that 2 tracks were published.
Room SID: RMddeeeb07aab7a4af90c9b943a34d7072 Participant id: PA9da8b2dc891b7ba95f1c213a0145539f
Hi @CyranMS,
Thank you for opening this issue. I see that there was an ICE Failure but nothing stands out to me through the logs. Is it possible to get some client side logs for when this happens? Or a repro link would be fantastic as well.
Thanks, Joyce
@PikaJoyce we will rework our logging to be able to provide it. However the problem is that an ICE failure happens on server side during the meeting and the frontend is not aware of it. The only thing we get is a network quality of 0 but what does that mean. The connection is still working but track subscriptions are not. So should we reconnect in these cases? What is the recommendation the application should do in case network quality 0 or a sudden ICE failure during the meeting.
Hi @CyranMS apologies that you are having this issue. When ICE fails, the SDK usually tries to reconnect for you. We also emit events when this happens. Please see this page https://www.twilio.com/docs/video/reconnection-states-and-events Are you subscribing to these events? Are they triggering? Also, if possible, please enable client side debugging and provide some logs.
Thank you, Charlie
