Example: Rate Map Configuration; Virtual Player Yahoo Type Configuration - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide

Example: Rate Map Configuration

By default, the match string (length 2 bytes) is extracted by going to the end of the URL and
skipping 12 Bytes from the end. The value in that location is mapped to the configured rate in
kbps. Example:
http://video.example.com/public/BBB87026/xy_750_1938344/
AC60E15B2A7C4A45AC4C1472E2AC0816_030000003F.flv
In the URL above, the value 03 (12 Bytes from the end of the URL) is extracted, and the
corresponding assured flow rate (1000Kbps) is applied. The configured CLI looks like this:
virtual-player my_virtual_player type 2
rate-map match 01 rate 300
rate-map match 02 rate 500
rate-map match 03 rate 1000
In this way, URLs containing 01 in the correct place (12 bytes from the end) maps to an
assured flow rate of 300; with 02 the assured flow rate is 500; and so on. Instead of using the
default match (12 bytes from the end of the URL) you can specify a query-string-parm or a
uol offset and length. For details on these options see

Virtual Player yahoo Type Configuration

After adding a yahoo virtual player, click Configure in the list of virtual players to open
configuration pages (in a new window) for that type of virtual-player. Click Add/Update on
each configuration page and simply close the window when you are done. Verify your
configurations by clicking Show in the virtual player list.
Compute MD-5 hash of query string parameters representing stream-id, auth-id, a
configured shared-secret, and time-interval; and match the computed value with the
specified match query-string-parm <string>. The HTTP GET proceeds if the computed MD-
5 hash matches; if there is no match, the session is rejected. Use virtual player <name> type
3 no req-auth to disable.
Important! Virtual-player yahoo requires a special license to be configured.
Media Flow Controller Configuration Tasks (Web Interface)
"Terminology" on page
Configuring Virtual Players (Web Interface)
30.
173