[Icecast] Config and other areas of struggle

Robert Jeffares jeffares.robert at gmail.com
Fri Jul 22 21:31:15 UTC 2016

Hi Alan,

Icecast set up is almost too easy:
heres the checklist

Give your server a fixed IP In Windows this is easy and there are plenty 
of help files.
Make sure you get the DNS number right. Various modem routers default to or or variants of 10.x.x.x

in a console [ black screen with c:> under accessories] type ipconfig 
<enter>  to see what you have now.

On your router set up port fowarding so the outside world connects to 
your router on x.x.x.x and port 8000 is fowarded to the fixed IP of your 

You can get in to your router by typing [or whatever it is] 
in a browser and the username admin password admin for 99% of the time.

Configure icecast.xml as below; this is from a linux server but 
basically it's the same

     <!-- location and admin are two arbitrary strings that are e.g. visible
          on the server info page of the icecast web interface
          (server_version.xsl). -->
     <admin>youremail at somewhere/admin>

         <clients>100</clients>			<--- note increases on defaults
         <!-- If enabled, this will provide a burst of data when a client
              first connects, thereby significantly reducing the startup
              time for listeners that do substantial buffering. However,
              it also significantly increases latency between the source
              client and listening client.  For low-latency setups, you
              might want to disable this. -->
         <!-- same as burst-on-connect, but this allows for being more
              specific on how much to burst. Most people won't need to
              change from the default 64k. Applies to all mountpoints  -->

         <!-- Sources log in with username 'source' -->
         <!-- Relays log in username 'relay' -->

         <!-- Admin logs in with the username given below -->

     <!-- set the mountpoint for a shoutcast source to use, the default if not
          specified is /stream but you can change it here if an alternative is
          wanted or an extension is required

     <!-- Uncomment this if you want directory listings -->

     <!-- This is the hostname other people will use to connect to your server.
     It affects mainly the urls generated by Icecast for playlists and yp
     listings. -->
     <hostname></hostname>					<-- this is where you put the server "name"

     <!-- You may have multiple <listener> elements -->
        <!-- <bind-address></bind-address> -->			<-- the <!-- and --> comment the line out
         <!-- <shoutcast-mount>/stream</shoutcast-mount> -->



     <!-- setting this makes all relays on-demand unless overridden, this is
          useful for master relays which do not have <relay> definitions here.
          The default is 0 -->



     <!-- Only define a <mount> section if you want to use advanced options,
          like alternative usernames or passwords -->

<!--    <mount>
         <mount-name>/thewirelessstation.mp3</mount-name>			<-- ignore this and leave defaults. I have this set up for something.



     <stream-name>The Wireless Station 1530kHz Hawkes Bay</stream-name>
     <stream-description>The best music you ever will hear</stream-description>



		<!-- basedir is only used if chroot is enabled -->

         <!-- Note that if <chroot> is turned on below, these paths must both
              be relative to the new root, not the original root -->
         <!-- <pidfile>/usr/share/icecast2/icecast.pid</pidfile> -->

         <!-- Aliases: treat requests for 'source' path as being for 'dest' path
              May be made specific to a port or bound address using the "port"
              and "bind-address" attributes.
         <alias source="/foo" destination="/bar"/>
         <!-- Aliases: can also be used for simple redirections as well,
              this example will redirect all requests for http://server:port/ to
              the status page
         <alias source="/" destination="/status.xsl"/>

         <!-- <playlistlog>playlist.log</playlistlog> -->
       	<loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
       	<logsize>10000</logsize> <!-- Max size of a logfile -->
         <!-- If logarchive is enabled (1), then when logsize is reached
              the logfile will be moved to [error|access|playlist].log.DATESTAMP,
              otherwise it will be moved to [error|access|playlist].log.old.
              Default is non-archive mode (i.e. overwrite)
         <!-- <logarchive>1</logarchive> -->

     <security>						<-- not sure what happens in windows but the default will work

This should help


*Communication Consultants*
64 Warner Park Avenue


Auckland 0604

09 8176358


06 650 6087
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/174f643e/attachment-0001.html>

More information about the Icecast mailing list