Icecast Streaming Media Server

[Anonymous]

How can I configure icecast to allow members to stream thier content WITHOUT knowing thier IP address?

I have several members and I know most of their ips change due to most are on dynamic ip addresses.

[karlH]

If it's a question of you relaying their content then use a DNS name which they can register and update.

karl.

[Guest]

Yes it is a question about relaying... but I would like to allow an open relay where I can set up a username and password and they can stream their content to our site.

I am looking into rtptools for I have seen online where others have used to to dynamically add streams to icecast.

Any suggestions? Hints?

[Anonymous]

how can I use rtp to reroute a stream from icecast or winamp to my icecast server?

[karlH]

[Anonymous]

Sounds like we are on the same page.

Yes I would be the icecast server and they have their stream pointed to my location for distribution.

I would not know where they will be exactly for they go to various areas to send the content, so I would like for it to be set up to where they have to use a password and username to authenticate. Once authenticated, then our icecast server will relay their show/movie/music stream.


The problem is I don't know what IP they will be using, nor will they want to install dynamic dns software.

so an example would be company XYZ is at location A and they authenticate and we relay the stream so that everyone can view it at http://our_company.com/XYZ

But say tomorrow they go to Location B then they should still be able to login and their stream would be viewable at http://our_company.com/XYZ

Users should not have to authenticate to view the stream though, just company XYZ to start the stream.

[karlH]

What you are talking about is not a relay, it's just a source client which supplies a mountpoint of /XYZ. They do the connection, supply the username and password as defined in the <mount> for /XYZ in your icecast xml file

They just need the appropriate source client, which one depends on there requirements, ie format to produce, source material etc.

karl.

[Anonymous]

well the twist to all this and I think I have confused the issue... is I want to have the mount points established on my servers.

So company XYZ when they go from location to location can use something like VideoLan or equivalent to send their stream to us.

From thier login, icecast should be able to say user XXX is associated with mountpoint XYZ and their stream is incoming on port 8000 (whatever port is assigned to them)

This is what I am trying to achieve.

[karlH]

We don't restrict which port is for which user, the mountpoint is enough of a selection mechanism. Just state a <mount> for /XYZ which takes a certain username and password which the source client has to provide to be accepted, it doesn't matter which IP the user is coming from. If you are thinking of shoutcast-style source clients then you are more limited as they don't provide a mountpoint.

karl.

[Anonymous]

I was thinking of source clients like net meeting, videolan, rtp and such.

[karlH]

I was talking about the protocol they use, not the actual name of the source client.

karl.