October 2010 - App_rpt-users - lists.keekles.org

Re: [App_rpt-users] Discontinuance of IRLP support
by Tony Langdon, VK3JED 23 Oct '10

23 Oct '10

At 09:53 AM 10/23/2010, kb8ude(a)gmail.com wrote: >That is unfortunate. It also explains why. requests to him for a >node number were ignored. Too many times the needs (wants) of the >few (one) get in the way of progress. > >I got on-board with the app_rpt project because it offered a way to >give our users a way to access three different networks cheaply >rather than duplicating hardware to achieve the same result. I >won't be constructing a new system to fill the gap, that's for sure. Actually, it could be done on an existing IRLP node in theory. A bit of a kludge, but EchoIRLP interfaces thebridge to existing IRLP software, and so I'm sure Asterisk could be interfaced to the IRLP software in a similar fashion. Not the nicest way to do things, but theoretically possible, and would be IRLP compliant. The AllStar side wouldn't need any hardware, since it would be using the radio/interface that IRLP uses. EchoIRLP, even though it's a bunch of shell scripts is GPL, so feel free to play. :) 73 de VK3JED / VK3IRL http://vkradio.com

7 8

I support Jim and Allstar 100%
by Neil Addis (WA5JXY) 23 Oct '10

23 Oct '10

Jim, Many, many THANKS for all the time and effort you have put into this project! I have been involved with repeater and linking systems since the '70s and currently work with the very latest Motorola Astro P25 trunking systems and I can tell you that the more I dig into app_rpt and Allstar, the more fun stuff I find! Today, I actually got a node configured to work with the Doug Hall RBI-1 and dual Kenwoods as a remote base! Very very cool! That makes 7 or so nodes I have built with various flavors of releases and SVN's. (all up to date now). The more I work with it, the more I learn, which after 34 years in the business, is bringing new life to Amateur radio as well as ROIP. Duuuude!, you ROCK! (and I completely agree with your decision to dump IRLP integration). In support of Jim and this project, I made a donation to the cause and hope others will do the same. Neil WA5JXY

1 0

(no subject)
by K&R Yoksh 23 Oct '10

23 Oct '10

While unfortunate, I, for one, am not surprised by this. The IRLP inner circle is very resistant to change, and seems quite happy to exist as they did in the 1990s. With the elimination of parallel ports in many newer computers, the reluctance to adopt a USB-based interface, and an unfriendly attitude toward other technologies, IRLP faces certain extinction. Personally, I believe the parallel board is being sold by Dave C until he runs out of stock. Not only does he sell these to hams, but also commercially (as ROIP). As some of you may know, I received a similar letter from Dave C. for publishing a compatible IRLP board schematic on my web site in 2008. He demanded that I remove the IRLP name from the schematic, so I did. It's now called a PLRI board. I just don't agree with the idea of selling $20 worth of parts to hams for $200, and the prohibition of homebrewed boards.. With the discontinuation of IRLP from app_rpt, is there any chance of legacy parallel port support? This might make it easier for IRLP stations to switch over to app_rpt.. It would be especially nice for the AUX1,2,3 ports, but I wouldn't complain if PTT and COS were also supported. Perhaps these stations could use their IRLP boards along with a "blob" USB fobs for audio only, since PTT and COS would be difficult to add? 73, Kyle K0KN --- Original Message --- From: Jim Duuuude Subject: [App_rpt-users] Discontinuance of IRLP support Per request of Dave Cameron, VE7LTD, support and functionality for IRLP connectivity is officially dropped from the app_rpt project. It is being removed from the SVN today, and will no longer be present in any further releases. If you have IRLP configured on your system, PLEASE REMOVE IT! Do NOT make any further connections into the IRLP network from an Allstar Link node (or anything else running app_rpt), as that is now officially against the rules on their network. Thank you for your cooperation. JIM WB6NIL

3 2

Very small question
by keith handscombe 23 Oct '10

23 Oct '10

Can the Allstar ladies voice that identifies connections be speeded up. When we have multiple connections in and out she is a tad slow with the pronunciation of all the node numbers. Not a problem she may need a few extra cups of coffee in the morning J, Like me. Many thanks Keith 2498 / 27333 Allstar 2m and 70cm 5503 / 5503 IRLP & Echolink www.handscombe.co.uk

3 2

Discontinuance of IRLP support
by Jim Duuuude 22 Oct '10

