April 2015 - App_rpt-users - lists.keekles.org

Loading Linux
by R. Wayne 16 Apr '15

16 Apr '15

Do you prefer to load the GUI when running Allstar, or bypassing it for added performance? I am debating whether or not to use Beagle boards remotely after all compared to RTCM’s.

1 0

Raspberry Pi cases
by Steve Zingman 14 Apr '15

14 Apr '15

I have bee buying metal cases for my Raspberry Pi boards. These are really nicely done. Takes a while for USPS to get them to you, but I think they are worth the wait. <http://www.emko.cz/en/catalog/it-cases/raspberry-pi/em-raspi-b-silver-h3564> He does take PayPal. 73, Steve N4IRS -- "Anything is possible if you don't know what you are talking about." 1st Law of Logic

2 2

Thumb Drive & BBB-X
by R. Wayne 13 Apr '15

13 Apr '15

If a BBB can run fine on a SSD, can a BBB-X with a simple 8GB thumb (flash) drive run fine?? Both are solid state.

1 0

App_rpt on a laptop
by Steve Zingman 12 Apr '15

12 Apr '15

Pete, There are some nice metal boxes available for the BBB and the RPI 1 and 2. Ubuntu being Debian based makes it pretty easy to compile and install AllStar Asterisk. 64 bit does not seem to be a problem either. The one concern I have is that there may not be support built in your kernel for OSS. I would make sure you have OSS and the kernel headers needed for compiling dahdi. The scripts I built to install AllStar on Linode should help a lot since it was 64 bit. See <https://github.com/N4IRS/AllStar/tree/master/platforms/linode> 73, Steve N4IRS On 04/12/2015 03:31 PM, app_rpt-users-request(a)ohnosec.org wrote: > Message: 1 > Date: Sun, 12 Apr 2015 12:31:41 -0400 > From: pete M<petem001(a)hotmail.com> > To: APP RPT<app_rpt-users(a)ohnosec.org> > Subject: [App_rpt-users] App_rpt on a laptop > Message-ID:<BAY176-W27131853987061CA19D04B97F80(a)phx.gbl> > Content-Type: text/plain; charset="iso-8859-1" > > Hi! > Looking to install app_rpt on my laptop with a graphical desktop.. > My laptop is a 64 bit machine > I want to beable to run asterisk ans allstar when I test some repeater in my basement. > I allready have ubuntu 14/04 lts installed.. > But I could change to another distro if it would be easier to do so.. > I run this on a ssd drive and I have 4 gig of ram on a I5 dual core cpu. > Want to have only one machine running in the shack, All computer do makes birdies and stuff like that.(the BBB is a killer on HF and same with the RPI). So one machine would be much more fun to have live.. > what would be the best solution? > Is there some howto somewhere to install app_rpt on another OS then acid?thanks. > PierreVE2PF

2 1

App_rpt on a laptop
by pete M 12 Apr '15

12 Apr '15

Hi! Looking to install app_rpt on my laptop with a graphical desktop.. My laptop is a 64 bit machine I want to beable to run asterisk ans allstar when I test some repeater in my basement. I allready have ubuntu 14/04 lts installed.. But I could change to another distro if it would be easier to do so.. I run this on a ssd drive and I have 4 gig of ram on a I5 dual core cpu. Want to have only one machine running in the shack, All computer do makes birdies and stuff like that.(the BBB is a killer on HF and same with the RPI). So one machine would be much more fun to have live.. what would be the best solution? Is there some howto somewhere to install app_rpt on another OS then acid?thanks. PierreVE2PF

5 4

BBBimage. Trouble
by vito＠alsrv.com 11 Apr '15

11 Apr '15

Keep getting #23 error from win32imager while trying to load the bbb image I got and unzipped from ham VoIP reformatted chip(8 GB) also redownloaded the file multiple times. Can't seem to get past this problem.any suggestions? Thanks Vito KD7GXW 9282477353 VITO(a)alsrv.com Sent from my Verizon 4G LTE Tablet

