| View previous topic :: View next topic |
| Author |
Message |
Anonymous Guest
|
Posted: Thu Nov 03, 2005 12:08 am Post subject: Connecting to an advanced mount with an Ices failback. |
|
|
I am running IceCast 2.3.0 and Ices v0.4
I successfully have my Ices running and mounted as /ices
in my Icecast configuration file, I have an advanced mount defined as follows :
| Code: |
<mount>
<mount-name>/radio</mount-name>
<username>alpha</username>
<password>beta</password>
<max-listeners>1000</max-listeners>
<dump-file>/tmp/dump-radio.m3u</dump-file>
<burst-size>65536</burst-size>
<fallback-mount>/ices</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<hidden>0</hidden>
<no-yp>1</no-yp>
</mount>
|
The mount is successfully created when Icecast is initialized... and immediately fails back to the /ices mount.
I don't seem to be able to connect to the /radio mount with any type of broadcasting client though. I am attempting to use JetCast at the moment because it works great creating other mounts. I tried using the "beta" password specified in the <mount> tags, and also the <source-password> which is what I normally use with JetCast to create a mount. It feels like maybe in order to control the advanced mount I need to be specifying a username somewhere, but JetCast doesn't seem to have a field anywhere to specify that.
The goal here is to have a permanently running mount that runs off the failback /ices mount unless a DJ connects to and takes control. Is there maybe a better way to do this? |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Thu Nov 03, 2005 12:37 am Post subject: |
|
|
Does jetcast allow for you to state the username for the mountpoint, if not then it may very well be using the username "source" not "alpha"
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Thu Nov 03, 2005 12:39 am Post subject: |
|
|
I just fixed it actually....
turns out that the <username> tag inside of <mount> is not a required field. Once I took it out, the mount reverted to the default username, which is "source", which is obviously what JetCast uses.
Somebody might want to tell the people at JetCast to add a "username" field to their External Server config options, otherwise you can't use it to connect to a private mount. |
|
| Back to top |
|
 |
|