You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 25, 2023. It is now read-only.
The workflow for every two calling parties to establish a WebRTC connection.
Two parties send their shared passphrase to signal server once connected through WebSocket.
The signal server tries to execute string set on Redis with command SET <passphrase> "" NX upon each party request, only the fastest party request arrives will be successful which returns 1, the other 0.
The signal server assigns the caller role to the party which executes previous step successfully, to the other callee role. And return back to their respective roles.
Now each party gets their roles. The caller party first sends its SDP offer, once the callee party receives its offer through signal server, it sends its SDP answer back. Then following WebRTC ICE candidates exchanging. Until WebRTC connection establishs successfully.
The workflow for every two calling parties to establish a WebRTC connection.
SET <passphrase> "" NXupon each party request, only the fastest party request arrives will be successful which returns1, the other0.callerrole to the party which executes previous step successfully, to the othercalleerole. And return back to their respective roles.callerparty first sends its SDP offer, once thecalleeparty receives its offer through signal server, it sends its SDP answer back. Then following WebRTC ICE candidates exchanging. Until WebRTC connection establishs successfully.