From jordan at coolmic.net  Mon Aug  2 20:07:43 2021
From: jordan at coolmic.net (Jordan Erickson)
Date: Mon, 2 Aug 2021 13:07:43 -0700
Subject: [Icecast] Cool Mic (Icecast source client for Android) v1.3.0
 released
Message-ID: <6a322eb1-fb32-37c2-4b93-a2ce9eca5c3b@coolmic.net>

Hi Friends,

I'm happy to announce a new version of Cool Mic, an Icecast source 
client for Android with native Ogg/Opus and Ogg/Vorbis support.

This version?s big improvement is that you now have many more options 
for passing different kinds of metadata to Icecast. In addition to 
"Title" and "Artist", you now have the following available which is 
separated into "Track" and "Station" metadata configuration:

Track Metadata:

* Title
* Version
* Album
* Artist
* Performer
* Copyright
* License
* Organization
* Description
* Genre
* Location
* Contact
* (As well as option for custom metadata entries)


Station Metadata:

* Name
* Genre
* URL
* Description
* IRC

In addition there were plenty of general fixes and improvements.

A HUGE thanks to Philipp Schafft and Stephan Jauernick of L?wenfelsen UG 
(haftungsbeschr?nkt) - https://www.loewenfelsen.net/ - for their work on 
this release. Cool Mic is a 100% F/OSS project. We hope you enjoy it :)


Cheers,
Jordan Erickson
Cool Mic Project Manager
https://coolmic.net/


From madsend at morningside.edu  Wed Aug  4 17:20:18 2021
From: madsend at morningside.edu (Dave Madsen)
Date: Wed, 4 Aug 2021 12:20:18 -0500
Subject: [Icecast] Shoutcast?
Message-ID: <c7040782d8294044d2ae017627deaef6@mail.gmail.com>

The link that we?ve published for people to get our student-run radio
station is http://shoutcast.morningside.edu:8000/KMSC-Music.m3u, but the
people at Shoutcast say they have nothing to do with our stream, and that
we?re actually using icecast. Can someone please help me figure out exactly
HOW our streaming is working? I?m not a tech guy, and the stream has been
working here for many years?but nobody currently here knows how it was set
up. We?re using a really old PC that I think is functioning as a server?but
I?m not sure. That PC doesn?t seem very stable, so I?m looking for
alternatives/fixes/whatever!


Dave



*Dave Madsen*

Associate Professor & Dept. Head

Mass Communication

_____



*Morningside University*

1501 Morningside Ave. Sioux City, IA 51106

o: 712-274-5480 *|* m: 712-490-3327 *|  *morningside.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20210804/e7648d9f/attachment.htm>

From thomsonjack41 at gmail.com  Wed Aug  4 20:00:48 2021
From: thomsonjack41 at gmail.com (Jack Thomson)
Date: Wed, 4 Aug 2021 16:00:48 -0400
Subject: [Icecast] Shoutcast?
In-Reply-To: <c7040782d8294044d2ae017627deaef6@mail.gmail.com>
References: <c7040782d8294044d2ae017627deaef6@mail.gmail.com>
Message-ID: <CAK1v2=nOVoBkgimY=-587r9wr+S+QRAa8ShhrEHGFYzfCYfUPA@mail.gmail.com>

You're almost definitely selfhosting it through your university on the
server that you mentioned. Are y'all trying to keep that setup? There are
quite a few companies that will take care of all the particulars for you as
well (Stream Guys etc. there was a thread recently on the CBI list about
recommendations). Self-hosting is not particularly hard, but takes some
commitment to figure it out. Are your IT folks able to help out?

On Wed, Aug 4, 2021 at 3:49 PM Dave Madsen <madsend at morningside.edu> wrote:

