understanding "RelayServer" and "RelayPort"
 

Hi. I work for an FM radio station that is starting an online stream. Our studio has limited bandwidth (384 upload), so we are sending a stream to another location and we're using their bandwidth to serve the stream. We want to basically forward our stream onto their server. What do I need to modify in the ShoutCast program both here and at the server in order to make this happen? I know the answer has something to do with RelayServer and RelayPort, but the documentation is a little sketchy on the details.
Thanks.
E

You don't need the DNAS bit, you just put their IP and port into the DSP, make sure they've opened their ports at their end to let you in!

edit/ oops sorry, not sure about their end, someone else here will though. :)

RelayServer and RelayPort tell a DNAS to NOT listen for a source [on PortBase+1], but instead, connect to the DNAS on IP RelayHost, and port RelayPort as the source, and relay that DNAS.

YOU would use this if you wanted the remote DNAS to "get" [and relay] the stream from a local [to you] DNAS server.

This config would be done to the remote DNAS.

ok, so just to make sure i'm clear on this...

*I assume by IP RelayHost you mean "RelayServer" as described in the configuration documentation?

1. I will take our radio station's audio, and feed it to the line in on the soundcard to stream from the studio.

2. The Shoutcast DSP Plugin will encode the audio to an mp3stream. This computer will NOT have a Shoutcast server DNAS running, rather, I will specify in the DSP the IP/port of the server.

3. The server will "get" the stream through the internet from the (local to us, distant to the server) DSP plugin and broadcast via the provided server IP/port.

Yes:

Analog/FM --- SoundCard -- WinAMP/DSP ---//---- Remote DNAS.

No relay involved at all.

FYI: with a [local] relay:

Analog/FM --- SoundCard -- WinAMP/DSP --- Local DNAS ---//---- Remote DNAS Relay.

in this case, as i am behind a firewall, am i going to have to punch a port hole in my router in order for the stream to get out to the server?

NO -- you only have to configure port forwarding for remotely-sourced inbound connection attempts.

You can always go OUTbound.

awesome, this is a piece of cake! thanks so much for your help.