- App_rpt-users - lists.keekles.org

Re: [App_rpt-users] Debian Wheezy and RPi update
by Doug Crompton 23 Mar '14

23 Mar '14

Buddy, I am using the latest stable Debian Wheezy - kernel 3.2.0-4-686-pae but you still need to use the acid release with old asterisk and I used the latest dahdi not zaptel compiled from source. I am not seeing any audio issues. Here are some of my notes on audio in Debian.... Installing Asterisk Allstar on a Debian system, sound issues. I am specifically addressing Debian Wheezy release but this should apply to all late Debian releases including Raspbien on the Pi. Removing the Pulseaudio code is optional if it is there to begin with. It probably does not hurt to leave it in but if you aren't going to use it why have it there taking up space. For me it worked with it in or out. To remove do the following steps. killall pulseaudio If it is not running this will just tell you that. No problem, just checking that its not running before removing. apt-get purge pulseaudio pulseaudio-utils gstreamer0.10-pulseaudio libpulse-browse0 paman pavumeter pavucontrol You may not have all of these install, delete those that are. Now make sure ALSA is installed. apt-get install alsa-base alsa-tools alsa-tools-gui alsa-utils alsa-oss alsamixergui libalsaplayer0 You may not need all of these but it does not hurt to install them. Base, tools, utils, and alsa-oss are the important ones. Possible problems If you get an error from Allstar that /dev/dsp does not exist make sure the snd-pcm-oss module is loaded. modprobe snd-pcm-oss Loading this creates the /dev/dsp file. To force the loading at each boot if necessary add snd-pcm-oss to the /etc/modules file. 73 Doug WA3DSP http://www.crompton.com/hamradio > Subject: Re: [App_rpt-users] Debian Wheezy and RPi update > From: buddy(a)brannan.name > Date: Sun, 23 Mar 2014 17:39:15 -0400 > To: doug(a)crompton.com > > Hi Doug, > > I’m running currently on Acid, but if the truth be known, I’m a Debian guy at heart and would really rather be using that. > > So does this mean that the audio issues or what have you in the 3.X kernels are resolved? Or do we need to get an older version of debian? I have a system running Wheezy, and I had a later version of Asterisk on it for other stuff.

1 0

Debian Wheezy and RPi update
by Doug Crompton 23 Mar '14

23 Mar '14

In my tests of the Pi I wanted to see if there were any issues using Allstar on Debian on a PC so I compiled it up on Debian Wheezy latest stable release and it works fine. I see no reason why Allstar could not be used on Debian. Is anyone else running Allstar with Debian on a PC? I am still running into problems with the Pi which seems to revolve around the USB interface. The Pi suffers from some real problems in the USB area. A rewrite of the Pi USB driver is underway but it is hard to say what the outcome will be, so far it has not fixed the problem. The Asterisk PBX community has had similar problems and the answer was the Beagle Black. I have one on order. It is $10 more than the Pi but has a stronger processor and apparently no USB problems. As I reported earlier the Pi does work with Allstar but has to be run in USB 1.1 mode. This results in delays that probably would be unacceptable to most people especially in repeater mode. That being said I am hopeful that in another month or two there might be something of production quality but maybe not on the Pi. Sorry for getting everyones hopes up and then having to report this but stay tuned. 73 Doug WA3DSP http://www.crompton.com/hamradio

2 2

Parallel Port Interface
by Tim Sawyer 20 Mar '14

20 Mar '14

SimpleUSB supports using a parallel port to interface with a radio for PTT, COR, CTCSS and static output. The documentation on the Drupal site has been updated to reflect this feature. http://ohnosec.org/drupal/node/193 This has been in simpleUSB for a long while but Drupal documentation was way behind. I’ve not tested CTCSS decoding myself but I know PTT and COR work. -- Tim :wq

2 1

hamlib ?
by Steve Wright 20 Mar '14

20 Mar '14

