August 2018 - App_rpt-users - lists.keekles.org

Re: [App_rpt-users] App_rpt-users Digest, Vol 114, Issue 12
by George Csahanin 12 Aug '18

12 Aug '18

I know the list has bigger issues but I just resolved my problem. Got the IP address off by a digit in one of the nodes rpt.conf. Works fine now. Now back to our larger issues... GeorgeC On 8/12/2018 11:00 AM, app_rpt-users-request(a)lists.allstarlink.org wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users(a)lists.allstarlink.o > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request(a)lists.allstarlink.org > > You can reach the person managing the list at > app_rpt-users-owner(a)lists.allstarlink.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > This site is dedicated to the memory of Jim Dixon WB6NIL > > > Today's Topics: > > 1. odd connect problem (George Csahanin) > 2. Re: odd connect problem (David KE6UPI) > 3. AllStarLink Maintenance followup (Bryan Fields) > 4. Re: AllStarLink Maintenance followup (David McGough) > 5. Re: AllStarLink Maintenance followup (Bryan Fields) > 6. Re: AllStarLink Maintenance followup (ARS W5OMR) > 7. BIG registration problem this morning (Paul - KN2R) > 8. Re: BIG registration problem this morning (Tim Sawyer) > 9. Re: BIG registration problem this morning (Paul - KN2R) > 10. Re: BIG registration problem this morning (Bryan Fields) > 11. Re: BIG registration problem this morning (Paul - KN2R) > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users --- This email has been checked for viruses by AVG. https://www.avg.com

1 0

AllStarLink Maintenance followup
by Bryan Fields 12 Aug '18

12 Aug '18

Our maintenance was completed successfully. AllStar Link is now running a geographically redundant registration cluster! This removes any single failure point from core AllStar services; a major advance in network reliability. Should any node in this cluster go offline, it will be removed and registration will fail over to another server. Most users have registered on the new system without issue. Some older installs may need to restart asterisk or their server to pickup the new IP address of the servers. After some late night debugging, the phone portal is working too. Should you still have issues, please drop a reply on list or to helpdesk(a)allstarlink.org and the admin team will look into it asap. We'd also like to announce a system services front end: https://grafana.allstarlink.org/ This is a public view of the core systems we run and their real time status. We'll post a more detailed update later today, however now we all need to get some sleep. 73's The AllStarLink Operations Team

3 3

odd connect problem
by George Csahanin 12 Aug '18

12 Aug '18

These were connecting fine earlier in the day and I'm lost as to why these two nodes cannot connect. 1999 reports: WARNING[8067]: chan_iax2.c:9221 socket_process: Call rejected by 192.168.1.202: No such context/extension 2360 reports: NOTICE[6374]: chan_iax2.c:4071 __auto_congest: Auto-congesting call due to slow response in rpt.conf they both have lines under [nodes] that point to each other. They can ping each other. I hate to say it but I'm lost on this one... GeorgeC W2DB --- This email has been checked for viruses by AVG. https://www.avg.com

2 1

AllStar Network Maintenance Announcement
by Bryan Fields 11 Aug '18

