Icecast Streaming Media Server Forum Index Icecast Streaming Media Server
Icecast is a Xiph Foundation Project
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

starting again
Goto page 1, 2  Next
 
Post new topic   Reply to topic    Icecast Streaming Media Server Forum Index -> Icecast Server
View previous topic :: View next topic  
Author Message
johnh100000



Joined: 14 Jul 2009
Posts: 20
Location: Newport UK

PostPosted: Thu Jul 16, 2009 9:13 am    Post subject: starting again Reply with quote

after trying without sucsess ther streamers Ive come back here. Before I install icecast2 again, could youguys confirm it WILL do what I want, which is:

Stream audio from say idjc, accross my network to be listed to by say windows media palyer?

if yes I will procead.
_________________
John "Hammie" Hamlin
http://tux.isa-geek.org
Back to top
View user's profile Send private message Send e-mail
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Thu Jul 16, 2009 11:15 am    Post subject: Reply with quote

There is no reason that it would not work. Obviously the player will need the plugins for ogg playback.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
johnh100000



Joined: 14 Jul 2009
Posts: 20
Location: Newport UK

PostPosted: Thu Jul 16, 2009 11:43 am    Post subject: Reply with quote

karlH wrote:
There is no reason that it would not work. Obviously the player will need the plugins for ogg playback.

karl.


ok following the destuctions I belive it to be runing.

Now how do I connect a player to it? and which one?
_________________
John "Hammie" Hamlin
http://tux.isa-geek.org
Back to top
View user's profile Send private message Send e-mail
johnh100000



Joined: 14 Jul 2009
Posts: 20
Location: Newport UK

PostPosted: Thu Jul 16, 2009 11:49 am    Post subject: Reply with quote

Oh yeah heres the link to howto I followed:

http://www.linux.ie/articles/streamingaudio.php
_________________
John "Hammie" Hamlin
http://tux.isa-geek.org
Back to top
View user's profile Send private message Send e-mail
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Thu Jul 16, 2009 12:03 pm    Post subject: Reply with quote

I'm sure Microsoft will give you help on using their application but check to see what shows in the browser. You have obviously not posted the IP, port or mountpoint that you have had to enter into the source client but those 3 items make up the url needed for the player. If you go to http://ip:port with your browser then you should see the status page

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
johnh100000



Joined: 14 Jul 2009
Posts: 20
Location: Newport UK

PostPosted: Thu Jul 16, 2009 12:30 pm    Post subject: Reply with quote

karlH wrote:
I'm sure Microsoft will give you help on using their application but check to see what shows in the browser. You have obviously not posted the IP, port or mountpoint that you have had to enter into the source client but those 3 items make up the url needed for the player. If you go to http://ip:port with your browser then you should see the status page

karl.


are Huston we have a problem. it don't connect.

Icecast---
<icecast>
<limits>
<clients>10</clients>
<sources>2</sources>
<threadpool>5</threadpool>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<!-- 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. -->
<burst-on-connect>1</burst-on-connect>
<!-- 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 -->
<burst-size>65535</burst-size>
</limits>

<authentication>
<!-- Sources log in with username 'source' -->
<source-password>xxxxx</source-password>
<!-- Relays log in username 'relay' -->
<relay-password>xxxxx/relay-password>

<!-- Admin logs in with the username given below -->
<admin-user>admin</admin-user>
<admin-password>xxxxx</admin-password>
</authentication>

<!-- 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
<shoutcast-mount>/live.nsv</shoutcast-mount>
-->

<!-- Uncomment this if you want directory listings -->
<!--
<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
</directory>
-->

<!-- 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>tux.isa-geek.org</hostname>

<!-- You may have multiple <listener> elements -->
<listen-socket>
<port>1935</port>
<!-- <bind-address>127.0.0.1</bind-address> -->
<!-- <shoutcast-mount>/stream</shoutcast-mount> -->
</listen-socket>
<!--
<listen-socket>
<port>8000</port>
</listen-socket>
-->