Anyone working on hamlib for app_rpt? This would be really useful. Steve -- Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers +64 21 040 5067

1 0

DMK URI GPIO temperature sensor
by Bob Roszkowski 19 Mar '14

19 Mar '14

Group, Does anyone know if it is possible to measure sensors like temperature, battery voltage, and S readings remotely using the URIs GPIO pins? My air conditioner in my cabinet at the repeater site decided to freeze up making it very hot in the cabinet. Would like to be able to monitor it. Another option is to plug something in to the USB port to monitor temperature and have the node able to notify if it falls outside the parameters set. Has anyone done this? thanks boB - W5EVH

4 4

Re: [App_rpt-users] DMK URI GPIO temperature sensor
by Steve Wright 19 Mar '14

19 Mar '14

On Thu, Mar 20, 2014 at 5:00 AM, <app_rpt-users-> > My air conditioner in my cabinet at the repeater site decided to freeze up making > it very hot in the cabinet. Would like to be able to monitor it. Moisture is getting into the building somewhere. You should do something about that or else you will be maintaining the room at or near 100% humidity - not good for equipment. Steve

2 1

Zaptel Patches for kernel 3.2.xx
by Dwaine Garden VE3GIF 19 Mar '14

19 Mar '14

Does anyone have the zaptel patches for kernel 3.2.xx kicking around. The last set of patches that I can find are for kernels 3.1.x.

1 0

Re: [App_rpt-users] Asterisk Allstar on the Raspberry Pi
by Doug Crompton 18 Mar '14

18 Mar '14