1 0

RPi2 V1.0 Released!!!
by Doug Crompton 11 Apr '15

11 Apr '15

We are very happy to announce the release of Allstar on the Raspberry Pi 2. The code has undergone many alpha and beta releases and we feel confident that it is ready for production use. Although the look and feel is very similar there are several changes from the BBB 1.2.1 release most of which are documented below. A BBB version 1.3 update is in the works and should be out in a few weeks. What has not changed - The RPi2 Allstar image is mostly modeled after the BBB. It has the same scripted setup and operation will look the same except for the changes noted below. What has changed or is new from the BBB 1.2.1 image - First of all the RPi2 is computationally faster than the BBB. It boots damn fast. You should have Allstar running and radio messages in 10-15 seconds after power on. It should handle two simplesusb radio nodes. usbradio is still NOT recommended and may never be in its current form. See future notes below. We are using the newest ArchLinux kernel and different networking and timesync functions then were used on the BBB. No difference should be noted at the user level but there are many behind the scene improvements. There are several new scripts which are described in the scripts how-to on the hamvoip.org web page. The setup routine now also configures simpleusb. There is a small radio database that will be expanded with user input in the future. Make sure you understand the configuration parameters before changing them indiscriminately. If you are moving a radio from another Allstar simpleusb configured system the settings including audio levels would be the same on the RPi2. So make a note of them before you switch. simpleusb now includes two new commands, preemphasis to go along with the long existing deemphasis and rxaudiodelay to eliminate squelch tails. rxaudiodelay takes a value from 0-24. 0 or commenting the line results in no delay. Values 1 to 24 are the number of 20ms frames of delay. Typical values are from 5-10. Listen on iaxrtp or another local node to hear your own squelch tail. It is the tail the node radio creates when you immediately unkey not when your radio squelches. Experiment and use the minimum value that consistently eliminates the squelch tail. Allmon2 is pre-installed. See the how-to on the hamvoip.org web page. The RPi2 does not have a shutdown switch. See the how-to on the web page for information on how to add a switch. Software support for a switch is built-in to the distribution but it needs to be turned on in /usr/local/etc/allstar.env Other methods of shutdown are sending a shutdown command using ssh or a HDMI monitor and keyboard or activating DTMF control in the rpt.conf functions section. When you halt the processor you will need to power cycle to restart. So this is generally not something you would want to do remotely. It is a good idea to always properly shutdown your system. Unless absolutely necessary don't just pull the power. GPIO works and the wiringpi GPIO C library and command line functions are included. See /usr/src/examples/GPIO/wiringpi for examples. The weather scripts have been updated. See the weather howto on the web page for updates. All other features except those noted below that are now on the BBB 1.2.1 version should work fine on the RPi2. What does not yet work on the RPi2 - Automated Wireless Ethernet is not yet implemented. It will be on the next version which should be out fairly quickly after the v1.0 release. It could be done manually and we may make a script or how-to available in the next few weeks. GPIO control of PTT and COS are also not implemented but will be very soon. See future development below. Future development - Development is under way to write new channel drivers specifically for the BBB and RPi2 using the ALSA rather than the obsolete OSS sound interface that is used in the current Allstar. If will be multi-threaded with a separate manager thread to handle telemetry. This will allow interface to virtually any audio device that can be hooked to the board. We also feel that the current usbradio type commands will have a high likelihood of working on the RPi2 with the new code and it will also make GPIO interfacing for COS, PTT, etc. much easier. It also opens the door to use better DSP software packages using the floating point capability of the RPi2. Audio noise floor and quality could be even better than it is now. We are very excited about the possibilities. You should see test versions of these drivers in the next few months. We will continue to update the BBB code but I can see much more development effort going into the RPi2 in the future. For that reason I would recommend that any future purchases for new servers be the RPi2 rather than the BBB. It is also likely we will see the BBB's availability go down and cost go up in the future as sales go down. It is hard to predict a time line on this so just be aware it could happen. That being said if your BBB board is working well and serving your needs there is no reason to replace it. More updates on the web page will happen over the next few weeks, so be patient. Some of the updates mentioned above are not yet complete. Also be sure to reload web pages and how-to's to make sure you have the current version. The RPi2 like the BBB is extremely easy to setup using the automated scripts. Just be sure to have all your information together before you start - node#, Node PW, IP address and gateway if static, etc. The direct download link for the RPi2 V1.0 release is: http://www.hamvoip.org/RPi2/RPi2_V1.0_Allstar.zip This link also appears on the hamvoip.org website. Thank you for your patience. Have fun, the RPi2 Allstar Team, WA3DSP, KB4FXC, W0AMN Visit http://hamvoip.org for more information. 73 Doug WA3DSP http://www.crompton.com/hamradio

