Smart Freelancers

I would like to have Icecast configured to its full potential. I want to take advantage of the features that they have in Icecast. With all its bells and whistle I want to have Icecast fully functional with its security.

Part 1.

Lets say if you have five djs who are employed by online radio station and they would like to setup a way where <aduio1> would always broadcast if <variable> is not active.

Variable = <mount>/DJ-1</mount>
<mount>/DJ-2</mount>
<mount>/DJ-3</mount>
<mount>/DJ-4</mount>
<mount>/DJ-5</mount>

Audio1 = <mount>/MLRLIVE</mount>

Part 2.

For security purpose the online radio station would like to setup a password for each mount that’s being used to ensure the privacy of the user (dj 1 or 2) of that particular mount.

Part 3.

At some point the online radio station would like to set some kind of restrictions as to when the user (dj 1 or 2) can access the mount for broadcast use.

Part 4.
To be listen in the Icecast directory.

—————————————————-
Please if you have any ideas that would be good for the setup I’m looking for please voice your opinion.

P.S.

On this mission Karl would be your code warrior to help you break down some walls in this programing journey. But I must warm you he would not write the program but he would lead you the light. lol.

Notes:

you can set per-mount source password with the <username> and <password> but those are not time restricted. The only way you can do that at the moment is to use my branch work (http://www.icecast.pwp.blueyonder.co.uk/) and use url authentication, specifically the stream_auth option. With that you can pass any decisions on whether an incoming connection can be allowed to an external engine eg php, icecast could still reject it if say there is a stream already running.

Place bid