> The link that we?ve published for people to get our student-run radio
> station is http://shoutcast.morningside.edu:8000/KMSC-Music.m3u, but the
> people at Shoutcast say they have nothing to do with our stream, and that
> we?re actually using icecast. Can someone please help me figure out exactly
> HOW our streaming is working? I?m not a tech guy, and the stream has been
> working here for many years?but nobody currently here knows how it was set
> up. We?re using a really old PC that I think is functioning as a server?but
> I?m not sure. That PC doesn?t seem very stable, so I?m looking for
> alternatives/fixes/whatever!
>
>
> Dave
>
>
>
> *Dave Madsen*
>
> Associate Professor & Dept. Head
>
> Mass Communication
>
> _____
>
>
>
> *Morningside University*
>
> 1501 Morningside Ave. Sioux City, IA 51106
>
> o: 712-274-5480 *|* m: 712-490-3327 *|  *morningside.edu
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20210804/718ce834/attachment.htm>

From mvandop at xs4all.nl  Wed Aug  4 20:13:48 2021
From: mvandop at xs4all.nl (Michel van Dop)
Date: Wed, 4 Aug 2021 22:13:48 +0200
Subject: [Icecast] Shoutcast?
In-Reply-To: <CAK1v2=nOVoBkgimY=-587r9wr+S+QRAa8ShhrEHGFYzfCYfUPA@mail.gmail.com>
References: <CAK1v2=nOVoBkgimY=-587r9wr+S+QRAa8ShhrEHGFYzfCYfUPA@mail.gmail.com>
Message-ID: <2534095A-3E50-4B5F-9592-17CFF663052A@xs4all.nl>

Hi,

Check here http://shoutcast.morningside.edu:8000/ and see your version on
http://shoutcast.morningside.edu:8000/server_version.xsl

Best regards, 
Michel

> Op 4 aug. 2021 om 22:01 heeft Jack Thomson <thomsonjack41 at gmail.com> het volgende geschreven:
> 
> ?
> You're almost definitely selfhosting it through your university on the server that you mentioned. Are y'all trying to keep that setup? There are quite a few companies that will take care of all the particulars for you as well (Stream Guys etc. there was a thread recently on the CBI list about recommendations). Self-hosting is not particularly hard, but takes some commitment to figure it out. Are your IT folks able to help out?
> 
>> On Wed, Aug 4, 2021 at 3:49 PM Dave Madsen <madsend at morningside.edu> wrote:
>> The link that we?ve published for people to get our student-run radio station is http://shoutcast.morningside.edu:8000/KMSC-Music.m3u, but the people at Shoutcast say they have nothing to do with our stream, and that we?re actually using icecast. Can someone please help me figure out exactly HOW our streaming is working? I?m not a tech guy, and the stream has been working here for many years?but nobody currently here knows how it was set up. We?re using a really old PC that I think is functioning as a server?but I?m not sure. That PC doesn?t seem very stable, so I?m looking for alternatives/fixes/whatever!
>> 
>> 
>> Dave
>> 
>>  
>> 
>> Dave Madsen
>> 
>> Associate Professor & Dept. Head
>> 
>> Mass Communication
>> 
>> _____
>> 
>>  
>> 
>> Morningside University
>> 
>> 1501 Morningside Ave. Sioux City, IA 51106
>> 
>> o: 712-274-5480 | m: 712-490-3327 |  morningside.edu
>> 
>>  
>> 
>> _______________________________________________
>> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20210804/52fc1715/attachment.htm>

From geoff at QuiteLikely.com  Wed Aug  4 21:02:18 2021
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Thu, 5 Aug 2021 00:02:18 +0300 (IDT)
Subject: [Icecast] Shoutcast?
In-Reply-To: <c7040782d8294044d2ae017627deaef6@mail.gmail.com>
References: <c7040782d8294044d2ae017627deaef6@mail.gmail.com>
Message-ID: <alpine.DEB.2.11.2108042332400.1870@debian.work>

On Wed, 4 Aug 2021, Dave Madsen wrote:

> The link that we?ve published for people to get our student-run radio
> station is http://shoutcast.morningside.edu:8000/KMSC-Music.m3u, but the
> people at Shoutcast say they have nothing to do with our stream, and that
> we?re actually using icecast.

You are.

Version          Icecast 2.3.2

http://shoutcast.morningside.edu:8000/server_version.xsl

At time of writing, there are two MP3 streams, one at 128 KBPS and one at 
24 KBPS.