<!--<master-server>127.0.0.1</master-server>-->
<!--<master-server-port>8001</master-server-port>-->
<!--<master-update-interval>120</master-update-interval>-->
<!--<master-password>hackme</master-password>-->

<!-- 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 -->
<!--<relays-on-demand>1</relays-on-demand>-->

<!--
<relay>
<server>127.0.0.1</server>
<port>8001</port>
<mount>/example.ogg</mount>
<local-mount>/different.ogg</local-mount>
<on-demand>0</on-demand>

<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
</relay>
-->

<!-- Only define a <mount> section if you want to use advanced options,
like alternative usernames or passwords
<mount>
<mount-name>/example-complex.ogg</mount-name>

<username>othersource</username>
<password>hackmemore</password>

<max-listeners>1</max-listeners>
<dump-file>/tmp/dump-example1.ogg</dump-file>
<burst-size>65536</burst-size>
<fallback-mount>/example2.ogg</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<intro>/example_intro.ogg</intro>
<hidden>1</hidden>
<no-yp>1</no-yp>
<authentication type="htpasswd">
<option name="filename" value="myauth"/>
<option name="allow_duplicate_users" value="0"/>
</authentication>
<on-connect>/home/icecast/bin/stream-start</on-connect>
<on-disconnect>/home/icecast/bin/stream-stop</on-disconnect>
</mount>

<mount>
<mount-name>/auth_example.ogg</mount-name>
<authentication type="url">
<option name="mount_add" value="http://myauthserver.net/notify_mount.php"/>
<option name="mount_remove" value="http://myauthserver.net/notify_mount.php"/>
<option name="listener_add" value="http://myauthserver.net/notify_listener.php"/>
<option name="listener_remove" value="http://myauthserver.net/notify_listener.php"/>
</authentication>
</mount>

-->

<fileserve>1</fileserve>

<paths>
<!-- basedir is only used if chroot is enabled -->
<basedir>/usr/share/icecast2</basedir>

<!-- Note that if <chroot> is turned on below, these paths must both
be relative to the new root, not the original root -->
<logdir>/var/log/icecast2</logdir>
<webroot>/usr/share/icecast2/web</webroot>
<adminroot>/usr/share/icecast2/admin</adminroot>
<!-- <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" dest="/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="/" dest="/status.xsl"/>
</paths>

<logging>
<accesslog>access.log</accesslog>
<errorlog>error.log</errorlog>
<!-- <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> -->
</logging>

<security>
<chroot>0</chroot>
<!--
<changeowner>
<user>nobody</user>
<group>nogroup</group>
</changeowner>
-->
</security>
</icecast>


Ices---
<?xml version="1.0"?>
<ices>

<!-- run in background -->
<background>0</background>
<!-- where logs go. -->
<logpath>/var/log/ices</logpath>
<logfile>ices.log</logfile>
<!-- size in kilobytes -->
<logsize>2048</logsize>
<!-- 1=error, 2=warn, 3=infoa ,4=debug -->
<loglevel>4</loglevel>
<!-- logfile is ignored if this is set to 1 -->
<consolelog>0</consolelog>

<!-- optional filename to write process id to -->
<pidfile>~/.ices/ices.pid</pidfile>

<stream>
<!-- metadata used for stream listing -->
<metadata>
<name>Example stream name</name>
<genre>Example genre</genre>
<description>A short description of your stream</description>
<url>http://icecast.isa-geek.org.org</url>
</metadata>

<!-- Input module.

This example uses the 'oss' module. It takes input from the
OSS audio device (e.g. line-in), and processes it for live
encoding. -->
<input>
<module>alsa</module>
<param name="rate">44100</param>
<param name="channels">2</param>
<param name="device">hw:0,0</param>
<!-- Read metadata (from stdin by default, or -->
<!-- filename defined below (if the latter, only on SIGUSR1) -->
<param name="metadata">1</param>
<param name="metadatafilename">test</param>
</input>

<!-- Stream instance.

You may have one or more instances here. This allows you to
send the same input data to one or more servers (or to different
mountpoints on the same server). Each of them can have different
parameters. This is primarily useful for a) relaying to multiple
independent servers, and b) encoding/reencoding to multiple
bitrates.