22 Oct '10

Per request of Dave Cameron, VE7LTD, support and functionality for IRLP connectivity is officially dropped from the app_rpt project. It is being removed from the SVN today, and will no longer be present in any further releases. If you have IRLP configured on your system, PLEASE REMOVE IT! Do NOT make any further connections into the IRLP network from an Allstar Link node (or anything else running app_rpt), as that is now officially against the rules on their network. Thank you for your cooperation. JIM WB6NIL

3 2

urb0
by Darril Holland 22 Oct '10

22 Oct '10

On linux console keep getting " cannot submit datapipe for urb0, error-22 internal error. What could be causing this? Darril/WD5GJP

4 4

Re: [App_rpt-users] Re Chan_IRLP updates
by Jon Rorke 21 Oct '10

21 Oct '10

Ok I will stop barking about this and await the solution. I will have a look at my node tonight. Jon > Hi, > > I *think* I got it sorted out. The change was to the statupdate script. > > Check for /home/irlp/update-files/scripts/statupdate and copy it to /home/irlp/scripts . > > Then, you may need to edit the file to add the wget variable. You can either change $WGET to /usr/bin/wget or add this line after the line to source common functions: > WGET=/usr/bin/wget > > > It seems to have run. Hopefully this means my node is now correctly updated. > -- > Buddy Brannan, KB5ELV - Erie, PA > Phone: (814) 860-3194 or 888-75-BUDDY > > > > On Oct 21, 2010, at 3:23 PM, Jon Rorke wrote: > >> See attached info. The updates seem to affect the status server reporting. >> Does anybody know which script(s) this affects? >> >> Despite some people saying that they have done the updates, they are still on the list below as mentioned by Dave C. >> >> Jon VA3RQ >> >> >>> All of it is contained in the new statupdate script, which is part of an update sent a week ago. I am shocked at the number of nodes that are not updating correctly. >>> >>> The server was changed, and we had to change the script to match. Soon these nodes will be tagged as down, and will be subject to PGP key removal. I am trying to help people get their nodes updating on a regular basis. >>> >>> If the update is not working, then there is no way that new features can be pushed to the nodes. They are essentially going to fade away and fall behind the system. >>> >>> Dave Cameron >>> VE7LTD >>> >>> --- Inirlp(a)yahoogroups.com, Buddy Brannan<buddy@...> wrote: >>>> So, what's the new URL, and where is it updated? >>>> -- >>>> Buddy Brannan, KB5ELV - Erie, PA >>>> Phone: (814) 860-3194 or 888-75-BUDDY >>>> >>>> >>>> >>>> On Oct 21, 2010, at 11:19 AM, ve7ltd wrote: >>>> >>>>> Here is the list so far today. Please note that these lists are the best I can get because I am going off of log files on the status page server. These nodes have not been updated since midnight mountain time last night. >>>>> >>>>> These are nodes that are using the OLD URL to try to send status updates. I am going to send a targeted email to the owners via their status page entries to get their attention. >>>>> >>>>> 1160 >>>>> 1250 >>>>> 1840 >>>>> 1882 >>>>> 2015 >>>>> 2020 >>>>> 2154 >>>>> 2184 >>>>> 2270 >>>>> 2304 >>>>> 2365 >>>>> 2414 >>>>> 2509 >>>>> 2537 >>>>> 2590 >>>>> 2600 >>>>> 2651 >>>>> 2736 >>>>> 2739 >>>>> 2882 >>>>> 2949 >>>>> 3018 >>>>> 3029 >>>>> 3059 >>>>> 3066 >>>>> 3075 >>>>> 3078 >>>>> 3088 >>>>> 3098 >>>>> 3102 >>>>> 3145 >>>>> 3152 >>>>> 3158 >>>>> 3170 >>>>> 3174 >>>>> 3192 >>>>> 3212 >>>>> 3225 >>>>> 3299 >>>>> 3330 >>>>> 3337 >>>>> 3396 >>>>> 3402 >>>>> 3415 >>>>> 3418 >>>>> 3440 >>>>> 3486 >>>>> 3500 >>>>> 3517 >>>>> 3530 >>>>> 3539 >>>>> 3629 >>>>> 3659 >>>>> 3667 >>>>> 3696 >>>>> 3727 >>>>> 3734 >>>>> 3744 >>>>> 3753 >>>>> 3759 >>>>> 3765 >>>>> 3767 >>>>> 3778 >>>>> 3793 >>>>> 3795 >>>>> 3826 >>>>> 3829 >>>>> 3865 >>>>> 3913 >>>>> 3917 >>>>> 3924 >>>>> 3927 >>>>> 3932 >>>>> 3962 >>>>> 3967 >>>>> 3969 >>>>> 3971 >>>>> 3976 >>>>> 3986 >>>>> 3994 >>>>> 4067 >>>>> 4068 >>>>> 4076 >>>>> 4077 >>>>> 4100 >>>>> 4103 >>>>> 4134 >>>>> 4147 >>>>> 4170 >>>>> 4200 >>>>> 4204 >>>>> 4280 >>>>> 4410 >>>>> 4467 >>>>> 4486 >>>>> 4494 >>>>> 4503 >>>>> 4529 >>>>> 4563 >>>>> 4606 >>>>> 4610 >>>>> 4650 >>>>> 4661 >>>>> 4671 >>>>> 4715 >>>>> 4722 >>>>> 4765 >>>>> 4777 >>>>> 4802 >>>>> 4835 >>>>> 4881 >>>>> 4922 >>>>> 4952 >>>>> 4967 >>>>> 5056 >>>>> 5070 >>>>> 5361 >>>>> 5429 >>>>> 5444 >>>>> 5466 >>>>> 5468 >>>>> 5503 >>>>> 5515 >>>>> 5588 >>>>> 5612 >>>>> 5660 >>>>> 5690 >>>>> 5717 >>>>> 5720 >>>>> 5776 >>>>> 5961 >>>>> 6122 >>>>> 6796 >>>>> 7001 >>>>> 7010 >>>>> 7011 >>>>> 7012 >>>>> 7013 >>>>> 7014 >>>>> 7015 >>>>> 7016 >>>>> 7018 >>>>> 7019 >>>>> 7020 >>>>> 7058 >>>>> 7149 >>>>> 7192 >>>>> 7550 >>>>> 7580 >>>>> 7661 >>>>> 7671 >>>>> 7689 >>>>> 7697 >>>>> 7718 >>>>> 7731 >>>>> 7820 >>>>> 7841 >>>>> 8038 >>>>> 8066 >>>>> 8190 >>>>> 8289 >>>>> 8322 >>>>> 8327 >>>>> 8365 >>>>> 8380 >>>>> 8484 >>>>> 8562 >>>>> 8720 >>>>> 8937 >> >> >> >> >> >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)qrvc.com >> http://qrvc.com/mailman/listinfo/app_rpt-users >