> Can someone please help me figure out exactly
> HOW our streaming is working? I?m not a tech guy, and the stream has been
> working here for many years?but nobody currently here knows how it was set
> up. We?re using a really old PC that I think is functioning as a server?but
> I?m not sure. That PC doesn?t seem very stable, so I?m looking for
> alternatives/fixes/whatever!

As you can see, Icecast is very much set and forget a lot of the time. 
Yes, you could pay someone to do this, but if you've got the resources, 
you can probably update your setup and have it be stable for many more 
years.

The Icecast server software is very simple.  It accepts audio streams from 
one or more sources and sends those streams out to any listener clients 
that are connected to that server mountpoint.

This means that, in addition to Icecast, there is also some software 
somewhere which is encoding the MP3 audio of your station and sending it 
to Icecast.  It could be running on the same PC, with the audio coming 
into a soundcard on the machine and a piece of software taking that audio 
and encoding it.  It could also be happening on another PC, with it being 
sent over the network to your Icecast server.

Given that there are two streams at time of writing, both could be 
happening.

If I had access to the admin page, I might be able to tell you more, such 
as the IP address that the streams are coming from and possibly the 
software that's encoding it.  I'm sure whoever set it up would have been 
sensible enough to change the default username and password for the admin 
screen, and I'm not disrespectful enough to try and hack my way in.

Don't worry if you don't have the admin credentials, if you can access the 
PC itself then you can see the credentials for the admin screen in the 
Icecast config file, and may be able to figure out a lot without it.

We may be able to provide more specific help if you can tell us which 
operating system the computer is running.

If it turns out that the audio is being streamed in from other machines, 
replacing the server computer may well be just as simple as:

* Copy current config file from old system
* Install Icecast on new system
* Drop in old config on new system
* Point appropriate DNS to  the new machine and do any other necessary 
network/firewall changes
* Start Icecast

Of course, you'd want to do some testing along the way, but swapping out 
the server PC *could* be fairly straight-forward, depending on your setup.

Cheers,
Geoff.

From rlbart53 at gmail.com  Thu Aug 19 12:36:27 2021
From: rlbart53 at gmail.com (Richard Bartholomew)
Date: Thu, 19 Aug 2021 13:36:27 +0100
Subject: [Icecast] BUFFERING
Message-ID: <01a601d794f6$d4e852e0$7eb8f8a0$@gmail.com>

Hi,

 

I've just installed V2.4.4 onto Debian 10 with a primary and fallback
mountpoint with default settings and am experiencing the following.

 

Primary mountpoint is set up for live streaming from Station Playlist and
the fallback mountpoint plays an mp3 file.

 

If I connect to the stream using Winamp, I hear the mp3 file start playing
within two seconds.  If I then connect via Station Playlist (SPL), it takes
around 40 seconds for the mp3 file to stop and the live stream to be heard.
The same is true if I then disconnect the live stream and the fallback file
starts playing.

 

However, if I stop and start Winamp playing as soon as I connect via SPL or
disconnect so that the mp3 fallback file plays, I hear the appropriate
stream straightaway!

 

I assume that the delay is being caused due to buffering but is there a way
of reducing the buffering, please, so that if someone is listening via a
media player like Winamp, they hear the current stream quicker than the 40
seconds delay I'm presently experiencing?

 

Any advice would be greatly appreciated and I hope the above explanation was
clear enough.

 

Thanks for any help.

 

Richard Bartholomew

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20210819/258d6d23/attachment.htm>

From lr at pripple.de  Thu Aug 19 15:02:27 2021
From: lr at pripple.de (Lorenz Reichelt)
Date: Thu, 19 Aug 2021 17:02:27 +0200
Subject: [Icecast] BUFFERING
In-Reply-To: <01a601d794f6$d4e852e0$7eb8f8a0$@gmail.com>
References: <01a601d794f6$d4e852e0$7eb8f8a0$@gmail.com>
Message-ID: <5C344D98-D78A-4AAB-A79E-3D91BA29227E@pripple.de>