If one instance fails (for example, the associated server goes
down, etc), the others will continue to function correctly.
This example defines a single instance doing live encoding at
low bitrate. -->

<instance>
<!-- Server details.

You define hostname and port for the server here, along
with the source password and mountpoint. -->

<hostname>tux.isa-geek.org</hostname>
<port>1935</port>
<password>xxxxxxx</password>
<mount>/example1.ogg</mount>
<yp>1</yp> <!-- allow stream to be advertised on YP, default 0 -->

<!-- Live encoding/reencoding:

channels and samplerate currently MUST match the channels
and samplerate given in the parameters to the oss input
module above or the remsaple/downmix section below. -->

<encode>
<quality>0</quality>
<samplerate>22050</samplerate>
<channels>2</channels>
</encode>

<!-- stereo->mono downmixing, enabled by setting this to 1 -->
<downmix>1</downmix>

<!-- resampling.

Set to the frequency (in Hz) you wish to resample to, -->

<resample>
<in-rate>44100</in-rate>
<out-rate>22050</out-rate>
</resample>
</instance>

</stream>
</ices>
_________________
John "Hammie" Hamlin
http://tux.isa-geek.org
Back to top
View user's profile Send private message Send e-mail
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Thu Jul 16, 2009 3:29 pm    Post subject: Reply with quote

A connect failure would indicate a firewall blocking access or a route failure. you can try http://tux.isa-geek.org:1935 in browser on the machine running the source client to check that. If a browser can connect then a source client can.

I can see that you are asking ices to downmix a stereo stream but have then asked to encode 2 channels. I would suggest you make your mind up, do you want 2 channels or 1.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
johnh100000



Joined: 14 Jul 2009
Posts: 20
Location: Newport UK

PostPosted: Thu Jul 16, 2009 3:42 pm    Post subject: Reply with quote

karlH wrote:
A connect failure would indicate a firewall blocking access or a route failure. you can try http://tux.isa-geek.org:1935 in browser on the machine running the source client to check that. If a browser can connect then a source client can.

I can see that you are asking ices to downmix a stereo stream but have then asked to encode 2 channels. I would suggest you make your mind up, do you want 2 channels or 1.

karl.


I did? I thought it said it was down mixing.

Any how got a new icecast2 startup script, without them they directory yp things. here we go.

once its started and working I'll be happier
_________________
John "Hammie" Hamlin
http://tux.isa-geek.org
Back to top
View user's profile Send private message Send e-mail
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Thu Jul 16, 2009 3:57 pm    Post subject: Reply with quote

downmix is enabled, but you have also specified <encode><channels>2</channels> which means 2 channels not 1

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
johnh100000



Joined: 14 Jul 2009
Posts: 20
Location: Newport UK

PostPosted: Thu Jul 16, 2009 5:38 pm    Post subject: Reply with quote

Please somebody help. What am I doing wrong? Yes it starts
When testing I remove the firewall on ubuntu, and trusting the router.
And still I can't get to http://tux..org:8000
I've opened the ports on the router.

When trying to use wowza yesterday, that responed. So it must be the configs.

I am getting close to giving up with this.


<icecast>
<limits>
<clients>10</clients>
<sources>5</sources>
<threadpool>5</threadpool>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<!-- 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. -->
<burst-on-connect>1</burst-on-connect>
<!-- 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 -->
<burst-size>65535</burst-size>
</limits>

<authentication>
<!-- Sources log in with username 'source' -->
<source-password>xxxxx</source-password>
<!-- Relays log in username 'relay' -->
<relay-password>xxxxxx</relay-password>

<!-- Admin logs in with the username given below -->
<admin-user>admin</admin-user>
<admin-password>xxxxx</admin-password>
</authentication>

<!-- 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
<shoutcast-mount>/live.nsv</shoutcast-mount>
-->

<!-- Uncomment this if you want directory listings -->
<!--
<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
</directory>
-->

<!-- 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>tux.isa-geek.org</hostname>

