2014-11-18 14:57:21 -05:00
<!DOCTYPE html>
< html lang = "en" >
< head >
< title > Icecast Docs Docs — Admin Interface< / title >
< meta charset = "utf-8" / >
< meta name = "viewport" content = "width=device-width, initial-scale=1.0" / >
< link rel = "stylesheet" type = "text/css" href = "assets/css/style.css" media = "screen, print" / >
< / head >
< body >
< div class = "header" >
< h1 > < a href = "#" title = "Home page" > Icecast< / a > < span > documentation< / span > < / h1 >
< / div >
< div class = "section" >
2014-12-31 12:33:36 -05:00
< h2 > Icecast 2.4.99.1 Docs — Admin Interface< / h2 >
2014-11-18 14:57:21 -05:00
< div class = "article" >
< h3 id = "overview" > Overview< / h3 >
< p > This section contains information about the admin interface of icecast. Through this interface the user can manipulate many server features. From it you can gather statistics, move listeners from mountpoint to mountpoint, disconnect connected sources, disconnect connected listeners, and many other activities. Each function is enumerated here as well as an example usage of the function.< / p >
< p > Each of these functions requires HTTP authentication via the appropriate username and password. For mount-specific functions, you may use either the < code > < admin-username> < / code > and < code > < admin-password> < / code > specified in the icecast config file, or the username and password specified for that mountpoint (if any). For general functions (not specific to a single mountpoint), you must use the admin username and password. It is also important to note that in all the examples 192.168.1.10 is used as the example host and 8000 is used as the example port for the icecast server.< / p >
< / div >
< div class = "article" >
< h3 id = "admin-functions-mount-specific" > Admin Functions (mount specific)< / h3 >
< p > All these admin functions are mount specific in that they only apply to a particular mountpoint
(as opposed to applying to the entire server). Each of these functions requires a mountpoint to
be specified as input.< / p >
< h4 id = "metadata-update" > Metadata Update< / h4 >
< p > This function provides the ability for either a source client or any external program to update
the metadata information for a particular mountpoint.< / p >
< p > Example:< br / >
< code > http://192.168.1.10:8000/admin/metadata?mount=/mystream& mode=updinfo& song=ACDC+Back+In+Black< / code > < / p >
< h4 id = "fallback-update" > Fallback Update< / h4 >
< p > This function provides the ability for either a source client or any external program to update the
“fallback mountpoint” for a particular mountpoint. Fallback mounts are those that are used in the even
of a source client disconnection. If a source client disconnects for some reason that all currently
connected clients are sent immediately to the fallback mountpoint.< / p >
< p > Example:< br / >
< code > http://192.168.1.10:8000/admin/fallbacks?mount=/mystream.ogg& fallback=/myfallback.ogg< / code > < / p >
< h4 id = "list-clients" > List Clients< / h4 >
< p > This function lists all the clients currently connected to a specific mountpoint. The results are sent
back in XML form.< / p >
< p > Example:< br / >
< code > http://192.168.1.10:8000/admin/listclients?mount=/mystream.ogg< / code > < / p >
< h4 id = "move-clients-listeners" > Move Clients (Listeners)< / h4 >
< p > This function provides the ability to migrate currently connected listeners from one mountpoint to another.
This function requires 2 mountpoints to be passed in: mount (the < em > from< / em > mountpoint) and destination
(the < em > to< / em > mountpoint). After processing this function all currently connected listeners on mount will
be connected to destination. Note that the destination mountpoint must exist and have a sounce client
already feeding it a stream.< / p >
< p > Example:
< code > http://192.168.1.10:8000/admin/moveclients?mount=/mystream.ogg& destination=/mynewstream.ogg< / code > < / p >
< h4 id = "kill-client-listener" > Kill Client (Listener)< / h4 >
< p > This function provides the ability to disconnect a specific listener of a currently connected mountpoint.
Listeners are identified by a unique id that can be retrieved by via the “List Clients” admin function.
This id must be passed in to the request via the variable < code > id< / code > . After processing this request, the listener will no longer be
connected to the mountpoint.< / p >
< p > Example:
< code > http://192.168.1.10:8000/admin/killclient?mount=/mystream.ogg& id=21< / code > < / p >
< h4 id = "kill-source" > Kill Source< / h4 >
< p > This function will provide the ability to disconnect a specific mountpoint from the server. The mountpoint
to be disconnected is specified via the variable < code > mount< / code > .< / p >
< p > Example:
< code > http://192.168.1.10:8000/admin/killsource?mount=/mystream.ogg< / code > < / p >
< / div >
< div class = "article" >
< h3 id = "admin-functions-general" > Admin Functions (general)< / h3 >
< h4 id = "stats" > Stats< / h4 >
< p > The stats function provides the ability to query the internal statistics kept by the Icecast server.
Almost all information about the internal workings of the server such as the mountpoints connected,
how many client requests have been served, how many listeners for each mountpoint, etc, are available
via this admin function.< br / >
Note that this admin function can also be invoked via the http://server:port/admin/stats.xml syntax,
however this syntax should not be used and will eventually become deprecated!< / p >
< p > Example:< br / >
< code > http://192.168.1.10:8000/admin/stats< / code > < / p >
< h4 id = "list-mounts" > List Mounts< / h4 >
< p > The list mounts function provides the ability to view all the currently connected mountpoints.< / p >
< p > Example:
< code > http://192.168.1.10:8000/admin/listmounts< / code > < / p >
< / div >
< div class = "article" >
< h3 id = "web-based-admin-interface" > Web-Based Admin Interface< / h3 >
< p > As an alternative to manually invoking these URLs, a web-based admin interface was developed. This
interface provides the same functions that were identified and described above but presents them in
a little nicer way. The web-based admin Interface to Icecast is shipped with Icecast provided in the
< code > admin< / code > directory and comes ready to use. All the user needs to do is set the path to this directory
in the config file via the < code > < adminroot> < / code > config variable.< br / >
The web-based admin interface is a series of XSLT files which are used to display all the XML obtained
via the URL admin interface. This can be changed and modified to suit the user’
XSLT and transformations from XML to HTML are required in order to make changes to these scripts. < / p >
< p > The main URL for the Web-Based Admin Interface is:< br / >
< code > http://192.168.1.10:8000/admin/stats.xsl< / code > < / p >
< p > From this URL all of the other admin functions can be exercised.
< strong > Modification of existing XSLT transforms in < code > /admin< / code > is allowed, but new files cannot be created here< / strong > .
Creation of new XSLT transforms as well as modification of existing transforms is allowed in < code > /web< / code > .
These work using the document returned by < code > /admin/stats.xml< / code > .< br / >
To see the XML document that is applied to each admin XSLT, just remove the < code > .xsl< / code > in your request
(i.e. < code > /admin/listclients< / code > ). You can then code your XSLT transform accordingly.< / p >
< / div >
< / div >
< div class = "footer" >
< p > Support icecast development at < a href = "http://icecast.org" > icecast.org< / a > < / p >
< / div >
< / body >
2014-12-31 12:33:36 -05:00
< / html >