Hi, it seems to me this is the same problem I was experiencing in the beginning: When you specify a fallback file and a listener connects while the stream is inactive, Icecast will loop the fallback file and stream it at maximum speed (even multiple times). Then, the player?s buffer is filled with the fallback file and must play through it before reaching the live stream, which will accordingly be delayed until you reload. The solution is to provide a backup stream instead of a backup file by streaming the backup file to a different mount via ezstream or the like. Take care, Lorenz

> Am 19.08.2021 um 14:36 schrieb Richard Bartholomew <rlbart53 at gmail.com>:
> 
> Hi,
>  
> I've just installed V2.4.4 onto Debian 10 with a primary and fallback mountpoint with default settings and am experiencing the following.
>  
> Primary mountpoint is set up for live streaming from Station Playlist and the fallback mountpoint plays an mp3 file.
>  
> If I connect to the stream using Winamp, I hear the mp3 file start playing within two seconds.  If I then connect via Station Playlist (SPL), it takes around 40 seconds for the mp3 file to stop and the live stream to be heard.  The same is true if I then disconnect the live stream and the fallback file starts playing.
>  
> However, if I stop and start Winamp playing as soon as I connect via SPL or disconnect so that the mp3 fallback file plays, I hear the appropriate stream straightaway!
>  
> I assume that the delay is being caused due to buffering but is there a way of reducing the buffering, please, so that if someone is listening via a media player like Winamp, they hear the current stream quicker than the 40 seconds delay I'm presently experiencing?
>  
> Any advice would be greatly appreciated and I hope the above explanation was clear enough.
>  
> Thanks for any help.
>  
> Richard Bartholomew
>  
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org <mailto:Icecast at xiph.org>
> http://lists.xiph.org/mailman/listinfo/icecast <http://lists.xiph.org/mailman/listinfo/icecast>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20210819/4b8dcf5c/attachment.htm>

From ichkhikvishvili at bog.ge  Tue Aug 31 12:21:53 2021
From: ichkhikvishvili at bog.ge (Irakli Chkhikvishvili)
Date: Tue, 31 Aug 2021 12:21:53 +0000
Subject: [Icecast] Icecast relay specific mount point over SSL
Message-ID: <0547df456aaf46ea9d1841cdf6d3b85c@bog.ge>

Hello,
 I'm trying to pull a stream from specific mountpoint and everything is fine if I'm connecting to plain HTTP master:

<relay>
        <server>listen.radioking.com</server>
        <port>80</port>
        <mount>/radio/282820/stream/328621</mount>
        <local-mount>/radioking</local-mount>
        <on-demand>0</on-demand>
        <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
    </relay>


But it totally doesn't wrok if I'm connecting to SSL master

<relay>
        <server>listen.radioking.com</server>
        <port>443</port>
        <mount>/radio/282820/stream/328621</mount>
        <local-mount>/radioking</local-mount>
        <on-demand>0</on-demand>
        <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
    </relay>

Log file:

