Media Flow Controller Configuration Tasks : How To : Configure Media Flow Controller with SmoothFlow Restricted by File Path

Configure Media Flow Controller with SmoothFlow Restricted by File Path
Configuring Media Flow Controller to apply SmoothFlow functionality to all video files located in a particular directory, requires a namespace configuration and a SmoothFlow virtual player Type 4 configuration.
1.
For our example company, www.example.com, the virtual player configuration for this task could look like this:
test-vos (config) # virtual-player HD type 4
test-vos (config virtual-player HD) # connection max-bandwith 0
test-vos (config virtual-player HD) # control-point player
test-vos (config virtual-player HD) # signals session-id query-string-parm sid state query-string-parm sf profile query-string-parm pf
test-vos (config virtual-player HD) # seek query-string-parm sk
test-vos (config virtual-player HD) # exit
test-vos (config) #
This configuration sets connection max-bandwidth to unbounded (0), control-point to player (what monitors the bandwidth), the query params for session-id (sid), state (sf), profile (pf), and seek (sk); and does not impose hash verification. The client player must be designed so that it knows when to send requests for which SmoothFlow functions, including serving different video bit-rate profiles.
2.
test-vos (config) # namespace exampleHD
test-vos (config namespace exampleHD) # domain www.example.com
test-vos (config namespace exampleHD) # match uri /videos/HD/
test-vos (config namespace exampleHD) # origin-server http www.exampleOS.com 80
test-vos (config namespace exampleHD) # virtual-player HD
test-vos (config namespace exampleHD) # status active
test-vos (config namespace exampleHD) # exit
test-vos (config) #
The match uri-prefix /videos/HD/ tells Media Flow Controller to use these namespace rules for incoming requests containing /videos/HD in the URL. Any incoming request for a file located in /videos/HD will use the assigned SmoothFlow virtual player Type 4, HD. That virtual player tells Media Flow Controller what actions to perform when certain query params are sent from the client player.
In this case, any incoming requests for videos at www.example.com/videos/HD will have SmoothFlow functionality applied as indicated, with a working SmoothFlow client player.
Just as with the initial namespace configuration, repeat the namespace configurations with the domain specified without the “www” prefix, and again specified with the IP address, if requests may come in those ways.
Tip! If unsure what port you are using for origin-server, use standard Linux shell commands to figure out the port, and then configure it along with the origin-server, if not the default.

Report an Error
Media Flow Controller Administrator's Guide and CLI Command Reference
Copyright © 2010 Juniper Networks, Inc.