1 0

Re Chan_IRLP updates
by Jon Rorke 21 Oct '10

21 Oct '10

See attached info. The updates seem to affect the status server reporting. Does anybody know which script(s) this affects? Despite some people saying that they have done the updates, they are still on the list below as mentioned by Dave C. Jon VA3RQ > All of it is contained in the new statupdate script, which is part of an update sent a week ago. I am shocked at the number of nodes that are not updating correctly. > > The server was changed, and we had to change the script to match. Soon these nodes will be tagged as down, and will be subject to PGP key removal. I am trying to help people get their nodes updating on a regular basis. > > If the update is not working, then there is no way that new features can be pushed to the nodes. They are essentially going to fade away and fall behind the system. > > Dave Cameron > VE7LTD > > --- Inirlp(a)yahoogroups.com, Buddy Brannan<buddy@...> wrote: > > > > So, what's the new URL, and where is it updated? > > -- > > Buddy Brannan, KB5ELV - Erie, PA > > Phone: (814) 860-3194 or 888-75-BUDDY > > > > > > > > On Oct 21, 2010, at 11:19 AM, ve7ltd wrote: > > > > > Here is the list so far today. Please note that these lists are the best I can get because I am going off of log files on the status page server. These nodes have not been updated since midnight mountain time last night. > > > > > > These are nodes that are using the OLD URL to try to send status updates. I am going to send a targeted email to the owners via their status page entries to get their attention. > > > > > > 1160 > > > 1250 > > > 1840 > > > 1882 > > > 2015 > > > 2020 > > > 2154 > > > 2184 > > > 2270 > > > 2304 > > > 2365 > > > 2414 > > > 2509 > > > 2537 > > > 2590 > > > 2600 > > > 2651 > > > 2736 > > > 2739 > > > 2882 > > > 2949 > > > 3018 > > > 3029 > > > 3059 > > > 3066 > > > 3075 > > > 3078 > > > 3088 > > > 3098 > > > 3102 > > > 3145 > > > 3152 > > > 3158 > > > 3170 > > > 3174 > > > 3192 > > > 3212 > > > 3225 > > > 3299 > > > 3330 > > > 3337 > > > 3396 > > > 3402 > > > 3415 > > > 3418 > > > 3440 > > > 3486 > > > 3500 > > > 3517 > > > 3530 > > > 3539 > > > 3629 > > > 3659 > > > 3667 > > > 3696 > > > 3727 > > > 3734 > > > 3744 > > > 3753 > > > 3759 > > > 3765 > > > 3767 > > > 3778 > > > 3793 > > > 3795 > > > 3826 > > > 3829 > > > 3865 > > > 3913 > > > 3917 > > > 3924 > > > 3927 > > > 3932 > > > 3962 > > > 3967 > > > 3969 > > > 3971 > > > 3976 > > > 3986 > > > 3994 > > > 4067 > > > 4068 > > > 4076 > > > 4077 > > > 4100 > > > 4103 > > > 4134 > > > 4147 > > > 4170 > > > 4200 > > > 4204 > > > 4280 > > > 4410 > > > 4467 > > > 4486 > > > 4494 > > > 4503 > > > 4529 > > > 4563 > > > 4606 > > > 4610 > > > 4650 > > > 4661 > > > 4671 > > > 4715 > > > 4722 > > > 4765 > > > 4777 > > > 4802 > > > 4835 > > > 4881 > > > 4922 > > > 4952 > > > 4967 > > > 5056 > > > 5070 > > > 5361 > > > 5429 > > > 5444 > > > 5466 > > > 5468 > > > 5503 > > > 5515 > > > 5588 > > > 5612 > > > 5660 > > > 5690 > > > 5717 > > > 5720 > > > 5776 > > > 5961 > > > 6122 > > > 6796 > > > 7001 > > > 7010 > > > 7011 > > > 7012 > > > 7013 > > > 7014 > > > 7015 > > > 7016 > > > 7018 > > > 7019 > > > 7020 > > > 7058 > > > 7149 > > > 7192 > > > 7550 > > > 7580 > > > 7661 > > > 7671 > > > 7689 > > > 7697 > > > 7718 > > > 7731 > > > 7820 > > > 7841 > > > 8038 > > > 8066 > > > 8190 > > > 8289 > > > 8322 > > > 8327 > > > 8365 > > > 8380 > > > 8484 > > > 8562 > > > 8720 > > > 8937

