@@ -35,6 +35,9 @@ <h3 id="type-of-relays">Type of Relays</h3>
35
35
will also periodically check the master server to see if any new mountpoints have attached and if so will relay those
36
36
as well. </ p >
37
37
38
+ < p > This "master-slave" type relay has been extended to support aggregation so that multiple masters can be given
39
+ and the slave will "aggregate" all of the mountpoints for those master servers. </ p >
40
+
38
41
< p > The second type of relay is a “single-broadcast” relay. In this case, the slave server is configured with a
39
42
server IP, port and mount and only the mountpoint specified is relayed. In order to relay a broadcast stream on
40
43
a Shoutcast server, you must use the “single-broadcast” relay and specify a mountpoint of < code > /</ code > .</ p >
@@ -61,6 +64,36 @@ <h3 id="setting-up-a-master-slave-relay">Setting Up a Master-Slave Relay</h3>
61
64
62
65
</ div >
63
66
67
+ < div class ="article ">
68
+ < h3 id ="setting-up-a-master-slave-aggregating-relay "> Setting Up a Master-Slave Aggregating Relay</ h3 >
69
+ < p > In order to setup a relay of this type all servers (the one you wish to relay and the one doing the relaying)
70
+ need to be Icecast 2 servers. The following configuration snippet is used as an example:</ p >
71
+
72
+ < div class ="highlight "> < pre > < code class ="language-xml " data-lang ="xml "> < span class ="nt "> <master-update-interval></ span > 120< span class ="nt "> </master-update-interval></ span >
73
+ < span class ="nt "> <master></ span >
74
+ < span class ="nt "> <server></ span > 192.168.1.11< span class ="nt "> </server></ span >
75
+ < span class ="nt "> <port></ span > 8001< span class ="nt "> </port></ span >
76
+ < span class ="nt "> <namespace></ span > /upstream1< span class ="nt "> </namespace></ span >
77
+ < span class ="nt "> <password></ span > hackme< span class ="nt "> </password></ span >
78
+ < span class ="nt "> <on-demand></ span > 1< span class ="nt "> </on-demand></ span >
79
+ < span class ="nt "> </master></ span >
80
+ < span class ="nt "> <master></ span >
81
+ < span class ="nt "> <server></ span > 192.168.1.12< span class ="nt "> </server></ span >
82
+ < span class ="nt "> <port></ span > 8001< span class ="nt "> </port></ span >
83
+ < span class ="nt "> <password></ span > hackme< span class ="nt "> </password></ span >
84
+ < span class ="nt "> </master></ span >
85
+ </ code > </ pre > </ div >
86
+
87
+ < p > In this example, this configuration is setup in the server which will be doing the relaying (slave server).
88
+ The master servers in this case need not be configured (and actually they are unaware of the relaying being performed)
89
+ as relays. When the slave server is started, it will connect to each of the master servers located at 192.168.1.11:8001
90
+ and 192.168.1.12:8001 and will begin to relay all mountpoints connected to the master servers. Additionally,
91
+ every master-update-interval (120 seconds in this case) the slave server will poll the master servers to see if any new
92
+ mountpoints have connected, and if so, the slave server will relay those as well. Note that all mountpoints of the master
93
+ server at 192.168.1.11:8001 will have the namespace "/upstream1" prepended to it's mountpoints. </ p >
94
+
95
+ </ div >
96
+
64
97
< div class ="article ">
65
98
< h3 id ="setting-up-a-single-broadcast-relay "> Setting Up a Single-Broadcast Relay</ h3 >
66
99
< p > In this case, the master server need not be an Icecast 2 server. Supported master servers for a single-broadcast
0 commit comments