openvidu | OpenVidu Platform main repository | Video Utils library

With those changes, I'm able to acheive 3 to 4 stable delay ;)

LINE 79 of

https://github.com/OpenVidu/openvidu/blob/master/openvidu-server/docker/openvidu-recording/scripts/composed.sh

I REPLACED

The WebRTC Obj-C API can be called from any thread, but most method calls are passed to WebRTC's internal thread called signalling thread.

Also, callbacks/observers like SetLocalDescriptionObserverInterface or RTCSetSessionDescriptionCompletionHandler are called from WebRTC on the signaling thread.

Looking at the screenshots, it seems that the signaling thread is currently blocked and can no longer call WebRTC API calls.

So, to avoid deadlocks, it's a good idea to create your own thread / dispatch_queue and handle callbacks.

See https://webrtc.googlesource.com/src/+/0a52ede821ba12ee6fff6260d69cddcca5b86a4e/api/g3doc/index.md and https://webrtc.googlesource.com/src/+/0a52ede821ba12ee6fff6260d69cddcca5b86a4e/api/g3doc/threading_design.md for details.

I found the solution, looks like this issue was device specific and required some configurations. From logs its clear that device's audioserver was crashing on a very rudimentary level. I switched from using MODE_IN_CALL to MODE_IN_COMMUNICATION for speakerphone and mic both and this issue disappeared. It's a weird issue and the solution is even weirder but it works. The device I was using was a AR Smart Glass that has a mic continuously 'on' to listen to your voice commands, I think that was the culprit or maybe misconfigured hardware drivers.

This can be achieved by doing the following in Ionic 4+.

1. You need to use the following plugin

https://github.com/neohelden/cordova-plugin-audiotoggle

@Vasniktel Technically it could be possible to record the video client side as there are a number of WebRTC examples that record locally on the client, however this is not natvie to openvidu. However recording on electronjs is...

github.com/hokein/electron-screen-recorder

tutorialspoint.com/electron/… You could integrate recording separately along side your openvidu app.

The main difference here is that you want to record an incoming call and while you likely won't be able to just write the incoming webrtc data you should be able to record the area of the app (canvas) where the video player is rendered. You will be re-encoding the decoded rendered video stream, but it shouldn't be too much of a hit performance wise.

In peer-to-peer mode, you can ensure the IP addresses of the peers aren't revealed by setting up and forcing the use of TURN server (using the iceTransportPolicy option of relay in the RTCPeerConnection() constructor).

Alternatively, using an intermediary media server (e.g. an SFU or a MCU) would also achieve the same effect.

You are using useEffect without parameter which mean your useEffect will call in every render