March 2014 - App_rpt-users - lists.keekles.org

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 17 Mar '14

17 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

Re: [App_rpt-users] acid install from usb thumb drive
by mike＠midnighteng.com 16 Mar '14

16 Mar '14

1 0

acid install from usb thumb drive
by REDBUTTON_CTRL 16 Mar '14

16 Mar '14

Anyone been able to get the acid distro to install via a usb thumb drive? I have tried to get this to work on a pc that supports boot from usb but the install gets stuck with the kickstart menu because it looking for files from a CD rom rather then a usb drive. Yes in know that the Xipper distro can be loaded via usb but I'm looking for Acid on a usb drive. I asked about this a couple of years ago but go no response. Hopefully somebody has this working now. Jon VA3RQ

2 1

URIx with Icom IC-910 Data Jacks?
by Kevin Oleniczak 16 Mar '14

16 Mar '14

Anyone know if either of the Icom data jacks can be used to work with the URIx successfully for a simplex node? Documentation notes this: DATA IN - Input terminal for data (common for both 1200 and 9600 bps) GND - Ground line for the DATA IN, DATA OUT and AF OUT. PTTP - Transmits when this terminal is grounded. DATA OUT - Received data output terminal for 9600 bps operation. AF OUT - Received data output terminal for 1200 bps operation. SQL - Output terminal for squelch condition (Open/Close). Outputs grounded level signal when squelch is opened, +8 V level signal when squelch is closed. I wired it up but not getting tx audio or rx audio to work. Tried using SQL with the URI COR_DET line. Maybe that's inverted here... Anyone have luck using this kind of data port to do the interfacing? thanks!

2 2

Asterisk Allstar on the Raspberry Pi
by Doug Crompton 14 Mar '14

14 Mar '14

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

5 8

(no subject)
by David Griffith 11 Mar '14

11 Mar '14

I have a few questions on setting up RTCM’s. We have three set up and working on a private node, say 1010. Two are connected to Tait T2020’s (simplex) and one to RLC-4 controller (repeater) . This is a NON-voting configuration for now. We connect node 1010 to our Public Asterisk Node. I have set the node stanza up as follows : rxchannel = Voter/1010 duplex = 0 hangtime = 1000 We can not hear each other on the RTCM’s but we can on the public node. Is there a setting to enable the ability to hear to each RTCM without being connected to the public node? The hang time is also a problem if connected to public node. The RTCM will hang for about 3-4 seconds before dropping. I have done the voter ping’s and worked the formula for the RX and TX buffers. No audio issues thru the public node. Should the rpt.conf stanza be setup as thought it was another node ie.. telemetry, function, macro’s, etc…? Can someone post a defacto standard node stanza for RTCM’s? Thanks for the help. -Dave Sent from my Galaxy S®III

1 0

RTCM Host Connection Failure
by Craig Sande 11 Mar '14

11 Mar '14

I am able to get my RTCM working with the server voter-demo.allstarlink.org, but when I try connecting it to my local server (CentOS Acid) it fails to get a host connection. This had worked for me in the past, but somewhere a setting got changed and I am having trouble debugging it. The server is on a local static IP 192.168.1.230 and the RTCM is on local static IP 192.168.1.210. Any suggestions on how to debug my client-host connection? Craig, AE7I

1 0