When you using LiquidSoap and have autoDJ running when I live stream comes on it cuts out the autoDj and you then hear the live stream. How does one see the source information for the live stream?  I had an instance where we needed to kick the live stream but didn't see where I was actually kicking them.

You need to log-in to the administration panel of Centova/ShoutCast/IceCast
for Centova the default port is :2199 (exampl.yourURL.com:2199) you would boot the
you can also log-in the the server admin (yourURL.com:portNumber)  default log-in ID is admin when logged-in you have full control and will have a button to "kick" them off be sure you don't kick a listener. 

You need to log-in to the administration panel of Centova/ShoutCast/IceCast
for Centova the default port is :2199 (exampl.yourURL.com:2199) you would boot the
you can also log-in the the server admin (yourURL.com:portNumber)  default log-in ID is admin when logged-in you have full control and will have a button to "kick" them off be sure you don't kick a listener. 

Sadly. this is good if the live stream is on the actual broadcasting port. With AutoDJ using liquid Soap, the live stream broadcasts to a different port altogether. When that port is in use it overrides the autoDJ feature on the main port.

Let's say the port number is 8000, which is what listeners tune into. The DNAS page will show autoDJ broadcasting.  When a live stream connects, they connect to a different port number, let's call it 7986. When a live stream connects to 7986 it overrides the autodj on 8000 and broadcasts the live stream. Going to the DNAS page will show all the info for the live stream. However, going into the admin function, it will have the IP number of the server, not the live stream. I am in need of the live stream IP that needs to be kicked.

Got my answer from Alexiu in a ticket response - Thanks Alexiu.

Sadly, what I was asking about can't be done when using the autoDJ feature. Bummer. The best option is for the customer to log into centova and stop server then start it... and cross fingers that the DJ doesn't have auto-connect open

I have just tested this and find the DJ management is not optimally solved. Especially strange is that all the changes to the respective DJ accounts become effective only after manual stopping and re-starting the Auto DJ. It would be better and more logical if that were done in real time. Probably neither sctrans2 nor liquidsoap are currently prepared for this.

The unchanged IP of the Shoutcast source is of course logical because instead of the DJ now the Auto DJ connects to the Shoutcast source which then connects to the Shoutcast and of course retains the IP of the server. This is one of the special features of sctrans2 and liquidsoap.

The advantage is that you no longer have to disable the Auto DJ or kick the stream as with Shoutcast 1 before a liveshow. However, the downside is that the same stream title and source IP remains the same - a big problem for websites like ours, which used this information to display the program and the moderator information from the website.

However, possible and also desirable would be to see the IPs of the respective moderators at least on the Centova Cast DJ panel. So the developer could add, for example, a status lamp, IP display and kick feature in future releases for each moderator, so the software interface immediately displays as soon as someone is streaming. A query of the respective DJ port and the data sent should be no problem for good programmers and also be independent of the used Auto DJ software, so sctrans2 or liquidsoap. 

With the help of a new widget, it would then also be possible to query and display the stream title of every moderator.