[arm-allstar] Broadcastify

[Patrick Perdue]

Try the instructions for streaming to Broadcastify using mptee, which 
is, I believe, one of the howto files on HamVoIP.org. It's safer, as the 
mptee binary acts as a buffer between app.rpt and lame/ezstream. Thus, 
ezstream and lame aren't being called by app.rpt directly. Even in the 
streaming process fails, it *shouldn't* bring your node down. You can 
run ezstream in the foreground to quickly figure out what's going on 
with it, in order to determine what your issue is with connecting to 
Broadcastify, then script it to run in the background for normal 
operation once you have it working.

This is what I use, both for HamVoIP and ASL. In the case of my ASL hub 
node, it generally works for about ten to twenty days at a time, until 
the hub core dumps for whatever reason, breaking the pipes and causing 
ezstream to complain. This hub, on average, handles about 30 to 40 
full-time connections, sometimes more, and little things occasionally 
cause Asterisk to not be impressed with life anymore. Nothing to what 
some of the larger networks experience, but that's a different topic.
If not for that, it would probably require less maintenance. At some 
point, I'm going to move streaming to another VPS adjacent to the hub, 
which will probably make this process even more stable.
The great thing about using mptee is that you can also provide a higher 
quality, less delayed stream than Broadcastify will allow as a second 
stream on your own Icecast server should you want such things. I did, 
which spawned discussions which eventually lead to mptee being created 
by KB4FXC, and it's been working well for me for over a year. Even if 
you don't care about having multiple streams at different formats or 
bitrates, using mptee is a safer way to do it.

On 12/12/2020 6:13 PM, "Chris Viningre via ARM-allstar" wrote:
> After I add the outstreamcmd=/bin/sh,-c,/usr/bin/lame --preset cbr 16 -r -m
> m -s 8--bitwidth 16 - - | /usr/bin/ezstream -qvc /etc/ezstream.xml line to
> my rpt.conf it shutdown my node after about 30 - 45 min. I have to reboot
> the server to get it to come back up. Even during the time it's up I'm
> still not getting a connection on Brodcastify. I know it's working for many
> others so I must be doing something wrong. Does anyone have any ideals or
> can I get some help offline on Team-Viewer or SSH?
>
> Chris Viningre
> 70 W. Roadrunner
> Salt Flat, Texas 79847
> C:(915) 504-1510
> Website: ws5b.com <http://ws5b.com>
> chrisviningre at gmail.com
> chris at ws5b.com
> Ham Radio Call Sign: WS5B
>
>
>
>
>
> On Fri, Dec 11, 2020 at 9:42 PM "Mark Johnston via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> I assume you are using ezstream
>>
>> what is in your /etc/ezstream....xml file?
>> do you have the line in /etc/asterisk/rpt.conf
>>
>> outstreamcmd=/bin/sh,-c,/usr/bin/lame --preset cbr 16 -r -m m -s 8
>> --bitwidth 16 - - | /usr/bin/ezstream -qvc /etc/ezstream....xml
>>
>> This would require ezstream and I believe LAME to be installed as well.
>>
>>
>>
>> 73
>> Mark
>> KC7DMF
>> _______________________________________________
>>
>> ARM-allstar mailing list
>> ARM-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
>>
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org