<!-- You may have multiple <listener> elements -->
<listen-socket>
<port>8000</port>
<bind-address>tux.isa-geek.org</bind-address>
<!-- <shoutcast-mount>/stream</shoutcast-mount> -->
</listen-socket>
<!--
<listen-socket>
<port>8000</port>
</listen-socket>
-->

<master-server>127.0.0.1</master-server>
<master-server-port>8001</master-server-port>
<master-update-interval>120</master-update-interval>
<master-password>viegas</master-password>

<!-- 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 -->
<relays-on-demand>0</relays-on-demand>

<!--
<relay>
<server>127.0.0.1</server>
<port>8001</port>
<mount>/tmp</mount>
<local-mount>/tmp</local-mount>
<on-demand>0</on-demand>

<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
</relay>
-->

<!-- Only define a <mount> section if you want to use advanced options,
like alternative usernames or passwords
<mount>
<mount-name>/example-complex.ogg</mount-name>

<username>othersource</username>
<password>hackmemore</password>

<max-listeners>1</max-listeners>
<dump-file>/tmp/dump-example1.ogg</dump-file>
<burst-size>65536</burst-size>
<fallback-mount>/example2.ogg</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<intro>/example_intro.ogg</intro>
<hidden>1</hidden>
<no-yp>1</no-yp>
<authentication type="htpasswd">
<option name="filename" value="myauth"/>
<option name="allow_duplicate_users" value="0"/>
</authentication>
<on-connect>/home/icecast/bin/stream-start</on-connect>
<on-disconnect>/home/icecast/bin/stream-stop</on-disconnect>
</mount>

<mount>
<mount-name>/auth_example.ogg</mount-name>
<authentication type="url">
<option name="mount_add" value="http://myauthserver.net/notify_mount.php"/>
<option name="mount_remove" value="http://myauthserver.net/notify_mount.php"/>
<option name="listener_add" value="http://myauthserver.net/notify_listener.php"/>
<option name="listener_remove" value="http://myauthserver.net/notify_listener.php"/>
</authentication>
</mount>

-->

<fileserve>1</fileserve>

<paths>
<!-- basedir is only used if chroot is enabled -->
<basedir>/usr/share/icecast2</basedir>

<!-- Note that if <chroot> is turned on below, these paths must both
be relative to the new root, not the original root -->
<logdir>/var/log/icecast2</logdir>
<webroot>/usr/share/icecast2/web</webroot>
<adminroot>/usr/share/icecast2/admin</adminroot>
<!-- <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" dest="/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="/" dest="/status.xsl"/>
</paths>

<logging>
<accesslog>/var/log/icecast2/access.log</accesslog>
<errorlog>/var/log/icecast2/error.log</errorlog>
<playlistlog>/var/log/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> -->
</logging>

<security>
<chroot>0</chroot>
<!--
<changeowner>
<user>nobody</user>
<group>nogroup</group>
</changeowner>
-->
</security>
</icecast>


<?xml version="1.0"?>
<ices>

<!-- run in background -->
<background>0</background>
<!-- where logs go. -->
<logpath>/var/log/ices</logpath>
<logfile>ices.log</logfile>
<!-- size in kilobytes -->
<logsize>2048</logsize>
<!-- 1=error, 2=warn, 3=infoa ,4=debug -->
<loglevel>4</loglevel>
<!-- logfile is ignored if this is set to 1 -->
<consolelog>0</consolelog>

<!-- optional filename to write process id to -->
<pidfile>~/.ices/ices.pid</pidfile>

<stream>
<!-- metadata used for stream listing -->
<metadata>
<name>Example stream name</name>
<genre>Example genre</genre>
<description>A short description of your stream</description>
<url>http://tux.isa-geek.org</url>
</metadata>

<!-- Input module.