2 1

chan_echolink improvements
by Jim Duuuude 21 Oct '10

21 Oct '10

I have made some major improvements to chan_echolink: 1. There were many problems stemming from use of the astdb for the echolink station entries. This has now been replaced with in-memory functionality. This included the /var/lib/asterisk/astdb file growing so large that the astdb didnt even work any more, and EXTREME slowness on writing to the database on ext4 filesystems. 2. There was a string buffer overflow problem if the connecting IP address had 3 digits in all 4 octets (e.g. 123.123.123.123). This caused intermittent (and in some cases consistent) failures in inbound connection authorization. 3. If an inbound connection is not recognized, it requests the latest info from the directory server, and lets the client automatically re-try the connection again (presumably after the download containing the clients information is completed) thus allowing the client to connect on the retry. 4. chan_echolink now has a couple of CLI commands: 'echolink debug level', 'echolink dbdump' and 'echolink dbget'. The latest versions of chan_echolink.c and app_rpt.c from SVN implement this. If you are going to upgrade, you *MUST* upgrade both chan_echolink *AND* app_rpt, since the interface between app_rpt and the chan_echolink database completely changed. Please let me know how it goes. If you find problems, let me know. Thanks. JIM WB6NIL

2 1

USB GPIO and Event handling
by Jim Duuuude 21 Oct '10

21 Oct '10

Is everyone that requested support of GPIO and/or event handling satisfied with the current state of the implementation?? Can this issue be 'put to bed'? Are there any more pending things to be concerned with in this realm currently?? If there is nothing else, I will duplicate the GPIO handling that was added into chan_usbradio into chan_simpleusb and basically consider it done for now. JIM WB6NIL

2 2