I have this weird condition where the peer creating the room is not able to get ICE server candidates from the signalling server, I do see the candidates appearing in the console, but they never get used (as per the chrome internals ). I am using Xirsys's fork of signalmaster.
At the moment I am populating the ICE server candidates using Xirsys's API call on the client end, which I believe is not the safest way to go ahead.
Although when another peer connected to the room, refreshes itself the needed ICE server candidates appear on the call initiator.
Any directions as why this might be happening ? and How I can resolve it ?
I have this weird condition where the peer creating the room is not able to get ICE server candidates from the signalling server, I do see the candidates appearing in the console, but they never get used (as per the chrome internals ). I am using Xirsys's fork of signalmaster. At the moment I am populating the ICE server candidates using Xirsys's API call on the client end, which I believe is not the safest way to go ahead.
Although when another peer connected to the room, refreshes itself the needed ICE server candidates appear on the call initiator.
Any directions as why this might be happening ? and How I can resolve it ?