[2021-08-31  16:19:59] INFO main/main Icecast 2.4.4 server started
[2021-08-31  16:19:59] DBUG yp/yp_recheck_config Updating YP configuration
[2021-08-31  16:19:59] INFO connection/get_ssl_certificate No SSL capability on any configured ports
[2021-08-31  16:19:59] INFO stats/_stats_thread stats thread started
[2021-08-31  16:19:59] INFO yp/yp_update_thread YP update thread started
[2021-08-31  16:20:00] DBUG slave/_slave_thread checking master stream list
[2021-08-31  16:20:00] DBUG slave/check_relay_stream Adding relay source at mountpoint "/radioking"
[2021-08-31  16:20:00] INFO slave/start_relay_stream Starting relayed source at mountpoint "/radioking"
[2021-08-31  16:20:00] INFO slave/open_relay_connection connecting to listen.radioking.com:443
[2021-08-31  16:20:00] EROR slave/open_relay_connection Header read failed for /radioking (listen.radioking.com:443/radio/282820/stream/328621)
[2021-08-31  16:20:00] DBUG source/source_clear_source clearing source "/radioking"
[2021-08-31  16:20:01] DBUG stats/modify_node_event update global clients (1)
[2021-08-31  16:20:01] DBUG stats/modify_node_event update global connections (1)
[2021-08-31  16:20:01] INFO fserve/fserve_client_create checking for file /radioking (/usr/share/icecast/web/radioking)
[2021-08-31  16:20:01] WARN fserve/fserve_client_create req for file "/usr/share/icecast/web/radioking" No such file or directory
[2021-08-31  16:20:01] DBUG fserve/fserve_add_client Adding client to file serving engine
[2021-08-31  16:20:01] DBUG fserve/fserve_add_pending fserve handler waking up
[2021-08-31  16:20:01] DBUG fserve/fserv_thread_function fserve handler exit
[2021-08-31  16:20:01] DBUG slave/check_relay_stream waiting for relay thread for "/radioking"
[2021-08-31  16:20:01] DBUG stats/modify_node_event update global client_connections (1)
[2021-08-31  16:20:01] DBUG stats/modify_node_event update global clients (0)
[2021-08-31  16:20:03] INFO fserve/fserve_client_create checking for file /radioking (/usr/share/icecast/web/radioking)
[2021-08-31  16:20:03] WARN fserve/fserve_client_create req for file "/usr/share/icecast/web/radioking" No such file or directory
[2021-08-31  16:20:03] DBUG fserve/fserve_add_client Adding client to file serving engine
[2021-08-31  16:20:03] DBUG fserve/fserve_add_pending fserve handler waking up
[2021-08-31  16:20:03] DBUG fserve/fserv_thread_function fserve handler exit
[2021-08-31  16:20:03] DBUG stats/modify_node_event update global clients (1)
[2021-08-31  16:20:03] DBUG stats/modify_node_event update global connections (2)
[2021-08-31  16:20:03] DBUG stats/modify_node_event update global client_connections (2)
[2021-08-31  16:20:03] DBUG stats/modify_node_event update global clients (0)
[2021-08-31  16:20:05] DBUG stats/modify_node_event update global clients (1)
[2021-08-31  16:20:05] DBUG stats/modify_node_event update global connections (3)
[2021-08-31  16:20:05] INFO fserve/fserve_client_create checking for file /radioking (/usr/share/icecast/web/radioking)
[2021-08-31  16:20:05] WARN fserve/fserve_client_create req for file "/usr/share/icecast/web/radioking" No such file or directory
[2021-08-31  16:20:05] DBUG fserve/fserve_add_client Adding client to file serving engine
[2021-08-31  16:20:05] DBUG fserve/fserve_add_pending fserve handler waking up
[2021-08-31  16:20:05] DBUG fserve/fserv_thread_function fserve handler exit
[2021-08-31  16:20:05] DBUG stats/modify_node_event update global client_connections (3)
[2021-08-31  16:20:05] DBUG stats/modify_node_event update global clients (0)
[2021-08-31  16:20:07] DBUG stats/modify_node_event update global clients (1)
[2021-08-31  16:20:07] DBUG stats/modify_node_event update global connections (4)
[2021-08-31  16:20:08] INFO fserve/fserve_client_create checking for file /radioking (/usr/share/icecast/web/radioking)
[2021-08-31  16:20:08] WARN fserve/fserve_client_create req for file "/usr/share/icecast/web/radioking" No such file or directory
[2021-08-31  16:20:08] DBUG fserve/fserve_add_client Adding client to file serving engine
[2021-08-31  16:20:08] DBUG fserve/fserve_add_pending fserve handler waking up
[2021-08-31  16:20:08] DBUG fserve/fserv_thread_function fserve handler exit
[2021-08-31  16:20:08] DBUG stats/modify_node_event update global client_connections (4)
[2021-08-31  16:20:08] DBUG stats/modify_node_event update global clients (0)

How can I make icecast support SSL on relay client config ?

Thank you,
Irakli

________________________________

Find out the latest about the Bank of Georgia Group products, services and recent developments from the Bank of Georgia monthly e-newsletter. If you wish to subscribe please simply send a request to enewsletter at bog.ge and write "subscribe" in the subject line.

This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. JSC Bank of Georgia shall not be responsible nor liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. JSC Bank of Georgia does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference.


