Hello,

We have a client (single customer) who is on a VPS and wants to use "shoutcast" to stream audio and video.

Now, I must admit that I'ma newbie to this stuff and my tech guys are pretty green, too. :)

Thus, I'm looking for info so I can wrap my mind around how this all works. :peace:

[1] The customer wants to have multiple "stations". My understanding is that we should install (as root) the shoutcast binaries in a single "common" location like what we do with Perl. (/local/bin/shoutcast which then points to the current shoutcast version directory, etc..) World user would have read access to these files. Only root will have write.

Is this correct?

[2] Using the above, each server would be "started" by having the customer doing something like this:

- log into SSH using their own user.
- create their shoutcast server config file (sc_serv.conf)
- start their shoutcast server, using their ssh user, like this: /local/bin/shoutcast/sc_serv ./sc_serv1.conf

(So the server runs as the user that started the process, etc..)

Is this correct?

[3] They want to have multiple "streams", with different content. Can they do this with a single domain? My thinking is that they can use the same binary file, and just specify a different config file that uses a different port number.. and all will be ok.

Is this correct?

[4] Is there any kind of graphical (web based) control panel to manage the configuration file(s) for their shoutcast server(s)? This customer doesn't know anything about SSH, and so it will be difficult to teach them and hold their hand while they constantly fiddle with settings, etc.. It would be nice if there is a simple config file interface. I found this one (http://www.cast-control.net/) but I'd like to know if there's anything else (or better).

[5] We're using cpanel, so does anyone know if WHM/cpanel already includes shoutcast server traffic in the bandwidth reporting? If not, what do you recommend so the customer can easily track their usage? We don't want to get into a situation where they are using hundreds of gigs without their knowledge..

Thanks for any help. If you have any advice, please be sure to share.

mrzippy,

hi there -

ok - a couple of pointers before i answer your questions -

- Stream hosting is bandwidth intensive - how much bandwidth have you got on that VPS package ?

a) Multiple streams are not a problem at all. Each stream actually utilises 2 ports on your server. You could theoretically host 100s of streams subject to the server's cpu capabilities and memory resources.

b) The shoutcast server software can be installed anywhere on your server. You must have shell access to the directory you install it in though.

c) Starting the server - yes - you can use shell to do that - once started - it should run in the background without problem (unless your server reboots or apache reboots).

d) Multiple streams - yes - use multiple config files.

e) re graphical GUI interface - don't knock cast-control. It's pretty damn good and it's free (IMHO)

f) Cast control logs bandwidth on each stream.

Again I would stress that you double check what bandwidth deals your VPS is on -
For example - ALL of our servers are on true unlimited bandwidth contracts as each one utilises well over 5000 Gb of bandwidth per month.

I don't know of many VPS services that give you that amount of bandwidth - so beware of this potential pitfall.

www.cast-control.com

scpanel is another good control panel for shoutcast and you can limit the bitrate and functionality of the server ie you dont want them subscribing to 100 slots at 64k and deciding to up things to 128k on you

be very careful and check on the shoutcast forums for bandwidth measurement tools so that you can guage the traffic