This example uses the 'oss' module. It takes input from the
OSS audio device (e.g. line-in), and processes it for live
encoding. -->
<input>
<module>alsa</module>
<param name="rate">44100</param>
<param name="channels">2</param>
<param name="device">hw:0,0</param>
<!-- Read metadata (from stdin by default, or -->
<!-- filename defined below (if the latter, only on SIGUSR1) -->
<param name="metadata">1</param>
<param name="metadatafilename">test</param>
</input>

<!-- Stream instance.

You may have one or more instances here. This allows you to
send the same input data to one or more servers (or to different
mountpoints on the same server). Each of them can have different
parameters. This is primarily useful for a) relaying to multiple
independent servers, and b) encoding/reencoding to multiple
bitrates.

If one instance fails (for example, the associated server goes
down, etc), the others will continue to function correctly.
This example defines a single instance doing live encoding at
low bitrate. -->

<instance>
<!-- Server details.

You define hostname and port for the server here, along
with the source password and mountpoint. -->

<hostname>tux.isa-geek.org</hostname>
<port>8000</port>
<password>xxxxx</password>
<mount>/</mount>
<yp>0</yp> <!-- allow stream to be advertised on YP, default 0 -->

<!-- Live encoding/reencoding:

channels and samplerate currently MUST match the channels
and samplerate given in the parameters to the oss input
module above or the remsaple/downmix section below. -->

<encode>
<quality>0</quality>
<samplerate>22050</samplerate>
<channels>2</channels>
</encode>

<!-- stereo->mono downmixing, enabled by setting this to 1 -->
<downmix>0</downmix>

<!-- resampling.

Set to the frequency (in Hz) you wish to resample to, -->

<resample>
<in-rate>44100</in-rate>
<out-rate>22050</out-rate>
</resample>
</instance>

</stream>
</ices>
_________________
John "Hammie" Hamlin
http://tux.isa-geek.org
Back to top
View user's profile Send private message Send e-mail
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Thu Jul 16, 2009 7:05 pm    Post subject: Reply with quote

If you are asking whether we can see the status page at http://tux.isa-geek.org:8000 then no, I get a connection refused so either you have a firewall enabled or you are using a NAT and you haven't set port forwarding up.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
johnh100000



Joined: 14 Jul 2009
Posts: 20
Location: Newport UK

PostPosted: Thu Jul 16, 2009 8:06 pm    Post subject: Reply with quote

karlH wrote:
If you are asking whether we can see the status page at http://tux.isa-geek.org:8000 then no, I get a connection refused so either you have a firewall enabled or you are using a NAT and you haven't set port forwarding up.

karl.


thats what i can't understand. i've ports 8000 and 8001 open at the router end. as wowza worked it can't be running, running baddly, they ices and icecast2 show up with pids that are killable
_________________
John "Hammie" Hamlin
http://tux.isa-geek.org
Back to top
View user's profile Send private message Send e-mail
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Thu Jul 16, 2009 8:35 pm    Post subject: Reply with quote

I cannot say whether the tests you have run are of any use because so little information is given. If you have port 8000 forwarding to the correct internal IP then any external attempts to access port 8000 will show up on your internal network. The firewall or NAT box will not prevent icecast/ices from running.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
johnh100000



Joined: 14 Jul 2009
Posts: 20
Location: Newport UK

PostPosted: Thu Jul 16, 2009 9:11 pm    Post subject: Reply with quote

karlH wrote:
I cannot say whether the tests you have run are of any use because so little information is given. If you have port 8000 forwarding to the correct internal IP then any external attempts to access port 8000 will show up on your internal network. The firewall or NAT box will not prevent icecast/ices from running.

karl.


right after reinstalling again... and running the default config files it workls well I can get to it in a webbrowser!
_________________
John "Hammie" Hamlin
http://tux.isa-geek.org
Back to top
View user's profile Send private message Send e-mail
johnh100000



Joined: 14 Jul 2009
Posts: 20
Location: Newport UK

PostPosted: Fri Jul 17, 2009 3:25 am    Post subject: doing it local Reply with quote

now After hours, got it working. Sorry to mess you guys around.
I presume doing it locally requires me to shut 8000-8001 on the router?
_________________
John "Hammie" Hamlin
http://tux.isa-geek.org
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic   Reply to topic    Icecast Streaming Media Server Forum Index -> Icecast Server All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2002 phpBB Group
subRebel style by ktauber