Juniper MEDIA FLOW CONTROLLER 2.0.4 -, Administrator'S Manual

Page: 78 / 400

Media Flow Controller Configuration Tasks (CLI) Media Flow Controller Administrator’s Guide
78 Creating and Configuring Virtual Players (CLI) Copyright © 2010, Juniper Networks, Inc.
rst=40&sver=3&expire=1266310800&key=yt1&signature=66222E9350B9BB5AC68297F12A
C1DCB4C53AAFDE.55B33FFFA04EBF001AF39A4F316E657FC318E0E5&factor=1.25&id=efa3a
0434887fdc0&redirect_counter=1”
It is observed that these two request formats do not have an explicit association or reference
to the media object, and the URI themselves are not cache friendly. The association to the
media object is provided using a combination of an id and format tag.
For case (a) this association is provided by the video_id and fmt query parameters.
For case (b) this association is provided by the id and itag query parameters.
Media Flow Controller uses a combination of these query parameters to generate an internal
cache name for the media object. YouTube videos in Media Flow Controller are cached with a
cache name format as:
yt_video_id_efa3a0434887fdc0_fmt_34
Media Flow Controller also supports random access via seek/scrub for YouTube videos.
YouTube signals a seek point via a query parameter, begin, with units of milliseconds. Media
Flow Controller translates this seek point to the correct position in the video file for both the
FLV or MP4 container formats and data that is delivered to the player is from the seek point
onwards to the end of the file.
Example: Configuring generic Virtual Player (CLI)
The generic virtual player can be used to cache most Web content.
To configure the type generic (formerly Type 0) virtual player:
1. Configure a virtual player with a name and type generic (enters you to virtual-player
configuration mode). Use no virtual-player <name> to delete; use virtual-player <name
no <option> to make changes to configurations (either reset default or remove setting).
virtual-player <name> type generic
2. Configure hash verification options. Note! In Release 2.0.4, only md-5 digest is
supported. Configure a shared secret value to be appended or prefixed to the URL as
specified, for matching against the hash value provided in the URL and indicated by the
match query-string-parm you configure.
hash-verify digest md-5 shared-secret <string> {append | prefix} match
query-string-parm <string>
3. Configure download parameters for delivering files at the fastest possible speed. If you
choose always, then file downloads are always delivered at the fastest possible speed;
otherwise, you must have either a query param or a header name that indicate that a full
download should be processed.
full-download {always | match <string> {query-string-parm <string> |
header <header_name>}}
4. Optionally, configure assured-flow delivery optimization. Note! The auto option is not
supported in Release 2.0.4. A query param can be used or define a static rate value in
kbps, a value of 0 (zero) means no throughput at all. After a value is entered, this
parameter is enabled. See
“Media Flow Controller AssuredFlow” on page 50 for more
information.
assured-flow {auto | query-string-parm <string> | rate <kbps>}