Media Flow Controller CLI Commands : delivery

Set delivery options, including listen interfaces, for delivering content to the player (end-user/consumer). If not specified, default actions take place in the delivery path. This command sets global attributes; use namespace to set these attributes on a namespace basis. See “Delivery Protocol Options” on page 70 for task details.
delivery protocol {http | rtsp}
allow-req {all | <method1> [<method2>] [<method3>]... [<method16>]}
max-arp-entry <number>
max-conn <number>
timeout <seconds>
connection [close use-reset | persistence num-requests <0 - 100>]
file-type <suffix> content-type <type>
interface {all | <interface> <interface> <interface> ...}
listen port {80 | <port> <port> <port> ...}
req-length maximum <bytes>
trace enable
Set content delivery options; choose either http (default port is 80), or rtsp (default port is 554). Two delivery protocol (one for http and one for rtsp) configurations are allowed. Not all options are available for rtsp. Use no delivery protocol <protocol> <option> to reset to default. Notes:
allow-req—(http only) Media Flow Controller supports known HTTP methods (GET, POST, TRACE, CONNECT, OPTIONS, DELETE, PUT) always; other HTTP access methods, including custom methods, are supported via this option; up to 16 may be added. Use all, to accept any request. Default, none, restricts access to only the known HTTP methods given above.
conn-pool—(http only). Set connection pooling (allows many HTTP requests to multiplex over a single TCP connection to the origin) options:
max-arp-entry—Set the maximum number of ARP entries in the ARP Cache Table
origin—Set connection pooling to origin options:
disable and enable—Either enable (default) or disable connection pooling to the origin server.
max-conn—Optionally, set a maximum number of connections that can be opened to the origin server concurrently. Default is 256; maximum allowed is 2048.
timeout—Optionally, set a timeout for a single connection in the connection pool; maximum allowed is 86,4000 seconds (24 hours), default is 300 seconds. Note that this is separate from network connection idle timeout.
file-type to content-type match—(http only) Associate certain file-types (e.g. HTML, FLV, MP4, MOV) with certain content-types (e.g. text/html, video/x-flv, video/mp4, video/quicktime) to be set in the HTTP header. When HTTP is used for access to origin, this command is needed only if a Content-Type header is not returned by the origin server; this has no effect if the origin server returns a Content-Type header. Repeat the command as needed to continue associating file types with content types. Use no to delete a specified entry.
interface—Specifiy the set of interfaces on which the media delivery protocol listens for incoming requests. If not specified, Media Flow Controller listens on ALL interfaces (default); if specified, Media Flow Controller listens ONLY on those specified. You can specify a list of space-separated interfaces such as eth2 eth3 eth4 eth5 or eth10 eth11 eth12 eth13 eth20 eth21 eth22, and so on. Up to 10 can be specified. Use no and specify the configured interface(s) to reset default (all) or remove a specified interface.
listen port—Set the TCP port used to listen for requests; multiple entries (up to 64) are allowed. Default port for HTTP is 80; for RTSP is 554. Use no to reset default.
req-length maximum—(http only) Set the maximum parse size for incoming requests (request line + headers) in bytes; requests larger than this size are rejected. Default is 16384 bytes; maximum allowed value is 32768.
trace—(http only) Enable the Media Flow Controller HTTP delivery trace; see "“Testing a Specific Transaction” on page 152" for details on using the trace utility. Use no to disable.
Note! If you change any delivery protocol options, you must run the service command for the delivery service: service restart mod-delivery.
show delivery protocol [http | rtsp]
Displays delivery protocol settings.

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