WebRTC DataChannel shuts down(close) after some time of operation about sipsorcery HOT 2 OPEN

Could you describe a little more what is your topology ? You talked about a JS client , a server and Sipsorcery ...
You have 2 clients (Web + SipSorcery) and in the middle a server ?

Do you send paquets often ? i.e. is there sometimes a long period without sending any data ?

The delay of 10 mns let me think about a device (a switch for example) which cut the link after some period of inactivity.

Have you tested a echo scenario (small packets but "often" like every seconds) ? Is it cut before 10 mns ?

from sipsorcery.

I have an ASP .Net Core server that uses SignalR for signaling and Sipsorcery to handle WebRTC. The client role is played by a React application. There is no middleware between them, they communicate directly. Packets are sent according to how they are decoded (if the image on the screen changes, a frame packet is sent. If not, no packets are sent). This is the logic of the Javascript decoder. I think in about 10 minutes the app breaks when transferring large packages and often (0-16kb every second). If you transfer small packages and not so often - the application will work longer. The server and client work on the same device, i.e. both on localhost. At the same time, I do nothing. The connection is fully established and I just leave the screen streaming (I open any YouTube video, so you get more packages and more often).

from sipsorcery.