Streaming Media Supplement sa2150 and sa2250

96
Chapter 9 Configuring Media-IXT for QuickTime
Four principles apply to writing QuickTime map rules:
• The map rules in remap.config. make QuickTime reverse proxy caching work by mapping the
advertised site name and RTSP port to the URL representing RTSP traffic on the origin QuickTime server.
• Use a scheme of rtsp for the URLs in the map rules.
• The default port for RTSP is 554. Specify a port in your map rule only when a non-standard RTSP port is
used.
• Do not write a reverse_map rule: reverse_map rules are not required for QuickTime, and will likely
be ignored if you do write them.
Here is an example:
If Media-IXT answers to an advertised site name of traffic.hp.com, has an RTSP port of 1091, and is the
reverse proxy for an origin QuickTime server, perfdev.hp.com, with an RTSP port of 554, the map rule
should be:
map rtsp://traffic.hp.com:1091/rtsp://perfdev.hp.com/ QT
The log entries contain the URL as requested by the client. This allows tracking based on the number of
URLs for which reverse proxy is used.
For hierarchical deployments, logging of the IP address of the server works like this:
• the child logs the IP address of the parent (which, to the child, is the origin server).
• the parent logs the IP address of the origin server.
For RTSP, the mapping rules for reverse proxy caching are in the remap.config file. Be aware that these
directions document only one scenario for reverse proxy, in which Media-IXT answers to the advertised name
of the website. That is, the advertised name of the website resolves to an IP address which is Media-IXT’s,
whether virtual or not.
Reverse proxy mapping rules must be different when a different reverse proxy scenario applies. See the
explanation of these issues in “Understanding forward proxy, reverse proxy, and transparency” on page 6.
Also be aware that writing correct mapping rules is necessary but not sufficient for reverse proxy to work
correctly. The Fully Qualified Domain Name portion of the URLs of the origin server’s content must contain
the advertised name of the website. Again, see the section just cited.
For this configuration example we assume:
• a Media-IXT host, whose IP address is 10.10.10.10
,
and which answers to
front.myreality.com
• an origin QuickTime server where our QuickTime streaming content resides; its IP address is
11.11.11.11, and it answers to back.myquickness.com
To configure reverse proxy caching for QuickTime:
1. Set the proxy.config.reverse_proxy.enabled variable in the records.config file on the
Media-IXT host to
true
.
2. Edit the remap.config file on Media-IXT, adding map and reverse_map
rules. Note that the trailing
slashes in all of the rules are required.
Add the RTSP map rule:
map rtsp://front.myreality.com/ rtsp://back.myquickness.com/
3. If our Media-IXT is performing reverse proxy for an origin RealNetworks server as well as an origin
QuickTime server, we need separate sets of rules for each origin server, and we must add tags to the rules
to specify the protocol to which each rule applies.