Configuring Media Flow Controller For Smoothflow (Cli); Configuring Smoothflow Virtual Player (Cli) - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Common Configuration Tasks (CLI)
requests to Media Flow Controller mid-tier proxy, instead of to origin servers. Media Flow
Controller serves the content just as an origin server would in a network without mid-tier
servers.
You can configure Media Flow Controller as a mid-tier proxy via a namespace setting. In this
deployment, you must also configure user browsers to point at the Media Flow Controller;
domain and match uri-prefix settings are generally irrelevant and can be set to any and /
(slash), respectively. If you have multiple namespaces, set a low precedence (10 is the lowest)
so incoming requests can pass to namespaces with specific uri-prefix matches (instead of /
that accepts all incoming requests).
1. Create a namespace with domain any, match uri / precedence 10 and origin-server
http absolute-url.
2. Configure your browser to point at the Media Flow Controller. In Internet Explorer™, you
do this through the Tools > Internet Options > Connections > LAN settings page. In
Mozilla Firefox™, use the Tools > Advanced > Network > Connection Settings page.
In this way, any connections to the Internet go through Media Flow Controller to the
appropriate namespace rather than this one.

Configuring Media Flow Controller for SmoothFlow (CLI)

The following Media Flow Controller configurations are required for SmoothFlow functioning.
They must be done by the Media Flow Controller administrator and are included here as an
example. See
•
"Configuring SmoothFlow Virtual Player (CLI)" on page 204
•
"Configuring SmoothFlow Namespaces (CLI)" on page 206

Configuring SmoothFlow Virtual Player (CLI)

Configure smoothflow type virtual players if you want to use the SmoothFlow feature.
Note! All virtual-player parameters are disabled until a value is set.
To configure the type smoothflow (formerly Type 4) virtual player:
1. Configure a virtual player with a name and type smoothflow (enters you to virtual-player
configuration mode).
virtual-player <name> type smoothflow
2. Configure the control point for signalling bandwidth changes at the client side; either
server or player for SmoothFlow signaling. If server, Media Flow Controller detects the
bandwidth variations at the client side and adjusts the bit-rate of the video accordingly. If
player, the player at the client side explicitly signals the bandwidth changes and Media
Flow Controller adjusts the bit-rate of the video accordingly.
control-point {player | server}
3. Set signal names for session-id, state, and profile delivery functions. Your client player
must understand the query params you use; for example sid (for session-id), sf (for SF
state), pf (for profile). See
information on SmoothFlow states.
signals session-id query-string-parm <string> state query-string-parm
<string> profile query-string-parm <string>
204 Configuring Media Flow Controller for SmoothFlow (CLI)
virtual-player type smoothflow
"virtual-player type smoothflow" on page 378
Media Flow Controller Administrator's Guide
for CLI details.
Copyright © 2010, Juniper Networks, Inc.
for further