RTCPeerConnection Reconnection Mechanism in a SipSorcery

[mail2mhossain]

We are currently utilizing SipSorcery in conjunction with a Janus server to manage our communications. We have observed that in instances where the internet connection is interrupted, the WebSocket connection with the Janus server is consequently lost. Fortunately, a reconnection mechanism is in place which effectively attempts to re-establish the connection to the Janus server, and has been performing optimally. It has been noted that reconnection is successful even if the internet connectivity is restored within a 25-second timeframe.

We are now turning our attention to the RTCPeerConnection and are keen to understand if a similar reconnection mechanism is implemented within it. Your insights on whether there is a connection retry system embedded in RTCPeerConnection, and any additional information on how it operates would be immensely valuable.

[sipsorcery]

Do you get any DTLS alert log messages in the application using the sipsorcery library?

By the time the DTLS alert gets from the BouncyCastle DTLS client/server to the sipsorcery RTCPeerConnection the DTLS session has already been closed and the state (encryption keys etc.) cleared. There's no way to restore a session after that.