[Icecast] Push relay from nicecast with icecast2?

[Chuck Tellechea]

Darrel,

Thanks for the help. I'm presuming then that I've misunderstood what is 
meant by "pull" vs. "push".

I understood, I guess erroneously, that the context of 'push' relaying 
was from the perspective of the icecast2 receiving a 'pushed' stream. I 
believe now that I have this backwards, and that the context is from 
the part of icecast2 not being set up to 'push'  a stream (broadcast as 
per nicecast or shoutcast client tools) to another icecast2 server (or 
icecast1, shoutcast, or whatever).

If such is the case, then I am still confused by the context of the 
"Specific Mountpoint Relay" paradigm and how to setup a mountpoint for 
the 'listening' icecast2 server at the datacenter which would be 
receiving a 'pushed' stream from the nicecast client/server at my 
customer's studio.

Or do I is the "Specific Mountpoint Relay" paradigm *not* applicable 
here, and what I need to do is merely to setup a <listen-socket> 
instance with the <shoutcast-compat> set to true, and setup Nicecast to 
send as if to a shoutcast server? Nicecast has a icecast2 option in its 
remote server configuration, however, it requires one to specify an 
mountpoint; and if such is the case, I'm back to using the "Specific 
Mountpoint Relay" paradigm, aren't I?

In any case, I'm going to try a few different ways while instrumenting 
the connections with tcpdump and see if I can figure this out. I'll be 
working on this the rest of the day today. Thanks again :)

On Mar 23, 2005, at 1:27 PM, Darrell Dominey wrote:

> i don't think anyone has really answered his question yet, so i'll
> give it a shot.
>
> from what you have said i think you are misunderstanding something.
> the customer that is running nicecast does not need any kind of server
> on his machine, all he would have to do is tell nicecast to stream to
> your server
>
> as for the archived content, all thet would be required is to run ices
> on the server machine to do that streming of static content
>
>
> On Wed, 23 Mar 2005 16:28:24 +0000, Dan Stowell <danstowell at gmail.com> 
> wrote:
>> On Thu, 24 Mar 2005 01:26:59 +1000, Geoff Shang 
>> <geoff at hitsandpieces.net> wrote:
>>> Chuck Tellechea wrote:
>>>
>>>> What I'm thinking of doing now, is to running an instance of either 
>>>> icecast1
>>>> or shoutcast, on the datacenter server, to receive the 'pushed' 
>>>> broadcast
>>>> from the Nicecast running on the G5 at my customer's office/studio.
>>>> Additionally running an instance of icecast2, on the same 
>>>> datacenter server
>>>> (and on another port(s)) to stream the archived mp3 content.
>>>
>>> It is true that Icecast2 can't do push relaying, but I don't 
>>> understand why
>>> you need it.  If Nicecast is going to be pushing the content to you, 
>>> what's
>>> the problem?  Maybe *I'm* missing something.
>>
>> Nicecast uses Icecast to do its broadcasting, so it can't do anything
>> that Icecast can't do. So I don't really understand either.
>>
>> Could you solve the DHCP problem by getting your customer set up with
>> dynDNS? Wouldn't that immediately solve the problem, meaning that
>> people could listen directly to the stream coming from his box?
>>
>> Dan
>>
>> --
>> http://www.mcld.co.uk
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
--
"Living is easy with eyes closed;
         misunderstanding all you see...."
                 John Lennon

         Chuck Tellechea