From epirat07 at gmail.com  Tue Aug 31 13:03:10 2021
From: epirat07 at gmail.com (Marvin Scholz)
Date: Tue, 31 Aug 2021 15:03:10 +0200
Subject: [Icecast] Icecast relay specific mount point over SSL
In-Reply-To: <0547df456aaf46ea9d1841cdf6d3b85c@bog.ge>
References: <0547df456aaf46ea9d1841cdf6d3b85c@bog.ge>
Message-ID: <E6374557-C5CF-4C4D-8A2F-818D64ADFAAE@gmail.com>

Hi,

On 31 Aug 2021, at 14:21, Irakli Chkhikvishvili wrote:

> Hello,
>  I'm trying to pull a stream from specific mountpoint and everything 
> is fine if I'm connecting to plain HTTP master:
>
> <relay>
>         <server>listen.radioking.com</server>
>         <port>80</port>
>         <mount>/radio/282820/stream/328621</mount>
>         <local-mount>/radioking</local-mount>
>         <on-demand>0</on-demand>
>         <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
>     </relay>
>
>
> But it totally doesn't wrok if I'm connecting to SSL master
>
> <relay>
>         <server>listen.radioking.com</server>
>         <port>443</port>
>         <mount>/radio/282820/stream/328621</mount>
>         <local-mount>/radioking</local-mount>
>         <on-demand>0</on-demand>
>         <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
>     </relay>
>
> Log file:
>
> [2021-08-31  16:19:59] INFO main/main Icecast 2.4.4 server started
> [2021-08-31  16:19:59] DBUG yp/yp_recheck_config Updating YP 
> configuration
> [2021-08-31  16:19:59] INFO connection/get_ssl_certificate No SSL 
> capability on any configured ports
> [2021-08-31  16:19:59] INFO stats/_stats_thread stats thread started
> [2021-08-31  16:19:59] INFO yp/yp_update_thread YP update thread 
> started
> [2021-08-31  16:20:00] DBUG slave/_slave_thread checking master stream 
> list
> [2021-08-31  16:20:00] DBUG slave/check_relay_stream Adding relay 
> source at mountpoint "/radioking"
> [2021-08-31  16:20:00] INFO slave/start_relay_stream Starting relayed 
> source at mountpoint "/radioking"
> [2021-08-31  16:20:00] INFO slave/open_relay_connection connecting to 
> listen.radioking.com:443
> [2021-08-31  16:20:00] EROR slave/open_relay_connection Header read 
> failed for /radioking 
> (listen.radioking.com:443/radio/282820/stream/328621)
> [2021-08-31  16:20:00] DBUG source/source_clear_source clearing source 
> "/radioking"
> [2021-08-31  16:20:01] DBUG stats/modify_node_event update global 
> clients (1)
> [2021-08-31  16:20:01] DBUG stats/modify_node_event update global 
> connections (1)
> [2021-08-31  16:20:01] INFO fserve/fserve_client_create checking for 
> file /radioking (/usr/share/icecast/web/radioking)
> [2021-08-31  16:20:01] WARN fserve/fserve_client_create req for file 
> "/usr/share/icecast/web/radioking" No such file or directory
> [2021-08-31  16:20:01] DBUG fserve/fserve_add_client Adding client to 
> file serving engine
> [2021-08-31  16:20:01] DBUG fserve/fserve_add_pending fserve handler 
> waking up
> [2021-08-31  16:20:01] DBUG fserve/fserv_thread_function fserve 
> handler exit
> [2021-08-31  16:20:01] DBUG slave/check_relay_stream waiting for relay 
> thread for "/radioking"
> [2021-08-31  16:20:01] DBUG stats/modify_node_event update global 
> client_connections (1)
> [2021-08-31  16:20:01] DBUG stats/modify_node_event update global 
> clients (0)
> [2021-08-31  16:20:03] INFO fserve/fserve_client_create checking for 
> file /radioking (/usr/share/icecast/web/radioking)
> [2021-08-31  16:20:03] WARN fserve/fserve_client_create req for file 
> "/usr/share/icecast/web/radioking" No such file or directory
> [2021-08-31  16:20:03] DBUG fserve/fserve_add_client Adding client to 
> file serving engine
> [2021-08-31  16:20:03] DBUG fserve/fserve_add_pending fserve handler 
> waking up
> [2021-08-31  16:20:03] DBUG fserve/fserv_thread_function fserve 
> handler exit
> [2021-08-31  16:20:03] DBUG stats/modify_node_event update global 
> clients (1)
> [2021-08-31  16:20:03] DBUG stats/modify_node_event update global 
> connections (2)
> [2021-08-31  16:20:03] DBUG stats/modify_node_event update global 
> client_connections (2)
> [2021-08-31  16:20:03] DBUG stats/modify_node_event update global 
> clients (0)
> [2021-08-31  16:20:05] DBUG stats/modify_node_event update global 
> clients (1)
> [2021-08-31  16:20:05] DBUG stats/modify_node_event update global 
> connections (3)
> [2021-08-31  16:20:05] INFO fserve/fserve_client_create checking for 
> file /radioking (/usr/share/icecast/web/radioking)
> [2021-08-31  16:20:05] WARN fserve/fserve_client_create req for file 
> "/usr/share/icecast/web/radioking" No such file or directory
> [2021-08-31  16:20:05] DBUG fserve/fserve_add_client Adding client to 
> file serving engine
> [2021-08-31  16:20:05] DBUG fserve/fserve_add_pending fserve handler 
> waking up
> [2021-08-31  16:20:05] DBUG fserve/fserv_thread_function fserve 
> handler exit
> [2021-08-31  16:20:05] DBUG stats/modify_node_event update global 
> client_connections (3)
> [2021-08-31  16:20:05] DBUG stats/modify_node_event update global 
> clients (0)
> [2021-08-31  16:20:07] DBUG stats/modify_node_event update global 
> clients (1)
> [2021-08-31  16:20:07] DBUG stats/modify_node_event update global 
> connections (4)
> [2021-08-31  16:20:08] INFO fserve/fserve_client_create checking for 
> file /radioking (/usr/share/icecast/web/radioking)
> [2021-08-31  16:20:08] WARN fserve/fserve_client_create req for file 
> "/usr/share/icecast/web/radioking" No such file or directory
> [2021-08-31  16:20:08] DBUG fserve/fserve_add_client Adding client to 
> file serving engine
> [2021-08-31  16:20:08] DBUG fserve/fserve_add_pending fserve handler 
> waking up
> [2021-08-31  16:20:08] DBUG fserve/fserv_thread_function fserve 
> handler exit
> [2021-08-31  16:20:08] DBUG stats/modify_node_event update global 
> client_connections (4)
> [2021-08-31  16:20:08] DBUG stats/modify_node_event update global 
> clients (0)
>
> How can I make icecast support SSL on relay client config ?
>

