RTCMultiConnection is a WebRTC JavaScript library for peer-to-peer applications (screen sharing, audio/video conferencing, file sharing, media streaming etc.)
We have implemented this screen sharing in our project. For initial testing, it is working on our inhouse network and on testing site also but when deployed on the production on client side we are facing following issues -
1) User can share a screen but sometime the other person is not able to see it.
2) User shared the screen and other one can see it but after some time it shows the white screen and it did not work after re-sharing also.
We tried by dynamic loading the socket.io JavaScript library but it worked for couple of machine not for all also it worked on some machine with using the Empty Cache and Hard Reload.
We stuck in above 2 scenarios so can you please suggest on this? Is there any limitations for this screen sharing like Firewalls, Protocols or Ports ?
Hello,
We have implemented this screen sharing in our project. For initial testing, it is working on our inhouse network and on testing site also but when deployed on the production on client side we are facing following issues -
1) User can share a screen but sometime the other person is not able to see it. 2) User shared the screen and other one can see it but after some time it shows the white screen and it did not work after re-sharing also.
We are using your connection.socketURL = 'https://rtcmulticonnection.herokuapp.com:443/'; server, Is there any restrictions for this server?
We tried by dynamic loading the socket.io JavaScript library but it worked for couple of machine not for all also it worked on some machine with using the Empty Cache and Hard Reload.
We stuck in above 2 scenarios so can you please suggest on this? Is there any limitations for this screen sharing like Firewalls, Protocols or Ports ?