Streaming Media Supplement sa2150 and sa2250

Chapter 6 Configuring Media-IXT: an Overview

Another difference between WMT remapping rules and those for RealNetworks and QuickTime, is the use of

Media-IXT’s IP address for WMT remapping rules.

Port numbers are only needed in remapping rules when a non-standard port is being used for the protocol in

question.

Example:

map rtsp://mymixt.com:9090 rtsp://actual-real-server.com RNI

Reverse proxy for multiple origin servers

Selective caching is used in a special way in deployments where Media-IXT performs reverse proxy for

multiple origin servers, each representing a different website, and where Media-IXT should not service requests

for any other origin servers.

Let’s say that you deploy Media-IXT to perform reverse proxy caching for three websites, whose advertised

names are alpha.com, beta.com and delta.com.

First you configure reverse proxy caching for each website.

Then you configure selective caching, placing a rule in each configuration file for each origin server, such that

content from that server is proxied and cached.

Finally, you place general rules (using wildcard characters) saying not to cache and not to proxy content for any

origin server, in the selective caching configuration files.

For each client request, Media-IXT reads the configuration files from top to bottom, so that requests for content

from alpha.com, beta.com and delta.com match the first several rules, and Media-IXT services these

requests. Requests for content from any other origin servers only match the general rules which say not proxy

or cache content, so Media-IXT does not service those requests.

Hierarchical caching and parent.config

For hierarchical proxy, make these changes on the child Media-IXT:

Enable parenting by setting this variable records.config to 1 (true):

proxy.config.http.parent_proxy_routing_enable

Put rules in the parent.config file.

(You make no changes on the parent Media-IXT.)

You can, optionally, add an

RNI

or QT tag to a parenting rule. This permits a child Media-IXT to have one parent

for QuickTime and another for RealNetworks.

You can only add tags by manually editing parent.config.

The format for the tag is to add tag= to the end of the rule, followed by the tag value of RNI or QT.

Example:

dest_domain=. parent=parent1:8080 tag=RNI

You can configure parenting from Traffic Manger, but not for the case where you want RealNetworks and

QuickTime to go to different parents, because Traffic Manger does not permit you to apply tags to parenting

rules.

Configuring a separate WMT parent from Traffic Manger works because the WMT rule is distinguished by its

scheme of mms, so there is no need for a tag.

RealNetworks

notes

• Do not modify rmserver.cfg to configure reverse proxy. This is an obsolete

method.

• Do not try to configure PNA reverse proxy. This is not supported.