11 Aug '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 AllStar Network Maintenance Announcement 10 August 2018 Summary During the evening on Sunday August 12, 2018 between 0400 to 0600 UTC, the AllStar Operations Team will perform a migration of registration and nodes servers. During this time, registration may be unavailable, and/or the portal may be unavailable via the website and via phone. We expect this migration to be completed in two hours time or backed out. Detailed notes AllStarLink is committed to the availability of our core network services. That's why we are migrating registration onto a modern server system. Our current server is about 9 years old and while we've seen no failures of hardware, prudent engineering dictates it must be replaced with newer hardware. The current server does much more than IAX registration of nodes; there's database, web portal, SIP access, proxy, nodelist generation and more. Many of these functions are not core network functions, meaning if the function is down, users can still register nodes and connect to other nodes. An example of this is the stats server, or the web portal. Either can be offline, but the network will still function. The Operations Team has built and tested a new registration server and new nodes servers which serve up the extnodes database files. Our team has been testing this for the last few months internally, and believes it's ready for production. We expect a much faster convergence time for node registration due to our new faster servers, better scripting and lighter load the servers. Our testing includes all major and historical AllStar versions, dating back to limey linux and ACID. We know many users have older hardware installed on a mountain or other inaccessible site, and requiring a node upgrade is not feasible. Any users requiring un-interrupted service between AllStar nodes are encouraged to use permanent linking and/or statically define nodes in their rpt.conf [nodes] section. Additional information A MOP or Method of Procedure is in-place for this maintenance with clear go/no-go steps and a back-out plan should we find any insurmountable problems. An update will be posted to the app_rpt mailing list once this is completed. The AllStarLink app_rpt mailing list provides a discussion forum and access to the admin and development teams. We encourage all users to join and participate. http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users Status of this Notice This notice provides information for the community. Distribution of this notice is unlimited. Copyright Copyright (C) AllStarLink, Inc (2018). All Rights Reserved. - -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEaESdNosUjpjcN/JhYTmgYVLGkUAFAlttHpEACgkQYTmgYVLG kUDaOg/+Pv3u50uvv+3fNRP/Bof7MRKN/8w3MYTaA2Nj4F3PSNkuC1849S6pa6fN 2kzdF/X3Suo4uLizFoJf2rAuARMZw3i2uhb4pFvFqie0ZExYsPdgnoHM8Lu2b09l IyxK5gqT6evo3wdFkUZZftFjedcxxVth4ITDaoQwOkOfMXC+wstVyZ/7uzOLC62I PohtyOPHoSx2J+jBTV8rVOgIt6BciE40njg8LMJVVuKevepoaJ/tc4i2vA57BWFY 44LW7Dg1Lt2YMJciuITps+z+7WvV/4bFNJ2lnRnN+TmZY60GHWe6arouUUJP+rnV 5G5UiVLuWaq57Sa7e+824ZWDvcR9rEwlBQSrc2uxn82jyXjBNlPqx51qNsWe+FgY qxRCy1HewZIaQhEssNutHahn8rAuxy4khi7eKX6iKzuAhvL1mNpqpJk2h1AfC84x FunJI9FrLcwpc+aXqIE8jAoik0vRkbu9YHv+MaU9KLb0YtYisgR0t3glmNnMUsGc JOkFOWxGJyakxbGS9qRhulEwkFviC2ZFFkuCThAf7QHpSwQbPNMbkLBBTHtlZp32 A7pLGBXyq0/1B2PW4Lnj/PHP2xYnP9P/zLdlXJvSKyxYIPwl25MTofINYYmX3pGv kV/dXco8KF80d15bdBkaSUB/bIKxWthBdW7U7UNO0Gw0GBDmaE4= =qLTz -----END PGP SIGNATURE-----

2 1

Using a handmic while using a URI
by Noah Chalker 09 Aug '18

09 Aug '18

Hey folks, I am still planning out the setup for my node. One issue that came up is that of microphones. With the URI, I will have to connect it to the microphone jack of the radio using a RJ45 and to the speaker output. The speaker problem can be easily solved with a splitter. As far as the mic goes, I am a bit confused. If the URI is plugged into the mic port, I obviously cannot use the radio with a hand mic. Is there a way that I can simultaneously use the radio with a RJ45 mic connector at the same time that the URI is connected? KE5VQL Noah

4 7

RA 35's and Rpt config file
by Loren Tedford 07 Aug '18

07 Aug '18

Greetings so sorry for the delay everything went well with surgery but i stepped on a wallwart and messed up my left foot for awhile so i hadn't been around to play on my repeater stuff until today.. My boyfriend KC9ZHR purchased two ra 35's after the recommendation on this list after our repeater locked open on us one night back in April. I need to know what to put into the rpt.conf under rxchannel= ?? Thanks again hope everyone is well 73 Loren Tedford (KC9ZHV)

2 1

Android IAXRPT
by Steve Zingman 07 Aug '18

07 Aug '18

I have been told there is some FUD (fake news) floating around about Android IAXRPT. This is a post from Mike N4IRR on the DVSwitch list: - I am going to post a new version "soon" with better layouts for small screens - Possible a version that supports an in-app purchase for macros - USRP support for Analog_Bridge so it works like my iOS app for access to all digital modes. - Bug fixes for auto-reconnect. Not sure when this would be ready, I have too many projects... -- Why don't I get email from Doogie telling me I should run a different version of AllStarLink?

