| View previous topic :: View next topic |
| Author |
Message |
Anonymous Guest
|
Posted: Wed Sep 26, 2007 11:05 am Post subject: listen url streaming help |
|
|
Hi i am completely new at this i am trying to stream using simplecast and icecast server some podcasts i have created. The listen url i have set up doesn't work and when i put my ip as my local host it doesn't work.
My ip is 172.168.11.115 Not sure which to put in and what settings to change. I am using windows xp professional. Any help anyone could give me would be really appreciated.
Thanks
Tim
icecast>
<limits>
<clients>100</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>hackme</source-password>
<!-- Relays log in username 'relay' -->
<relay-password>hackme</relay-password>
<!-- Admin logs in with the username given below -->
<admin-user>admin</admin-user>
<admin-password>hackme</admin-password>
</authentication>
<!-- 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>
<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://www.oddsock.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>172.168.11.115/alhaurin</hostname>
<!-- You can use these two if you only want a single listener -->
<!--<port>8000</port> -->
<!--<bind-address>127.0.0.1</bind-address>-->
<!-- You may have multiple <listener> elements -->
<listen-socket>
<port>8000</port>
<!-- <bind-address>127.0.0.1</bind-address> -->
</listen-socket>
<!--
<listen-socket>
<port>8001</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>
<!-- 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>
-->
<paths>
<!-- basedir is only used if chroot is enabled -->
<basedir>./</basedir>
<!-- Note that if <chroot> is turned on below, these paths must both
be relative to the new root, not the original root -->
<logdir>./logs</logdir>
<webroot>./web</webroot>
<adminroot>./admin</adminroot>
<!-- <pidfile>./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>4</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> |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Wed Sep 26, 2007 1:33 pm Post subject: |
|
|
It's hard to say what could be wrong when the report is "doesn't work", it may be completely unrelated to icecast, like a configuration problem with a firewall. You have not said whether the status.xsl page can be retrieved.
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Wed Sep 26, 2007 2:03 pm Post subject: HI |
|
|
Hi sorry very new at this where do i get the status page
the icecast server works fine and simplecast says encoding so it should work but can't access it on the web or through itunes windows media etc |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Wed Sep 26, 2007 2:53 pm Post subject: hi |
|
|
Hi i may be incredibly thick here but do i need to upload the .xml file and is so where do i upload it too
thanks for all of our help
tim |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Wed Sep 26, 2007 3:22 pm Post subject: |
|
|
Your xml states that requests for / are translated into /status.xsl so just request http://ip:8000/ in your browser. You should also get use to looking in your icecast log files.
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Wed Sep 26, 2007 4:02 pm Post subject: Hi |
|
|
hi sorry i tried that in my browser and nothing is happening. I am sorry i am being a little slow on this i am a real beginner here.
I am running simplecast and icecast. It is all set up as best as i can tell. I do have a website that is seperate from this do i need to upload any .xml files or .xsl into any directories.
Icecast says the url is http://172.168.11.115:8000/live
I am running it at the moment but can't listen on the net for some reason.
Thanks
Tim |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Wed Sep 26, 2007 4:12 pm Post subject: |
|
|
if a TCP connection cannot be established then no uploads of xsl files will help. If the source client (simplecast) is streaming then fine, your error log file should show that up easily. I think in every case of failures of connection the problem has been down to firewall, incorrect port or incorrect bind-address. Seeing that your port is 8000 and bin-address is not defined then it has to be network related, maybe NAT not configured correctly or firewall blocking, talk to your network administrator.
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Wed Sep 26, 2007 4:29 pm Post subject: hi |
|
|
| hi thanks will try and find out i have opened the port on the firewall so it might be that i live in spain so it could be the isp |
|
| Back to top |
|
 |
|