Stream timeout in firefox client when the misses packets at the time of joining
179 views
Skip to first unread message
nitin kumar saini
unread,
Oct 30, 2023, 8:31:54 AM10/30/23
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to discuss-webrtc
Hi Everyone,
My application is in ReactJS and SFU (Gstreamer with webrtcbin) is used for video conferencing, When I join the meeting with more than 4 participants some times subscribing streams gets timeout at the time of joining and the video tiles results in black screen while application is woking fine in case of chrome and safari. When I debug it over firefox browser build, I found that if some rtp packets got missed in the beginning (i.e. not from packet sequence 0) the stream gets timeout however by taking the pcap from wireshark it is clear that the network interface received the all rtp packets (i.e from sequence no. 0). I am not getting why did the packet get missed in between and also why firefox client is giving stream timeout as It must have decode the very next keyframe but it is resulting in stream timeout. Any help is appreciated
Message has been deleted
Message has been deleted
nitin kumar saini
unread,
Dec 4, 2023, 10:06:35 AM12/4/23
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to discuss-webrtc
After some more analysis over firefox build, I found a difference in non working case i.e. setRemoteDescription is calling after media transmission started and resulted in synchronisation issue so that black screen is coming for remote video stream. After renegotiation media transmission started 33 ms (Not fixed) earlier than the calling of setRemoteDescription this is happening some what due to latency of 200 ms in my conferencing architecture. Somehow chrome and safari are handling this but firefox not. what can be done in this scenario to avoid this black screen.