This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/op25-dev@lists.osmocom.org/.
wllmbecks@gmail.com [op25-dev] op25-dev at yahoogroups.comSteve, Problem solved and no need to interface with Allstar. Instead all that is needed is to add the functionality of a streaming audio server to your Raspberry Pi and you can then simply connect to the built in server over your LAN at home or over the Internet from anywhere else that you have connectivity. Here’s the procedure… sudo apt-get install darkice sudo apt-get install icecase2 [Note that the installation script will spawn a menu to configure icecast where you configure passwords and port number] sudo cp /localpath/asound.conf /etc/asound.conf sudo cp /localpath/darkice.cfg /etc/darkice.cfg sudo cp /localpath/bcm2835.conf /etc/modprobe.d/bcm2835.conf Edit the attached op25.sh to specify your own rx.py command line options but retain the -O loop0 option that directs op25 audio to darkice via the audio loopback. Reboot the Pi then connect to the Pi’s IP on port 8000 (default) accordingly to the following examples. Icecast Administration URL: http://xxxx.xxx.xxx.xxx:8000 [login username = admin, password = string set when installing icecast] Icecast Audio Stream URL: http://xxxx.xxx.xxx.xxx:8000/op25.mp3 You don’t need to connect to the admin except to determine if the mount point (op25.mp3) is active (darkice running and connected) or to view and manage connections to the Icecast server. Incidentally, you can use this same general configuration to put op25 audio to a broadcastify.com mount point as well. Notes Although the example configs start darkice from the same script that I use to start op25 that a much better approach is to crate a cron job or to create a service that gets run at boot time by system. The reason for this is that if you need to stop and restart op25 to make or test configuration changes, then you’d need to kill the darkice process too before executing op25.sh. The Raspberry Pi3-A+ has some hardware differences that require a slightly different configuration. Contact my via PM if anyone needs that info. Happy New Year! Bill, WA8WG From: op25-dev at yahoogroups.com <op25-dev at yahoogroups.com> Sent: Thursday, December 27, 2018 8:17 PM To: op25-dev at yahoogroups.com Subject: [op25-dev] Allstar integration? I wish there was a way to feed op25 into a local Allstar (Asterisk app_rpt) node to drive an analog transmitter. That way I can keep tabs on a few digital systems when I am out and about or via the the IP phone on my desk. One way would be fine till such a time that transmitting with op25 via direct modulator input becomes more common. Has any thought been given to that sort of thing? Just curious All the existing digital to analog bridges pretty much rely one one being personally involved with the digital repeaters to configure things on both ends (IP network level etc). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20181228/1f5f988c/attachment.htm>