I will also look into the possibility of accepting icecast source's on the src port, this would require that you use the src port in the icecast sourcing tool instead. I can't guarantee this one to happen soon because it may require more work then I wish to add at this time but I will guarantee that ...

the issue is that an icecast source connects to the serv port always rather then the src Port. It's a difference between the two protocals, the description of srcIP in the config is a bit more tied to the shoutcast specification. Under Icecast2 there is no seperate src port. Under your configuration ...

well setting ServIP to localhost would make it unavailable to any outside connections. Are you running Icecast or SHOUTcast on the same machine? If so what are their relay config settings?

no you would just use SourceIP in this case assigning a unique IP to each mount.

yea you have two SourceIsDefault's specified steamcast only allows one.

If you want both mounts to list you will need to get a second IP for your server.

"quote: If you feel there is a market for this then let me know" Other thing It came to my mind that shoutcast team didnt developed is a way to block the status page.

I mean you can leave the menu of the top: status, listen, admin, about. But hidding the source and listeners is requested a lot by ...

One of my original goals for this application was to provide a api to steamcast that could allow realtime control over steamcast from an external system for just this purpose. It is definately a feature on the development list.

if a user is setup under a source user they will not be able to modify any of the parameters of their mount point. I have considered an extra option in the config file for variable locking which will not allow certain variables to be modified from the admin panel. If you feel there is a market for ...

ah yea, shoutcast will only list on the shoutcast yp. Their server is not open to listing on other providers such as steamcast.

actually I would leave SrvIP set to ANY in this particular configuration.

yes

as far as clustering make sure that when you specify the relay that you do so with an ip and port, no http:// and no other characters.

ex: ServerRelay=127.0.0.1:8000

This will ensure the SHOUTcast YP understands this is what you need to cluster with. Use of any other characters confuses it.

As ...

the admin one will display all mounts regardless of state, you might want to use that one for any automated tools. For privacy reasons mounts not publically available are not displayed on the public xml sheet.

is this on the xml sheet in the admin panel or the public stats sheet?

yea hopefully I will have something new soon. Also I think it may be time to break out of the beta phase.