Icecast Streaming Media Server

m-dizzle · Joined: 09 Aug 2007 Posts: 18

Hi guys...

i am trying out SAM... looks very good.

I can get ogg working fine... but shoutcast will not connect.

I don't think i have configured the icecast properly to server a shoutcast stream.

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

your understanding is correct, although in 2.3.2 you can just define it as

<listen-socket>
<port>8001</port>
<shoutcast-mount>/stream</shoutcast-mount>
</listen-socket>

in 2.3.2, this will implicitly allocate port 8002 as well. Use netstat to verify whether the ports are being listened on and use a web browser to get the status page from port 8001. The usual cause for no connection is a firewall blocking the ports or a NAT box not forwarding ports.

karl.

m-dizzle · Joined: 09 Aug 2007 Posts: 18

Hi Karl,

thanks for the reply...

do i need the <shoutcast-mount>/live</shoutcast-mount> in 2.3.1 ?

in 2.3.1 which socket would i add this in...? THe one with the shoutcast-compat declaration...?

I am going to upgrade to 2.3.2 at some point... for now though... 2.3.1 is woking sweet... unless there are any security fixes that require me to upgrade.

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

shoutcast mount in 2.3.1 is a global setting, so only 1 shoutcast source client could connect to a single instance of icecast (along with the shoutcast compat setting in the second.listen-socket). In 2.3.2, the shoutcast mount setting is now possible in the listen-socket allowing for multiple source clients to connect at the same time (using different ports). The second explicit listen-socket in the xml in such cases is not required as it is required by the protocol.

What you had originally would work for 2.3.1 but I would advise you to upgrade as there are many fixes in 2.3.2.

karl.

m-dizzle · Joined: 09 Aug 2007 Posts: 18

Hi Karl,

thanks for the help so far...

when i try and connect to the shoutcast by typing http://myserver:8002/live i get an 'Error Syncing to stream' message in winamp

i have included the shoutcast-mount in the second listen socket statement for port 8002. is that correct?
I will have a play around

m-dizzle · Joined: 09 Aug 2007 Posts: 18

i am now able to connect the SAM SHoutcast encoder and it is encoding the mix to icecast...

the trouble now is that winamp gets the sync error...

so the issue with the encoder not being able to connect is now resolved

hTHanks!!!

m-dizzle · Joined: 09 Aug 2007 Posts: 18

Hi Karl,

really having trouble with this now.

I can see the encoder in SAM streaming to icecast fine.

My listener socket config is now:

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

First thing... your listen-sockets are confusing now. port 800 is ok. The question is now what do you want. Assuming 2.3.1 then you need two listen-socket for a shoutcast compatible source client, but sam can do shoutcast or icecast so you need clarification there. If you are supplying a mountpoint in sam then it's using an icecast protocol.

assuming 2.3.1, then port N needs to be defined like your port 8000, and port N+1 needs the shoutcast-compat set.

assuming 2.3.2, the above will work, but alternatively you can define a listen-socket like port 8000 but with a <shoutcast-mount> within it. That will _implicitly_ allocate the next port number (N+1) as shoutcast compatabile.

Second. sync error from winamp typically means that it is using the wrong decoder for the stream. The typical example is streaming in ogg but because the mountpoint does not end in .ogg (eg /live.ogg) then it uses another decoder like mp3 and fails.

karl.