2 1

Rtcm configuration
by Tom Caspar 11 Apr '15

11 Apr '15

I'd like to be able to dynamically control from a macro or the asterisk CLI, whether a particular rtcm in a voter node is enabled as a transmitter. Is this possible without having to manually edit the voter.conf and restart asterisk? Thanks, Tom

3 3

CLI> Message "Registered IAX2 to..."
by kk6ecm 11 Apr '15

11 Apr '15

Our repeater is getting multiple messages in CLI> -- Registered IAX2 to '67.215.233.178', who sees us as 173.30.82.62:4569 with no messages waiting The IP address '67.215.233.178' is in Santa Ana, and there are no indications of any further contact. Any ideas of what is happening? Thanks, Bob kk6ecm

2 1

Re: [App_rpt-users] App_rpt-users Digest, Vol 74, Issue 16
by Steve Zingman 11 Apr '15

11 Apr '15

Mitch, As far as I know the BBB image uses the /etc/asterisk/custom sub-directory. Acid uses /etc/asterisk for it's configuration file. You may have to move the configs. 73, Steve N4IRS On 04/10/2015 04:23 PM, app_rpt-users-request(a)ohnosec.org wrote: > Message: 3 > Date: Fri, 10 Apr 2015 17:45:42 +0000 (UTC) > From: Mitch Mitchell<mitchmitchell1616(a)yahoo.com> > To:"app_rpt-users(a)ohnosec.org" <app_rpt-users(a)ohnosec.org> > Subject: [App_rpt-users] Question about connecting an existing > asterisk server (used as a PBX) with ACID version of asterisk via IAX2 > trunks > Message-ID: > <1249844348.399648.1428687942908.JavaMail.yahoo(a)mail.yahoo.com> > Content-Type: text/plain; charset="utf-8" > > All, > I have just set up my Allstar node using the latest ACID image. ? I have the node connected to the Allstar network successfully, with Echolink and APRS interfaces working. > I am now trying to set up an IAX2 trunk between my existing asterisk installations and my Allstar node asterisk. > For background, I have Asterisk 8 on a 64 bit Intel machine as the main PBX, and an auxiliary PBX running asterisk 11 on a beagle bone black connected by an IAX2 trunk. ?GIven the ease of set up there, I figured it would be relatively simple to connect the asterisk 8 machine to the ACID asterisk instance with another IAX2 trunk. ? However it didn't work out that way. > I created an iax.conf file in /etc/asterisk/custom sub-directory on the ACID machine with credentials in the same format as I had used between the other two asterisks and then created a corresponding trunk on the asterisk 8 machine. ? Both asterisks show the trunk as connected and running, but when I try to route a call from the asterisk 8 machine to the ACID machine, the asterisk on the ACID machine rejects the call claiming the sending node did not authenticate correctly. > Asterisk on the ACID machine shows some unknown information elements coming from the asterisk 8 box when it tries to authenticate the call so I am wondering if there is some version difference between the instance of asterisk running on ACID and the asterisk 8 I am using as my main PBX. > Does anyone have any thoughts on this? ? Anyone out there have a similar configuration where you tied an ACID machine to another asterisk instance using an IAX2 trunk? > Thanks, > Mitch Mitchell, AE5HO >

1 0