Media Flow Controller Configuration Tasks (CLI)
Media Flow Controller Administrator’s Guide
74
Creating and Configuring Virtual Players (CLI)
Copyright © 2010, Juniper Networks, Inc.
to tunnel any request. Default is none, only the known methods listed are allowed. Use no
to remove the specified method or methods.
delivery protocol http allow-req all
2.
Optionally, disable/enable connection pooling (enabled by default) and configure
parameters; for delivery protocol http only.
delivery protocol http conn-pool origin {enable | disable}
a.
Use max-conn to limit the maximum allowed pooled connection; default is 256,
maximum allowed is 2048.
b.
Use timeout to configure a pooled connection timeout; default is 300 seconds,
maximum allowed is 86,4000 seconds (24 hours).
3.
Optionally, configure interfaces for Media Flow Controller traffic; after configured, Media
Flow Controller accepts traffic on those interfaces only. Applies to both http and rtsp
delivery protocols. Up to 10 interfaces can be specified.
delivery protocol [http | rtsp] interface <interface_name>...
4.
Optionally, configure listen ports for the traffic interfaces as needed; default is port 80 for
http, port 554 for rtsp. By default, Media Flow Controller listens on port 80 for HTTP and
port 554 for RTSP on all interfaces.
delivery protocol http listen port <port>
5.
Optionally, set the maximum request length ( URI + Query Headers),
in characters/bytes, for incoming requests (http delivery protocol only). Default is 16384
bytes; maximum allowed value is 32768. Incoming requests with lengths exceeding the
configured value are rejected.
delivery protocol http req-length maximum <bytes>
6.
Since delivery changes have been made (steps
3
and
4
), restart the delivery service
(mod-delivery).
service restart mod-delivery
7.
To verify configurations.
show delivery protocol http
8.
Save configuration settings.
write memory
Example:
test-vos (config) #
delivery protocol http conn-pool origin max-conn 200
test-vos (config) #
delivery protocol http interface eth11 eth12 eth13
test-vos (config) #
delivery protocol http listen port 80
test-vos (config) #
delivery protocol http req-length maximum 23576
test-vos (config) #
service restart mod-delivery
test-vos (config) #
write memory
Creating and Configuring Virtual Players (CLI)
Create virtual players to customize how videos are delivered; after created, they are assigned
to a namespace. This is optional; if a namespace does not have a defined virtual player
assigned to it, it uses the network connection settings.
You may want to create a virtual player for each type of video you deliver; for example, if you
deliver YouTube® videos, create a type youtube virtual-player for use in the corresponding
namespace. Media Flow Controller virtual players support and complement client-side video
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...