This is a known limitation, so it is currently unfortunately not 
possible.

> Thank you,
> Irakli
>
> ________________________________
>
> Find out the latest about the Bank of Georgia Group products, services 
> and recent developments from the Bank of Georgia monthly e-newsletter. 
> If you wish to subscribe please simply send a request to 
> enewsletter at bog.ge and write "subscribe" in the subject line.
>
> This message (including any attachments) is confidential and may be 
> privileged. If you have received it by mistake please notify the 
> sender by return e-mail and delete this message from your system. Any 
> unauthorized use or dissemination of this message in whole or in part 
> is strictly prohibited. Please note that e-mails are susceptible to 
> change. JSC Bank of Georgia shall not be responsible nor liable for 
> the proper and complete transmission of the information contained in 
> this communication nor for any delay in its receipt or damage to your 
> system. JSC Bank of Georgia does not guarantee that the integrity of 
> this communication has been maintained nor that this communication is 
> free of viruses, interceptions or interference.
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From phschafft at de.loewenfelsen.net  Tue Aug 31 13:09:41 2021
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Tue, 31 Aug 2021 13:09:41 +0000
Subject: [Icecast] Icecast relay specific mount point over SSL
In-Reply-To: <E6374557-C5CF-4C4D-8A2F-818D64ADFAAE@gmail.com>
References: <0547df456aaf46ea9d1841cdf6d3b85c@bog.ge>
 <E6374557-C5CF-4C4D-8A2F-818D64ADFAAE@gmail.com>