1 0

Disable Receiver for X milliseconds after TX UNKEY
by Skyler F 07 Aug '18

07 Aug '18

I am dealing with a system (half duplex), which sends a pulse through the network. I've had this question quite a bit, but never been able to word it right. Hope this is understandable. This "ping pong" issue only occurs after the transmitter is unkeyed. There is no way to fix this in hardware ( don't need to complicate it by going into technical details on how the link is setup) RXONDELAY WORKS, but it is sort of pointless because now the beginning of everybody's transmission gets cut off, and is physically does not need to be. We are really looking for TX UNKEYS ------> Disable RX ------ > Wait 1/4 second ------> Enable RX NOT RXONDELAY: USER KEYS ---> DISABLE RX ------> WAIT 1/4 Second -----> ENABLE RX Is there any way to perform the function in mind? ( in either usbradio, or simpleusb). Has anybody here thought about this before? Thank You, Skyler KDØWHB

5 7

Admin Email Announcement
by Bryan Fields 07 Aug '18

07 Aug '18

If you've sent an email to admin(a)allstarlink.org over the past few months you may see follow up email with a subject of [AllStar #nnn]. AllStar has recently implemented a ticketing system to better track admin requests, and ensure they are responded to in a timely manner. The last few months of admin correspondence has been entered in this new system, to ensure everything has been responded to and resolved. If you have received one of these [AllStar #nnn] emails, please either respond to that email and let us know it's been resolved or that you still require assistance. You may login to https://rt.allstarlink.org using your callsign and portal password to update it as well. We've updated the support page to show helpdesk(a)allstarlink.org as the primary contact address if to get in touch with an admin. For general configuration and setup help, the mailing list is still the best way to get community support. 73's The AllStar Admin Team, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 0

Re: [App_rpt-users] [arm-allstar] Node registration failures
by Tim Sawyer 06 Aug '18

06 Aug '18

