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
Copying from forum.
Thanks. SIP proxy is on the line. I can think of quick implementation based on this - https://github.com/pchab/ProjectRTC - Simply build a separate topic as a sub topic of your group url groupchat/call so that everyone will receive the url since they are subscribed to groupchat/*. Upload all your sdp and ice candidates so as to initiate the call. Not sure how to extend it to group though. One possible way is to replace groupchat/call with groupchat/memberid where everyone publishes their information on their channel and you receive the updates for every user in your group. At the same time we don't want these information offline delayed so these information can be send with QOS0.
The text was updated successfully, but these errors were encountered:
Both cases can be handled by publishing on topics. Easier thing is to publish on their own sub node so that client can differentiate. Channel - groupchatid/call/clientid.
Copying from forum.
Thanks. SIP proxy is on the line. I can think of quick implementation based on this - https://github.com/pchab/ProjectRTC - Simply build a separate topic as a sub topic of your group url groupchat/call so that everyone will receive the url since they are subscribed to groupchat/*. Upload all your sdp and ice candidates so as to initiate the call. Not sure how to extend it to group though. One possible way is to replace groupchat/call with groupchat/memberid where everyone publishes their information on their channel and you receive the updates for every user in your group. At the same time we don't want these information offline delayed so these information can be send with QOS0.
The text was updated successfully, but these errors were encountered: