![Juniper MEDIA FLOW CONTROLLER 2.0.4 - Administrator'S Manual Download Page 91](http://html1.mh-extra.com/html/juniper/media-flow-controller-2-0-4/media-flow-controller-2-0-4_administrators-manual_2032854091.webp)
Creating a Namespace and Setting Namespace Options (CLI)
91
Media Flow Controller Administrator’s Guide
Media Flow Controller Configuration Tasks (CLI)
Note!
Set origin-request host-header inherit incoming-req in accordance with the
origin-server setting; see
Table 10, “Namespace origin-server and origin-request
Dependencies per Proxy Deployment
for CLI details. Use x-forwarded-for to allow
(with enable) or disallow (with disable) setting the X-Forwarded-For header to the
client IP address; default is enable.
origin-request
cache-revalidation {deny | permit}
header <name> [<value>] action add ...
host-header inherit incoming-req {deny | permit}
x-forwarded-for {disable | enable}
Example:
test-vos (config) #
namespace test
test-vos (config namespace test) #
domain any
test-vos (config namespace test) #
origin-server http example.com/video
test-vos (config namespace test) #
match uri / precedence 3
test-vos (config namespace test) #
delivery protocol http
test-vos (config namespace test delivery protocol http) #
client-request cookie
action no-cache
test-vos (config namespace test delivery protocol http) #
client-response header
Location action delete
test-vos (config namespace test delivery protocol http) #
origin-fetch
cache-age-default 14400
test-vos (config namespace test delivery protocol http) #
origin-request x-
forwarded-for enable
test-vos (config namespace test delivery protocol http) #
exit
test-vos (config namespace test) #
exit
6.
Optionally, make live-pub-point settings if needed for live streaming.
•
caching—Enable caching for this service (default is disabled).
•
receive-mode—Set a method for receiving live streaming:
•
on-demand—When a request is received.
•
sdp-name <URL>—Use an SDP (service delivery protocol) file to set the live
publishing point. The URL can be scp://... or http://... only. After Media Flow
Controller encounters this, it pulls in the file from the specified location, and saves
it in the file system (not disk cache) so it is available for RTP/RTSP. Optionally,
choose immediate, to start as soon as the file is retrieved or enter a start-time
and, optionally, an end-time. See
“Terminology” on page 30
for the scp URL
format).
•
status—Make active or inactive the live-pub-point.
7.
Set parameters for pre-staging content from origin; authentication schemes must be pre-
configured to be used. See
namespace
for CLI details. The ftp user is auto-generated as
<namespace>_ftpuser, without a password (login disallowed). Set the password here;
this entry overrides a user <namespace>_ftpuser password setting. Verify with show
usernames. Remove set password with no pre-stage ftp user <user_name>.
pre-stage ftp user <name> password {RADIUS | TACACS | <password>
[encrypt]}
Example:
test-vos (config namespace test) #
domain any
test-vos (config namespace test) #
origin-server http example.com/video
test-vos (config namespace test) #
pre-stage ftp user test_ftpuser
password 678
Summary of Contents for MEDIA FLOW CONTROLLER 2.0.4 -
Page 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Page 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Page 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Page 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Page 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Page 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...