We looked that up last night and I'm just getting around to posting this now, sorry for the delay. See below: The UDP port comes from the Allstar portal (as configured by the user). The port is reported to the Allstar database by the node itself. As you can see they are different. That generally happens when the users router is not port forwarded correctly. ISP blocking the port would cause the same problem. +-------+----------------+---------+-------+-----------------+----------+ | name | ipaddr | udpport | port | node_remotebase | proxy_ip | +-------+----------------+---------+-------+-----------------+----------+ | 46831 | 198.40.x.x | 4565 | 44288 | | | +-------+----------------+---------+-------+-----------------+----------+ On Sat, Jun 23, 2018 at 7:46 PM "David McGough via arm-allstar" < arm-allstar(a)hamvoip.org> wrote: > > Hi Chris, > > I'm glad you were able to get going again. As for UDP port 4569 being > blocked???? Interesting.... If you've got some time in the next few days, > I'd like to perform some brief testing, too. > > I use AT&T 4G hotspots extensively, in several areas of the USA, and > haven't uncountered port 4569 being blocked, so far. > > > 73, David KB4FXC > > > On Sat, 23 Jun 2018, "Chris Zenchenko via arm-allstar" wrote: > > > Lots of help from Allstar admin team and we now know a part of what is > going > > on. > > AT&T is filtering outbound VOIP on my port 4569. > > Much thanks as I said goes to the server admin folks that spent a huge > > amount of their Saturday tracing and debugging the traffic to and from my > > network. > > 73 > > > > > > -----Original Message----- > > From: arm-allstar <arm-allstar-bounces(a)hamvoip.org> On Behalf Of "David > > McGough via arm-allstar" > > Sent: Saturday, June 23, 2018 11:08 AM > > To: "Chris Zenchenko via arm-allstar" <arm-allstar(a)hamvoip.org> > > Cc: David McGough <kb4fxc(a)inttek.net>; Chris Zenchenko <wb9rsq(a)me.com> > > Subject: Re: [arm-allstar] Node registration failures > > > > > > Chris, > > > > Many of us are playing Field Day, today. We'll help you find a > resolution > > just as soon as we get a moment to breath. > > > > 73, David KB4FXC > > > > > > On Sat, 23 Jun 2018, "Chris Zenchenko via arm-allstar" wrote: > > > > > Following up on this. > > > It has been a week and my nodes still won't register. > > > The nscheck returns good on all look-ups. > > > The ping to register.allstarlink.org returns just fine. > > > The nodes just won't register. > > > I've left the computer off for anywhere from 5 minutes to over an hour. > > > There must be some log or something that can tell me why the server > won't > > > register my nodes. > > > It did in the past as indicated in my earlier message. > > > I'm completely stuck. > > > > > > > > > -----Original Message----- > > > From: arm-allstar <arm-allstar-bounces(a)hamvoip.org> On Behalf Of "Doug > > > Crompton via arm-allstar" > > > Sent: Tuesday, June 19, 2018 10:26 AM > > > To: ARM Allstar <arm-allstar(a)hamvoip.org> > > > Cc: Doug Crompton <wa3dsp(a)gmail.com> > > > Subject: Re: [arm-allstar] Node registration failures > > > > > > Chris, > > > > > > It seems you are doing everything right and since it is happening on > > > multiple nodes it is not anything you are doing. The problem is the > > Allstar > > > registration server which we know has problems. The fact that you are > > > having the problem might be related to, but not the fault of, your > > Internet > > > connection. If a connection goes down and you lose registration using > the > > > current registration system it could fail to return in some cases. This > > > could happen in just a minute or two. When this happens as you have > found > > > out the only answer is to go completely offline for a period and then > > > return. > > > > > > The answer is a new registration server which we are about to > introduce. > > So > > > if you can bear with it for a bit we should have an answer and since > you > > > are apparently experiencing this problem consistently you would be a > prime > > > candidate for a beta test. This will be happening very soon. > > > > > > > > > *73 Doug* > > > > > > *WA3DSP* > > > > > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>* > > > > > > > > > On Tue, Jun 19, 2018 at 11:14 AM, "Chris Zenchenko via arm-allstar" < > > > arm-allstar(a)hamvoip.org> wrote: > > > > > > > Looking for ways to troubleshoot an on-going problem with nodes > failing > > to > > > > register. > > > > > > > > 1. No changes in server info on allstar.org. > > > > 2. 2. No changes in .conf files > > > > 3. 3. No changes in public ip of server with nodes. > > > > 4. 4. 60 minutes or more with node server powered down. > > > > 5. 5. Nodes registered and working and connecting at times. > > > > 6. Using new dns method. > > > > 7. 7. Confirmed pings to allstar registration server. > > > > 8. 8. Successful pings to servers during system_diagnostics. > > > > 9. Code updates have been run. > > > > > > > > This registration problem has been popping up over the past two > months > > or > > > > so. > > > > In the latest case I was out of town for 5 days. > > > > When I left nodes were connecting and all was well. > > > > When I returned nodes could not connect and check_reg returned > > > > unregistered. > > > > See above points. > > > > I have no idea where to look next but stability just doesn't exist. > > > > In the past I have tried the 5 to 10 minute power off with success > but > > it > > > > shouldn't be necessary several times per week. > > > > The latest failure to register has gone on since Sunday evening and > > still > > > > wasn't working this morning. > > > > There must be a logical reason for this but I can't find it. > > > > Any thoughts would be helpful > > > > tnx > > > > > > > > _______________________________________________ > > > > > > > > arm-allstar mailing list > > > > arm-allstar(a)hamvoip.org > > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar > > > > > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org > > > > > > > _______________________________________________ > > > > > > arm-allstar mailing list > > > arm-allstar(a)hamvoip.org > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar > > > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org > > > > > > _______________________________________________ > > > > > > arm-allstar mailing list > > > arm-allstar(a)hamvoip.org > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar > > > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org > > > > > > > _______________________________________________ > > > > arm-allstar mailing list > > arm-allstar(a)hamvoip.org > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org > > > > _______________________________________________ > > > > arm-allstar mailing list > > arm-allstar(a)hamvoip.org > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org > > > > _______________________________________________ > > arm-allstar mailing list > arm-allstar(a)hamvoip.org > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar > > Visit the BBB and RPi2/3 web page - http://hamvoip.org > -- Tim WD6AWP

1 0