The WebRTC is worked on firefox or google chrome.And ı want to ran applet on the same browser too.Namely simultaneously. But the applet can't run because JRE problem.I ran the WebRTC Node Server on 1337 port. But i can't run other applet aplications after i opened the WebRTC application on port 1337. Why is WebRTC blocking other applications which use different ports. I opened one port (1337) for webRTC. I wonder that the webRTC also use some other ports because of video streaming ? Is WebRTC blocking because of UDP or TCP ? Why is it blocking ? Can't i use applet application which uses port and webRTC application simultaneously. What can i do for this problem?
Related
I am creating media server using WebRTC for video conferencing. As you might know when a user connects to the server two ports will be opened on the server side. RTP and RTCP ports over TCP. Thus, media server will need wide-range of available ports. The case here is not about multiplexing RTP and RTCP ports.
Assume that the media server is behind firewall and ports are blocked so that cannot open wide-range of ports. For example, the media server will use 8080 for signalling and 443 for RTP/RTCP. All video traffic will flow into 443 on the server side.
Is that possible?
It is possible, and many media servers provide that feature.
Wowza enables single port for WebRTC over TCP; Unreal Media Server enables single port for WebRTC over TCP and for WebRTC over UDP as well.
Technically, it's quite challenging to develop such a feature; especially for providing single port for WebRTC over UDP. You need to relay incoming WebRTC traffic, arriving to your single port, to internal endpoints of particular RTCPeerConnections in the server. Initial Stun requests carry information that helps you find the right context and map the external to internal.
We are investigating adding the Kaa client to our products and using the Kaa server operationally, and we have some questions in the networking and protocol area. Our main concern is having the IoT device access the IoT server through the Internet without being blocked by the firewall at the IoT device in a "typical" environment. For this reason we see that HTTP/HTTPS using port 80/443 is often used.
Do you believe that most of the IoT device will communicate because most firewalls allow all outgoing traffic?
Or do you think that most end users will have to explicitly configure a firewall rule for the IoT device?
What was the rationale for using the port numbers 9889/9888 and 9999/9997?
Can these port numbers be reasonablely modified? If so, where and how?
Is there a specification of the Kaa TCP protocol?
Thank You
Keith Krajewski
About Kaa TCP protocol use official documentation page
you can change ports of bootstrap and operations services in this files:
bootstrap-http-transport.config
bootstrap-tcp-transport.config
operations-http-transport.config
operations-tcp-transport.config
Assuming there is a client-server application running in a LAN. Clients are WPF applications and the server is a Windows service. Are there any benefits to use Websockets instead of raw TCP sockets for client-server communication?
No. The primary benefit of WebSockets in general is that they are available in web browsers. If your application is not running in a web browser, there is no point in using WebSockets.
I am woking on a Mobile application, which sends GPS co-ordinates from the mobile to an azure website.
Right now I am able to do this using TCP endpoints in Azure Web/Worker Role. The Mobile hardware I am using is SIM300 module.
SIM300 also provides sending data via UDP, which is much simpler, faster for my application.
I have heard Azure Connect uses UDP to communicate between local and virtual machines through UDP.
I am not sure, but is there any way to implement the same application to use UDP instead of TCP in Azure?
I managed to get UDP to work over the service bus using a UDP -> TCP tunnel. But as Simon says, you're better off using TCP if you can.
http://coderead.wordpress.com/2012/03/14/tunnelling-udp-over-the-service-bus-or-how-to-get-sentinel-licencing-server-working-on-azure/
Azure doesn't support public UDP endpoints (yet). The only current alternative is to use an non-Azure server that listens on UDP and, via Windows Azure Connect, forwards it to the 'internal' endpoint. Since your device already uses TCP anyway, I would stick with that for now.
This is my application setup.
I have written an application (in Qt ) which will run on a linux computer (Ubuntu). The application accepts requests from web app and sends them to a serial device that is connected to the computer. Also application will send back the response to web app as well. This linux computer is connected to internet via wifi router.
Now my question is, Is there a way (other than port forwarding in wifi router) that I can achieve this functionality. Using port forwarding I can ask the router to forward the requests coming for a particular port to my computer at a particular port and my application would be listening for that. But for that I would have to configure the router and I don't want to do that. Is there a way I can do that automatically?
Thanks,
DPatel
Your issue is traversing non-routable NAT addresses.
UPNP is an option: http://en.wikipedia.org/wiki/Universal_Plug_and_Play
It will automatically configure port forwarding.
There is a library out there called STUNT for this as well:
http://nutss.gforge.cis.cornell.edu/stunt.php