Message-ID: <10fe5b0f4e21e26484d02456e6dc5f22436e0d8a.camel@de.loewenfelsen.net>

On Tue, 2021-08-31 at 15:03 +0200, Marvin Scholz wrote:
> Hi,
> 
> On 31 Aug 2021, at 14:21, Irakli Chkhikvishvili wrote:
> 
> > Hello,
> >  I'm trying to pull a stream from specific mountpoint and
> > everything 
> > is fine if I'm connecting to plain HTTP master:
> > 
> > <relay>
> >         <server>listen.radioking.com</server>
> >         <port>80</port>
> >         <mount>/radio/282820/stream/328621</mount>
> >         <local-mount>/radioking</local-mount>
> >         <on-demand>0</on-demand>
> >         <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
> >     </relay>
> > 
> > 
> > But it totally doesn't wrok if I'm connecting to SSL master
> > 
> > <relay>
> >         <server>listen.radioking.com</server>
> >         <port>443</port>
> >         <mount>/radio/282820/stream/328621</mount>
> >         <local-mount>/radioking</local-mount>
> >         <on-demand>0</on-demand>
> >         <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
> >     </relay>
> > 
> > Log file:
> > 
> > [...]
> > 
> > How can I make icecast support SSL on relay client config ?
> > 
> 
> This is a known limitation, so it is currently unfortunately not 
> possible.

I would like to point to:
http://lists.xiph.org/pipermail/icecast/2021-July/015566.html

@Marvin Scholz: Maybe you want to ping me about this the next days? I
feel like we should maybe add an entry to the FAQs.


> > 
> > This message (including any attachments) is confidential and may
> > be privileged.

Yes... Please do not send messages to public lists if they are
confidential OR remove the disclaimer claiming something that isn't
true.


With best regards,

-- 
Philipp Schafft (CEO/Gesch?ftsf?hrer) 
Telephon: +49.3535 490 17 92

L?wenfelsen UG (haftungsbeschr?nkt)     Registration number:
Bickinger Stra?e 21                     HRB 12308 CB
04916 Herzberg (Elster)                 VATIN/USt-ID:
Germany                                 DE305133015
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20210831/ccde4717/attachment.sig>

From ichkhikvishvili at bog.ge  Tue Aug 31 13:18:25 2021
From: ichkhikvishvili at bog.ge (Irakli Chkhikvishvili)
Date: Tue, 31 Aug 2021 13:18:25 +0000
Subject: [Icecast] [EXTERNAL] Re: Icecast relay specific mount point
 over SSL
In-Reply-To: <E6374557-C5CF-4C4D-8A2F-818D64ADFAAE@gmail.com>
References: <0547df456aaf46ea9d1841cdf6d3b85c@bog.ge>
 <E6374557-C5CF-4C4D-8A2F-818D64ADFAAE@gmail.com>
Message-ID: <6e7565fc529f490f99342369ba4cb495@bog.ge>

TY Marvin !

-----Original Message-----
From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Marvin Scholz
Sent: Tuesday, August 31, 2021 17:03
To: Icecast streaming server user discussions <icecast at xiph.org>
Subject: [EXTERNAL] Re: [Icecast] Icecast relay specific mount point over SSL

*** ?????????: ?? ?????? ????????????? ???? ?????? ????. ????????? ?????? ????? ????????? ?? ???????? ?????????. *** CAUTION: This email was sent from an EXTERNAL source. Think before clicking on links or opening attachments. ***

> How can I make icecast support SSL on relay client config ?
>

This is a known limitation, so it is currently unfortunately not possible.

> Thank you,
> Irakli
>

________________________________

Find out the latest about the Bank of Georgia Group products, services and recent developments from the Bank of Georgia monthly e-newsletter. If you wish to subscribe please simply send a request to enewsletter at bog.ge and write "subscribe" in the subject line.

This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. JSC Bank of Georgia shall not be responsible nor liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. JSC Bank of Georgia does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference.