Para poder acceder a los servicios de streaming de Windows Media Server (MMS) tenemos que abrir el puerto 1755 en los dos sentidos (ambas reglas de firewall) ya que las peticiones contra el servidor provocan que el mismo servidor genere conexiones nuevas contra el puerto 1755 del cliente. Para el servicio a través del Adobe Flash Media Server (RTMP) abriremos el puerto 1935 en el sentido de entrada.

A continuación se detallan todos los puertos involucrados en los protocolos usados para streaming, así como un poco más de información:

  • RTSP: the Real Time Streaming Protocol (RTSP), developed by the IETF and published in 1998 as RFC 2326, is a protocol for use in streaming media systems which allows a client to remotely control a streaming media server, issuing VCR-like commands such as “play” and “pause”, and allowing time-based access to files on a server. Some RTSP servers use RTP as the transport protocol for the actual audio/video data. Many RTSP servers use RealNetworks’s proprietary RDT as the transport protocol.
    • TCP 554 (In/Out): used for accepting incoming RTSP client connections and for delivering data packets to clients that are streaming by using RTSPT.
    • UDP 5004 (Out): used for delivering data packets to clients that are streaming by using RTSPU.
    • UDP 5005 (In/Out): used for receiving packet loss information from clients and providing synchronization information to clients that are streaming by using RTSPU.
  • MMS: Microsoft’s streaming server uses the Microsoft Media Services (MMS) protocol (also called NetShow Services) to transfer unicast data. MMS can be transported via UDP or TCP. If the Windows Media Player client cannot negotiate a good connection using MMS over UDP, it will resort to MMS over TCP. If that fails, the connection can be made using a modified version of HTTP (always over TCP). This is not as ideal for streaming as MMS over UDP, but ensures connectivity nonetheless. The default port for MMS is 1755.
    • TCP 1755 (In/Out): used for accepting incoming MMS client connections and for delivering data packets to clients that are streaming by using MMST.
    • UDP 1755 (In/Out): used for receiving packet loss information from clients and providing synchronization information to clients that are streaming by using MMSU.
    • UDP 1024-5000 (Out): used for delivering data packets to clients that are streaming by using MMSU. Open only the necessary number of ports.
  • HTTP: HTTP streaming is a mechanism for sending data from a Web server to a Web browser in response to an event. HTTP Streaming is achieved through several common mechanisms. In one such mechanism the web server does not terminate the response to the client after data has been served. This differs from the typical HTTP cycle in which the response is closed immediately following data transmission. The web server leaves the response open such that if an event is received, it can immediately be sent to the client. Otherwise the data would have to be queued until the client’s next request is made to the web server. The act of repeatedly queing and re-requesting information is known as a Polling mechanism. Typical uses for HTTP Streaming include market data distribution (stock tickers), live chat/messaging systems, online betting and gaming, sport results, monitoring consoles and Sensor network monitoring.
    • TCP 80 (In/Out): used for accepting incoming HTTP client connections and for delivering data packets to clients that are streaming by using HTTP.
  • RTMP: Real Time Messaging Protocol Is a proprietary protocol developed by Adobe Systems (formerly developed by Macromedia) that is primarily used with Macromedia Flash Media Server to stream audio and video over the internet to the Adobe Flash Player client. The default connection port is 1935. The traffic goes through TCP port 1935 (inbound and outbound, since there needs to be a 2 way communication). In order to test this, you can use this Adobe page: http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_16466&sliceId=1
    • TCP 1935 (In/Out)