Media Flow Controller Configuration Tasks : Policy Configurations : Delivery Protocol Options

Delivery Protocol Options
These are the ports on the Media Flow Controller that receive and deliver media. These ports typically have Internet access, and should be connected with highest-quality cables. See Table 6, “Example Machine Setup of Management and Traffic Ports for an example.
Configuring Delivery Protocol
The delivery protocol command lets you specify what protocols to use for media delivery and manipulate headers; in Release 2.0.2 http and rtsp are allowed values. By default, Media Flow Controller listens on all interfaces; if you set specific traffic interfaces, only those are used for traffic. See delivery for CLI details.
Media Flow Controller supports known HTTP methods (GET, POST, TRACE, CONNECT, OPTIONS, DELETE, PUT) always. To add support for http request methods, use allow-req and specify up to 16 custom request methods. Use all to permit Media Flow Controller to tunnel any request. Default is none, only the known methods listed above are allowed. Use no to remove the specified method(s).
delivery protocol http allow-req all
delivery protocol http conn-pool origin {enable | disable}
Use max-conn to limit the maximum allowed pooled connection; default is 256, maximum allowed is 2048.
Use timeout to set a pooled connection timeout; default is 300 seconds, maximum allowed is 86,4000 seconds (24 hours).
Optionally, configure interfaces for Media Flow Controller traffic; once 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>...
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>
Optionally, set the maximum request length (domain + URI + Query Params + 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 set value are rejected.
delivery protocol http req-length maximum <bytes>
Since delivery changes have been made (steps 3 and 4), restart the delivery service (mod-delivery).
service restart mod-delivery
show delivery protocol http
write memory
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
To make these configurations using the Management Console, go to the Service Config tab, Delivery Protocol page; use the EZconfig page Service Restart area to restart the mod-delivery service; see Service Config > Delivery Protocol for details.

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