I am trying out the WebRTC examples of MuazKhan. It is working perfectly fine when the broadcaster is on AWS/Azure(or any other network) and the receiver is through my phones 4G network. But as soon as I switch to my broadband from 4G, the video stream is unable to connect and I the video player keeps on trying. Therefore I assumed that the problem is of the router NATting and will be resolved if I use a tried-n-tested TURN service such as Xirsys.
Sadly, even after using their TURN servers, I still am blocked with my broadband connection issue as mentioned above. Here are a few queries that I wanted to discuss:-
This issue seems to be due to NATting through my broadbands routers. Shouldn't using the TURN server solve it?
How can I verify if even the TURN servers are getting used and its not just the STUN servers.
Can this issue be due to the Signalling Server?
Do i need to enable some specific protocols in my router to make this work?
What else could be responsible for the issue that I should debug?
The video chat works with most users, but I couldn't get a video chat to work with one of the user of my website.
She couldn't see me, and I couldn't see her.
I don't have any details how it failed like if it was at the SDP negotiation, or if she failed a connection to our TURN server (coturn), but hopefully someone has made it work for VPN users and has an answer for this issue.
ICE failures can happen, no matter what. The ice connection state will go to failed and simplewebrtc will give you an iceFailed event here. You'll need to handle that in your UI somehow.
When I click the send button for sending my app in Application Loader, it is waiting for a response (sent API usage to iTunes Connect, waiting for response) and waiting without error. I am getting a message "the network connection was lost" after a couple minutes. I tried another network connection but the issue was not resolved. Could the issue be on iTunes network?
It should just work if you quit Application Loader, then re-open it.
To submit an application to iTunes Connect, your Mac always need to be up to date, or you will be able to get errors. To do this click on Apple's logo > Software Update. I was having the same problem, and it solved for me. Cheers =)
I had to force quit and the re-open to make it work.
A normal restart did not work, nor did a restart of my Mac. Very weird.
Make sure your iTunes Connect user has admin privileges. I had it set at Technician and everything looked like it was working but it would hang on the "Sending API Usage to iTunes".
None of the above suggestions work for me. Likely the real cause is physical and related how Application Loader is using the internet. I have ADSL connection with a Netgear modem/router assigning each device at home a fixed IP address according to the mac address of the network interface of each device. I had noticed that when Application Loader is uploading, my Windows PC could not connect to the internet. However, if in Mac mini I use Safari doing various things like watching video, my Windows PC can access internet.
Even stranger, when Application Loader is uploading, the modem/router could easily lost connection to the internet, as I could see from the LED lights of the modem. The connection is lost randomly at any progress of uploading the 20 MB file.
So I had turned off Windows PCs, iPads, iPhones and Android device at home, so Mac mini is the only device using the Internet, the Application Loading has finally been able to upload the app successfully in one go.
My guess is, my home phone line has some noise, and Application Loader is using the internet aggressively particularly the up link, so stressing out the modem, then causing other devices like my Windows PC lost connection, not even able to resolve host.
So my working solution is to make Mac be the only device using the Internet, given that the internet connection is already in poor condition with noise, near the edge of losing connection.
I have a piece of software I have written that talks to a web service over it's Wifi connection on a Casio WinCE handheld.
Unfortunately the Wifi network and the network created by WMDC (or ActiveSync) to host the debugger connection clash, they are both 192.168.55.0/24. So I can't have them both connected at the same time.
Does anybody know if you can reconfigure WMDC to use a different address range?
I've hunted through the registry but can't see anything obvious, and Google is not turning up anything useful.
Thanks,
James.
Is the development PC on teh same network as the WiFi connection? If so, I'd abandon ActiveSync/WMDC altogetehr and just use ethernet debugging over the same connection that it's using for the web service calls.
I've developed a Windows phone app which consumes some data from WCF Service. My app seems to be very slow in Wi-Fi on comparing it with 3G or LAN. I'm a new bee to both Windows phone app dev and WCF. I've verified a number of variables on WiFi bandwidth and connection. Wi-Fi looks good, but the app still slows down. So not sure where the problem is? Do I need to add any configuration to my service to avoid this? Or do I need to check my device? Can anyone help me to find out the cause?
I have had a similar issue. Seems like the 3G data and WiFi do not work smoothly when they're both turned on. Disable 3G data and only enable WiFi and vice versa.
This issue appeared for me after the 7.10.8107.79 update.
This bug have been reported to Microsoft and they are looking into the issue.