<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.30.3">
</HEAD>
<BODY>
<FONT COLOR="#000080">Ah, ok Satz, I did not know that's right :(</FONT><BR>
<BR>
<FONT COLOR="#000080">Now I am trying:</FONT><BR>
<BR>
<FONT COLOR="#000000"><server>194.232.200.156</server></FONT><BR>
<FONT COLOR="#000000"><port>8000</port></FONT><BR>
<FONT COLOR="#000000"><mount>/listen.pls</mount></FONT><BR>
<FONT COLOR="#000000"><local-mount>/oe3.mp3</local-mount></FONT><BR>
<BR>
<FONT COLOR="#000080">... but I do not get the mountpoint "oe3.mp3" in <A HREF="http://186.56.96.133:8200">http://186.56.96.133:8200</A></FONT><BR>
<FONT COLOR="#000080">May be something related with the extension "pls" ?.</FONT><BR>
<BR>
El mié, 20-02-2013 a las 19:30 +0100, Satz Klauer escribió: <BR>
<BLOCKQUOTE TYPE=CITE>
    Jose,<BR>
    <BR>
    <BR>
    <BR>
    I'm already using "/" as mountpoint since the streams is sent from this URL directly (with no additional name appended to it)<BR>
    <BR>
    On Wed, Feb 20, 2013 at 7:22 PM, José Luis Artuch <<A HREF="mailto:artuch@speedy.com.ar">artuch@speedy.com.ar</A>> wrote:<BR>
    <BLOCKQUOTE>
        <FONT COLOR="#000080">Satz,</FONT><BR>
        <BR>
        <FONT COLOR="#000080">At first you should define <mount>.</FONT><BR>
        <BR>
        <FONT COLOR="#000080"><mount> is the mountpoint to be relayed, located on remote server (master server).</FONT><BR>
        <FONT COLOR="#000080"><local-mount> is the previous mountpoint, but now, located on local server (relay server).</FONT><BR>
        <BR>
        <FONT COLOR="#000080">Trying "wget <A HREF="http://mp3stream7.apasf.apa.at">http://mp3stream7.apasf.apa.at</A>" I get "<A HREF="http://194.232.200.156:8000/listen.pls">http://194.232.200.156:8000/listen.pls</A>" and this works ok.</FONT><BR>
        <BR>
        <FONT COLOR="#000080">Otherwise, each mountpoint relayed is considered as a source in the relay server, so, you must configure correctly <sources> in the "icecast.xml" file in the relay server.</FONT><BR>
        <BR>
        El mié, 20-02-2013 a las 18:08 +0100, Satz Klauer escribió: <BR>
        <BLOCKQUOTE TYPE=CITE>
            The relaying-configuration seems to be straight-forward, unfortunately it does not work. That's my configuration:<BR>
            <BR>
            <BR>
            <BR>
            <relays-on-demand>1</relays-on-demand><BR>
            <BR>
            <relay><BR>
            <server><A HREF="http://mp3stream7.apasf.apa.at">http://mp3stream7.apasf.apa.at</A></server><BR>
            <port>8000</port><BR>
            <mount>/</mount><BR>
            <local-mount>/oe3.mp3</local-mount><BR>
            <on-demand>1</on-demand><BR>
            <BR>
            <relay-shoutcast-metadata>0</relay-shoutcast-metadata><BR>
            </relay><BR>
            <BR>
            <BR>
            <BR>
            And that's what the error log says:<BR>
            <BR>
            <BR>
            [2013-02-20 17:56:19] INFO connection/get_ssl_certificate No SSL capability<BR>
            [2013-02-20 17:56:20] DBUG slave/_slave_thread checking master stream list<BR>
            [2013-02-20 17:56:20] DBUG slave/check_relay_stream Adding relay source at mountpoint "/oe3.mp3"<BR>
            [2013-02-20 17:56:21] DBUG slave/_slave_thread checking master stream list<BR>
            [2013-02-20 17:56:37] DBUG auth/add_listener_to_source max on /oe3.mp3 is -1 (cur 0)<BR>
            [2013-02-20 17:56:37] DBUG auth/add_listener_to_source kicking off on-demand relay<BR>
            [2013-02-20 17:56:37] DBUG auth/add_listener_to_source Added client to /oe3.mp3<BR>
            [2013-02-20 17:56:37] DBUG auth/add_authenticated_listener client authenticated, passed to source<BR>
            [2013-02-20 17:56:37] DBUG stats/modify_node_event update node clients (1)<BR>
            [2013-02-20 17:56:37] DBUG stats/modify_node_event update node connections (1)<BR>
            [2013-02-20 17:56:37] DBUG stats/modify_node_event update node client_connections (1)<BR>
            [2013-02-20 17:56:38] INFO slave/start_relay_stream Starting relayed source at mountpoint "/oe3.mp3"<BR>
            [2013-02-20 17:56:38] INFO slave/open_relay_connection connecting to <A HREF="http://mp3stream7.apasf.apa.at:8000">http://mp3stream7.apasf.apa.at:8000</A><BR>
            [2013-02-20 17:56:38] WARN slave/open_relay_connection Failed to connect to <A HREF="http://mp3stream7.apasf.apa.at:8000">http://mp3stream7.apasf.apa.at:8000</A><BR>
            [2013-02-20 17:56:38] DBUG source/source_clear_source clearing source "/oe3.mp3"<BR>
            <BR>
            <BR>
            <BR>
            When I'm doing a plain, simple <BR>
            <BR>
            <BR>
            wget <A HREF="http://mp3stream7.apasf.apa.at">http://mp3stream7.apasf.apa.at</A><BR>
            <BR>
            <BR>
            the stream is downloaded properly. Any Ideas what I'm doing wrong here?<BR>
            <BR>
            <BR>
            Thanks!<BR>
            <BR>
            <BR>
            <BR>
            On Wed, Feb 20, 2013 at 11:07 AM, Rücker Thomas <<A HREF="mailto:thomas.ruecker@tieto.com">thomas.ruecker@tieto.com</A>> wrote:<BR>
            <BLOCKQUOTE>
                Hi, <BR>
                <BR>
                <BR>
                On 20/02/13 11:38, Mike Thompsett wrote:<BR>
                <BR>
                <BLOCKQUOTE TYPE=CITE>
                    Hi All, <BR>
                    <BR>
                    <BR>
                    Will this also bounce new connections to the relay server once the master server is maxed out? <BR>
                </BLOCKQUOTE>
                <BR>
                <BR>
                So far we haven't done anything in this area. Also because I'd consider this to be outside of core icecast scope. (I won't oppose patches, though)<BR>
                The basic approach is round-robin DNS, which should give you an even distribution across servers.<BR>
                If that's not your intention, then you can use a simple http-redirect with some business logic behind that to account for distribution ratio or geo-ip distribution. I think I've seen such a script on git-hub even.<BR>
                <BR>
                Cheers<BR>
                <BR>
                <FONT COLOR="#888888">Thomas</FONT> <BR>
                <BR>
                <BR>
                <BLOCKQUOTE TYPE=CITE>
                    Regards, <BR>
                    Mike <BR>
                    <BR>
                    On 20 Feb 2013, at 07:53, Xabier Oneca  --  xOneca <<A HREF="mailto:xoneca+icecast@gmail.com">xoneca+icecast@gmail.com</A>> wrote:<BR>
                    <BR>
                    <BR>
                    <BLOCKQUOTE TYPE=CITE>
                        You have (little) documentation at<BR>
                        <A HREF="Http://icecast.org/docs/icecast-2.3.2/icecast2_config_file.html#relay">Http://icecast.org/docs/icecast-2.3.2/icecast2_config_file.html#relay</A><BR>
                        <BR>
                        Xabier Oneca_,,_<BR>
                        <BR>
                        El 20/02/2013 08:48, "Xabier Oneca -- xOneca" <<A HREF="mailto:xoneca%2Bicecast@gmail.com">xoneca+icecast@gmail.com</A>> escribió:<BR>
                        <BLOCKQUOTE>
                            You can set globally with the <relays-on-demand>1</relays-on-demand> in the global <icecast/> section, or you can configure per-relay with <on-demand>.<BR>
                            <BR>
                            You can find it in the sample config file. (Does not say much more.)<BR>
                            <BR>
                            Xabier Oneca_,,_<BR>
                            <BR>
                            El 20/02/2013 08:39, "Satz Klauer" <<A HREF="mailto:satzklauer@googlemail.com">satzklauer@googlemail.com</A>> escribió:<BR>
                            <BLOCKQUOTE>
                                Thanks, but which parameter influences this behaviour? I could not find anything in description of relaying parameters...<BR>
                                <BR>
                                On Wed, Feb 20, 2013 at 8:30 AM, Xabier Oneca -- xOneca <<A HREF="mailto:xoneca+icecast@gmail.com">xoneca+icecast@gmail.com</A>> wrote:<BR>
                                <BLOCKQUOTE>
                                    Hello Satz,<BR>
                                    <BR>
                                    You can configure that behavior from the config file.<BR>
                                    <BR>
                                    Xabier Oneca_,,_<BR>
                                    <BR>
                                    El 20/02/2013 07:58, "Satz Klauer" <<A HREF="mailto:satzklauer@googlemail.com">satzklauer@googlemail.com</A>> escribió: <BR>
                                    <BLOCKQUOTE>
                                        Hi, <BR>
                                        <BR>
                                        <BR>
                                        I found there is a possibility to let IceCast relay other, existing streams. But how is it working exactly when no clients are connected to my relay server: <BR>
                                        <BR>
                                        <BR>
                                        - is it going to stand-by and not streaming andy data from the source <BR>
                                        <BR>
                                        <BR>
                                        or <BR>
                                        <BR>
                                        <BR>
                                        - is it pulling data from the source all the time also when no client is available that could consume this stream? This would mean the relay would consume traffic and bandwidth also when nobody will use it... <BR>
                                        <BR>
                                        <BR>
                                        Thanks! <BR>
                                        <BR>
                                        <BR>
                                        <BR>
                                        <BR>
                                        _______________________________________________<BR>
                                        Icecast mailing list<BR>
                                        <A HREF="mailto:Icecast@xiph.org">Icecast@xiph.org</A><BR>
                                        <A HREF="http://lists.xiph.org/mailman/listinfo/icecast">http://lists.xiph.org/mailman/listinfo/icecast</A><BR>
                                        <BR>
                                    </BLOCKQUOTE>
                                </BLOCKQUOTE>
                                <BR>
                                <BR>
                                _______________________________________________<BR>
                                Icecast mailing list<BR>
                                <A HREF="mailto:Icecast@xiph.org">Icecast@xiph.org</A><BR>
                                <A HREF="http://lists.xiph.org/mailman/listinfo/icecast">http://lists.xiph.org/mailman/listinfo/icecast</A><BR>
                                <BR>
                            </BLOCKQUOTE>
                        </BLOCKQUOTE>
                        _______________________________________________<BR>
                        Icecast mailing list<BR>
                        <A HREF="mailto:Icecast@xiph.org">Icecast@xiph.org</A><BR>
                        <A HREF="http://lists.xiph.org/mailman/listinfo/icecast">http://lists.xiph.org/mailman/listinfo/icecast</A><BR>
                        <BR>
                    </BLOCKQUOTE>
                </BLOCKQUOTE>
                <BR>
                <BR>
                <BR>
                _______________________________________________<BR>
                Icecast mailing list<BR>
                <A HREF="mailto:Icecast@xiph.org">Icecast@xiph.org</A><BR>
                <A HREF="http://lists.xiph.org/mailman/listinfo/icecast">http://lists.xiph.org/mailman/listinfo/icecast</A><BR>
                <BR>
            </BLOCKQUOTE>
            <BR>
<PRE>
_______________________________________________
Icecast mailing list
<A HREF="mailto:Icecast@xiph.org">Icecast@xiph.org</A>
<A HREF="http://lists.xiph.org/mailman/listinfo/icecast">http://lists.xiph.org/mailman/listinfo/icecast</A>
</PRE>
        </BLOCKQUOTE>
        <BR>
        <BR>
    </BLOCKQUOTE>
    <BR>
</BLOCKQUOTE>
<BR>
<BR>
</BODY>
</HTML>