Library Table of Contents Index Previous Next Comments

MMS streaming media protocol details

MMS streaming example: UDP to clients  Top

The following example shows the typical client and server connections required for MMS streaming. Note that in this example, NetCache receives content from the streaming server over TCP and delivers the content to clients over UDP.

If a firewall did not allow TCP port 1755, the NetCache appliance would use HTTP encapsulation over TCP port 80 to send data to servers or clients. This scenario is not illustrated.

Understanding MMS connection requirements  Top

The following table describes the types of protocols NetCache must service to deliver MMS content to clients.

Use the proceeding table to configure the NetCache appliance and associated network devices, such as a switch, router, or firewall, that must pass traffic to and from the NetCache appliance. To ease configuration, the Appliance Manager provides default settings that correspond to the port information provided in the following table.

Protocol

Transport

Explanation

Upstream traffic

Downstream

traffic

MMS

TCP

Microsoft Media Streaming. Used for data and control in Windows Media streams only.

Received on NetCache port 1755

Sent to port 1755

Received on arbitrary NetCache port

Sent from
NetCache port 1755 to arbitrary client port

MMS

UDP

Microsoft Media Streaming. Used for data and retransmit requests in Windows Media streams only.

Received on NetCache port 1755

Sent from arbitrary client port

N/A

Sent to
arbitrarily advertised UDP ports

HTTP

TCP

HTTP encapsulation is used from NetCache to clients and NetCache to servers when the firewall blocks TCP or UDP.

Received on NetCache port 80

Sent to origin server port 80

Received from origin server port 80 or 3128

Sent from NetCache port 80 or 3128

Library Table of Contents Index Previous Next Comments