Icecast Streaming Media Server

[Y3K-Radio]

Have a choice to authenticate the source, a bit like listener auth.

In my scenario it would be very handy to be able to send over the source auth details to a php script like url authentication for listeners and then only let the DJ connecting to stream if its their turn and if for some reason we need to we can tell the script to return that the source isnt allowed to stream as we have disabled them (maybe due to abusive DJ/inactive DJ that wont leave), this will also make it easier to make sure we know which DJ is currently streaming.

Im not sure if this would be suitable solution for everyone, but the choice would be handy and im sure theres more than just me that would like to see this feature.

Thanks for listening,
Daniel @ Y3K-Radio

[karlH]

This should be possible to add, report this in bugs.xiph.org list so that it isn't forgotten about.

karl.

[Anonymous]

I'd like to second this request, but expand it a little.

It would be really great if Icecast could ask an SQL database (or even just an external application) for mount point details.

I have a system where various people sign up for mount points for specific periods of time, and right now that either involves me manually editing the icecast.xml file to add their settings, or having a rather convoluted php/perl script which edits icecast.xml for me... but that's just asking for trouble.

It would be really great if you could define a simple SQL database of all mount points and their related settings, which you could then change on the fly to add new customers (sources) without having to edit the config and HUP the server each time....

Also being able to record access and error logs seperately per mount point...

I guess what I'm after are features to enable virtualisation of an icecast server so a customer can be given their own mount point, and access to their own logs and stats without seeing anyone elses.

[Y3K-Daniel]

[karlH]

I haven't had many comments on this particular feature in my branch work yet so feel free to try it out. The authentication option is 'stream-auth' and it works in a similar way to listener urls, sends POST and checks for a returned header. Note that for shoutcast style streams, metadata updates also trigger this url but with an added setting on the POST.

karl.

[Y3K-Daniel]