Thanks for all the replies on my announcement. I got so many that I am sorry I cannot respond to everyone individually. So there definitely is interest in doing this. I am currently working on compiling it with the latest USB rewrite updates in the 3.10 kernel. While it works OK now there are some slight delay issues I am not happy with. It currently only runs in USB 1.1 mode which on the Pi puts the Ethernet into low speed also. Hopefully the updates will fix that. I certainly understand the enthusiasm out there for this but I would not want to put out something prematurely that would cause problems. So bear with me for a bit until things are ironed out. In the meantime you can get your RPI, USB FOB, and SD card ready. I would recommend a Sandisk Ultra class 10 16gb or better. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Mon, 17 Mar 2014 22:04:50 -0500 Subject: Re: [App_rpt-users] Asterisk Allstar on the Raspberry Pi From: mhebert1975(a)gmail.com To: doug(a)crompton.com Any update? What do you need help with? On Mon, Mar 10, 2014 at 12:09 AM, Doug Crompton <doug(a)crompton.com> wrote: Update on the Raspberry Pi Asterisk Allstar project Great news, Allstar is running on the Raspberry Pi! I have been working on this over the last few months and testing now for several weeks. It seems to be stable. Audio is great using simpleusb. The project makes it possible to assemble a small, low power, and inexpensive Allstar server and node that fits in the palm of your hand minus the radio. The project was started by Mihhail, ES1BIS who successfully compiled the code on Pidora FC17 on the Pi. I took that code, optimized it, and made it work well in the real world. I later successfully compiled the code under the latest Raspbien release for the Pi. This was an important transition for a number of reasons as Pidora has been poorly supported recently and does not have direct overclocking and memory management capabilities. It is the Acid release except using Dahdi. The code is on a 16G SD card and while it would fit on an 8G card the added space at little additional cost are worth it. Using a larger size SD card is also purported to increase the life of the card giving more space for wear levelling. The Pi is run as a "headless" system with ssh access. I also have added the apache2 web browser and my lsnodes remote web display and control program which allows you to monitor and control the server remotely. The test system is running with a DMK URI USB interface but would work with an inexpensive modified sound FOB. An entire system could be built for around $50 in this way. It would also be possible to write code and build a small interface to allow the Pi GPIO pins control the PTT and COS. Asterisk typically uses about 10-20% of CPU on the Pi and other operations like web accesses and even a compile going on while Allstar is running caused no glitches. I currently run overclocking at modest (800mhz) but it could be run at much higher speeds if necessary. I have two nodes running on the Pi but only one connected to a radio. If you did not know it was running on the Pi you would not know the difference to any other server. Things to be done include - Recompile under USB driver rewrite kernel A script to install your node information and setup Test use of a wireless card in the Pi Test Mobile node applications Test Additional nodes (2 or more simultaneous nodes) Test usbradio (it might be possible for one node with overclocking) Item number one on this list is the most important right now. There is a problem running the USB at full (2.0) speed with USB audio. This shows up as unacceptable distortion in the receive (DAC) audio. Running in USB high (1.1) speed solves the audio problem but causes some minor delay problems. In the scheme of things this is acceptable but I am not completely happy with this and I want to get this running in USB 2.0 mode before I release it. There is currently a complete rewrite of the Pi USB stack going on that hopefully will solve this problem. My plans are to let things settle a little and pick up the new kernel and recompile very soon. So stay tuned for that. When I do make the image available it will not be plug and play. It will require IP address and port setup for your LAN and editing of rpt.conf and other configuration files. I will put together a checklist of tasks you will need to complete in bringing up your own Pi Allstar server. This is a server and node so you will have to transfer an existing server and node or set up a new one at allstarlink.org If you don't feel comfortable mucking in Linux this might be a problem but the upside is that you will have the original image to go back to should you mess something up and need to start over. It is always a good idea to save additional image copies after you make significant changes and you are sure it is working. This allows you to go back to prior images that work rather than recreating things from earlier images. A quick note about SD card life since I know this is a big topic and a question you would ask. First I will say I have several IRLP Pi nodes, one running for 10 months straight, without a failure. I have never had an SD card fail period. Not due to power failure, longevity or any other cause. I also only buy good quality cards like the Sandisk Ultra class 10 or better. That is not to say one won't fail at some point but that is what backups are for and with an SD card it is easy, pop one out and put the other one that you have burned the image to in. Like anything else it is important to have a backup. I have done most everything practical to minimize writes to the SD card. Only time will tell how long it will last but I have confidence it will be a long time. I will be setting up a web page for this and there will be additional information as well as image downloads there when they are available. I would be glad to answer any questions you may have. And finally I saw this statement on an Asterisk site and I though it pointed out how far we have come in the past 15-20 years! "I just received my Raspberry Pi and looking forward to running Asterisk on it. I’ve been in tech for 30 years and I can’t believe what is in front of me. 15 years ago, as a department head, I signed off on a $200K project to upgrade a PBX system with a voicemail system that can email you the sound file and provide web access to your VM messages. Now, I am about to deploy a full PBX system for $50. Maybe a $75 if I buy a case for my Raspberry Pi." 73 Doug WA3DSP http://www.crompton.com/hamradio _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

1 0

Making Life simpler
by Geoff 17 Mar '14

17 Mar '14

This makes my life simpler... your mileage may vary. More on using the OS to help in asterisk. I made a simple alias... alias rpt='asterisk -rx' and then pass parameters to it. #> rpt "rpt nodes [node_number]" for one example... Another is simply 'nodes' alias nodes='asterisk -rx "rpt nodes [node_number]" Do all this at the Command prompt, as opposed to the CLI> prompt. To make these changes permanent, edit /root/.bashrc and add them there. You'll have to log out, and log back in to make changes effective. 73 = Best Regards, -Geoff/W5OMR

2 1

rpt.conf duplex=
by Bob 16 Mar '14

16 Mar '14

The node stanza in rpt.conf does not have a "duplex=2" statement for our repeater. How is it operating without "duplex=2" for our full duplex repeater? Also, the operator can hear his/her final words just after releasing PTT. I'm not sure why it is working with out "duplex=2" Should I add "duplex=3" so we don't hear the last part of our own transmission? Thanks, Bob kk6ecm

2 1