From Bob at Fot.com.au Wed Aug 1 08:16:06 2018 From: Bob at Fot.com.au (Bob) Date: Wed, 01 Aug 2018 16:16:06 +0800 Subject: [App_rpt-users] NanoPi In-Reply-To: <384997c2-9382-16d4-5560-e68c64219726@msgstor.com> References: <0c7901d423f2$ebcc4e80$c364eb80$@Fot.com.au> <1d855e82-661c-6840-b52c-2b6e2d70bc82@msgstor.com> <0d5d01d424df$7bb34480$7319cd80$@Fot.com.au> <3B526312-1907-4FFA-82A8-0AB6DA0460F1@gmail.com> <384997c2-9382-16d4-5560-e68c64219726@msgstor.com> Message-ID: <164f48ef170.279b.3abf4921a338d2d55223dfb5f6d5c2e6@Fot.com.au> Hi Steve Thks for the response ! Where can I download the solution ? Thks for all your work 73 Bob VK6ZGN On 26 July 2018 21:56:18 Steve Zingman wrote: > JJ is correct. When the kernel was updated the new kernel no longer > supports OSS. While waiting for JJ to publish his work around or for the > dev team to produce a nono OSS channel driver, I'll post the info to put > the kernel and headers on hold to keep OSS support. > I'll have the info up by tomorrow morning. > > Steve N4IRS > > > On 7/26/2018 9:08 AM, JJC wrote: >> This is because OSS is not supported and marked as broken in current Linux >> distributions. You can either use a kernel that has it compiled in or you >> can do what I did and use: >> >> ALSA >> PulseAudio >> osspd (emulates oss through pulse) >> >> I?ll write up some basic instructions for how mine is working... but the >> net of it it is that without /dev/dsp1 your asl can?t send or receive audio >> via your sound card (URI) >> >> Maybe I?m talking out of turn, I did not read the entire thread back. >> >> >> Sent from the iRoad >> >> On Jul 26, 2018, at 07:52, Bob Good wrote: >> >>> Hi Steve >>> >>> >>> >>> Thanks that worked?? However now all seems to load and registers OK but >>> SimpleUSB wont loa/run ? >>> >>> >>> >>> return email: Bob at Fot.com.au >>> >>> >>> >>> NODE=47324 >>> >>> REGPASS=47324:xxxxxx at register.allstarlink.org ; This must be >>> changed to your node number, password >>> >>> >>> >>> >>> >>> >>> >>> Call sign: VK6ZGN >>> >>> Interface type: SimpleUSB/usb_47324 ; SimpleUSB >>> >>> Echolink Callsign: INVALID >>> >>> Echolink node: 000000 ASL node used: >>> >>> >>> >>> Ping test to 8.8.8.8 >>> >>> PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. >>> >>> 64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=77.5 ms >>> >>> 64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=70.6 ms >>> >>> 64 bytes from 8.8.8.8: icmp_seq=3 ttl=117 time=84.1 ms >>> >>> 64 bytes from 8.8.8.8: icmp_seq=4 ttl=117 time=84.4 ms >>> >>> >>> >>> --- 8.8.8.8 ping statistics --- >>> >>> 4 packets transmitted, 4 received, 0% packet loss, time 3004ms >>> >>> rtt min/avg/max/mdev = 70.664/79.212/84.453/5.656 ms >>> >>> >>> >>> Ping test to register.allstarlink.org >>> >>> PING register.allstarlink.org (67.215.233.178) 56(84) bytes of data. >>> >>> 64 bytes from seal.lambdatel.com (67.215.233.178): icmp_seq=1 ttl=50 >>> time=209 ms >>> >>> 64 bytes from seal.lambdatel.com (67.215.233.178): icmp_seq=2 ttl=50 >>> time=208 ms >>> >>> 64 bytes from seal.lambdatel.com (67.215.233.178): icmp_seq=3 ttl=50 >>> time=208 ms >>> >>> 64 bytes from seal.lambdatel.com (67.215.233.178): icmp_seq=4 ttl=50 >>> time=208 ms >>> >>> >>> >>> --- register.allstarlink.org ping statistics --- >>> >>> 4 packets transmitted, 4 received, 0% packet loss, time 3004ms >>> >>> rtt min/avg/max/mdev = 208.471/208.709/209.006/0.220 ms >>> >>> >>> >>> Ouput of ifconfig >>> >>> eth0: flags=4163 mtu 1500 >>> >>> inet 192.168.168.39 netmask 255.255.255.0 broadcast 192.168.168.255 >>> >>> inet6 fe80::4f:49ff:fe38:5803 prefixlen 64 scopeid 0x20 >>> >>> ether 02:4f:49:38:58:03 txqueuelen 1000 (Ethernet) >>> >>> RX packets 1641 bytes 149786 (146.2 KiB) >>> >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> >>> TX packets 1781 bytes 554581 (541.5 KiB) >>> >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> >>> device interrupt 33 >>> >>> >>> >>> lo: flags=73 mtu 65536 >>> >>> inet 127.0.0.1 netmask 255.0.0.0 >>> >>> inet6 ::1 prefixlen 128 scopeid 0x10 >>> >>> loop txqueuelen 1000 (Local Loopback) >>> >>> RX packets 16 bytes 1312 (1.2 KiB) >>> >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> >>> TX packets 16 bytes 1312 (1.2 KiB) >>> >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> >>> >>> >>> >>> >>> Output of lsmod grep dahdi >>> >>> dahdi 200704 28 >>> >>> >>> >>> IAX2 registry >>> >>> Host dnsmgr Username Perceived Refresh State >>> >>> 67.215.233.178:4569 Y 47324 58.178.114.94:64301 60 >>> Registered >>> >>> >>> >>> Asterisk version: >>> >>> Asterisk GIT Version adaec47 built by root @ odroidxu4 on a armv7l running >>> Linux on 2018-03-07 14:53:41 UTC >>> >>> >>> >>> Current date and time: 2018-07-26.04:32 >>> >>> >>> >>> updatenodelist service running? >>> >>> root 682 0.0 0.4 4428 2384 ? Ss 04:29 0:00 /bin/bash >>> /usr/local/bin/rc.updatenodelist & >>> >>> root 1650 0.0 0.1 3764 560 pts/2 S+ 04:35 0:00 grep >>> updatenodelist >>> >>> >>> >>> /tmp/rpt_extnodes-temp file >>> >>> -rw-r--r-- 1 root root 0 Jul 26 04:30 /tmp/rpt_extnodes-temp >>> >>> >>> >>> /var/lib/asterisk/rpt_extnodes file >>> >>> -rwx------ 1 root root 140551 Jul 26 04:26 /var/lib/asterisk/rpt_extnodes >>> >>> >>> >>> ####### Begin warnings from messages file >>> >>> [Jul 26 04:26:42] WARNING[987] chan_simpleusb.c: Loaded parameters from >>> simpleusb_tune_usb_47324.conf for device usb_47324 . >>> >>> [Jul 26 04:26:42] WARNING[987] chan_simpleusb.c: Unable to re-open DSP >>> device 1 (usb_47324): No such file or directory >>> >>> [Jul 26 04:26:42] WARNING[986] chan_simpleusb.c: Unable to re-open DSP >>> device 1 (usb_47324): No such file or directory >>> >>> And so on forever !! >>> >>> >>> >>> ####### Begin warnings from messages.1 file >>> >>> >>> >>> 73 >>> >>> Bob >>> >>> VK6ZGN >>> >>> >>> >>> From: App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] On >>> Behalf Of Steve Zingman >>> Sent: Wednesday, 25 July 2018 17:58 >>> To: Users of Asterisk app_rpt >>> Subject: Re: [App_rpt-users] NanoPi >>> >>> >>> >>> Bob, >>> It looks like DKMS did not rebuild DAHDI properly. >>> >>> Please do as root: >>> dpkg-reconfigure asl-dahdi-linux-dkms >>> reboot >>> >>> Should now be fixed. Check DAHDI is running by: >>> lsmod | grep dahdi >>> >>> 73, Steve N4IRS >>> >>> On 07/25/2018 04:38 AM, Bob Good wrote: >>> >>> >>> >>> Hi Guys >>> >>> >>> >>> I have tried loading ASL_1.01-20180228-armhf-nanopi image onto a NanoPi >>> >>> >>> >>> Seems to load fine I run the updates etc then the Menu >>> all seems OK but AllStar does not seem to run ? >>> >>> >>> >>> return email: bob at Fot.com.au >>> >>> >>> >>> NODE=47324 >>> >>> REGPASS=47324:xxxxx at register.allstarlink.org ; This must be >>> changed to your node number, password >>> >>> >>> >>> >>> >>> >>> >>> Anyone got any ideas ?? >>> >>> >>> >>> 73 >>> >>> VK6ZGN >>> Bob Bob at Fot.com.au >>> Western Australia Mob. 61 (0) 418 902 194 >>> >>> The contents of this e-mail (including any attachments) may be >>> confidential and privileged. Any unauthorised use of this document >>> or it's contents is prohibited. If you have received this e-mail in >>> error, please notify us immediately and erase this document >>> E&OE >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit >>> http://lists.allstarlink.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. >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit >>> http://lists.allstarlink.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. >> >> >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg at gmohr.com Wed Aug 1 16:57:08 2018 From: Greg at gmohr.com (Greg Mohr) Date: Wed, 1 Aug 2018 16:57:08 +0000 Subject: [App_rpt-users] After last update to audio is not working Message-ID: I just updated to the most recent version of the Allstar image and my audio on my repeater disappeared. I can key up the system and it will reply back with the courtesy tone and the required ID every 15 minutes. It just doesn't transmit the audio through when someone trys to call out to another person. I checked the cables and radios and all are up and running and connected fine. I have disconnectged the cables and plugged them back in to test and the same lack of audio occurs. When I plug in the old ham-o-matic, audio comes through. Where should I be looking to check audio settings for the Motorola gm300 radios in the rpt.conf file? Thank you, Greg W2GCM -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at midnighteng.com Wed Aug 1 17:08:30 2018 From: mm at midnighteng.com (Mike) Date: Wed, 1 Aug 2018 13:08:30 -0400 Subject: [App_rpt-users] After last update to audio is not working In-Reply-To: References: Message-ID: You did not state method of audio at app_rpt but double check your usb 'id of the audio device' and then look for corruptions in usbradio/simpleusb in the form of hidden characters. (use notepad+++ or similar 'show all characters') Also, did you re-write any of those config files and do you have the switching logic of cor correct. It's a place to start. ...mike/kb8jnm On 8/1/2018 12:57 PM, Greg Mohr wrote: > I just updated to the most recent version of the Allstar image and my audio on my repeater disappeared. I can key up the system and it will reply back with the courtesy tone and the required ID every 15 minutes. It just doesn't transmit the audio through when someone trys to call out to another person. > > I checked the cables and radios and all are up and running and connected fine. I have disconnectged the cables and plugged them back in to test and the same lack of audio occurs. When I plug in the old ham-o-matic, audio comes through. Where should I be looking to check audio settings for the Motorola gm300 radios in the rpt.conf file? > > Thank you, > Greg > W2GCM > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > From cummingsj at gmail.com Wed Aug 1 17:27:53 2018 From: cummingsj at gmail.com (JJC) Date: Wed, 1 Aug 2018 11:27:53 -0600 Subject: [App_rpt-users] After last update to audio is not working In-Reply-To: References: Message-ID: <613D5969-B5AB-4942-AAA8-9217947940D2@gmail.com> Log review for errors is also a good place to start Sent from the iRoad > On Aug 1, 2018, at 11:08, Mike wrote: > > You did not state method of audio at app_rpt but double check your usb 'id of the audio device' and then look for corruptions in usbradio/simpleusb in the form of hidden characters. > (use notepad+++ or similar 'show all characters') > Also, did you re-write any of those config files and do you have the switching logic of cor correct. > > It's a place to start. > > ...mike/kb8jnm > >> On 8/1/2018 12:57 PM, Greg Mohr wrote: >> I just updated to the most recent version of the Allstar image and my audio on my repeater disappeared. I can key up the system and it will reply back with the courtesy tone and the required ID every 15 minutes. It just doesn't transmit the audio through when someone trys to call out to another person. >> I checked the cables and radios and all are up and running and connected fine. I have disconnectged the cables and plugged them back in to test and the same lack of audio occurs. When I plug in the old ham-o-matic, audio comes through. Where should I be looking to check audio settings for the Motorola gm300 radios in the rpt.conf file? >> Thank you, >> Greg >> W2GCM >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> To unsubscribe from this list please visit http://lists.allstarlink.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. > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. From kb4fxc at inttek.net Wed Aug 1 17:29:02 2018 From: kb4fxc at inttek.net (David McGough) Date: Wed, 1 Aug 2018 13:29:02 -0400 (EDT) Subject: [App_rpt-users] After last update to audio is not working In-Reply-To: Message-ID: For a full repeater, make sure you have duplex=2 in your rpt.conf node stanza. ...From your description, you may be configured in duplex=1. 73, David KB4FXC On Wed, 1 Aug 2018, Greg Mohr wrote: > I just updated to the most recent version of the Allstar image and my audio on my repeater disappeared. I can key up the system and it will reply back with the courtesy tone and the required ID every 15 minutes. It just doesn't transmit the audio through when someone trys to call out to another person. > > I checked the cables and radios and all are up and running and connected fine. I have disconnectged the cables and plugged them back in to test and the same lack of audio occurs. When I plug in the old ham-o-matic, audio comes through. Where should I be looking to check audio settings for the Motorola gm300 radios in the rpt.conf file? > > Thank you, > Greg > W2GCM > > > From cummingsj at gmail.com Wed Aug 1 22:19:24 2018 From: cummingsj at gmail.com (JJC) Date: Wed, 1 Aug 2018 16:19:24 -0600 Subject: [App_rpt-users] ASL without OSS Message-ID: So it's a quick and dirty post but it's all that I had time to do.... Please be sure to read the whole thing including the "CAVEATS" section if you try this at home lol... http://enhanced.github.io/2018/08/ASL_With_ALSA Using the info that I posted at the above URL I have a current kernel running and very clean audio, please note the TO-DO section also.. because the "clean" part is anecdotal. Please let me know if something isn't working for you (or if it is) and we can adjust fire to compensate as needed.. N0PKT Jay -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg at gmohr.com Fri Aug 3 01:23:25 2018 From: Greg at gmohr.com (Greg Mohr) Date: Fri, 3 Aug 2018 01:23:25 +0000 Subject: [App_rpt-users] App_rpt-users Digest, Vol 114, Issue 2 In-Reply-To: References: Message-ID: David, Your tip did the trick! Why would an update change the rpt.conf duplex setting to 1 from 2? All other settings stayed the same. Thank you! Greg, W2GCM -----Original Message----- From: App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] On Behalf Of app_rpt-users-request at lists.allstarlink.org Sent: Thursday, August 02, 2018 12:00 PM To: app_rpt-users at lists.allstarlink.org Subject: App_rpt-users Digest, Vol 114, Issue 2 Send App_rpt-users mailing list submissions to app_rpt-users at lists.allstarlink.org 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 at lists.allstarlink.org You can reach the person managing the list at app_rpt-users-owner at 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. After last update to audio is not working (Greg Mohr) 2. Re: After last update to audio is not working (Mike) 3. Re: After last update to audio is not working (JJC) 4. Re: After last update to audio is not working (David McGough) 5. ASL without OSS (JJC) ---------------------------------------------------------------------- Message: 1 Date: Wed, 1 Aug 2018 16:57:08 +0000 From: Greg Mohr To: "app_rpt-users at lists.allstarlink.org" Subject: [App_rpt-users] After last update to audio is not working Message-ID: Content-Type: text/plain; charset="us-ascii" I just updated to the most recent version of the Allstar image and my audio on my repeater disappeared. I can key up the system and it will reply back with the courtesy tone and the required ID every 15 minutes. It just doesn't transmit the audio through when someone trys to call out to another person. I checked the cables and radios and all are up and running and connected fine. I have disconnectged the cables and plugged them back in to test and the same lack of audio occurs. When I plug in the old ham-o-matic, audio comes through. Where should I be looking to check audio settings for the Motorola gm300 radios in the rpt.conf file? Thank you, Greg W2GCM -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Wed, 1 Aug 2018 13:08:30 -0400 From: Mike To: app_rpt-users at lists.allstarlink.org Subject: Re: [App_rpt-users] After last update to audio is not working Message-ID: Content-Type: text/plain; charset=windows-1252; format=flowed You did not state method of audio at app_rpt but double check your usb 'id of the audio device' and then look for corruptions in usbradio/simpleusb in the form of hidden characters. (use notepad+++ or similar 'show all characters') Also, did you re-write any of those config files and do you have the switching logic of cor correct. It's a place to start. ...mike/kb8jnm On 8/1/2018 12:57 PM, Greg Mohr wrote: > I just updated to the most recent version of the Allstar image and my audio on my repeater disappeared. I can key up the system and it will reply back with the courtesy tone and the required ID every 15 minutes. It just doesn't transmit the audio through when someone trys to call out to another person. > > I checked the cables and radios and all are up and running and connected fine. I have disconnectged the cables and plugged them back in to test and the same lack of audio occurs. When I plug in the old ham-o-matic, audio comes through. Where should I be looking to check audio settings for the Motorola gm300 radios in the rpt.conf file? > > Thank you, > Greg > W2GCM > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > ------------------------------ Message: 3 Date: Wed, 1 Aug 2018 11:27:53 -0600 From: JJC To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] After last update to audio is not working Message-ID: <613D5969-B5AB-4942-AAA8-9217947940D2 at gmail.com> Content-Type: text/plain; charset=us-ascii Log review for errors is also a good place to start Sent from the iRoad > On Aug 1, 2018, at 11:08, Mike wrote: > > You did not state method of audio at app_rpt but double check your usb 'id of the audio device' and then look for corruptions in usbradio/simpleusb in the form of hidden characters. > (use notepad+++ or similar 'show all characters') Also, did you > re-write any of those config files and do you have the switching logic of cor correct. > > It's a place to start. > > ...mike/kb8jnm > >> On 8/1/2018 12:57 PM, Greg Mohr wrote: >> I just updated to the most recent version of the Allstar image and my audio on my repeater disappeared. I can key up the system and it will reply back with the courtesy tone and the required ID every 15 minutes. It just doesn't transmit the audio through when someone trys to call out to another person. >> I checked the cables and radios and all are up and running and connected fine. I have disconnectged the cables and plugged them back in to test and the same lack of audio occurs. When I plug in the old ham-o-matic, audio comes through. Where should I be looking to check audio settings for the Motorola gm300 radios in the rpt.conf file? >> Thank you, >> Greg >> W2GCM >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> To unsubscribe from this list please visit http://lists.allstarlink.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. > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. ------------------------------ Message: 4 Date: Wed, 1 Aug 2018 13:29:02 -0400 (EDT) From: David McGough To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] After last update to audio is not working Message-ID: Content-Type: TEXT/PLAIN; charset=US-ASCII For a full repeater, make sure you have duplex=2 in your rpt.conf node stanza. ...From your description, you may be configured in duplex=1. 73, David KB4FXC On Wed, 1 Aug 2018, Greg Mohr wrote: > I just updated to the most recent version of the Allstar image and my audio on my repeater disappeared. I can key up the system and it will reply back with the courtesy tone and the required ID every 15 minutes. It just doesn't transmit the audio through when someone trys to call out to another person. > > I checked the cables and radios and all are up and running and connected fine. I have disconnectged the cables and plugged them back in to test and the same lack of audio occurs. When I plug in the old ham-o-matic, audio comes through. Where should I be looking to check audio settings for the Motorola gm300 radios in the rpt.conf file? > > Thank you, > Greg > W2GCM > > > ------------------------------ Message: 5 Date: Wed, 1 Aug 2018 16:19:24 -0600 From: JJC To: Users of Asterisk app_rpt , app_rpt-users at ohnosec.org Subject: [App_rpt-users] ASL without OSS Message-ID: Content-Type: text/plain; charset="utf-8" So it's a quick and dirty post but it's all that I had time to do.... Please be sure to read the whole thing including the "CAVEATS" section if you try this at home lol... http://enhanced.github.io/2018/08/ASL_With_ALSA Using the info that I posted at the above URL I have a current kernel running and very clean audio, please note the TO-DO section also.. because the "clean" part is anecdotal. Please let me know if something isn't working for you (or if it is) and we can adjust fire to compensate as needed.. N0PKT Jay -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users ------------------------------ End of App_rpt-users Digest, Vol 114, Issue 2 ********************************************* From kb4fxc at inttek.net Fri Aug 3 01:44:27 2018 From: kb4fxc at inttek.net (David McGough) Date: Thu, 2 Aug 2018 21:44:27 -0400 (EDT) Subject: [App_rpt-users] App_rpt-users Digest, Vol 114, Issue 2 In-Reply-To: Message-ID: Hi Greg, I don't know why the duplex setting changed, but I'm glad that fixed it. 73, David KB4FXC On Fri, 3 Aug 2018, Greg Mohr wrote: > David, > > Your tip did the trick! Why would an update change the rpt.conf duplex setting to 1 from 2? All other settings stayed the same. > > Thank you! > > Greg, W2GCM > From k6ecm1 at gmail.com Fri Aug 3 03:49:07 2018 From: k6ecm1 at gmail.com (Bob Pyke) Date: Thu, 2 Aug 2018 20:49:07 -0700 Subject: [App_rpt-users] App_rpt-users Digest, Vol 114, Issue 2 In-Reply-To: References: Message-ID: This is significant. Has the ?documentation? in the examples/config file comments been updated? Thanks, Bob K6ECM 73 > On Aug 2, 2018, at 6:44 PM, David McGough wrote: > > > Hi Greg, > > I don't know why the duplex setting changed, but I'm glad that fixed it. > > > 73, David KB4FXC > > >> On Fri, 3 Aug 2018, Greg Mohr wrote: >> >> David, >> >> Your tip did the trick! Why would an update change the rpt.conf duplex setting to 1 from 2? All other settings stayed the same. >> >> Thank you! >> >> Greg, W2GCM >> > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. From aglorioso62 at gmail.com Fri Aug 3 12:04:54 2018 From: aglorioso62 at gmail.com (Angelo) Date: Fri, 3 Aug 2018 07:04:54 -0500 Subject: [App_rpt-users] Rxondelay in SimpleUsb Message-ID: ?Good morning all, ?I have been trying to set the rxondelay in the simpleusb to different values. No matter what value I put in, it seems the behavior does not change. I remember reading a while back that function may not be compiled standard release. ?I am running the new version of ASL. I think the release was in April of this year.? Can anyone confirm this? 73 de Angelo From Ramesh at va3uv.com Sat Aug 4 12:03:30 2018 From: Ramesh at va3uv.com (Ramesh Dhami) Date: Sat, 4 Aug 2018 08:03:30 -0400 Subject: [App_rpt-users] UPS for a PI 3 B+ Message-ID: Hi All: This topic comes up from time-to-time! Does anyone have experience with the following UPS HAT: http://www.pimodulescart.com/shop/item.aspx?itemid=50 The ordering options seems to be a little confusing! Additionally, what I am looking for is: 1.? Does this fully restore power once the battery has been discharged and the AC power is restored? - i.e., no buttons to press (my application is in an unattended / remote location) 2.? Is this the s/w that I need to install: https://github.com/modmypi/PiModules/wiki/UPS-PIco-Installation -> Any incompatibility / will it break a DIAL install? Thanks, Ramesh. VA3UV / KN4RSD #27919 (and others!) From mm at midnighteng.com Sat Aug 4 12:16:24 2018 From: mm at midnighteng.com (Mike) Date: Sat, 4 Aug 2018 08:16:24 -0400 Subject: [App_rpt-users] UPS for a PI 3 B+ In-Reply-To: References: Message-ID: <79b150b4-b9a7-9481-24f0-31e025750422@midnighteng.com> While I can't comment on that board, I might suggest, if you are just looking for a more simple method to do a battery power that can be recharged while live... Look on ebay for a few items... 18650 battery holder (3 or 4 cell) https://www.ebay.com/itm/DIY-Black-Storage-Box-Holder-Case-For-1-2-4-x-18650-3-7V-Rechargeable-Batteries/112896485215?_trkparms=aid%3D222007%26algo%3DSIM.MBE%26ao%3D2%26asc%3D52935%26meid%3Dc04f481f1ee842f8963405c64a8b587e%26pid%3D100005%26rk%3D6%26rkt%3D12%26sd%3D202350734774%26itm%3D112896485215&_trksid=p2047675.c100005.m1851 This little critter which will both charge the cells and bosst the output from 3.7v to 5v https://www.ebay.com/itm/USB-3-7V-Lithium-Li-ion-Battery-Charger-Module-4-2V-Boost-Step-Up-5V-9V-12V-24V/122534900120?rt=nc&_trkparms=aid%3D555018%26algo%3DPL.SIM%26ao%3D2%26asc%3D52935%26meid%3De907643b2c754f6ab88f7af65d18a77f%26pid%3D100005%26rk%3D2%26rkt%3D12%26mehot%3Dpp%26sd%3D263846439847%26itm%3D122534900120&_trksid=p2047675.c100005.m1851 There are many ways of doing the same thing. This method of course does not integrate with software to warn you about battery condition or do automated shutdown but do you really need it ??? anyway, food for thought, ...mike/kb8jnm On 8/4/2018 8:03 AM, Ramesh Dhami wrote: > Hi All: > > This topic comes up from time-to-time! > > Does anyone have experience with the following UPS HAT: > > http://www.pimodulescart.com/shop/item.aspx?itemid=50 > > The ordering options seems to be a little confusing! > > Additionally, what I am looking for is: > > 1.? Does this fully restore power once the battery has been discharged > and the AC power is restored? - i.e., no buttons to press (my > application is in an unattended / remote location) > > 2.? Is this the s/w that I need to install: > https://github.com/modmypi/PiModules/wiki/UPS-PIco-Installation -> Any > incompatibility / will it break a DIAL install? > > > Thanks, > > Ramesh. > > VA3UV / KN4RSD > > #27919 (and others!) > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. From david at kg5rdf.com Sat Aug 4 12:24:00 2018 From: david at kg5rdf.com (David) Date: Sat, 04 Aug 2018 07:24:00 -0500 Subject: [App_rpt-users] UPS for a PI 3 B+ In-Reply-To: Message-ID: This one works: https://www.amazon.com/dp/B01MQYX4UX?ref=yo_pop_ma_swf -------- Original message --------From: Ramesh Dhami Date: 8/4/18 7:03 AM (GMT-06:00) To: app_rpt-users at lists.allstarlink.org Subject: [App_rpt-users] UPS for a PI 3 B+ Hi All: This topic comes up from time-to-time! Does anyone have experience with the following UPS HAT: http://www.pimodulescart.com/shop/item.aspx?itemid=50 The ordering options seems to be a little confusing! Additionally, what I am looking for is: 1.? Does this fully restore power once the battery has been discharged and the AC power is restored? - i.e., no buttons to press (my application is in an unattended / remote location) 2.? Is this the s/w that I need to install: https://github.com/modmypi/PiModules/wiki/UPS-PIco-Installation -> Any incompatibility / will it break a DIAL install? Thanks, Ramesh. VA3UV / KN4RSD #27919 (and others!) _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at midnighteng.com Sat Aug 4 12:27:46 2018 From: mm at midnighteng.com (Mike) Date: Sat, 4 Aug 2018 08:27:46 -0400 Subject: [App_rpt-users] Rxondelay in SimpleUsb In-Reply-To: References: Message-ID: <58ac6fb5-0c1d-b6bd-8957-e10ec7bcc521@midnighteng.com> At this point in time, I'm not positive I remember the workings of rxondelay but... As I remember it, it is just a minimum value of time in miliseconds of a active cor before it validates in the software as a valid cor. I don't know if that helps but I seem to remember folks thinking it did something else many years ago so I thought I might brush on that. I also think there may have been issues under certain duplex modes but that is where my brain is probably fried...LOL... Anyway, what is the issue that you feel you need to use it in the first place? ...mike/kb8jnm On 8/3/2018 8:04 AM, Angelo wrote: > ?Good morning all, > > > ?I have been trying to set the rxondelay in the simpleusb to different > values. No matter what value I put in, it seems the behavior does not > change. I remember reading a while back that function may not be > compiled standard release. > > ?I am running the new version of ASL. I think the release was in April > of this year.? Can anyone confirm this? > > 73 de Angelo > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. From mm at midnighteng.com Sat Aug 4 12:58:19 2018 From: mm at midnighteng.com (Mike) Date: Sat, 4 Aug 2018 08:58:19 -0400 Subject: [App_rpt-users] Rxondelay in SimpleUsb In-Reply-To: References: Message-ID: <8ef199e0-5c26-e5b2-8ae4-7bde05766a56@midnighteng.com> Actually found this on the old drupal site: ;rxondelay=20 ; Uncomment and/or adjust for simplex nodes to eliminate "Ping ; Ponging" or "Relay Racing". ; A positive value here will instruct the usbradio driver to ignore ; the COR line for a specified number of 20mSec intervals following ; the release of PTT. Use this only on simplex nodes, and ; leave commented out for repeaters or other full duplex nodes. So, it has no effect on duplex modes. Perhaps there is hope for my brain...LOL... ...mike/kb8jnm On 8/3/2018 8:04 AM, Angelo wrote: > ?Good morning all, > > > ?I have been trying to set the rxondelay in the simpleusb to different > values. No matter what value I put in, it seems the behavior does not > change. I remember reading a while back that function may not be > compiled standard release. > > ?I am running the new version of ASL. I think the release was in April > of this year.? Can anyone confirm this? > > 73 de Angelo > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. From smccarthy61 at gmail.com Sat Aug 4 17:00:42 2018 From: smccarthy61 at gmail.com (Sean McCarthy) Date: Sat, 4 Aug 2018 13:00:42 -0400 Subject: [App_rpt-users] UPS for a PI 3 B+ In-Reply-To: References: Message-ID: I read that this board will not recharge the batteries without physical intervention, i.e. pressing the switch, after a power failure. this would make if fine unless you want unattended operation. On Sat, Aug 4, 2018 at 8:24 AM, David wrote: > This one works: > > https://www.amazon.com/dp/B01MQYX4UX?ref=yo_pop_ma_swf > > > -------- Original message -------- > From: Ramesh Dhami > Date: 8/4/18 7:03 AM (GMT-06:00) > To: app_rpt-users at lists.allstarlink.org > Subject: [App_rpt-users] UPS for a PI 3 B+ > > Hi All: > > This topic comes up from time-to-time! > > Does anyone have experience with the following UPS HAT: > > http://www.pimodulescart.com/shop/item.aspx?itemid=50 > > The ordering options seems to be a little confusing! > > Additionally, what I am looking for is: > > 1. Does this fully restore power once the battery has been discharged > and the AC power is restored? - i.e., no buttons to press (my > application is in an unattended / remote location) > > 2. Is this the s/w that I need to install: > https://github.com/modmypi/PiModules/wiki/UPS-PIco-Installation -> Any > incompatibility / will it break a DIAL install? > > > Thanks, > > Ramesh. > > VA3UV / KN4RSD > > #27919 (and others!) > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david at kg5rdf.com Sat Aug 4 17:20:29 2018 From: david at kg5rdf.com (David) Date: Sat, 04 Aug 2018 12:20:29 -0500 Subject: [App_rpt-users] UPS for a PI 3 B+ In-Reply-To: Message-ID: That not true works great, have two in the field at repeater sites. https://www.dropbox.com/s/05mdzjuqz87xi78/20180626_100527.jpg?dl=0 -------- Original message --------From: Sean McCarthy Date: 8/4/18 12:00 PM (GMT-06:00) To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] UPS for a PI 3 B+ I read that this board will not recharge the batteries without physical intervention, i.e. pressing the switch, after a power failure. this would make if fine unless you want unattended operation. On Sat, Aug 4, 2018 at 8:24 AM, David wrote: This one works: https://www.amazon.com/dp/B01MQYX4UX?ref=yo_pop_ma_swf -------- Original message --------From: Ramesh Dhami Date: 8/4/18 7:03 AM (GMT-06:00) To: app_rpt-users at lists.allstarlink.org Subject: [App_rpt-users] UPS for a PI 3 B+ Hi All: This topic comes up from time-to-time! Does anyone have experience with the following UPS HAT: http://www.pimodulescart.com/shop/item.aspx?itemid=50 The ordering options seems to be a little confusing! Additionally, what I am looking for is: 1.? Does this fully restore power once the battery has been discharged and the AC power is restored? - i.e., no buttons to press (my application is in an unattended / remote location) 2.? Is this the s/w that I need to install: https://github.com/modmypi/PiModules/wiki/UPS-PIco-Installation -> Any incompatibility / will it break a DIAL install? Thanks, Ramesh. VA3UV / KN4RSD #27919 (and others!) _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ramesh at va3uv.com Sat Aug 4 18:07:02 2018 From: Ramesh at va3uv.com (Ramesh Dhami) Date: Sat, 4 Aug 2018 14:07:02 -0400 Subject: [App_rpt-users] UPS for a PI 3 B+ In-Reply-To: References: Message-ID: On 2018-08-04 1:20 PM, David wrote: > That not true works great, have two in the field at repeater sites. > > https://www.dropbox.com/s/05mdzjuqz87xi78/20180626_100527.jpg?dl=0 > > <-- Great! - that's very interesting.? Among the FAQ's for that product, someone does reference the need to push a button.? I have a RAVPower USB bank - and it works great - but once the battery has discharged, it needs a button to be pushed.? I use the Allstar PI as a jump box to tunnel through to other devices on the same network - hence my need for the device to auto-recover and gracefully shutdown to avoid corruption of the SD card. I've been thinking about a UPS as I could use that to keep other devices powered up during a power outage.? It would be awesome to have a UPS where the AC outputs can be switched remotely (i.e., to recycle an appliance / device).? My initial thought was to use an IP9258T power bar. I'm currently using one of these: https://www.amazon.com/Jinvoo-Protector-Outlet-Charging-Station/dp/B071ZGDDQG/ref=sr_1_1_sspa?s=electronics&ie=UTF8&qid=1533405729&sr=1-1-spons&keywords=jinvoo+smart+plug&psc=1 The great thing about this is that it allows you to remotely control each output and the USB ports - the bad thing is that when there's a power outage, it seems to default to all outlets OFF and turns on the USB power..... DUH - since my RAVPower USB bank has been plugged into one of the AC outlets, the fact that the power bar defaults to OFF after a power outage, is forcing my USB battery bank to discharge over time. Cheers, Ramesh. VA3UV / KN4RSD -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Mon Aug 6 04:51:32 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Mon, 6 Aug 2018 00:51:32 -0400 Subject: [App_rpt-users] Fwd: Node 46831 is no longer in the database In-Reply-To: <3b6b62e0-497b-e51a-fc6e-ec4cbc9d9191@mycns.net> References: <3b6b62e0-497b-e51a-fc6e-ec4cbc9d9191@mycns.net> Message-ID: <4a41a66c-adc3-f732-9c4e-afdff73f8717@bryanfields.net> On 8/5/18 2:22 PM, "STAN SIEMS" wrote: > my node 46831 no longer shows up in the data base and I can not connect > to any nodes it has worked fine for over 6mo then quit there have been > no changes in programing It's likely you're behind NAT and your NAT device is no longer doing a static mapping. * Name : 46831 Secret : Context : radio-in Mailbox : Dynamic : Yes Callnum limit: 0 Calltoken req: No Trunk : No Callerid : "" <> Expire : 255260283 ACL : No Addr->IP : 198.40.250.201 Port 44288 Your port you have configured for that server is 4565, but it's using 44288 to register. It's not posting to the stats server at all, and looks like that is disabled in rpt.conf. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From tisawyer at gmail.com Mon Aug 6 14:11:35 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Mon, 6 Aug 2018 07:11:35 -0700 Subject: [App_rpt-users] [arm-allstar] Node registration failures In-Reply-To: References: <00c701d40b1a$88d7b440$9a871cc0$@me.com> Message-ID: 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 at 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 On Behalf Of "David > > McGough via arm-allstar" > > Sent: Saturday, June 23, 2018 11:08 AM > > To: "Chris Zenchenko via arm-allstar" > > Cc: David McGough ; Chris Zenchenko > > 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 On Behalf Of "Doug > > > Crompton via arm-allstar" > > > Sent: Tuesday, June 19, 2018 10:26 AM > > > To: ARM Allstar > > > Cc: Doug Crompton > > > 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 * > > > > > > > > > On Tue, Jun 19, 2018 at 11:14 AM, "Chris Zenchenko via arm-allstar" < > > > arm-allstar at 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 at 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 at 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 at 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 at 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 at 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 at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From electricity440 at gmail.com Mon Aug 6 22:18:14 2018 From: electricity440 at gmail.com (Skyler F) Date: Mon, 6 Aug 2018 16:18:14 -0600 Subject: [App_rpt-users] Disable Receiver for X milliseconds after TX UNKEY Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wllmbecks at gmail.com Mon Aug 6 22:33:12 2018 From: wllmbecks at gmail.com (William Becks) Date: Mon, 6 Aug 2018 17:33:12 -0500 Subject: [App_rpt-users] Disable Receiver for X milliseconds after TX UNKEY In-Reply-To: References: Message-ID: <000b01d42dd5$76362190$62a264b0$@gmail.com> Hi Skyler, Can you please be more specific what you mean by ?ping pong? issue and sends a pulse through the network? I am presently using half duplex here and have not experienced anything as you describe. What radio are you using and how is it interfaced? Bill, WA8WG From: App_rpt-users On Behalf Of Skyler F Sent: Monday, August 6, 2018 5:18 PM To: Users of Asterisk app_rpt Subject: [App_rpt-users] Disable Receiver for X milliseconds after TX UNKEY 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From electricity440 at gmail.com Mon Aug 6 22:41:12 2018 From: electricity440 at gmail.com (Skyler F) Date: Mon, 6 Aug 2018 16:41:12 -0600 Subject: [App_rpt-users] Disable Receiver for X milliseconds after TX UNKEY In-Reply-To: <000b01d42dd5$76362190$62a264b0$@gmail.com> References: <000b01d42dd5$76362190$62a264b0$@gmail.com> Message-ID: > > > Can you please be more specific what you mean by ?ping pong? issue and > sends a pulse through the network? I am presently using half duplex here > and have not experienced anything as you describe. What radio are you > using and how is it interfaced? When I unkey, the receiver keys up for 50ms sending a carrier through the network any time someone unkeys. This is a motorola Maxtrac setup as a remote base listening to a certain repeater which is setup for "TX PL on Input Only" through the radio club. The repeater is a tad bit slow on it's Transmit CTCSS turning off however, so it sends a bit through the network when the remote base unkeys. If that makes any sense.... On Mon, Aug 6, 2018 at 4:33 PM William Becks wrote: > Hi Skyler, > > > > Can you please be more specific what you mean by ?ping pong? issue and > sends a pulse through the network? I am presently using half duplex here > and have not experienced anything as you describe. What radio are you > using and how is it interfaced? > > > > Bill, WA8WG > > > > > > *From:* App_rpt-users *On > Behalf Of *Skyler F > *Sent:* Monday, August 6, 2018 5:18 PM > *To:* Users of Asterisk app_rpt > *Subject:* [App_rpt-users] Disable Receiver for X milliseconds after TX > UNKEY > > > > 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 > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Skyler Fennell amsatnet.info KD?WHB electricity440 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From wllmbecks at gmail.com Mon Aug 6 22:57:24 2018 From: wllmbecks at gmail.com (William Becks) Date: Mon, 6 Aug 2018 17:57:24 -0500 Subject: [App_rpt-users] Disable Receiver for X milliseconds after TX UNKEY In-Reply-To: References: <000b01d42dd5$76362190$62a264b0$@gmail.com> Message-ID: <000a01d42dd8$d7b9c950$872d5bf0$@gmail.com> Are you using COR and possibly CTCSS logic output from your Maxtrac? Please define ?unkey?. Do you mean when the Maxtrac drops PTT after someone on the Internet side of the node unkeys? If both of these are true then you should use a scope on the COR and CTCSS leads to see what happens as the radio switches back to receive from transmit. I don?t remember at the moment what Motorola radios have this feature, but some of them have a debounce setting that may solve the issue if the logic I/O?s are triggering rapidly on a change of state between transmit and receive. If you?d like, PM me a copy of your codeplug and I?ll have a look at it. Bill, WA8WG E-Mail: wllmbecks at gmail.com From: App_rpt-users On Behalf Of Skyler F Sent: Monday, August 6, 2018 5:41 PM To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] Disable Receiver for X milliseconds after TX UNKEY Can you please be more specific what you mean by ?ping pong? issue and sends a pulse through the network? I am presently using half duplex here and have not experienced anything as you describe. What radio are you using and how is it interfaced? When I unkey, the receiver keys up for 50ms sending a carrier through the network any time someone unkeys. This is a motorola Maxtrac setup as a remote base listening to a certain repeater which is setup for "TX PL on Input Only" through the radio club. The repeater is a tad bit slow on it's Transmit CTCSS turning off however, so it sends a bit through the network when the remote base unkeys. If that makes any sense.... On Mon, Aug 6, 2018 at 4:33 PM William Becks > wrote: Hi Skyler, Can you please be more specific what you mean by ?ping pong? issue and sends a pulse through the network? I am presently using half duplex here and have not experienced anything as you describe. What radio are you using and how is it interfaced? Bill, WA8WG From: App_rpt-users > On Behalf Of Skyler F Sent: Monday, August 6, 2018 5:18 PM To: Users of Asterisk app_rpt > Subject: [App_rpt-users] Disable Receiver for X milliseconds after TX UNKEY 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 _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -- Skyler Fennell amsatnet.info KD?WHB electricity440 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From electricity440 at gmail.com Tue Aug 7 00:02:54 2018 From: electricity440 at gmail.com (Skyler F) Date: Mon, 6 Aug 2018 18:02:54 -0600 Subject: [App_rpt-users] Disable Receiver for X milliseconds after TX UNKEY In-Reply-To: <000a01d42dd8$d7b9c950$872d5bf0$@gmail.com> References: <000b01d42dd5$76362190$62a264b0$@gmail.com> <000a01d42dd8$d7b9c950$872d5bf0$@gmail.com> Message-ID: I?m using everything correctly on my radio because it works fine on a simplex. It?s just when I use it as a remote base linked up to a repeater. I was simply asking if app-rpt had an implementation of the function i had in mind in any of the usb channel drivers, not if my setup is correct. Thanks Skyler On Mon, Aug 6, 2018 at 4:57 PM William Becks wrote: > Are you using COR and possibly CTCSS logic output from your Maxtrac? > Please define ?unkey?. Do you mean when the Maxtrac drops PTT after > someone on the Internet side of the node unkeys? If both of these are > true then you should use a scope on the COR and CTCSS leads to see what > happens as the radio switches back to receive from transmit. > > > > I don?t remember at the moment what Motorola radios have this feature, but > some of them have a debounce setting that may solve the issue if the logic > I/O?s are triggering rapidly on a change of state between transmit and > receive. If you?d like, PM me a copy of your codeplug and I?ll have a > look at it. > > > > Bill, WA8WG > > > > E-Mail: wllmbecks at gmail.com > > > > > > *From:* App_rpt-users *On > Behalf Of *Skyler F > *Sent:* Monday, August 6, 2018 5:41 PM > *To:* Users of Asterisk app_rpt > *Subject:* Re: [App_rpt-users] Disable Receiver for X milliseconds after > TX UNKEY > > > > > Can you please be more specific what you mean by ?ping pong? issue and > sends a pulse through the network? I am presently using half duplex here > and have not experienced anything as you describe. What radio are you > using and how is it interfaced? > > When I unkey, the receiver keys up for 50ms sending a carrier through the > network any time someone unkeys. > > > > This is a motorola Maxtrac setup as a remote base listening to a certain > repeater which is setup for "TX PL on Input Only" through the radio club. > The repeater is a tad bit slow on it's Transmit CTCSS turning off however, > so it sends a bit through the network when the remote base unkeys. > > > > If that makes any sense.... > > > > On Mon, Aug 6, 2018 at 4:33 PM William Becks wrote: > > Hi Skyler, > > > > Can you please be more specific what you mean by ?ping pong? issue and > sends a pulse through the network? I am presently using half duplex here > and have not experienced anything as you describe. What radio are you > using and how is it interfaced? > > > > Bill, WA8WG > > > > > > *From:* App_rpt-users *On > Behalf Of *Skyler F > *Sent:* Monday, August 6, 2018 5:18 PM > *To:* Users of Asterisk app_rpt > *Subject:* [App_rpt-users] Disable Receiver for X milliseconds after TX > UNKEY > > > > 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 > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > > > > > -- > > Skyler Fennell > > amsatnet.info > > KD?WHB > > electricity440 at gmail.com > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Skyler Fennell amsatnet.info KD?WHB electricity440 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jd0 at broadsci.com Tue Aug 7 01:13:22 2018 From: jd0 at broadsci.com (Jeff DePolo) Date: Mon, 6 Aug 2018 21:13:22 -0400 Subject: [App_rpt-users] Disable Receiver for X milliseconds after TX UNKEY In-Reply-To: References: <000b01d42dd5$76362190$62a264b0$@gmail.com> Message-ID: <5A747A7B6B1A4A1890898350D99F02B0@OUTLAW> > This is a motorola Maxtrac setup as a remote base listening > to a certain repeater which is setup for "TX PL on Input > Only" through the radio club. The repeater is a tad bit slow > on it's Transmit CTCSS turning off however, so it sends a bit > through the network when the remote base unkeys. The repeater would have to be a whole lot longer than "a tad bit slow" to turn off the PL encoder. When the PTT goes inactive, the Maxtrac sends reverse burst and then unkeys, a process which takes on the order of 200 ms. During that sequence, the repeater should have recognized the reverse burst and closed its squelch and concunrrently stopped encoding PL; both of those actions should have completed before the Maxtracs transmitter even drops. If the repeater is still transmitting PL by the time the Maxtrac transmitter has unkeyed PLUS the time it takes for the Maxtrac to switch back to receive mode (takes a bit of time for the PLL to lock) PLUS the time needed re-aquire PL decode again (and Maxtracs are not great performers in this regard), then something is wrong with the logic at the repeater as it would appear it's encoding PL MUCH longer than it should be - by several hundreds of milliseconds at a minimum. Fix the problem at the repeater. --- Jeff WN3A --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From mm at midnighteng.com Tue Aug 7 01:31:11 2018 From: mm at midnighteng.com (Mike) Date: Mon, 6 Aug 2018 21:31:11 -0400 Subject: [App_rpt-users] Disable Receiver for X milliseconds after TX UNKEY In-Reply-To: References: Message-ID: <4fd79838-e26f-3116-006f-5e471e1af218@midnighteng.com> Skyler, I think you seek a software fix for a electronics problem. The pulse you are getting at rx/cor is from the switching of the TXer and I don't think a software delay is going to fix the issue. Are you toggling the TX with a relay ? Did you put a zener across the coil of the relay if so ? You need to scope the source. Probably at the TX/PTT line / relay contacts, even a transistor may need changed/filtered with a cap. Is frame ground bonded with negative ? Should it be ? Check radio specs. Things to think about. ...mike/kb8jnm On 8/6/2018 6:18 PM, Skyler F wrote: > 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 > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > From Bryan at bryanfields.net Tue Aug 7 04:08:51 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Tue, 7 Aug 2018 00:08:51 -0400 Subject: [App_rpt-users] Admin Email Announcement Message-ID: <02ea5ef6-f4e6-3014-ca74-7aace51b5202@bryanfields.net> If you've sent an email to admin at 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 at 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 From Benjamin at Project23D.com Tue Aug 7 12:16:43 2018 From: Benjamin at Project23D.com (Benjamin Naber) Date: Tue, 07 Aug 2018 07:16:43 -0500 Subject: [App_rpt-users] Disable Receiver for X milliseconds after TX UNKEY In-Reply-To: <4fd79838-e26f-3116-006f-5e471e1af218@midnighteng.com> References: <4fd79838-e26f-3116-006f-5e471e1af218@midnighteng.com> Message-ID: <1533644203.1751.3.camel@Project23D.com> I see what the lad wants to do. Ping pong is the non-descript term for the action happening during the repeater hang time. Skyler- The wise guys have spoken, with their knowledge still mentally lingering, I am going to throw this tid bit in there too: Unless you have technical control of the repeaters, you are going to experience the un-desired ping-pong action you are having -BECAUSE- what I said in my first statement.. For an ASL remote base to a repeater, one we had control of, at the repeater side, the repeater controller was set to only TX PL when the repeater's RX was active. That solved our ping pong issue. As I lead on to earlier, you are just going to have to deal with that as repeaters and their operation are created in the image of the owner - we are all unique. Benjamin, KB9LFZ On Mon, 2018-08-06 at 21:31 -0400, Mike wrote: > Skyler, > I think you seek a software fix for a electronics problem. > > > The pulse you are getting at rx/cor??is from the switching of the > TXer? > and I don't think a software delay is going to fix the issue. > > Are you toggling the TX with a relay ? > Did you put a zener across the coil of the relay if so ? > You need to scope the source. Probably at the TX/PTT line / relay? > contacts, even a transistor may need changed/filtered with a cap. > Is frame ground bonded with negative ? Should it be ? Check radio > specs. > > Things to think about. > > ...mike/kb8jnm > > On 8/6/2018 6:18 PM, Skyler F wrote: > > 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 > > > > > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at lists.allstarlink.org > > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > To unsubscribe from this list please visit http://lists.allstarlink > > .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. > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.o > rg/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.? From szingman at msgstor.com Tue Aug 7 17:06:47 2018 From: szingman at msgstor.com (Steve Zingman) Date: Tue, 7 Aug 2018 13:06:47 -0400 Subject: [App_rpt-users] Android IAXRPT Message-ID: <7d001077-7cea-1ad1-547b-0815d4b64183@msgstor.com> 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? From loren at lorentedford.com Tue Aug 7 18:30:10 2018 From: loren at lorentedford.com (Loren Tedford) Date: Tue, 7 Aug 2018 13:30:10 -0500 Subject: [App_rpt-users] RA 35's and Rpt config file Message-ID: <4e4af4b6-7c66-399f-edc9-9219b1c64cb8@lorentedford.com> 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) From nhardman1428 at gmail.com Tue Aug 7 19:49:48 2018 From: nhardman1428 at gmail.com (nhardman1428 at gmail.com) Date: Tue, 7 Aug 2018 15:49:48 -0400 Subject: [App_rpt-users] RA 35's and Rpt config file In-Reply-To: <4e4af4b6-7c66-399f-edc9-9219b1c64cb8@lorentedford.com> References: <4e4af4b6-7c66-399f-edc9-9219b1c64cb8@lorentedford.com> Message-ID: <56E96309-554F-4BEC-99FF-039EB90BCE44@gmail.com> What are you currrently using as an audio interface? You would use either usbradio or simpleusb depending on dsp needs with the ra-35s Sent from my iPhone > On Aug 7, 2018, at 2:30 PM, Loren Tedford wrote: > > 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) > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. From ke5vql at gmail.com Thu Aug 9 00:21:13 2018 From: ke5vql at gmail.com (Noah Chalker) Date: Wed, 8 Aug 2018 19:21:13 -0500 Subject: [App_rpt-users] Using a handmic while using a URI Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wllmbecks at gmail.com Thu Aug 9 00:35:43 2018 From: wllmbecks at gmail.com (William Becks) Date: Wed, 8 Aug 2018 19:35:43 -0500 Subject: [App_rpt-users] Using a handmic while using a URI In-Reply-To: References: Message-ID: <000501d42f78$e84f0220$b8ed0660$@gmail.com> Noah, Does your radio have an auxiliary connector where you could connect the URI to leave your RJ45 connector free to use with the microphone? Alternatively, you might consider installing iaxRpt on one of your PC?s that will give you a desktop dispatch application type access to the radio over via the URI over your LAN. I do that here and it works great. Bill, WA8WG From: App_rpt-users On Behalf Of Noah Chalker Sent: Wednesday, August 8, 2018 7:21 PM To: App_rpt-users at lists.allstarlink.org Subject: [App_rpt-users] Using a handmic while using a URI 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ke5vql at gmail.com Thu Aug 9 00:44:13 2018 From: ke5vql at gmail.com (Noah Chalker) Date: Wed, 8 Aug 2018 19:44:13 -0500 Subject: [App_rpt-users] Using a handmic while using a URI In-Reply-To: <000501d42f78$e84f0220$b8ed0660$@gmail.com> References: <000501d42f78$e84f0220$b8ed0660$@gmail.com> Message-ID: Bill and all, It does not. The only ports are the RJ45 for the microphone and the speaker output on the back. The alternative is possible but I rather find a solution to using the stock mic. KE5VQL On Wed, Aug 8, 2018 at 7:35 PM William Becks wrote: > Noah, > > > > Does your radio have an auxiliary connector where you could connect the > URI to leave your RJ45 connector free to use with the microphone? > Alternatively, you might consider installing iaxRpt on one of your PC?s > that will give you a desktop dispatch application type access to the radio > over via the URI over your LAN. I do that here and it works great. > > > > Bill, WA8WG > > > > > > *From:* App_rpt-users *On > Behalf Of *Noah Chalker > *Sent:* Wednesday, August 8, 2018 7:21 PM > *To:* App_rpt-users at lists.allstarlink.org > *Subject:* [App_rpt-users] Using a handmic while using a URI > > > > 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 > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- From, Noah Chalker 2Do not conform any longer to the pattern of this world, but be transformed by the renewing of your mind. Then you will be able to test and approve what God's will is?his good, pleasing and perfect will. Romans 12:2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wllmbecks at gmail.com Thu Aug 9 00:58:07 2018 From: wllmbecks at gmail.com (William Becks) Date: Wed, 8 Aug 2018 19:58:07 -0500 Subject: [App_rpt-users] Using a handmic while using a URI In-Reply-To: References: <000501d42f78$e84f0220$b8ed0660$@gmail.com> Message-ID: <000a01d42f7c$0971cc50$1c5564f0$@gmail.com> The iaxRpt app works really well but if you could interface at least the microphone line through a RIGblaster if you have one laying around. You obviously would not use the internal USB sound device if your blaster model is so equipped, but would rather just route the mic audio and PTT through the blaster and connect your stock microphone to the front mic port. The last option would be to homebrew a switchbox with a connector that fits your mic and a cable with an RJ45 plug to your radio and will only need to wire in DPDT toggle switch that will allow you to switch the transceivers mic and PTT lines between the local microphone and the URI. Bill, WA8WG From: App_rpt-users On Behalf Of Noah Chalker Sent: Wednesday, August 8, 2018 7:44 PM To: app_rpt-users at lists.allstarlink.org Subject: Re: [App_rpt-users] Using a handmic while using a URI Bill and all, It does not. The only ports are the RJ45 for the microphone and the speaker output on the back. The alternative is possible but I rather find a solution to using the stock mic. KE5VQL On Wed, Aug 8, 2018 at 7:35 PM William Becks > wrote: Noah, Does your radio have an auxiliary connector where you could connect the URI to leave your RJ45 connector free to use with the microphone? Alternatively, you might consider installing iaxRpt on one of your PC?s that will give you a desktop dispatch application type access to the radio over via the URI over your LAN. I do that here and it works great. Bill, WA8WG From: App_rpt-users > On Behalf Of Noah Chalker Sent: Wednesday, August 8, 2018 7:21 PM To: App_rpt-users at lists.allstarlink.org Subject: [App_rpt-users] Using a handmic while using a URI 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 _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -- From, Noah Chalker 2Do not conform any longer to the pattern of this world, but be transformed by the renewing of your mind. Then you will be able to test and approve what God's will is?his good, pleasing and perfect will. Romans 12:2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From piecorab at gmail.com Thu Aug 9 03:58:04 2018 From: piecorab at gmail.com (Ben Piecora) Date: Wed, 8 Aug 2018 23:58:04 -0400 Subject: [App_rpt-users] Using a handmic while using a URI In-Reply-To: <000a01d42f7c$0971cc50$1c5564f0$@gmail.com> References: <000501d42f78$e84f0220$b8ed0660$@gmail.com> <000a01d42f7c$0971cc50$1c5564f0$@gmail.com> Message-ID: Well, you could take apart the radio and solder to the back of the mic jack, which I have done in the past, but if youre using it for an allstar node there will not be much purpose for the mic as it will only TX to the radios listening to the output frequency of the node, and will not be transmitted via any internet links. On Wed, Aug 8, 2018 at 8:58 PM William Becks wrote: > The iaxRpt app works really well but if you could interface at least the > microphone line through a RIGblaster if you have one laying around. You > obviously would not use the internal USB sound device if your blaster model > is so equipped, but would rather just route the mic audio and PTT through > the blaster and connect your stock microphone to the front mic port. The > last option would be to homebrew a switchbox with a connector that fits > your mic and a cable with an RJ45 plug to your radio and will only need to > wire in DPDT toggle switch that will allow you to switch the transceivers > mic and PTT lines between the local microphone and the URI. > > > > Bill, > > > > WA8WG > > > > > > *From:* App_rpt-users *On > Behalf Of *Noah Chalker > *Sent:* Wednesday, August 8, 2018 7:44 PM > *To:* app_rpt-users at lists.allstarlink.org > *Subject:* Re: [App_rpt-users] Using a handmic while using a URI > > > > Bill and all, > > > > It does not. The only ports are the RJ45 for the microphone and the > speaker output on the back. The alternative is possible but I rather find a > solution to using the stock mic. > > > > KE5VQL > > > > On Wed, Aug 8, 2018 at 7:35 PM William Becks wrote: > > Noah, > > > > Does your radio have an auxiliary connector where you could connect the > URI to leave your RJ45 connector free to use with the microphone? > Alternatively, you might consider installing iaxRpt on one of your PC?s > that will give you a desktop dispatch application type access to the radio > over via the URI over your LAN. I do that here and it works great. > > > > Bill, WA8WG > > > > > > *From:* App_rpt-users *On > Behalf Of *Noah Chalker > *Sent:* Wednesday, August 8, 2018 7:21 PM > *To:* App_rpt-users at lists.allstarlink.org > *Subject:* [App_rpt-users] Using a handmic while using a URI > > > > 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 > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > > > > -- > > From, > Noah Chalker > 2Do not conform any longer to the pattern of this world, but be > transformed by the renewing of your mind. Then you will be able to test and > approve what God's will is?his good, pleasing and perfect will. > Romans 12:2 > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Ben K2CPU -------------- next part -------------- An HTML attachment was scrubbed... URL: From piecorab at gmail.com Thu Aug 9 04:30:12 2018 From: piecorab at gmail.com (Ben Piecora) Date: Thu, 9 Aug 2018 00:30:12 -0400 Subject: [App_rpt-users] Using a handmic while using a URI In-Reply-To: References: <000501d42f78$e84f0220$b8ed0660$@gmail.com> <000a01d42f7c$0971cc50$1c5564f0$@gmail.com> Message-ID: Then grab the recieved audio from the high side of the volume control pot. On Wed, Aug 8, 2018 at 11:58 PM Ben Piecora wrote: > Well, you could take apart the radio and solder to the back of the mic > jack, which I have done in the past, but if youre using it for an allstar > node there will not be much purpose for the mic as it will only TX to the > radios listening to the output frequency of the node, and will not be > transmitted via any internet links. > > On Wed, Aug 8, 2018 at 8:58 PM William Becks wrote: > >> The iaxRpt app works really well but if you could interface at least the >> microphone line through a RIGblaster if you have one laying around. You >> obviously would not use the internal USB sound device if your blaster model >> is so equipped, but would rather just route the mic audio and PTT through >> the blaster and connect your stock microphone to the front mic port. The >> last option would be to homebrew a switchbox with a connector that fits >> your mic and a cable with an RJ45 plug to your radio and will only need to >> wire in DPDT toggle switch that will allow you to switch the transceivers >> mic and PTT lines between the local microphone and the URI. >> >> >> >> Bill, >> >> >> >> WA8WG >> >> >> >> >> >> *From:* App_rpt-users *On >> Behalf Of *Noah Chalker >> *Sent:* Wednesday, August 8, 2018 7:44 PM >> *To:* app_rpt-users at lists.allstarlink.org >> *Subject:* Re: [App_rpt-users] Using a handmic while using a URI >> >> >> >> Bill and all, >> >> >> >> It does not. The only ports are the RJ45 for the microphone and the >> speaker output on the back. The alternative is possible but I rather find a >> solution to using the stock mic. >> >> >> >> KE5VQL >> >> >> >> On Wed, Aug 8, 2018 at 7:35 PM William Becks wrote: >> >> Noah, >> >> >> >> Does your radio have an auxiliary connector where you could connect the >> URI to leave your RJ45 connector free to use with the microphone? >> Alternatively, you might consider installing iaxRpt on one of your PC?s >> that will give you a desktop dispatch application type access to the radio >> over via the URI over your LAN. I do that here and it works great. >> >> >> >> Bill, WA8WG >> >> >> >> >> >> *From:* App_rpt-users *On >> Behalf Of *Noah Chalker >> *Sent:* Wednesday, August 8, 2018 7:21 PM >> *To:* App_rpt-users at lists.allstarlink.org >> *Subject:* [App_rpt-users] Using a handmic while using a URI >> >> >> >> 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 >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. >> >> >> >> -- >> >> From, >> Noah Chalker >> 2Do not conform any longer to the pattern of this world, but be >> transformed by the renewing of your mind. Then you will be able to test and >> approve what God's will is?his good, pleasing and perfect will. >> Romans 12:2 >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. >> > > > -- > Ben > K2CPU > -- Ben K2CPU -------------- next part -------------- An HTML attachment was scrubbed... URL: From ke5vql at gmail.com Thu Aug 9 19:39:21 2018 From: ke5vql at gmail.com (Noah Chalker) Date: Thu, 9 Aug 2018 14:39:21 -0500 Subject: [App_rpt-users] Using a handmic while using a URI In-Reply-To: References: <000501d42f78$e84f0220$b8ed0660$@gmail.com> <000a01d42f7c$0971cc50$1c5564f0$@gmail.com> Message-ID: Well, I need the radio to be able to use the microphone. I know that it is not the easy solution but it is the one that I am going for. I do not want to open up the radio so I am going to try and design a circuit so that the mic and the URI can be connected into the microphone jack. I will also include some digital logic so that if both the URI and the mic a trying to key up, then only the signal from the mic will go through. I will try and upload a schematic later. Noah On Wed, Aug 8, 2018 at 10:58 PM Ben Piecora wrote: > Well, you could take apart the radio and solder to the back of the mic > jack, which I have done in the past, but if youre using it for an allstar > node there will not be much purpose for the mic as it will only TX to the > radios listening to the output frequency of the node, and will not be > transmitted via any internet links. > > On Wed, Aug 8, 2018 at 8:58 PM William Becks wrote: > >> The iaxRpt app works really well but if you could interface at least the >> microphone line through a RIGblaster if you have one laying around. You >> obviously would not use the internal USB sound device if your blaster model >> is so equipped, but would rather just route the mic audio and PTT through >> the blaster and connect your stock microphone to the front mic port. The >> last option would be to homebrew a switchbox with a connector that fits >> your mic and a cable with an RJ45 plug to your radio and will only need to >> wire in DPDT toggle switch that will allow you to switch the transceivers >> mic and PTT lines between the local microphone and the URI. >> >> >> >> Bill, >> >> >> >> WA8WG >> >> >> >> >> >> *From:* App_rpt-users *On >> Behalf Of *Noah Chalker >> *Sent:* Wednesday, August 8, 2018 7:44 PM >> *To:* app_rpt-users at lists.allstarlink.org >> *Subject:* Re: [App_rpt-users] Using a handmic while using a URI >> >> >> >> Bill and all, >> >> >> >> It does not. The only ports are the RJ45 for the microphone and the >> speaker output on the back. The alternative is possible but I rather find a >> solution to using the stock mic. >> >> >> >> KE5VQL >> >> >> >> On Wed, Aug 8, 2018 at 7:35 PM William Becks wrote: >> >> Noah, >> >> >> >> Does your radio have an auxiliary connector where you could connect the >> URI to leave your RJ45 connector free to use with the microphone? >> Alternatively, you might consider installing iaxRpt on one of your PC?s >> that will give you a desktop dispatch application type access to the radio >> over via the URI over your LAN. I do that here and it works great. >> >> >> >> Bill, WA8WG >> >> >> >> >> >> *From:* App_rpt-users *On >> Behalf Of *Noah Chalker >> *Sent:* Wednesday, August 8, 2018 7:21 PM >> *To:* App_rpt-users at lists.allstarlink.org >> *Subject:* [App_rpt-users] Using a handmic while using a URI >> >> >> >> 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 >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. >> >> >> >> -- >> >> From, >> Noah Chalker >> 2Do not conform any longer to the pattern of this world, but be >> transformed by the renewing of your mind. Then you will be able to test and >> approve what God's will is?his good, pleasing and perfect will. >> Romans 12:2 >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. >> > > > -- > Ben > K2CPU > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- From, Noah Chalker 2Do not conform any longer to the pattern of this world, but be transformed by the renewing of your mind. Then you will be able to test and approve what God's will is?his good, pleasing and perfect will. Romans 12:2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jd0 at broadsci.com Thu Aug 9 20:11:34 2018 From: jd0 at broadsci.com (Jeff DePolo) Date: Thu, 9 Aug 2018 16:11:34 -0400 Subject: [App_rpt-users] Using a handmic while using a URI In-Reply-To: References: <000501d42f78$e84f0220$b8ed0660$@gmail.com> <000a01d42f7c$0971cc50$1c5564f0$@gmail.com> Message-ID: <8AFA69BEBC2E4A3CA7BC772914FF1BB2@OUTLAW> > Well, I need the radio to be able to use the microphone. I > know that it is not the easy solution but it is the one that > I am going for. I do not want to open up the radio so I am > going to try and design a circuit so that the mic and the URI > can be connected into the microphone jack. I will also > include some digital logic so that if both the URI and the > mic a trying to key up, then only the signal from the mic > will go through. I will try and upload a schematic later. You didn't say what kind of radio it is (or if you did, I didn't see it). The best and/or easiest way to implement this is going to vary with the type of radio. At the very worst, you need is a SPDT switch (CD4053 appropriately biased, reed relay, whatever) and a couple of steering diodes. But depending on the radio, it could be as simple as hard-OR'ing the PTT's together and resistively summing the audio. You likely have way more audio output available from the URI than you'll need to drive the mic input, so there's a good chance all you need to do is add enough series R in the audio coming from the URI to prevent loading the hand mic. Assuming you're using the AC-coupled output from the URI you don't even have to worry about DC-blocking the mic bias. --- Jeff WN3A --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From Bryan at bryanfields.net Fri Aug 10 05:11:45 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Fri, 10 Aug 2018 01:11:45 -0400 Subject: [App_rpt-users] AllStar Network Maintenance Announcement Message-ID: -----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----- From petem001 at gmail.com Sat Aug 11 00:21:27 2018 From: petem001 at gmail.com (Pierre Martel) Date: Fri, 10 Aug 2018 20:21:27 -0400 Subject: [App_rpt-users] AllStar Network Maintenance Announcement In-Reply-To: References: Message-ID: Thanks for the hard work of all the team to keep Jim's vision of the network alive and even thriving. This is not just a thank you just to be well seen on the group. I am no more in charge of any repeater. But I still follow the scene as I beleive it is the best, powerfull and flexible solution to repeater control and linking. Long live Allstarlink! Pierre VE2PF Le ven. 10 ao?t 2018 ? 01:11, Bryan Fields a ?crit : > -----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----- > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at dyb.com Sat Aug 11 23:00:25 2018 From: george at dyb.com (George Csahanin) Date: Sat, 11 Aug 2018 18:00:25 -0500 Subject: [App_rpt-users] odd connect problem Message-ID: <3fc493de-0658-fa36-0631-8a4ea60b832a@dyb.com> 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 From dshaw at ke6upi.com Sun Aug 12 05:23:43 2018 From: dshaw at ke6upi.com (David KE6UPI) Date: Sat, 11 Aug 2018 22:23:43 -0700 Subject: [App_rpt-users] odd connect problem In-Reply-To: <3fc493de-0658-fa36-0631-8a4ea60b832a@dyb.com> References: <3fc493de-0658-fa36-0631-8a4ea60b832a@dyb.com> Message-ID: Hello George, Can you copy and paste the node section from both nodes. David On Sat, Aug 11, 2018 at 4:00 PM George Csahanin wrote: > 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 > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Sun Aug 12 09:17:40 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Sun, 12 Aug 2018 05:17:40 -0400 Subject: [App_rpt-users] AllStarLink Maintenance followup Message-ID: 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 at 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 From kb4fxc at inttek.net Sun Aug 12 09:36:44 2018 From: kb4fxc at inttek.net (David McGough) Date: Sun, 12 Aug 2018 05:36:44 -0400 (EDT) Subject: [App_rpt-users] AllStarLink Maintenance followup In-Reply-To: Message-ID: Bryan, I know it has been a long night for you all. But, my logs are filling with registration errors--see below. These errors are going to make it impossible to troubleshoot registration related problems. Any ideas on solving this?? Thanks, 73, David KB4FXC Asterisk CLI output: ---------------------------------------------------------------------------------------------- [Aug 12 05:28:15] NOTICE[20463]: dnsmgr.c:178 dnsmgr_refresh: host 'register.allstarlink.org' changed from 44.72.21.13 to 44.103.0.49 [Aug 12 05:28:15] NOTICE[20463]: dnsmgr.c:178 dnsmgr_refresh: host 'register.allstarlink.org' changed from 44.98.254.145 to 44.72.21.13 [Aug 12 05:28:15] NOTICE[20463]: dnsmgr.c:178 dnsmgr_refresh: host 'register.allstarlink.org' changed from 44.72.21.13 to 44.103.0.49 [Aug 12 05:28:15] NOTICE[20463]: dnsmgr.c:178 dnsmgr_refresh: host 'register.allstarlink.org' changed from 44.72.21.13 to 44.103.0.49 [Aug 12 05:28:15] NOTICE[20463]: dnsmgr.c:178 dnsmgr_refresh: host 'register.allstarlink.org' changed from 44.98.254.145 to 44.72.21.13 [Aug 12 05:28:19] WARNING[20472]: chan_iax2.c:7395 iax2_ack_registry: Received unsolicited registry ack from '44.98.254.145' [Aug 12 05:28:19] WARNING[20472]: chan_iax2.c:9820 socket_process: Registration failure [Aug 12 05:28:19] WARNING[20471]: chan_iax2.c:7395 iax2_ack_registry: Received unsolicited registry ack from '44.72.21.13' [Aug 12 05:28:19] WARNING[20471]: chan_iax2.c:9820 socket_process: Registration failure [Aug 12 05:29:13] NOTICE[20472]: chan_iax2.c:9828 socket_process: Registration of '2290' rejected: '' from: '44.103.0.49' [Aug 12 05:29:51] NOTICE[20470]: dnsmgr.c:178 dnsmgr_refresh: host 'register.allstarlink.org' changed from 44.103.0.49 to 44.98.254.145 -- Registered IAX2 to '44.98.254.145', who sees us as 12.17.28.14:4569 with no messages waiting [Aug 12 05:30:27] NOTICE[20470]: dnsmgr.c:178 dnsmgr_refresh: host 'register.allstarlink.org' changed from 44.103.0.49 to 44.72.21.13 -- Registered IAX2 to '44.72.21.13', who sees us as 12.17.28.14:4569 with no messages waiting [Aug 12 05:31:10] NOTICE[20471]: dnsmgr.c:178 dnsmgr_refresh: host 'register.allstarlink.org' changed from 44.72.21.13 to 44.98.254.145 [Aug 12 05:31:10] NOTICE[20472]: chan_iax2.c:9828 socket_process: Registration of '2289' rejected: '' from: '44.98.254.145' [Aug 12 05:31:33] NOTICE[20472]: chan_iax2.c:9828 socket_process: Registration of '2290' rejected: '' from: '44.72.21.13' [Aug 12 05:31:34] NOTICE[20471]: dnsmgr.c:178 dnsmgr_refresh: host 'register.allstarlink.org' changed from 44.103.0.49 to 44.72.21.13 [Aug 12 05:31:34] NOTICE[20472]: chan_iax2.c:9828 socket_process: Registration of '2286' rejected: '' from: '44.72.21.13' Allstar-inttek*CLI> iax2 show registry Host dnsmgr Username Perceived Refresh State 44.72.21.13:4569 Y 2290 12.17.28.14:4569 60 Rejected 44.98.254.145:4569 Y 2289 60 Rejected 44.98.254.145:4569 Y 2288 12.17.28.14:4569 60 Registered 44.98.254.145:4569 Y 2287 12.17.28.14:4569 60 Registered 44.72.21.13:4569 Y 2286 60 Rejected 44.72.21.13:4569 Y 2285 12.17.28.14:4569 60 Registered On Sun, 12 Aug 2018, Bryan Fields wrote: > 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 at 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 > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > From Bryan at bryanfields.net Sun Aug 12 11:37:25 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Sun, 12 Aug 2018 07:37:25 -0400 Subject: [App_rpt-users] AllStarLink Maintenance followup In-Reply-To: References: Message-ID: <606a9a24-f24c-aa4d-9e33-b13b7e51d98c@bryanfields.net> On 8/12/18 5:36 AM, David McGough wrote: > > Bryan, > > I know it has been a long night for you all. But, my logs are filling with > registration errors--see below. These errors are going to make it > impossible to troubleshoot registration related problems. I've been busy cleaning up for the evening here. The team has been hammering this system with over 15k node registrations for the last couple months. Our use of IAX2 on the registration server is quite limited, it's there to get the IAX port (as it appears), and the port from authenticated hosts. This gets put in a database with a time stamp. The system considers someone registered if they have a timestamp in the last 600 seconds, it's not based on IAX status. So long as you hit one registration server and register to it in a 10 minute interval, you're in the nodes file. With dnsmgr running, IAX2 will tear down reestablish a connection every time DNS changes. This has the effect of spreading load out on the servers, and giving us redundancy. Should a server go down it will stop updating the timestamp on DNS entries in the database and that IP will time out of the DNS. The connections between nodes are built using IAX2 between nodes, so long as they have a copy of the nodes file they will connect up. These connections don't hit the registration server, and only depend on it insofar as getting the updated nodes list. You'll note the nodes list now is updated much faster, and in near real time from the database. This is a huge improvement in the 5+ min delay on the prior nodes list. For checking if your registered from the perspective of the servers use https://allstar.aargdmr.net/nodelist/ or the main allstarlink.org portal and check you last registration time and if you're green. You may also pull the extnodes file directly from http://nodes.regsvcs.allstarlink.org/cgi-bin/nodes.pl if you're on a registered node. The "errors" you are seeing in the logs are just the notice of the IP address resolving for register.allstarlink.org. Some of the rejections we due to the loading, when 2500 nodes hit the server all at once, it can take a bit of time to get registered. We're in steady state now and registration is stable. Example: > Itchy*CLI> iax2 show registry > Host dnsmgr Username Perceived Refresh State > 44.72.21.13:4569 Y 44233 44.98.249.6:4569 60 Registered > 44.72.21.13:4569 Y 42032 44.98.249.6:4569 60 Registered > 44.98.254.145:4569 Y 41618 44.98.249.6:4569 60 Registered > 44.98.254.145:4569 Y 40821 44.98.249.6:4569 60 Registered The time/cpu it takes to build a new connection is the same as refreshing an existing connection. Most people will not notice anything, and hopefully if we have a server fail, they will continue not to notice anything. I'm off to bed now. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From ars.w5omr at gmail.com Sun Aug 12 11:43:36 2018 From: ars.w5omr at gmail.com (ARS W5OMR) Date: Sun, 12 Aug 2018 06:43:36 -0500 Subject: [App_rpt-users] AllStarLink Maintenance followup In-Reply-To: <606a9a24-f24c-aa4d-9e33-b13b7e51d98c@bryanfields.net> References: <606a9a24-f24c-aa4d-9e33-b13b7e51d98c@bryanfields.net> Message-ID: > > Thanks to you and all the team for all your hard work! -------------- next part -------------- An HTML attachment was scrubbed... URL: From paulkn2r at gmail.com Sun Aug 12 13:11:44 2018 From: paulkn2r at gmail.com (Paul - KN2R) Date: Sun, 12 Aug 2018 09:11:44 -0400 Subject: [App_rpt-users] BIG registration problem this morning Message-ID: <003401d4323e$050371e0$0f0a55a0$@com> This morning ALL my nodes are somehow reporting wrong AllStar port numbers from Registration server. Every one of them. A search shows port 54799, shown below for my node 27034. But the actual port I have defined everywhere is and should be 44569! Where did that 54799 number come from? All my incoming connections are down at this point. AllStar Node Number Search for: "27034" --------------------------------------- 27034 KN2R [HUB2] Cape Coral, SW Florida, USA DNS DNS radio at 76.101.48.66:54799/27034 Paul / KN2R -------------- next part -------------- An HTML attachment was scrubbed... URL: From tisawyer at gmail.com Sun Aug 12 15:17:16 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Sun, 12 Aug 2018 08:17:16 -0700 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: <003401d4323e$050371e0$0f0a55a0$@com> References: <003401d4323e$050371e0$0f0a55a0$@com> Message-ID: We're looking into this. Is your correct port really 44569? On Sun, Aug 12, 2018 at 5:44 AM Paul - KN2R wrote: > This morning ALL my nodes are somehow reporting wrong AllStar port numbers > from Registration server. Every one of them. > > > > A search shows port 54799, shown below for my node 27034. > > But the actual port I have defined everywhere is and should be 44569! > > > > Where did that 54799 number come from? All my incoming connections are > down at this point. > > > > > > AllStar Node Number Search for: "27034" > --------------------------------------- > > 27034 > > KN2R > > [HUB2] > > Cape Coral, SW Florida, USA > > DNS DNS radio at 76.101.48.66:54799/27034 > > > > > > Paul / KN2R > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From paulkn2r at gmail.com Sun Aug 12 15:46:58 2018 From: paulkn2r at gmail.com (Paul - KN2R) Date: Sun, 12 Aug 2018 11:46:58 -0400 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: References: <003401d4323e$050371e0$0f0a55a0$@com> Message-ID: <004901d43253$b44d0d90$1ce728b0$@com> Yes 44569. From: App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] On Behalf Of Tim Sawyer Sent: Sunday, August 12, 2018 11:17 AM To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] BIG registration problem this morning We're looking into this. Is your correct port really 44569? On Sun, Aug 12, 2018 at 5:44 AM Paul - KN2R wrote: This morning ALL my nodes are somehow reporting wrong AllStar port numbers from Registration server. Every one of them. A search shows port 54799, shown below for my node 27034. But the actual port I have defined everywhere is and should be 44569! Where did that 54799 number come from? All my incoming connections are down at this point. AllStar Node Number Search for: "27034" --------------------------------------- 27034 KN2R [HUB2] Cape Coral, SW Florida, USA DNS DNS radio at 76.101.48.66:54799/27034 Paul / KN2R _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Sun Aug 12 15:26:48 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Sun, 12 Aug 2018 11:26:48 -0400 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: <003401d4323e$050371e0$0f0a55a0$@com> References: <003401d4323e$050371e0$0f0a55a0$@com> Message-ID: <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> On 8/12/18 9:11 AM, Paul - KN2R wrote: > This morning ALL my nodes are somehow reporting wrong AllStar port numbers > from Registration server. Every one of them. > > > > A search shows port 54799, shown below for my node 27034. > > But the actual port I have defined everywhere is and should be 44569! > > Where did that 54799 number come from? All my incoming connections are down > at this point. >From the server: iax2 show peer 27034 * Name : 27034 Description : Secret : Context : radio-in Parking lot : Mailbox : Dynamic : Yes Callnum limit: 0 Calltoken req: No Trunk : No Encryption : No Callerid : "" <> Expire : 45018 ACL : No Addr->IP : 76.101.48.66 Port 54799 Defaddr->IP : (null) Port (null) Username : Codecs : (gsm|ulaw|alaw|g726aal2|adpcm|slin|g729|speex|ilbc|g726|g722|siren7|siren14|slin16) Codec Order : (ulaw|alaw|siren14|siren7|g722|slin16|slin|g726|g726aal2|adpcm|gsm|ilbc|speex|g729) Status : Unmonitored Qualify : every 60000ms when OK, every 10000ms when UNREACHABLE (sample smoothing Off) You're registering with that port number. Can you check your bound port number? Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From paulkn2r at gmail.com Sun Aug 12 16:06:29 2018 From: paulkn2r at gmail.com (Paul - KN2R) Date: Sun, 12 Aug 2018 12:06:29 -0400 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> Message-ID: <004e01d43256$6e432f20$4ac98d60$@com> I have all set and been using port 44569 for well over a year on that server. Now this morning the registration server is reporting the incorrect port number of 54799. I Never used that number. Now inbound connections are not working any more. Paul -----Original Message----- From: App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] On Behalf Of Bryan Fields Sent: Sunday, August 12, 2018 11:27 AM To: app_rpt-users at lists.allstarlink.org Subject: Re: [App_rpt-users] BIG registration problem this morning On 8/12/18 9:11 AM, Paul - KN2R wrote: > This morning ALL my nodes are somehow reporting wrong AllStar port > numbers from Registration server. Every one of them. > > > > A search shows port 54799, shown below for my node 27034. > > But the actual port I have defined everywhere is and should be 44569! > > Where did that 54799 number come from? All my incoming connections > are down at this point. >From the server: iax2 show peer 27034 * Name : 27034 Description : Secret : Context : radio-in Parking lot : Mailbox : Dynamic : Yes Callnum limit: 0 Calltoken req: No Trunk : No Encryption : No Callerid : "" <> Expire : 45018 ACL : No Addr->IP : 76.101.48.66 Port 54799 Defaddr->IP : (null) Port (null) Username : Codecs : (gsm|ulaw|alaw|g726aal2|adpcm|slin|g729|speex|ilbc|g726|g722|siren7|siren14| slin16) Codec Order : (ulaw|alaw|siren14|siren7|g722|slin16|slin|g726|g726aal2|adpcm|gsm|ilbc|spee x|g729) Status : Unmonitored Qualify : every 60000ms when OK, every 10000ms when UNREACHABLE (sample smoothing Off) You're registering with that port number. Can you check your bound port number? Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. From tisawyer at gmail.com Sun Aug 12 16:05:47 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Sun, 12 Aug 2018 09:05:47 -0700 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: <004e01d43256$6e432f20$4ac98d60$@com> References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> Message-ID: Both asterisk and tcpdump show the wrong port being reported. Sometimes NAT routers get confused. Could you try rebooting your router? On Sun, Aug 12, 2018 at 8:39 AM Paul - KN2R wrote: > I have all set and been using port 44569 for well over a year on that > server. > Now this morning the registration server is reporting the incorrect port > number of 54799. > I Never used that number. Now inbound connections are not working any > more. > > Paul > > > -----Original Message----- > From: App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] > On > Behalf Of Bryan Fields > Sent: Sunday, August 12, 2018 11:27 AM > To: app_rpt-users at lists.allstarlink.org > Subject: Re: [App_rpt-users] BIG registration problem this morning > > On 8/12/18 9:11 AM, Paul - KN2R wrote: > > This morning ALL my nodes are somehow reporting wrong AllStar port > > numbers from Registration server. Every one of them. > > > > > > > > A search shows port 54799, shown below for my node 27034. > > > > But the actual port I have defined everywhere is and should be 44569! > > > > Where did that 54799 number come from? All my incoming connections > > are down at this point. > > > From the server: > > iax2 show peer 27034 > > * Name : 27034 > Description : > Secret : > Context : radio-in > Parking lot : > Mailbox : > Dynamic : Yes > Callnum limit: 0 > Calltoken req: No > Trunk : No > Encryption : No > Callerid : "" <> > Expire : 45018 > ACL : No > Addr->IP : 76.101.48.66 Port 54799 > Defaddr->IP : (null) Port (null) > Username : > Codecs : > > (gsm|ulaw|alaw|g726aal2|adpcm|slin|g729|speex|ilbc|g726|g722|siren7|siren14| > slin16) > Codec Order : > > (ulaw|alaw|siren14|siren7|g722|slin16|slin|g726|g726aal2|adpcm|gsm|ilbc|spee > x|g729) > Status : Unmonitored > Qualify : every 60000ms when OK, every 10000ms when UNREACHABLE > (sample > smoothing Off) > > You're registering with that port number. Can you check your bound port > number? > > Thanks, > > -- > Bryan Fields > > 727-409-1194 - Voice > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Sun Aug 12 16:06:20 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Sun, 12 Aug 2018 12:06:20 -0400 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: <004e01d43256$6e432f20$4ac98d60$@com> References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> Message-ID: <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> On 8/12/18 12:06 PM, Paul - KN2R wrote: > I have all set and been using port 44569 for well over a year on that > server. > Now this morning the registration server is reporting the incorrect port > number of 54799. > I Never used that number. Now inbound connections are not working any more. Ok, are you behind NAT? What are you doing there that iax is not connecting outbound with a source port of 44569? I just pulled a dump of your traffic to the registration server and I see you're hitting it with a source port of 54799, not 44569. I think this has to be some nat funkyness, using a different outgoing port vs incoming. Can you check that and give some details if you are behind nat as to the setup you have? Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From wolthuis at gmail.com Sun Aug 12 16:21:40 2018 From: wolthuis at gmail.com (Michael Wolthuis) Date: Sun, 12 Aug 2018 16:21:40 +0000 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> Message-ID: I have seen this before if you are using PFSense as your outbound router and you are NOT static locking NAT outbound, it will pick a port at random. Other firewalls have also done it if not set for static, but most consumer grade routers do NOT mangle NAT this way. Mike Kb8zgl ?On 8/12/18, 12:06 PM, "App_rpt-users on behalf of Bryan Fields" wrote: On 8/12/18 12:06 PM, Paul - KN2R wrote: > I have all set and been using port 44569 for well over a year on that > server. > Now this morning the registration server is reporting the incorrect port > number of 54799. > I Never used that number. Now inbound connections are not working any more. Ok, are you behind NAT? What are you doing there that iax is not connecting outbound with a source port of 44569? I just pulled a dump of your traffic to the registration server and I see you're hitting it with a source port of 54799, not 44569. I think this has to be some nat funkyness, using a different outgoing port vs incoming. Can you check that and give some details if you are behind nat as to the setup you have? Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. From kb2ear at kb2ear.net Sun Aug 12 17:31:27 2018 From: kb2ear at kb2ear.net (Scott Weis) Date: Sun, 12 Aug 2018 13:31:27 -0400 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> Message-ID: <010101d43262$4d047ab0$e70d7010$@kb2ear.net> The portal has a port in it and that?s where you used to specify the port for the rpt_extnodes file to resolve the incorrect reported port. From: App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] On Behalf Of Tim Sawyer Sent: Sunday, August 12, 2018 12:06 PM To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] BIG registration problem this morning Both asterisk and tcpdump show the wrong port being reported. Sometimes NAT routers get confused. Could you try rebooting your router? On Sun, Aug 12, 2018 at 8:39 AM Paul - KN2R > wrote: I have all set and been using port 44569 for well over a year on that server. Now this morning the registration server is reporting the incorrect port number of 54799. I Never used that number. Now inbound connections are not working any more. Paul -----Original Message----- From: App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org ] On Behalf Of Bryan Fields Sent: Sunday, August 12, 2018 11:27 AM To: app_rpt-users at lists.allstarlink.org Subject: Re: [App_rpt-users] BIG registration problem this morning On 8/12/18 9:11 AM, Paul - KN2R wrote: > This morning ALL my nodes are somehow reporting wrong AllStar port > numbers from Registration server. Every one of them. > > > > A search shows port 54799, shown below for my node 27034. > > But the actual port I have defined everywhere is and should be 44569! > > Where did that 54799 number come from? All my incoming connections > are down at this point. >From the server: iax2 show peer 27034 * Name : 27034 Description : Secret : Context : radio-in Parking lot : Mailbox : Dynamic : Yes Callnum limit: 0 Calltoken req: No Trunk : No Encryption : No Callerid : "" <> Expire : 45018 ACL : No Addr->IP : 76.101.48.66 Port 54799 Defaddr->IP : (null) Port (null) Username : Codecs : (gsm|ulaw|alaw|g726aal2|adpcm|slin|g729|speex|ilbc|g726|g722|siren7|siren14| slin16) Codec Order : (ulaw|alaw|siren14|siren7|g722|slin16|slin|g726|g726aal2|adpcm|gsm|ilbc|spee x|g729) Status : Unmonitored Qualify : every 60000ms when OK, every 10000ms when UNREACHABLE (sample smoothing Off) You're registering with that port number. Can you check your bound port number? Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at dyb.com Sun Aug 12 18:02:24 2018 From: george at dyb.com (George Csahanin) Date: Sun, 12 Aug 2018 13:02:24 -0500 Subject: [App_rpt-users] App_rpt-users Digest, Vol 114, Issue 12 In-Reply-To: References: Message-ID: 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 at lists.allstarlink.org wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users at 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 at lists.allstarlink.org > > You can reach the person managing the list at > app_rpt-users-owner at 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 at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at dyb.com Sun Aug 12 18:24:18 2018 From: george at dyb.com (George Csahanin) Date: Sun, 12 Aug 2018 13:24:18 -0500 Subject: [App_rpt-users] one node registering but no dnsmgr Message-ID: Can connect to some nodes. 2360*CLI> iax2 show registry Host????????????????? dnsmgr? Username??? Perceived Refresh? State 44.98.254.145:4569??? N?????? 2360 108.198.90.149:4570??????? 60? Registered 2360*CLI> This is also running Limey 1.15 GeorgeC W2DB 2360 28599 --- This email has been checked for viruses by AVG. https://www.avg.com From Bryan at bryanfields.net Sun Aug 12 18:48:39 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Sun, 12 Aug 2018 14:48:39 -0400 Subject: [App_rpt-users] one node registering but no dnsmgr In-Reply-To: References: Message-ID: <971dbea9-4d6f-d0da-544e-ba14f5f4ced5@bryanfields.net> On 8/12/18 2:24 PM, George Csahanin wrote: > 2360*CLI> iax2 show registry > Host????????????????? dnsmgr? Username??? Perceived Refresh? State > 44.98.254.145:4569??? N?????? 2360 108.198.90.149:4570??????? 60? Registered > 2360*CLI> > > This is also running Limey 1.15 Yea, all dnsmgr does is refresh the dns lookups with out needing to restart asterisk or your server. If you enable this in modules.conf, it will refresh dns ever 5 min. This is why many of the older servers are still trying to register to the server in LA, and why we suggested they be restarted. If you have any specific node issues, let us know, but right now you're registered and online. 73's -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From tisawyer at gmail.com Sun Aug 12 18:52:53 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Sun, 12 Aug 2018 11:52:53 -0700 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> Message-ID: I too have seen this, with improperly configured MikroTik routers. On Sun, Aug 12, 2018 at 9:21 AM Michael Wolthuis wrote: > I have seen this before if you are using PFSense as your outbound router > and you are NOT static locking NAT outbound, it will pick a port at > random. Other firewalls have also done it if not set for static, but most > consumer grade routers do NOT mangle NAT this way. > > Mike > Kb8zgl > > > ?On 8/12/18, 12:06 PM, "App_rpt-users on behalf of Bryan Fields" < > app_rpt-users-bounces at lists.allstarlink.org on behalf of > Bryan at bryanfields.net> wrote: > > On 8/12/18 12:06 PM, Paul - KN2R wrote: > > I have all set and been using port 44569 for well over a year on that > > server. > > Now this morning the registration server is reporting the incorrect > port > > number of 54799. > > I Never used that number. Now inbound connections are not working > any more. > > Ok, are you behind NAT? What are you doing there that iax is not > connecting > outbound with a source port of 44569? > > I just pulled a dump of your traffic to the registration server and I > see > you're hitting it with a source port of 54799, not 44569. I think > this has to > be some nat funkyness, using a different outgoing port vs incoming. > > Can you check that and give some details if you are behind nat as to > the setup > you have? > > Thanks, > -- > Bryan Fields > > 727-409-1194 - Voice > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From kj6ko at innercite.com Sun Aug 12 19:59:40 2018 From: kj6ko at innercite.com (Greg Stahlman) Date: Sun, 12 Aug 2018 12:59:40 -0700 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> Message-ID: <000001d43277$02122e70$06368b50$@innercite.com> Getting this on a couple of my nodes this morning. [Aug 12 12:55:50] NOTICE[2004]: chan_iax2.c:9712 socket_process: Registration of '29827' rejected: '' from: '67.215.233.178' -----Original Message----- From: App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] On Behalf Of Michael Wolthuis Sent: Sunday, August 12, 2018 9:22 AM To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] BIG registration problem this morning I have seen this before if you are using PFSense as your outbound router and you are NOT static locking NAT outbound, it will pick a port at random. Other firewalls have also done it if not set for static, but most consumer grade routers do NOT mangle NAT this way. Mike Kb8zgl ?On 8/12/18, 12:06 PM, "App_rpt-users on behalf of Bryan Fields" wrote: On 8/12/18 12:06 PM, Paul - KN2R wrote: > I have all set and been using port 44569 for well over a year on that > server. > Now this morning the registration server is reporting the incorrect port > number of 54799. > I Never used that number. Now inbound connections are not working any more. Ok, are you behind NAT? What are you doing there that iax is not connecting outbound with a source port of 44569? I just pulled a dump of your traffic to the registration server and I see you're hitting it with a source port of 54799, not 44569. I think this has to be some nat funkyness, using a different outgoing port vs incoming. Can you check that and give some details if you are behind nat as to the setup you have? Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. From Bryan at bryanfields.net Sun Aug 12 21:53:34 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Sun, 12 Aug 2018 17:53:34 -0400 Subject: [App_rpt-users] IP List, L00K Please Message-ID: <01d8a82b-09c3-008d-a52e-8346b224be8b@bryanfields.net> We've been tracking some performance issues with the registration service and found a number of nodes badgering with IAX registrations for invalid node numbers. These IP's have been black-holed on the servers now so as to not cause the larger issues. Keep in mind these are public IP's, so check if your node isn't registering and then check it's public IP. If it's below, please hit us up with the IP and node number(s) at helpdesk at allstarlink.org and we'll get you going. 108.198.90.149 108.206.232.96 115.187.139.133 155.186.240.206 162.251.189.146 166.130.154.56 173.163.76.73 174.18.157.76 174.214.14.206 174.94.157.48 199.0.207.38 199.167.96.50 199.188.136.222 199.188.138.214 208.122.115.53 216.67.40.50 24.104.74.198 24.179.104.123 24.180.12.178 44.25.128.121 47.50.155.134 67.58.206.154 68.145.212.61 68.15.179.212 70.15.18.172 70.175.65.252 71.205.206.122 71.63.182.199 71.95.13.254 72.253.204.91 Thank you, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From Bryan at bryanfields.net Mon Aug 13 01:53:35 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Sun, 12 Aug 2018 21:53:35 -0400 Subject: [App_rpt-users] IP List, L00K Please In-Reply-To: <01d8a82b-09c3-008d-a52e-8346b224be8b@bryanfields.net> References: <01d8a82b-09c3-008d-a52e-8346b224be8b@bryanfields.net> Message-ID: <782e50a5-ecfe-85c8-a24e-e0433e90a5f0@bryanfields.net> On 8/12/18 5:53 PM, Bryan Fields wrote: > We've been tracking some performance issues with the registration service and > found a number of nodes badgering with IAX registrations for invalid node > numbers. These IP's have been black-holed on the servers now so as to not > cause the larger issues. > > Keep in mind these are public IP's, so check if your node isn't registering > and then check it's public IP. If it's below, please hit us up with the IP > and node number(s) at helpdesk at allstarlink.org and we'll get you going. Additional IP: 172.10.225.182 thanks! -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From tisawyer at gmail.com Mon Aug 13 03:02:33 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Sun, 12 Aug 2018 20:02:33 -0700 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: <000001d43277$02122e70$06368b50$@innercite.com> References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> <000001d43277$02122e70$06368b50$@innercite.com> Message-ID: One of the ways to test registration is to add the register line to another server on a different network. I'm one of the Allstar admins so I can lookup your node password. I added your 2577 node to a test server here at home. As you can see (below) it assumes the port I have configured for this node. All is ok, system is working the way it's suposed to. I suspect 'iax2 show registry' on your system has long shown the incorrect ports, but it still worked because the portal configuration overrode the network reported port. The new system uses the port reported by the network and ignores the portal config. That has advantage of not needing to set you server port on the allstarlink.org site. So now you need to figure out why the network is reporting the wrong port. Hope this helps. I've removed your registration from my node as the test is complete. *CLI> iax2 show registry Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 2577 47.157.254.238:4567 60 Registered 44.98.254.145:4569 Y 2502 47.157.254.238:4567 60 Registered On Sun, Aug 12, 2018 at 12:59 PM Greg Stahlman wrote: > Getting this on a couple of my nodes this morning. > > [Aug 12 12:55:50] NOTICE[2004]: chan_iax2.c:9712 socket_process: > Registration of '29827' rejected: '' from: '67.215.233.178' > > -----Original Message----- > From: App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] > On Behalf Of Michael Wolthuis > Sent: Sunday, August 12, 2018 9:22 AM > To: Users of Asterisk app_rpt > Subject: Re: [App_rpt-users] BIG registration problem this morning > > I have seen this before if you are using PFSense as your outbound router > and you are NOT static locking NAT outbound, it will pick a port at > random. Other firewalls have also done it if not set for static, but most > consumer grade routers do NOT mangle NAT this way. > > Mike > Kb8zgl > > > ?On 8/12/18, 12:06 PM, "App_rpt-users on behalf of Bryan Fields" < > app_rpt-users-bounces at lists.allstarlink.org on behalf of > Bryan at bryanfields.net> wrote: > > On 8/12/18 12:06 PM, Paul - KN2R wrote: > > I have all set and been using port 44569 for well over a year on that > > server. > > Now this morning the registration server is reporting the incorrect > port > > number of 54799. > > I Never used that number. Now inbound connections are not working > any more. > > Ok, are you behind NAT? What are you doing there that iax is not > connecting > outbound with a source port of 44569? > > I just pulled a dump of your traffic to the registration server and I > see > you're hitting it with a source port of 54799, not 44569. I think > this has to > be some nat funkyness, using a different outgoing port vs incoming. > > Can you check that and give some details if you are behind nat as to > the setup > you have? > > Thanks, > -- > Bryan Fields > > 727-409-1194 - Voice > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From k5cg at hamoperator.org Mon Aug 13 03:06:40 2018 From: k5cg at hamoperator.org (Danny K5CG) Date: Sun, 12 Aug 2018 20:06:40 -0700 (PDT) Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: <000001d43277$02122e70$06368b50$@innercite.com> References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> <000001d43277$02122e70$06368b50$@innercite.com> Message-ID: <1806791267.65281.1534129600629.JavaMail.zimbra@siminiuk.com> I'm running pfSense and I "could" setup a static port for the outbound NAT but since when does the source port ever match the destination port, for any protocol? I'm not touching it. 46679*CLI> iax2 show registry Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 46679 47.187.195.172:29961 60 Auth. Sent 4569 is what's set on the portal for my node. 29961 appears to be what is recorded on the server from my registration. The portal port needs to be used or there has to be a way to set the port in rpt.conf to have that communicated to the registration server. Relying on the source port (which can be anything) is not a good idea. Next steps? Danny K5CG From tisawyer at gmail.com Mon Aug 13 05:15:14 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Sun, 12 Aug 2018 22:15:14 -0700 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: <1806791267.65281.1534129600629.JavaMail.zimbra@siminiuk.com> References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> <000001d43277$02122e70$06368b50$@innercite.com> <1806791267.65281.1534129600629.JavaMail.zimbra@siminiuk.com> Message-ID: Why do some nodes not have this problem? Is NAT somehow different from different routers? I'd really like to understand so I can take it back to the technical folks and explain why it needs to be put back the way it was. On Sun, Aug 12, 2018 at 8:06 PM Danny K5CG wrote: > I'm running pfSense and I "could" setup a static port for the outbound NAT > but since when does the source port ever match the destination port, for > any protocol? I'm not touching it. > > 46679*CLI> iax2 show registry > Host dnsmgr Username Perceived > Refresh State > 44.98.254.145:4569 Y 46679 47.187.195.172:29961 > 60 Auth. Sent > > 4569 is what's set on the portal for my node. 29961 appears to be what is > recorded on the server from my registration. > > The portal port needs to be used or there has to be a way to set the port > in rpt.conf to have that communicated to the registration server. Relying > on the source port (which can be anything) is not a good idea. > > Next steps? > > Danny > K5CG > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From bryan at k6cbr.us Mon Aug 13 05:31:50 2018 From: bryan at k6cbr.us (Bryan St Clair) Date: Sun, 12 Aug 2018 22:31:50 -0700 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> <000001d43277$02122e70$06368b50$@innercite.com> <1806791267.65281.1534129600629.JavaMail.zimbra@siminiuk.com> Message-ID: My understanding pfSense rewrites the source port on outgoing packets. Not all router manufacturers do this. On Sun, Aug 12, 2018 at 10:15 PM, Tim Sawyer wrote: > Why do some nodes not have this problem? Is NAT somehow different from > different routers? I'd really like to understand so I can take it back to > the technical folks and explain why it needs to be put back the way it was. > > On Sun, Aug 12, 2018 at 8:06 PM Danny K5CG wrote: >> >> I'm running pfSense and I "could" setup a static port for the outbound NAT >> but since when does the source port ever match the destination port, for any >> protocol? I'm not touching it. >> >> 46679*CLI> iax2 show registry >> Host dnsmgr Username Perceived >> Refresh State >> 44.98.254.145:4569 Y 46679 47.187.195.172:29961 >> 60 Auth. Sent >> >> 4569 is what's set on the portal for my node. 29961 appears to be what is >> recorded on the server from my registration. >> >> The portal port needs to be used or there has to be a way to set the port >> in rpt.conf to have that communicated to the registration server. Relying on >> the source port (which can be anything) is not a good idea. >> >> Next steps? >> >> Danny >> K5CG >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. > > > > -- > Tim WD6AWP > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Bryan K6CBR bryan at k6cbr.us Allstar Base: 43918, 43991 Allstar Hub: 43919, 47036 www.k6cbr.us QRZ From Bryan at bryanfields.net Mon Aug 13 06:34:08 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Mon, 13 Aug 2018 02:34:08 -0400 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: <1806791267.65281.1534129600629.JavaMail.zimbra@siminiuk.com> References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> <000001d43277$02122e70$06368b50$@innercite.com> <1806791267.65281.1534129600629.JavaMail.zimbra@siminiuk.com> Message-ID: <4b1c671a-cebf-330b-f963-cbd42668c3a6@bryanfields.net> On 8/12/18 11:06 PM, Danny K5CG wrote: > I'm running pfSense and I "could" setup a static port for the outbound NAT > but since when does the source port ever match the destination port, for > any protocol? I'm not touching it. Most VoIP-ish protocols require what's known as "full cone NAT". This is where a router/packet mangler takes an external address and port/protocol and maps it to the same internal port/protocol in a bidirectional fashion. When you "port forward" on most consumer grade routers, it creates a full cone NAT. Many consumer routers do full-cone NAT for dynamic protocols as well. Due to IAX being UDP based (stateless) most NAT implementations will automatically map this in both directions, for all external hosts. Simply put if your internal device uses port 5000 it will map as follows: Outbound direction: IntIP:srcPort-5000 > NAT device > ExtSrcIP:srcPort-5000 > ExtDstIP:dst-5000 If the router is doing full-cone NAT (most consumer grade routers do this by default it will add a mapping like this automagically: Inbound direction: IntSrcIP:dst5000 < NAT device < *:5000 This has the distinct advantage of just working behind NAT for certain realtime protocols without needing an application aware gateway. This does however open up the world inbound if you know this, so most higher end firewalls don't do this, and will lock down that inbound connection to what the source has talked to externally. This requires some memory and connection tracking of UDP. When you configure outbound PAT or port address translation which is a many to one, the router will dynamically remap your source ports on the external device so they don't overlap with other users on your network. This will map the local source port of say 4569 to some random high value, say 75401. Your packet will now go out and talk to the external user as your extIP:src75401:dst4569. With IAX, the external user will now be able to talk back to you as there's a mapping on your router of externalHostIP:dst75401 to your internalIP:dst4569, but it's only valid for that one external Host of the IAX server. No other servers can use externalIP:dst75401 to talk to your IAX server as the external srcIP is different. The way to solve this is to statically map extIP:dst4569 to intIP:dst4569 and ensure intIP:4569 to extIP: is not mangled but allowed to pass to extIP:4569. SIP solves this via application layer gateways (ALG) on firewalls, same as FTP. This will make a full cone NAT and is what's needed for IAX to work. Right now you have a unidirectional mapping from ext to int, but not int to ext. Further reading: https://en.wikipedia.org/wiki/Network_address_translation#Methods_of_translation > 46679*CLI> iax2 show registry Host dnsmgr Username > Perceived Refresh State 44.98.254.145:4569 Y 46679 > 47.187.195.172:29961 60 Auth. Sent > > 4569 is what's set on the portal for my node. 29961 appears to be what is > recorded on the server from my registration. Yea, that was a dirty hack. > The portal port needs to be used or there has to be a way to set the port > in rpt.conf to have that communicated to the registration server. Relying > on the source port (which can be anything) is not a good idea. 95% of the time it works every time. Your have a corner case, and as you have a decent packet filter (pfsense) it's easily configured to work for this. Based on this doc, https://www.3cx.com/docs/pfsense-firewall/ you will need to enable "Port Preservation" for your IAX server. > Next steps? Turn on Port Preservation and report back. Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From david.osborn at manx.net Mon Aug 13 10:06:37 2018 From: david.osborn at manx.net (David Osborn) Date: Mon, 13 Aug 2018 11:06:37 +0100 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: <004e01d43256$6e432f20$4ac98d60$@com> References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> Message-ID: <002f01d432ed$53335ce0$f99a16a0$@manx.net> I'm afraid that I, too now have this issue with three of my four nodes. Like Paul, no changes have been made for many, many months (or even years) but suddenly, AllStar has got its ports in a knot. The only one that's right is 2481 which is on its own ADSL connection. The other three share a common public IP. There are the outputs from iax2 show registry on each node and, below that, the relevant bindport line from iax.conf Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 N 2480 87.254.91.169:15280 60 Auth. Sent bindport=4568 Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 2481 89.107.6.110:4569 60 Registered bindport=4569 Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 N 2482 87.254.91.169:25963 60 Registered bindport=4569 Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 2484 87.254.91.169:43287 60 Registered bindport = 4570 (2480, 2482 and 2484 are all on a private LAN behind the same NAT firewall, hence the different iax ports) I'm also seeing plenty of these: NOTICE[351]: chan_iax2.c:9712 socket_process: Registration of '2481' rejected: '' from: '44.98.254.145' for all nodes Subsequently, registration succeeds without intervention from me. Something's gone awry. Any ideas? David Osborn - GD4HOZ -----Original Message----- From: Paul - KN2R [mailto:paulkn2r at gmail.com] Sent: 12 August 2018 17:06 To: 'Users of Asterisk app_rpt' Subject: Re: [App_rpt-users] BIG registration problem this morning I have all set and been using port 44569 for well over a year on that server. Now this morning the registration server is reporting the incorrect port number of 54799. I Never used that number. Now inbound connections are not working any more. Paul -----Original Message----- From: App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] On Behalf Of Bryan Fields Sent: Sunday, August 12, 2018 11:27 AM To: app_rpt-users at lists.allstarlink.org Subject: Re: [App_rpt-users] BIG registration problem this morning On 8/12/18 9:11 AM, Paul - KN2R wrote: > This morning ALL my nodes are somehow reporting wrong AllStar port > numbers from Registration server. Every one of them. > > > > A search shows port 54799, shown below for my node 27034. > > But the actual port I have defined everywhere is and should be 44569! > > Where did that 54799 number come from? All my incoming connections > are down at this point. >From the server: iax2 show peer 27034 * Name : 27034 Description : Secret : Context : radio-in Parking lot : Mailbox : Dynamic : Yes Callnum limit: 0 Calltoken req: No Trunk : No Encryption : No Callerid : "" <> Expire : 45018 ACL : No Addr->IP : 76.101.48.66 Port 54799 Defaddr->IP : (null) Port (null) Username : Codecs : (gsm|ulaw|alaw|g726aal2|adpcm|slin|g729|speex|ilbc|g726|g722|siren7|siren14| slin16) Codec Order : (ulaw|alaw|siren14|siren7|g722|slin16|slin|g726|g726aal2|adpcm|gsm|ilbc|spee x|g729) Status : Unmonitored Qualify : every 60000ms when OK, every 10000ms when UNREACHABLE (sample smoothing Off) You're registering with that port number. Can you check your bound port number? Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. From paulkn2r at gmail.com Mon Aug 13 10:51:12 2018 From: paulkn2r at gmail.com (Paul - KN2R) Date: Mon, 13 Aug 2018 06:51:12 -0400 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> <000001d43277$02122e70$06368b50$@innercite.com> <1806791267.65281.1534129600629.JavaMail.zimbra@siminiuk.com> Message-ID: <001801d432f3$8d488990$a7d99cb0$@com> Tim, I am for putting the previous Registration server back in operation! All my nodes are having problems registering with different port numbers I do not have configured anywhere. I use a commercial grade SonicWall TZ-205N firewall/router which has been working fine for years! No changes have been made to that server or the router in over a year or two. Now all of a sudden, since the change, all is not working. Paul / KN2R From: App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] On Behalf Of Tim Sawyer Sent: Monday, August 13, 2018 1:15 AM To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] BIG registration problem this morning Why do some nodes not have this problem? Is NAT somehow different from different routers? I'd really like to understand so I can take it back to the technical folks and explain why it needs to be put back the way it was. On Sun, Aug 12, 2018 at 8:06 PM Danny K5CG wrote: I'm running pfSense and I "could" setup a static port for the outbound NAT but since when does the source port ever match the destination port, for any protocol? I'm not touching it. 46679*CLI> iax2 show registry Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 46679 47.187.195.172:29961 60 Auth. Sent 4569 is what's set on the portal for my node. 29961 appears to be what is recorded on the server from my registration. The portal port needs to be used or there has to be a way to set the port in rpt.conf to have that communicated to the registration server. Relying on the source port (which can be anything) is not a good idea. Next steps? Danny K5CG _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From harvard5362 at yahoo.com Mon Aug 13 12:40:48 2018 From: harvard5362 at yahoo.com (C B) Date: Mon, 13 Aug 2018 12:40:48 +0000 (UTC) Subject: [App_rpt-users] My ip blacklisted, ticket 602 In-Reply-To: <1529575896.2164591.1534163896738@mail.yahoo.com> References: <1529575896.2164591.1534163896738.ref@mail.yahoo.com> <1529575896.2164591.1534163896738@mail.yahoo.com> Message-ID: <376498360.6847731.1534164048341@mail.yahoo.com> My ip address was blacklisted according to an email set to the group. ticket 602 was opened. the reason given was that i had some private nodes (mostly aux receivers) trying to register. that was corrected. the ip address was likely unblocked as my node was registered again. then i was told i have the following error [Aug 13 01:57:19] NOTICE[18339]: chan_iax2.c:8284 register_verify: No registration for peer 'xxxxx' (from ip address removed) Please note the xxxxx was the node number given in the email from the allstar staff i enquired how to find this amongst the more that 40 nodes behind the firewall on my system. the response was? "idk, it's behind your IP.? tcpdump or wireshark?" IDK was looked up as i do not routinely use internet acronyms, the most likely answers where IDK = "i don't care" or IDK = "i don't know" wireshark filters where requested as i do not know how the registration process works. No reply. then my ip address was apparently blacklisted again CLI> iax2 show registryHost? ? ? ? ? ? ? ? ? dnsmgr? Username? ? ? ? Perceived? ? ? ? ? ? ?Refresh? State44.98.254.145:4569? ? Y? ? ? ?29883? ? ? ? ? ?? ? ? ? ? ? ?60? Request Sent As i do not know how to find node xxxxx nor do i understand what data the registration process sent to make it work thus i can not make a filter to find the issue and i am not a wireshark expert thus i will not be able to resolve this issue. note i did try the following filters tcp contains "node" udp contains "node" tcp contains "register" udp contains "register" udp contains "register.allstarlink.org" tcp contains "register.allstarlink.org" tcp contains "xxxxx" udp contains "xxxxx" all with no results Chris - - Chris via RT? ? - - Aug 12 at 7:09?PM - To - - harvard5362 at yahoo.com - Message body as most of my nodes have unique port numbers is there a way for you to tell the iax port number? From:?Chris via RT To:?harvard5362 at yahoo.com? Sent:?Sunday, August 12, 2018 7:06 PM Subject:?Re: [AllStar #602] 71.95.13.254 blacklisted i am not the best at wireshark (i do use it a little) any idea of a filter to look for it? thanks for your help < b>From:?Bryan via RT To:?harvard5362 at yahoo.com? Sent:?Sunday, August 12, 2018 7:04 PM Subject:?[AllStar #602] 71.95.13.254 blacklisted idk, it's behind your IP.? tcpdump or wireshark? This is why I hate NAT :)--? Bryan Fields, W9CR AllStarLink, Inc.?On Sun Aug 12 22:02:30 2018, N6LXX wrote: Ok i must not have saved the changes on 1121 and 1123?they should be good now.?how am i going to find node xxxx? that has me stumped. ?From:?Bryan via RT To:?harvard5362 at yahoo.com Sent:?Sunday, August 12, 2018 6:58 PM Subject:?[AllStar #602] 71.95.13.254 blacklisted?[Aug 13 01:57:19] NOTICE[18339]: chan_iax2.c:8284 register_verify: No registration for peer 'xxxxx' (ip address removed) that's a new one too. Thanks,--? Bryan Fields, W9CR AllStarLink, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From k2krs at arrl.net Mon Aug 13 13:53:36 2018 From: k2krs at arrl.net (K2KRS Ken) Date: Mon, 13 Aug 2018 08:53:36 -0500 Subject: [App_rpt-users] no longer in the database, Can not find info Message-ID: <42f0d1c81c7a47a5ce5b0ec5c65136af@arrl.net> Good Morning, I had a node running, pretty basic default setup for a while then this weekend I added a another server/node but it's on a completely different offsite network so no issues with ports from the first interfering with ports from the second. Both of them show up on https://allstarlink.org/nodelist.php with a green online status but neither show up on http://stats.allstarlink.org The first one 48198 used to show up on http://stats.allstarlink.org but as of this weekend it no longer is there. I know there were some changes on the infrastructure side of things just wondering if I should wait it out and see what happens or if there is something on my end I can do to look into what is going on. My first node 48198 has been and will continue to be on a Verizon jetpack. While I did go ahead and setup port forwarding on the jetpack I heard Verizon doesn't allow incoming connections. My second one that I created this weekend 48715 is 'in the cloud'. So it has a lot more bandwidth and should be able to receive incoming connections. When I click on the links on nodelist.php I get these: Node 48198 is no longer in the database Can not find info for node 48715 I'm open to any suggestions on changing .conf files or obtaining any logging from either of them. Enjoy today! Ken From flatpossum1231 at yahoo.com Mon Aug 13 14:17:41 2018 From: flatpossum1231 at yahoo.com (Mr. Possum (Bill)) Date: Mon, 13 Aug 2018 14:17:41 +0000 (UTC) Subject: [App_rpt-users] no longer in the database, Can not find info In-Reply-To: <42f0d1c81c7a47a5ce5b0ec5c65136af@arrl.net> References: <42f0d1c81c7a47a5ce5b0ec5c65136af@arrl.net> Message-ID: <762126767.6005675.1534169862014@mail.yahoo.com> Hi Ken, I feel your pain - I did some reconfiguration on some nodes that have been around for a LONG time and yeah....? Allstarlink.org servers have lost their mind... Nodes that never had problems showing up are now bouncing registration several times an HOUR!? Rejects are crawling across my CLI screens incessantly... Sit back, be patient and wait it out for a bit...? A "fix" is in the works, we are told! Patience isn't necessarily my strong suit!? (ahem!) Bill - N5MBM From: K2KRS Ken To: Users of Asterisk app_rpt Sent: Monday, August 13, 2018 8:53 AM Subject: [App_rpt-users] no longer in the database, Can not find info Good Morning, I had a node running, pretty basic default setup for a while then this weekend I added a another server/node but it's on a completely different offsite network so no issues with ports from the first interfering with ports from the second. Both of them show up on https://allstarlink.org/nodelist.php with a green online status but neither show up on http://stats.allstarlink.org The first one 48198 used to show up on http://stats.allstarlink.org but as of this weekend it no longer is there. I know there were some changes on the infrastructure side of things just wondering if I should wait it out and see what happens or if there is something on my end I can do to look into what is going on. My first node 48198 has been and will continue to be on a Verizon jetpack.? While I did go ahead and setup port forwarding on the jetpack I heard Verizon doesn't allow incoming connections. My second one that I created this weekend 48715 is 'in the cloud'. So it has a lot more bandwidth and should be able to receive incoming connections. When I click on the links on nodelist.php I get these: Node 48198 is no longer in the database Can not find info for node 48715 I'm open to any suggestions on changing .conf files or obtaining any logging from either of them. Enjoy today! Ken _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mwbesemer at cox.net Mon Aug 13 14:31:11 2018 From: mwbesemer at cox.net (Mike Besemer - WM4B) Date: Mon, 13 Aug 2018 14:31:11 +0000 (GMT) Subject: [App_rpt-users] no longer in the database, Can not find info Message-ID: <3115ba.74b1.16533b2aa35.Webtop.0@cox.net> I'm showing up in both lists, but used to show green on https://allstarlink.org/nodelist.php, but I don't now. Then again, I'm not really sure what makes it show up green; seems like the majority of the nodes listed do not. Mike WM4B On Mon, Aug 13, 2018 at 9:53 AM, K2KRS Ken wrote: > Good Morning, > > I had a node running, pretty basic default setup for a while then this > weekend > I added a another server/node but it's on a completely different > offsite network so no issues > with ports from the first interfering with ports from the second. > > Both of them show up on https://allstarlink.org/nodelist.php with a > green online status but > neither show up on http://stats.allstarlink.org > > The first one 48198 used to show up on http://stats.allstarlink.org > but as of this weekend it no > longer is there. > > I know there were some changes on the infrastructure side of things > just wondering if I should > wait it out and see what happens or if there is something on my end I > can do to look into what is > going on. > > My first node 48198 has been and will continue to be on a Verizon > jetpack. While I did go ahead and setup port forwarding on the > jetpack I heard Verizon doesn't allow incoming connections. > > My second one that I created this weekend 48715 is 'in the cloud'. So > it has a lot more bandwidth and should be able to receive incoming > connections. > > When I click on the links on nodelist.php I get these: > Node 48198 is no longer in the database > Can not find info for node 48715 > > I'm open to any suggestions on changing .conf files or obtaining any > logging from either of them. > > Enjoy today! > Ken > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. From tisawyer at gmail.com Mon Aug 13 14:35:42 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Mon, 13 Aug 2018 07:35:42 -0700 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: <001801d432f3$8d488990$a7d99cb0$@com> References: <003401d4323e$050371e0$0f0a55a0$@com> <0e39d498-5f97-4c3a-70b0-8584cb4d0ddf@bryanfields.net> <004e01d43256$6e432f20$4ac98d60$@com> <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> <000001d43277$02122e70$06368b50$@innercite.com> <1806791267.65281.1534129600629.JavaMail.zimbra@siminiuk.com> <001801d432f3$8d488990$a7d99cb0$@com> Message-ID: I'm partially responsible for this change. I want to make the AllStar portal as simple to use as possible. It seemed to me that not having to put the IAX port in the portal would make life easier. I forget to do that when I move or setup new servers as have many others. When I discovered Asterisk is reporting the actual source port to the portal database I thought it would make sense to use that port for the nodes list. On Mon, Aug 13, 2018 at 3:48 AM Paul - KN2R wrote: > Tim, > > > > I am for putting the previous Registration server back in operation! > > > > All my nodes are having problems registering with different port numbers I > do not have configured anywhere. > > I use a commercial grade SonicWall TZ-205N firewall/router which has been > working fine for years! > > No changes have been made to that server or the router in over a year or > two. Now all of a sudden, since the change, all is *not* working. > > > > Paul / KN2R > > > > > > *From:* App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] > *On Behalf Of *Tim Sawyer > *Sent:* Monday, August 13, 2018 1:15 AM > *To:* Users of Asterisk app_rpt > *Subject:* Re: [App_rpt-users] BIG registration problem this morning > > > > Why do some nodes not have this problem? Is NAT somehow different from > different routers? I'd really like to understand so I can take it back to > the technical folks and explain why it needs to be put back the way it was. > > > > On Sun, Aug 12, 2018 at 8:06 PM Danny K5CG wrote: > > I'm running pfSense and I "could" setup a static port for the outbound NAT > but since when does the source port ever match the destination port, for > any protocol? I'm not touching it. > > 46679*CLI> iax2 show registry > Host dnsmgr Username Perceived > Refresh State > 44.98.254.145:4569 Y 46679 47.187.195.172:29961 > 60 Auth. Sent > > 4569 is what's set on the portal for my node. 29961 appears to be what is > recorded on the server from my registration. > > The portal port needs to be used or there has to be a way to set the port > in rpt.conf to have that communicated to the registration server. Relying > on the source port (which can be anything) is not a good idea. > > Next steps? > > Danny > K5CG > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > > > > > -- > > Tim WD6AWP > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From k5cg at hamoperator.org Mon Aug 13 15:10:26 2018 From: k5cg at hamoperator.org (Danny K5CG) Date: Mon, 13 Aug 2018 08:10:26 -0700 (PDT) Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: References: <003401d4323e$050371e0$0f0a55a0$@com> <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> <000001d43277$02122e70$06368b50$@innercite.com> <1806791267.65281.1534129600629.JavaMail.zimbra@siminiuk.com> <001801d432f3$8d488990$a7d99cb0$@com> Message-ID: <1448032737.16542.1534173026903.JavaMail.zimbra@siminiuk.com> Tim, Because some routers follow the assumption doesn't make it a universal concept that applies to all. You have to assume the source port is unpredictable and random. If I rebooted my node, my router or just disconnected my Internet, it would likely be different source port every time it reconnected and registered. Danny K5CG From: "Tim Sawyer" To: "Users of Asterisk app_rpt" Sent: Monday, August 13, 2018 9:35:42 AM Subject: Re: [App_rpt-users] BIG registration problem this morning I'm partially responsible for this change. I want to make the AllStar portal as simple to use as possible. It seemed to me that not having to put the IAX port in the portal would make life easier. I forget to do that when I move or setup new servers as have many others. When I discovered Asterisk is reporting the actual source port to the portal database I thought it would make sense to use that port for the nodes list. On Mon, Aug 13, 2018 at 3:48 AM Paul - KN2R < [ mailto:paulkn2r at gmail.com | paulkn2r at gmail.com ] > wrote: Tim, I am for putting the previous Registration server back in operation! All my nodes are having problems registering with different port numbers I do not have configured anywhere. I use a commercial grade SonicWall TZ-205N firewall/router which has been working fine for years! No changes have been made to that server or the router in over a year or two. Now all of a sudden, since the change, all is not working. Paul / KN2R From: App_rpt-users [mailto: [ mailto:app_rpt-users-bounces at lists.allstarlink.org | app_rpt-users-bounces at lists.allstarlink.org ] ] On Behalf Of Tim Sawyer Sent: Monday, August 13, 2018 1:15 AM To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] BIG registration problem this morning Why do some nodes not have this problem? Is NAT somehow different from different routers? I'd really like to understand so I can take it back to the technical folks and explain why it needs to be put back the way it was. On Sun, Aug 12, 2018 at 8:06 PM Danny K5CG < [ mailto:k5cg at hamoperator.org | k5cg at hamoperator.org ] > wrote: BQ_BEGIN I'm running pfSense and I "could" setup a static port for the outbound NAT but since when does the source port ever match the destination port, for any protocol? I'm not touching it. 46679*CLI> iax2 show registry Host dnsmgr Username Perceived Refresh State [ http://44.98.254.145:4569/ | 44.98.254.145:4569 ] Y 46679 [ http://47.187.195.172:29961/ | 47.187.195.172:29961 ] 60 Auth. Sent 4569 is what's set on the portal for my node. 29961 appears to be what is recorded on the server from my registration. The portal port needs to be used or there has to be a way to set the port in rpt.conf to have that communicated to the registration server. Relying on the source port (which can be anything) is not a good idea. Next steps? Danny K5CG _______________________________________________ App_rpt-users mailing list [ mailto:App_rpt-users at lists.allstarlink.org | App_rpt-users at lists.allstarlink.org ] [ http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users | http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users ] To unsubscribe from this list please visit [ http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users | http://lists.allstarlink.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. -- Tim WD6AWP _______________________________________________ App_rpt-users mailing list [ mailto:App_rpt-users at lists.allstarlink.org | App_rpt-users at lists.allstarlink.org ] [ http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users | http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users ] To unsubscribe from this list please visit [ http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users | http://lists.allstarlink.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. BQ_END -- Tim WD6AWP _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mwbesemer at cox.net Mon Aug 13 15:19:50 2018 From: mwbesemer at cox.net (Mike Besemer - WM4B) Date: Mon, 13 Aug 2018 15:19:50 +0000 (GMT) Subject: [App_rpt-users] no longer in the database, Can not find info Message-ID: Ken, I'm connected to 48715 right now. 48198 is showing registered now, but I can't connect to it. You must be right about Verizon not allowing incoming connects. Mike WM4B On Mon, Aug 13, 2018 at 9:53 AM, K2KRS Ken wrote: > Good Morning, > > I had a node running, pretty basic default setup for a while then this > weekend > I added a another server/node but it's on a completely different > offsite network so no issues > with ports from the first interfering with ports from the second. > > Both of them show up on https://allstarlink.org/nodelist.php with a > green online status but > neither show up on http://stats.allstarlink.org > > The first one 48198 used to show up on http://stats.allstarlink.org > but as of this weekend it no > longer is there. > > I know there were some changes on the infrastructure side of things > just wondering if I should > wait it out and see what happens or if there is something on my end I > can do to look into what is > going on. > > My first node 48198 has been and will continue to be on a Verizon > jetpack. While I did go ahead and setup port forwarding on the > jetpack I heard Verizon doesn't allow incoming connections. > > My second one that I created this weekend 48715 is 'in the cloud'. So > it has a lot more bandwidth and should be able to receive incoming > connections. > > When I click on the links on nodelist.php I get these: > Node 48198 is no longer in the database > Can not find info for node 48715 > > I'm open to any suggestions on changing .conf files or obtaining any > logging from either of them. > > Enjoy today! > Ken > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. From nhardman1428 at gmail.com Mon Aug 13 15:30:02 2018 From: nhardman1428 at gmail.com (Nate Hardman) Date: Mon, 13 Aug 2018 11:30:02 -0400 Subject: [App_rpt-users] no longer in the database, Can not find info In-Reply-To: <42f0d1c81c7a47a5ce5b0ec5c65136af@arrl.net> References: <42f0d1c81c7a47a5ce5b0ec5c65136af@arrl.net> Message-ID: https://allstarlink.org/nodelist.php and http://stats.allstarlink.org/nodeinfo.cgi?node=48198 are two separate systems. please check your line in iax.conf file for the register= 48198;XXXXXX at register.allstarlink.org where XXXXXX is your registration password once this is complete you should show green on the nodelist please check you line in rpt.conf file for statpost_program = /usr/bin/wget,............. line and ensure it is NOT commented out with (;) in front once this is complete you should be posting stats to the stats server. asterisk reload will be required for changes to take effect. On Mon, Aug 13, 2018 at 9:53 AM, K2KRS Ken wrote: > Good Morning, > > I had a node running, pretty basic default setup for a while then this > weekend > I added a another server/node but it's on a completely different offsite > network so no issues > with ports from the first interfering with ports from the second. > > Both of them show up on https://allstarlink.org/nodelist.php with a green > online status but > neither show up on http://stats.allstarlink.org > > The first one 48198 used to show up on http://stats.allstarlink.org but > as of this weekend it no > longer is there. > > I know there were some changes on the infrastructure side of things just > wondering if I should > wait it out and see what happens or if there is something on my end I can > do to look into what is > going on. > > My first node 48198 has been and will continue to be on a Verizon > jetpack. While I did go ahead and setup port forwarding on the jetpack I > heard Verizon doesn't allow incoming connections. > > My second one that I created this weekend 48715 is 'in the cloud'. So it > has a lot more bandwidth and should be able to receive incoming connections. > > When I click on the links on nodelist.php I get these: > Node 48198 is no longer in the database > Can not find info for node 48715 > > I'm open to any suggestions on changing .conf files or obtaining any > logging from either of them. > > Enjoy today! > Ken > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.org/c > gi-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. -- Nathan Hardman nhardman1428 at gmail.com N8THN at ARRL.NET -------------- next part -------------- An HTML attachment was scrubbed... URL: From mwbesemer at cox.net Mon Aug 13 15:38:50 2018 From: mwbesemer at cox.net (Mike Besemer - WM4B) Date: Mon, 13 Aug 2018 15:38:50 +0000 (GMT) Subject: [App_rpt-users] no longer in the database, Can not find info Message-ID: <1137fe6.74f2.16533f09720.Webtop.0@cox.net> 48198 is showing up green on the node-list now. Ken and I just connected. Ken... maybe this answers your question about the stat server. Sidebar question: I see now that no highlighting is not-registered and green is registered. I also see a node in red that says it is registered. Why the red highlight? Mike WM4B On Mon, Aug 13, 2018 at 11:30 AM, Nate Hardman wrote: https://allstarlink.org/nodelist.php and? http://stats.allstarlink.org/nodeinfo.cgi?node=48198 ? are two separate systems.?? please check your line in iax.conf file for the register= 48198;XXXXXX at register.allstarlink.org ? ? where XXXXXX is your registration password? once this is complete you should show green on the nodelist please check you line in rpt.conf file for?statpost_program = /usr/bin/wget,.............? ?line and ensure it is NOT commented out with (;) in front? ?once this is complete you should be posting stats to the stats server. asterisk reload will be required for changes to take effect. On Mon, Aug 13, 2018 at 9:53 AM, K2KRS Ken < k2krs at arrl.net > wrote: Good Morning, I had a node running, pretty basic default setup for a while then this weekend I added a another server/node but it's on a completely different offsite network so no issues with ports from the first interfering with ports from the second. Both of them show up on https://allstarlink.org/nodeli st.php with a green online status but neither show up on http://stats.allstarlink.org The first one 48198 used to show up on http://stats.allstarlink.org but as of this weekend it no longer is there. I know there were some changes on the infrastructure side of things just wondering if I should wait it out and see what happens or if there is something on my end I can do to look into what is going on. My first node 48198 has been and will continue to be on a Verizon jetpack.? While I did go ahead and setup port forwarding on the jetpack I heard Verizon doesn't allow incoming connections. My second one that I created this weekend 48715 is 'in the cloud'. So it has a lot more bandwidth and should be able to receive incoming connections. When I click on the links on nodelist.php I get these: Node 48198 is no longer in the database Can not find info for node 48715 I'm open to any suggestions on changing .conf files or obtaining any logging from either of them. Enjoy today! Ken ______________________________ _________________ App_rpt-users mailing list App_rpt-users at lists.allstarlin k.org http://lists.allstarlink.org/c gi-bin/mailman/listinfo/app_rp t-users To unsubscribe from this list please visit http://lists.allstarlink.org/c gi-bin/mailman/listinfo/app_rp t-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. -- Nathan Hardman nhardman1428 at gmail.com N8THN at ARRL.NET ------------------------------ _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org ? http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users ? To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From harvard5362 at yahoo.com Mon Aug 13 15:45:41 2018 From: harvard5362 at yahoo.com (C B) Date: Mon, 13 Aug 2018 15:45:41 +0000 (UTC) Subject: [App_rpt-users] My ip blacklisted, ticket 602 In-Reply-To: <376498360.6847731.1534164048341@mail.yahoo.com> References: <1529575896.2164591.1534163896738.ref@mail.yahoo.com> <1529575896.2164591.1534163896738@mail.yahoo.com> <376498360.6847731.1534164048341@mail.yahoo.com> Message-ID: <950973575.7004896.1534175141099@mail.yahoo.com> Why is my post not showing up on the reflector? Have I been banned? If so why am i banned with no notice? From: C B To: "app_rpt-users at lists.allstarlink.org" Sent: Monday, August 13, 2018 5:40 AM Subject: My ip blacklisted, ticket 602 My ip address was blacklisted according to an email set to the group. ticket 602 was opened. the reason given was that i had some private nodes (mostly aux receivers) trying to register. that was corrected. the ip address was likely unblocked as my node was registered again. then i was told i have the following error [Aug 13 01:57:19] NOTICE[18339]: chan_iax2.c:8284 register_verify: No registration for peer 'xxxxx' (from ip address removed) Please note the xxxxx was the node number given in the email from the allstar staff i enquired how to find this amongst the more that 40 nodes behind the firewall on my system. the response was? "idk, it's behind your IP.? tcpdump or wireshark?" IDK was looked up as i do not routinely use internet acronyms, the most likely answers where IDK = "i don't care" or IDK = "i don't know" wireshark filters where requested as i do not know how the registration process works. No reply. then my ip address was apparently blacklisted again CLI> iax2 show registryHost? ? ? ? ? ? ? ? ? dnsmgr? Username? ? ? ? Perceived? ? ? ? ? ? ?Refresh? State44.98.254.145:4569? ? Y? ? ? ?29883? ? ? ? ? ?? ? ? ? ? ? ?60? Request Sent As i do not know how to find node xxxxx nor do i understand what data the registration process sent to make it work thus i can not make a filter to find the issue and i am not a wireshark expert thus i will not be able to resolve this issue. note i did try the following filters tcp contains "node" udp contains "node" tcp contains "register" udp contains "register" udp contains "register.allstarlink.org" tcp contains "register.allstarlink.org" tcp contains "xxxxx" udp contains "xxxxx" all with no results Chris - - Chris via RT? ? - - Aug 12 at 7:09?PM - To - - harvard5362 at yahoo.com - Message body as most of my nodes have unique port numbers is there a way for you to tell the iax port number? From:?Chris via RT To:?harvard5362 at yahoo.com? Sent:?Sunday, August 12, 2018 7:06 PM Subject:?Re: [AllStar #602] 71.95.13.254 blacklisted i am not the best at wireshark (i do use it a little) any idea of a filter to look for it? thanks for your help < b>From:?Bryan via RT To:?harvard5362 at yahoo.com? Sent:?Sunday, August 12, 2018 7:04 PM Subject:?[AllStar #602] 71.95.13.254 blacklisted idk, it's behind your IP.? tcpdump or wireshark? This is why I hate NAT :)--? Bryan Fields, W9CR AllStarLink, Inc.?On Sun Aug 12 22:02:30 2018, N6LXX wrote: Ok i must not have saved the changes on 1121 and 1123?they should be good now.?how am i going to find node xxxx? that has me stumped. ?From:?Bryan via RT To:?harvard5362 at yahoo.com Sent:?Sunday, August 12, 2018 6:58 PM Subject:?[AllStar #602] 71.95.13.254 blacklisted?[Aug 13 01:57:19] NOTICE[18339]: chan_iax2.c:8284 register_verify: No registration for peer 'xxxxx' (ip address removed) that's a new one too. Thanks,--? Bryan Fields, W9CR AllStarLink, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tisawyer at gmail.com Mon Aug 13 15:53:31 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Mon, 13 Aug 2018 08:53:31 -0700 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: <1448032737.16542.1534173026903.JavaMail.zimbra@siminiuk.com> References: <003401d4323e$050371e0$0f0a55a0$@com> <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> <000001d43277$02122e70$06368b50$@innercite.com> <1806791267.65281.1534129600629.JavaMail.zimbra@siminiuk.com> <001801d432f3$8d488990$a7d99cb0$@com> <1448032737.16542.1534173026903.JavaMail.zimbra@siminiuk.com> Message-ID: I've changed the nodes list IAX port back to using the AllStarLink.org provided port. Thanks everybody for your input. Good discussion! On Mon, Aug 13, 2018 at 8:10 AM Danny K5CG wrote: > Tim, > > Because some routers follow the assumption doesn't make it a universal > concept that applies to all. You have to assume the source port is > unpredictable and random. If I rebooted my node, my router or just > disconnected my Internet, it would likely be different source port every > time it reconnected and registered. > > Danny > K5CG > > ------------------------------ > *From: *"Tim Sawyer" > *To: *"Users of Asterisk app_rpt" > *Sent: *Monday, August 13, 2018 9:35:42 AM > *Subject: *Re: [App_rpt-users] BIG registration problem this morning > > I'm partially responsible for this change. I want to make the AllStar > portal as simple to use as possible. It seemed to me that not having to put > the IAX port in the portal would make life easier. I forget to do that when > I move or setup new servers as have many others. When I discovered Asterisk > is reporting the actual source port to the portal database I thought it > would make sense to use that port for the nodes list. > > On Mon, Aug 13, 2018 at 3:48 AM Paul - KN2R wrote: > >> Tim, >> >> >> >> I am for putting the previous Registration server back in operation! >> >> >> >> All my nodes are having problems registering with different port numbers >> I do not have configured anywhere. >> >> I use a commercial grade SonicWall TZ-205N firewall/router which has been >> working fine for years! >> >> No changes have been made to that server or the router in over a year or >> two. Now all of a sudden, since the change, all is *not* working. >> >> >> >> Paul / KN2R >> >> >> >> >> >> *From:* App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] >> *On Behalf Of *Tim Sawyer >> *Sent:* Monday, August 13, 2018 1:15 AM >> *To:* Users of Asterisk app_rpt >> *Subject:* Re: [App_rpt-users] BIG registration problem this morning >> >> >> >> Why do some nodes not have this problem? Is NAT somehow different from >> different routers? I'd really like to understand so I can take it back to >> the technical folks and explain why it needs to be put back the way it was. >> >> >> >> On Sun, Aug 12, 2018 at 8:06 PM Danny K5CG wrote: >> >> I'm running pfSense and I "could" setup a static port for the outbound >> NAT but since when does the source port ever match the destination port, >> for any protocol? I'm not touching it. >> >> 46679*CLI> iax2 show registry >> Host dnsmgr Username Perceived >> Refresh State >> 44.98.254.145:4569 Y 46679 47.187.195.172:29961 >> 60 Auth. Sent >> >> 4569 is what's set on the portal for my node. 29961 appears to be what is >> recorded on the server from my registration. >> >> The portal port needs to be used or there has to be a way to set the port >> in rpt.conf to have that communicated to the registration server. Relying >> on the source port (which can be anything) is not a good idea. >> >> Next steps? >> >> Danny >> K5CG >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. >> >> >> >> >> -- >> >> Tim WD6AWP >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. >> > > > -- > Tim WD6AWP > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From k2krs at arrl.net Mon Aug 13 16:34:48 2018 From: k2krs at arrl.net (K2KRS Ken) Date: Mon, 13 Aug 2018 11:34:48 -0500 Subject: [App_rpt-users] no longer in the database, Can not find info In-Reply-To: References: <42f0d1c81c7a47a5ce5b0ec5c65136af@arrl.net> Message-ID: <468cf4889e0947434b7bf9a8a9d34cfb@arrl.net> Thanks for the info. Nate, Both are currently registered on the node list. But neither are showing up on the stats page. For the new 48715 node both look correct but I'll post here anyway maybe you'll see something I'm overlooking. iax.conf -------- bindport = 4569 register =48715:xhidden?x?x?@register.allstarlink.org rpt.conf -------- statpost_program = /usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null statpost_url = http://stats.allstarlink.org/uhandler.php I can't access the 48198 node at the moment without switching the network this laptop is on. But that one has been running for a couple of weeks without changes and it was showing in both places previously. On 2018-08-13 10:30 AM, Nate Hardman wrote: > https://allstarlink.org/nodelist.php and > http://stats.allstarlink.org/nodeinfo.cgi?node=48198 are two separate > systems. > > please check your line in iax.conf file for the register= > 48198;XXXXXX at register.allstarlink.org where XXXXXX is your > registration > password once this is complete you should show green on the nodelist > > please check you line in rpt.conf file for statpost_program = > /usr/bin/wget,............. line and ensure it is NOT commented out > with > (;) in front once this is complete you should be posting stats to the > stats server. > > asterisk reload will be required for changes to take effect. > > > On Mon, Aug 13, 2018 at 9:53 AM, K2KRS Ken wrote: > >> Good Morning, >> >> I had a node running, pretty basic default setup for a while then this >> weekend >> I added a another server/node but it's on a completely different >> offsite >> network so no issues >> with ports from the first interfering with ports from the second. >> >> Both of them show up on https://allstarlink.org/nodelist.php with a >> green >> online status but >> neither show up on http://stats.allstarlink.org >> >> The first one 48198 used to show up on http://stats.allstarlink.org >> but >> as of this weekend it no >> longer is there. >> >> I know there were some changes on the infrastructure side of things >> just >> wondering if I should >> wait it out and see what happens or if there is something on my end I >> can >> do to look into what is >> going on. >> >> My first node 48198 has been and will continue to be on a Verizon >> jetpack. While I did go ahead and setup port forwarding on the >> jetpack I >> heard Verizon doesn't allow incoming connections. >> >> My second one that I created this weekend 48715 is 'in the cloud'. So >> it >> has a lot more bandwidth and should be able to receive incoming >> connections. >> >> When I click on the links on nodelist.php I get these: >> Node 48198 is no longer in the database >> Can not find info for node 48715 >> >> I'm open to any suggestions on changing .conf files or obtaining any >> logging from either of them. >> >> Enjoy today! >> Ken >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.org/c >> gi-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. > > > > > -- > > Nathan Hardman > nhardman1428 at gmail.com > N8THN at ARRL.NET > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. From david.osborn at manx.net Mon Aug 13 17:34:51 2018 From: david.osborn at manx.net (David Osborn) Date: Mon, 13 Aug 2018 18:34:51 +0100 Subject: [App_rpt-users] BIG registration problem this morning In-Reply-To: References: <003401d4323e$050371e0$0f0a55a0$@com> <4ba33cf6-f08f-1a6a-c77d-04baa4eb89a0@bryanfields.net> <000001d43277$02122e70$06368b50$@innercite.com> <1806791267.65281.1534129600629.JavaMail.zimbra@siminiuk.com> <001801d432f3$8d488990$a7d99cb0$@com> <1448032737.16542.1534173026903.JavaMail.zimbra@siminiuk.com> Message-ID: <00c101d4332b$f0f16830$d2d43890$@manx.net> Nice one, Tim. That fixed it. Thank you so much for what you?ve been doing. Really appreciated. GD4HOZ From: Tim Sawyer [mailto:tisawyer at gmail.com] Sent: 13 August 2018 16:54 To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] BIG registration problem this morning I've changed the nodes list IAX port back to using the AllStarLink.org provided port. Thanks everybody for your input. Good discussion! On Mon, Aug 13, 2018 at 8:10 AM Danny K5CG wrote: Tim, Because some routers follow the assumption doesn't make it a universal concept that applies to all. You have to assume the source port is unpredictable and random. If I rebooted my node, my router or just disconnected my Internet, it would likely be different source port every time it reconnected and registered. Danny K5CG _____ From: "Tim Sawyer" To: "Users of Asterisk app_rpt" Sent: Monday, August 13, 2018 9:35:42 AM Subject: Re: [App_rpt-users] BIG registration problem this morning I'm partially responsible for this change. I want to make the AllStar portal as simple to use as possible. It seemed to me that not having to put the IAX port in the portal would make life easier. I forget to do that when I move or setup new servers as have many others. When I discovered Asterisk is reporting the actual source port to the portal database I thought it would make sense to use that port for the nodes list. On Mon, Aug 13, 2018 at 3:48 AM Paul - KN2R wrote: Tim, I am for putting the previous Registration server back in operation! All my nodes are having problems registering with different port numbers I do not have configured anywhere. I use a commercial grade SonicWall TZ-205N firewall/router which has been working fine for years! No changes have been made to that server or the router in over a year or two. Now all of a sudden, since the change, all is not working. Paul / KN2R From: App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] On Behalf Of Tim Sawyer Sent: Monday, August 13, 2018 1:15 AM To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] BIG registration problem this morning Why do some nodes not have this problem? Is NAT somehow different from different routers? I'd really like to understand so I can take it back to the technical folks and explain why it needs to be put back the way it was. On Sun, Aug 12, 2018 at 8:06 PM Danny K5CG wrote: I'm running pfSense and I "could" setup a static port for the outbound NAT but since when does the source port ever match the destination port, for any protocol? I'm not touching it. 46679*CLI> iax2 show registry Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 46679 47.187.195.172:29961 60 Auth. Sent 4569 is what's set on the portal for my node. 29961 appears to be what is recorded on the server from my registration. The portal port needs to be used or there has to be a way to set the port in rpt.conf to have that communicated to the registration server. Relying on the source port (which can be anything) is not a good idea. Next steps? Danny K5CG _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -- Tim WD6AWP _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -- Tim WD6AWP _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at dyb.com Mon Aug 13 18:02:52 2018 From: george at dyb.com (George Csahanin) Date: Mon, 13 Aug 2018 13:02:52 -0500 Subject: [App_rpt-users] still dnsmgr problem Message-ID: <78cdc583-64a6-bb12-a226-15e3243aa31d@dyb.com> I have rebooted restarted, etc, looked in modules.conf and there is no mention of dnsmgr. Checked a newer DIAL modules.conf and can't see it there either. Need a clue where to look...??? GeorgeC W2DB nodes 2360, 28599 --- This email has been checked for viruses by AVG. https://www.avg.com From szingman at msgstor.com Mon Aug 13 18:05:30 2018 From: szingman at msgstor.com (Steve Zingman) Date: Mon, 13 Aug 2018 14:05:30 -0400 Subject: [App_rpt-users] still dnsmgr problem In-Reply-To: <78cdc583-64a6-bb12-a226-15e3243aa31d@dyb.com> References: <78cdc583-64a6-bb12-a226-15e3243aa31d@dyb.com> Message-ID: <5692d8c1-c520-1f66-4e50-aedb88ca854e@msgstor.com> On 8/13/2018 2:02 PM, George Csahanin wrote: > I have rebooted restarted, etc, looked in modules.conf and there is no > mention of dnsmgr. Checked a newer DIAL modules.conf and can't see it > there either. > > Need a clue where to look...??? > > GeorgeC W2DB nodes 2360, 28599 > > > --- > This email has been checked for viruses by AVG. > https://www.avg.com > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. From tisawyer at gmail.com Mon Aug 13 18:35:17 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Mon, 13 Aug 2018 11:35:17 -0700 Subject: [App_rpt-users] still dnsmgr problem In-Reply-To: <5692d8c1-c520-1f66-4e50-aedb88ca854e@msgstor.com> References: <78cdc583-64a6-bb12-a226-15e3243aa31d@dyb.com> <5692d8c1-c520-1f66-4e50-aedb88ca854e@msgstor.com> Message-ID: Some Allstar versions don't have this conf file. Add to your /etc/asterisk directory. Then restart your node or do *CLI> dnsmgr reload /etc/asterisk/dnsmgr.conf [general] enable=yes ; enable creation of managed DNS lookups ; default is 'no' refreshinterval=300 ; refresh managed DNS lookups every seconds ; default is 300 (5 minutes) On Mon, Aug 13, 2018 at 11:05 AM Steve Zingman wrote: > < > https://github.com/AllStarLink/Asterisk/blob/develop/asterisk/configs/modules.conf.sample > > > > On 8/13/2018 2:02 PM, George Csahanin wrote: > > I have rebooted restarted, etc, looked in modules.conf and there is no > > mention of dnsmgr. Checked a newer DIAL modules.conf and can't see it > > there either. > > > > Need a clue where to look...??? > > > > GeorgeC W2DB nodes 2360, 28599 > > > > > > --- > > This email has been checked for viruses by AVG. > > https://www.avg.com > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at lists.allstarlink.org > > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > To unsubscribe from this list please visit > > http://lists.allstarlink.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. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at dyb.com Mon Aug 13 19:03:22 2018 From: george at dyb.com (George Csahanin) Date: Mon, 13 Aug 2018 14:03:22 -0500 Subject: [App_rpt-users] cant ping or traceroute to register.allstarlink.org Message-ID: <00701d59-3689-4d71-402c-07fc02cb82f8@dyb.com> OK, it wasn't in modules.conf, but had to add a dnsmgr.conf file now shows "Y" but still no register. tried to ping the server, didn't work. Tried traceroute also no go, should I see it or does it block icmp? [root at 2360 asterisk]# traceroute 44.98.254.145 traceroute to 44.98.254.145 (44.98.254.145), 30 hops max, 38 byte packets ?1? homeportal (192.168.1.254)? 7.593 ms? 6.354 ms? 9.444 ms ?2? 108-198-88-1.lightspeed.rcsntx.sbcglobal.net (108.198.88.1) 33.393 ms? 24.639 ms? 23.120 ms ?3? 71.155.112.230 (71.155.112.230)? 28.088 ms? 30.553 ms 26.064 ms ?4? *? *? 70.143.193.126 (70.143.193.126)? 29.092 ms ?5? 12.83.80.185 (12.83.80.185)? 36.344 ms? 12.83.80.189 (12.83.80.189)? 36.245 ms? 12.83.80.185 (12.83.80.185)? 29.868 ms ?6? gar25.dlstx.ip.att.net (12.122.85.233)? 30.305 ms? 30.601 ms? 31.341 ms ?7? 192.205.36.222 (192.205.36.222)? 29.046 ms? 29.070 ms 29.989 ms ?8? be2764.ccr32.dfw01.atlas.cogentco.com (154.54.47.213) 32.496 ms? be2763.ccr31.dfw01.atlas.cogentco.com (154.54.28.73) 27.303 ms? 26.848 ms ?9? be2441.ccr41.iah01.atlas.cogentco.com (154.54.41.65)? 35.356 ms? 33.722 ms? 35.345 ms 10? be3302.rcr21.msy01.atlas.cogentco.com (154.54.81.86)? 40.227 ms? 41.719 ms? 41.762 ms 11? be3303.rcr21.tpa01.atlas.cogentco.com (154.54.81.89)? 62.391 ms? 62.046 ms? 58.817 ms 12? be2578.nr12.b005666-1.tpa01.atlas.cogentco.com (154.24.16.98)? 71.652 ms? 67.870 ms? 64.507 ms 13? 38.140.225.146 (38.140.225.146)? 66.960 ms? 64.501 ms 67.099 ms 14? 66.216.50.34 (66.216.50.34)? 59.505 ms? 59.802 ms? 60.373 ms 15? ASL-hv.keekles.org (199.47.174.141)? 63.397 ms? 58.017 ms 57.555 ms 16? *? *? * 17? *? *? * 18? *? *? * 19? *? *? * 20? *? *? * 21? *? *? * 22? *? *? * 23? *? *? * 24? *? *? * 25? *? *? * 26? *? *? * 27? *? *? * 28? *? *? * 29? *? *? * 30? *? *? * --- This email has been checked for viruses by AVG. https://www.avg.com From tisawyer at gmail.com Mon Aug 13 19:09:39 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Mon, 13 Aug 2018 12:09:39 -0700 Subject: [App_rpt-users] cant ping or traceroute to register.allstarlink.org In-Reply-To: <00701d59-3689-4d71-402c-07fc02cb82f8@dyb.com> References: <00701d59-3689-4d71-402c-07fc02cb82f8@dyb.com> Message-ID: You'll need to fix ping to register.allstarlink.org. Maybe check if you can ping your router and go from there? On Mon, Aug 13, 2018 at 12:03 PM George Csahanin wrote: > OK, it wasn't in modules.conf, but had to add a dnsmgr.conf file now > shows "Y" but still no register. > > tried to ping the server, didn't work. > > Tried traceroute also no go, should I see it or does it block icmp? > > [root at 2360 asterisk]# traceroute 44.98.254.145 > traceroute to 44.98.254.145 (44.98.254.145), 30 hops max, 38 byte packets > 1 homeportal (192.168.1.254) 7.593 ms 6.354 ms 9.444 ms > 2 108-198-88-1.lightspeed.rcsntx.sbcglobal.net (108.198.88.1) 33.393 > ms 24.639 ms 23.120 ms > 3 71.155.112.230 (71.155.112.230) 28.088 ms 30.553 ms 26.064 ms > 4 * * 70.143.193.126 (70.143.193.126) 29.092 ms > 5 12.83.80.185 (12.83.80.185) 36.344 ms 12.83.80.189 > (12.83.80.189) 36.245 ms 12.83.80.185 (12.83.80.185) 29.868 ms > 6 gar25.dlstx.ip.att.net (12.122.85.233) 30.305 ms 30.601 ms 31.341 > ms > 7 192.205.36.222 (192.205.36.222) 29.046 ms 29.070 ms 29.989 ms > 8 be2764.ccr32.dfw01.atlas.cogentco.com (154.54.47.213) 32.496 ms > be2763.ccr31.dfw01.atlas.cogentco.com (154.54.28.73) 27.303 ms 26.848 ms > 9 be2441.ccr41.iah01.atlas.cogentco.com (154.54.41.65) 35.356 ms > 33.722 ms 35.345 ms > 10 be3302.rcr21.msy01.atlas.cogentco.com (154.54.81.86) 40.227 ms > 41.719 ms 41.762 ms > 11 be3303.rcr21.tpa01.atlas.cogentco.com (154.54.81.89) 62.391 ms > 62.046 ms 58.817 ms > 12 be2578.nr12.b005666-1.tpa01.atlas.cogentco.com (154.24.16.98) > 71.652 ms 67.870 ms 64.507 ms > 13 38.140.225.146 (38.140.225.146) 66.960 ms 64.501 ms 67.099 ms > 14 66.216.50.34 (66.216.50.34) 59.505 ms 59.802 ms 60.373 ms > 15 ASL-hv.keekles.org (199.47.174.141) 63.397 ms 58.017 ms 57.555 ms > 16 * * * > 17 * * * > 18 * * * > 19 * * * > 20 * * * > 21 * * * > 22 * * * > 23 * * * > 24 * * * > 25 * * * > 26 * * * > 27 * * * > 28 * * * > 29 * * * > 30 * * * > > > --- > This email has been checked for viruses by AVG. > https://www.avg.com > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From petem001 at gmail.com Mon Aug 13 19:09:35 2018 From: petem001 at gmail.com (Pierre Martel) Date: Mon, 13 Aug 2018 15:09:35 -0400 Subject: [App_rpt-users] cant ping or traceroute to register.allstarlink.org In-Reply-To: <00701d59-3689-4d71-402c-07fc02cb82f8@dyb.com> References: <00701d59-3689-4d71-402c-07fc02cb82f8@dyb.com> Message-ID: working from here C:\Users\XX>tracert register.allstarlink.org D?termination de l?itin?raire vers register.regsvcs.allstarlink.org [44.98.254.145] avec un maximum de 30 sauts : 1 29 ms 3 ms 1 ms 192.168.1.1 2 17 ms 18 ms 13 ms modemcableXX.XX-56-74.mc.videotron.ca [74.56.XX.XX] 3 14 ms 18 ms 19 ms 10.170.154.XXX 4 44 ms 64 ms 46 ms 216.113.126.XXX 5 45 ms 38 ms 64 ms eqx.20ge.iad.bboi.net [206.126.236.47] 6 90 ms 56 ms 61 ms atl-ten3-1-ash-ten3-1.bboi.net [66.216.1.157] 7 51 ms 52 ms 54 ms 66.216.2.10 8 53 ms 78 ms 56 ms 66.216.50.34 9 55 ms 71 ms 51 ms ASL-hv.keekles.org [199.47.174.141] 10 58 ms 53 ms * register-tpa.allstarlink.org [44.98.254.145] 11 58 ms 59 ms 60 ms register-tpa.allstarlink.org [44.98.254.145] Itin?raire d?termin?. (using a french windows) that why it show response in french) XX to protect some private info Le lun. 13 ao?t 2018 ? 15:03, George Csahanin a ?crit : > OK, it wasn't in modules.conf, but had to add a dnsmgr.conf file now > shows "Y" but still no register. > > tried to ping the server, didn't work. > > Tried traceroute also no go, should I see it or does it block icmp? > > [root at 2360 asterisk]# traceroute 44.98.254.145 > traceroute to 44.98.254.145 (44.98.254.145), 30 hops max, 38 byte packets > 1 homeportal (192.168.1.254) 7.593 ms 6.354 ms 9.444 ms > 2 108-198-88-1.lightspeed.rcsntx.sbcglobal.net (108.198.88.1) 33.393 > ms 24.639 ms 23.120 ms > 3 71.155.112.230 (71.155.112.230) 28.088 ms 30.553 ms 26.064 ms > 4 * * 70.143.193.126 (70.143.193.126) 29.092 ms > 5 12.83.80.185 (12.83.80.185) 36.344 ms 12.83.80.189 > (12.83.80.189) 36.245 ms 12.83.80.185 (12.83.80.185) 29.868 ms > 6 gar25.dlstx.ip.att.net (12.122.85.233) 30.305 ms 30.601 ms 31.341 > ms > 7 192.205.36.222 (192.205.36.222) 29.046 ms 29.070 ms 29.989 ms > 8 be2764.ccr32.dfw01.atlas.cogentco.com (154.54.47.213) 32.496 ms > be2763.ccr31.dfw01.atlas.cogentco.com (154.54.28.73) 27.303 ms 26.848 ms > 9 be2441.ccr41.iah01.atlas.cogentco.com (154.54.41.65) 35.356 ms > 33.722 ms 35.345 ms > 10 be3302.rcr21.msy01.atlas.cogentco.com (154.54.81.86) 40.227 ms > 41.719 ms 41.762 ms > 11 be3303.rcr21.tpa01.atlas.cogentco.com (154.54.81.89) 62.391 ms > 62.046 ms 58.817 ms > 12 be2578.nr12.b005666-1.tpa01.atlas.cogentco.com (154.24.16.98) > 71.652 ms 67.870 ms 64.507 ms > 13 38.140.225.146 (38.140.225.146) 66.960 ms 64.501 ms 67.099 ms > 14 66.216.50.34 (66.216.50.34) 59.505 ms 59.802 ms 60.373 ms > 15 ASL-hv.keekles.org (199.47.174.141) 63.397 ms 58.017 ms 57.555 ms > 16 * * * > 17 * * * > 18 * * * > 19 * * * > 20 * * * > 21 * * * > 22 * * * > 23 * * * > 24 * * * > 25 * * * > 26 * * * > 27 * * * > 28 * * * > 29 * * * > 30 * * * > > > --- > This email has been checked for viruses by AVG. > https://www.avg.com > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From petem001 at gmail.com Mon Aug 13 19:16:24 2018 From: petem001 at gmail.com (Pierre Martel) Date: Mon, 13 Aug 2018 15:16:24 -0400 Subject: [App_rpt-users] cant ping or traceroute to register.allstarlink.org In-Reply-To: References: <00701d59-3689-4d71-402c-07fc02cb82f8@dyb.com> Message-ID: If he can traceroute out of his router (like we can see from his second hops) he cant fix much on his side. Unless he have an ampr gateway badly configured Le lun. 13 ao?t 2018 ? 15:09, Tim Sawyer a ?crit : > You'll need to fix ping to register.allstarlink.org. Maybe check if you > can ping your router and go from there? > > On Mon, Aug 13, 2018 at 12:03 PM George Csahanin wrote: > >> OK, it wasn't in modules.conf, but had to add a dnsmgr.conf file now >> shows "Y" but still no register. >> >> tried to ping the server, didn't work. >> >> Tried traceroute also no go, should I see it or does it block icmp? >> >> [root at 2360 asterisk]# traceroute 44.98.254.145 >> traceroute to 44.98.254.145 (44.98.254.145), 30 hops max, 38 byte packets >> 1 homeportal (192.168.1.254) 7.593 ms 6.354 ms 9.444 ms >> 2 108-198-88-1.lightspeed.rcsntx.sbcglobal.net (108.198.88.1) 33.393 >> ms 24.639 ms 23.120 ms >> 3 71.155.112.230 (71.155.112.230) 28.088 ms 30.553 ms 26.064 ms >> 4 * * 70.143.193.126 (70.143.193.126) 29.092 ms >> 5 12.83.80.185 (12.83.80.185) 36.344 ms 12.83.80.189 >> (12.83.80.189) 36.245 ms 12.83.80.185 (12.83.80.185) 29.868 ms >> 6 gar25.dlstx.ip.att.net (12.122.85.233) 30.305 ms 30.601 ms >> 31.341 ms >> 7 192.205.36.222 (192.205.36.222) 29.046 ms 29.070 ms 29.989 ms >> 8 be2764.ccr32.dfw01.atlas.cogentco.com (154.54.47.213) 32.496 ms >> be2763.ccr31.dfw01.atlas.cogentco.com (154.54.28.73) 27.303 ms 26.848 ms >> 9 be2441.ccr41.iah01.atlas.cogentco.com (154.54.41.65) 35.356 ms >> 33.722 ms 35.345 ms >> 10 be3302.rcr21.msy01.atlas.cogentco.com (154.54.81.86) 40.227 ms >> 41.719 ms 41.762 ms >> 11 be3303.rcr21.tpa01.atlas.cogentco.com (154.54.81.89) 62.391 ms >> 62.046 ms 58.817 ms >> 12 be2578.nr12.b005666-1.tpa01.atlas.cogentco.com (154.24.16.98) >> 71.652 ms 67.870 ms 64.507 ms >> 13 38.140.225.146 (38.140.225.146) 66.960 ms 64.501 ms 67.099 ms >> 14 66.216.50.34 (66.216.50.34) 59.505 ms 59.802 ms 60.373 ms >> 15 ASL-hv.keekles.org (199.47.174.141) 63.397 ms 58.017 ms 57.555 ms >> 16 * * * >> 17 * * * >> 18 * * * >> 19 * * * >> 20 * * * >> 21 * * * >> 22 * * * >> 23 * * * >> 24 * * * >> 25 * * * >> 26 * * * >> 27 * * * >> 28 * * * >> 29 * * * >> 30 * * * >> >> >> --- >> This email has been checked for viruses by AVG. >> https://www.avg.com >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. >> > > > -- > Tim WD6AWP > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tisawyer at gmail.com Mon Aug 13 19:17:26 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Mon, 13 Aug 2018 12:17:26 -0700 Subject: [App_rpt-users] Still Working on Migration Message-ID: Hey Folks, The AllStar developer team knows there are still problems with the new registration system. The are working on it. The goal continues to be to make a better AllStar for everyone. Please be patient while they work out the bugs. -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From tisawyer at gmail.com Mon Aug 13 19:19:02 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Mon, 13 Aug 2018 12:19:02 -0700 Subject: [App_rpt-users] cant ping or traceroute to register.allstarlink.org In-Reply-To: References: <00701d59-3689-4d71-402c-07fc02cb82f8@dyb.com> Message-ID: I agree. However it is up and I can ping it: ping register.allstarlink.org PING register.regsvcs.allstarlink.org (44.98.254.145) 56(84) bytes of data. 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=1 ttl=53 time=59.5 ms 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=2 ttl=53 time=59.6 ms 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=3 ttl=53 time=59.7 ms 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=4 ttl=53 time=59.1 ms ^C --- register.regsvcs.allstarlink.org ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 59.151/59.521/59.731/0.375 ms On Mon, Aug 13, 2018 at 12:16 PM Pierre Martel wrote: > If he can traceroute out of his router (like we can see from his second > hops) he cant fix much on his side. Unless he have an ampr gateway badly > configured > > Le lun. 13 ao?t 2018 ? 15:09, Tim Sawyer a ?crit : > >> You'll need to fix ping to register.allstarlink.org. Maybe check if you >> can ping your router and go from there? >> >> On Mon, Aug 13, 2018 at 12:03 PM George Csahanin wrote: >> >>> OK, it wasn't in modules.conf, but had to add a dnsmgr.conf file now >>> shows "Y" but still no register. >>> >>> tried to ping the server, didn't work. >>> >>> Tried traceroute also no go, should I see it or does it block icmp? >>> >>> [root at 2360 asterisk]# traceroute 44.98.254.145 >>> traceroute to 44.98.254.145 (44.98.254.145), 30 hops max, 38 byte packets >>> 1 homeportal (192.168.1.254) 7.593 ms 6.354 ms 9.444 ms >>> 2 108-198-88-1.lightspeed.rcsntx.sbcglobal.net (108.198.88.1) 33.393 >>> ms 24.639 ms 23.120 ms >>> 3 71.155.112.230 (71.155.112.230) 28.088 ms 30.553 ms 26.064 ms >>> 4 * * 70.143.193.126 (70.143.193.126) 29.092 ms >>> 5 12.83.80.185 (12.83.80.185) 36.344 ms 12.83.80.189 >>> (12.83.80.189) 36.245 ms 12.83.80.185 (12.83.80.185) 29.868 ms >>> 6 gar25.dlstx.ip.att.net (12.122.85.233) 30.305 ms 30.601 ms >>> 31.341 ms >>> 7 192.205.36.222 (192.205.36.222) 29.046 ms 29.070 ms 29.989 ms >>> 8 be2764.ccr32.dfw01.atlas.cogentco.com (154.54.47.213) 32.496 ms >>> be2763.ccr31.dfw01.atlas.cogentco.com (154.54.28.73) 27.303 ms 26.848 >>> ms >>> 9 be2441.ccr41.iah01.atlas.cogentco.com (154.54.41.65) 35.356 ms >>> 33.722 ms 35.345 ms >>> 10 be3302.rcr21.msy01.atlas.cogentco.com (154.54.81.86) 40.227 ms >>> 41.719 ms 41.762 ms >>> 11 be3303.rcr21.tpa01.atlas.cogentco.com (154.54.81.89) 62.391 ms >>> 62.046 ms 58.817 ms >>> 12 be2578.nr12.b005666-1.tpa01.atlas.cogentco.com (154.24.16.98) >>> 71.652 ms 67.870 ms 64.507 ms >>> 13 38.140.225.146 (38.140.225.146) 66.960 ms 64.501 ms 67.099 ms >>> 14 66.216.50.34 (66.216.50.34) 59.505 ms 59.802 ms 60.373 ms >>> 15 ASL-hv.keekles.org (199.47.174.141) 63.397 ms 58.017 ms 57.555 ms >>> 16 * * * >>> 17 * * * >>> 18 * * * >>> 19 * * * >>> 20 * * * >>> 21 * * * >>> 22 * * * >>> 23 * * * >>> 24 * * * >>> 25 * * * >>> 26 * * * >>> 27 * * * >>> 28 * * * >>> 29 * * * >>> 30 * * * >>> >>> >>> --- >>> This email has been checked for viruses by AVG. >>> https://www.avg.com >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit >>> http://lists.allstarlink.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. >>> >> >> >> -- >> Tim WD6AWP >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. >> > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From tisawyer at gmail.com Mon Aug 13 19:20:36 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Mon, 13 Aug 2018 12:20:36 -0700 Subject: [App_rpt-users] cant ping or traceroute to register.allstarlink.org In-Reply-To: References: <00701d59-3689-4d71-402c-07fc02cb82f8@dyb.com> Message-ID: Maybe his resolver is messed up? On Mon, Aug 13, 2018 at 12:19 PM Tim Sawyer wrote: > I agree. However it is up and I can ping it: > > ping register.allstarlink.org > PING register.regsvcs.allstarlink.org (44.98.254.145) 56(84) bytes of > data. > 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=1 > ttl=53 time=59.5 ms > 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=2 > ttl=53 time=59.6 ms > 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=3 > ttl=53 time=59.7 ms > 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=4 > ttl=53 time=59.1 ms > ^C > --- register.regsvcs.allstarlink.org ping statistics --- > 4 packets transmitted, 4 received, 0% packet loss, time 3004ms > rtt min/avg/max/mdev = 59.151/59.521/59.731/0.375 ms > > > On Mon, Aug 13, 2018 at 12:16 PM Pierre Martel wrote: > >> If he can traceroute out of his router (like we can see from his second >> hops) he cant fix much on his side. Unless he have an ampr gateway badly >> configured >> >> Le lun. 13 ao?t 2018 ? 15:09, Tim Sawyer a ?crit : >> >>> You'll need to fix ping to register.allstarlink.org. Maybe check if you >>> can ping your router and go from there? >>> >>> On Mon, Aug 13, 2018 at 12:03 PM George Csahanin wrote: >>> >>>> OK, it wasn't in modules.conf, but had to add a dnsmgr.conf file now >>>> shows "Y" but still no register. >>>> >>>> tried to ping the server, didn't work. >>>> >>>> Tried traceroute also no go, should I see it or does it block icmp? >>>> >>>> [root at 2360 asterisk]# traceroute 44.98.254.145 >>>> traceroute to 44.98.254.145 (44.98.254.145), 30 hops max, 38 byte >>>> packets >>>> 1 homeportal (192.168.1.254) 7.593 ms 6.354 ms 9.444 ms >>>> 2 108-198-88-1.lightspeed.rcsntx.sbcglobal.net (108.198.88.1) >>>> 33.393 >>>> ms 24.639 ms 23.120 ms >>>> 3 71.155.112.230 (71.155.112.230) 28.088 ms 30.553 ms 26.064 ms >>>> 4 * * 70.143.193.126 (70.143.193.126) 29.092 ms >>>> 5 12.83.80.185 (12.83.80.185) 36.344 ms 12.83.80.189 >>>> (12.83.80.189) 36.245 ms 12.83.80.185 (12.83.80.185) 29.868 ms >>>> 6 gar25.dlstx.ip.att.net (12.122.85.233) 30.305 ms 30.601 ms >>>> 31.341 ms >>>> 7 192.205.36.222 (192.205.36.222) 29.046 ms 29.070 ms 29.989 ms >>>> 8 be2764.ccr32.dfw01.atlas.cogentco.com (154.54.47.213) 32.496 ms >>>> be2763.ccr31.dfw01.atlas.cogentco.com (154.54.28.73) 27.303 ms 26.848 >>>> ms >>>> 9 be2441.ccr41.iah01.atlas.cogentco.com (154.54.41.65) 35.356 ms >>>> 33.722 ms 35.345 ms >>>> 10 be3302.rcr21.msy01.atlas.cogentco.com (154.54.81.86) 40.227 ms >>>> 41.719 ms 41.762 ms >>>> 11 be3303.rcr21.tpa01.atlas.cogentco.com (154.54.81.89) 62.391 ms >>>> 62.046 ms 58.817 ms >>>> 12 be2578.nr12.b005666-1.tpa01.atlas.cogentco.com (154.24.16.98) >>>> 71.652 ms 67.870 ms 64.507 ms >>>> 13 38.140.225.146 (38.140.225.146) 66.960 ms 64.501 ms 67.099 ms >>>> 14 66.216.50.34 (66.216.50.34) 59.505 ms 59.802 ms 60.373 ms >>>> 15 ASL-hv.keekles.org (199.47.174.141) 63.397 ms 58.017 ms 57.555 ms >>>> 16 * * * >>>> 17 * * * >>>> 18 * * * >>>> 19 * * * >>>> 20 * * * >>>> 21 * * * >>>> 22 * * * >>>> 23 * * * >>>> 24 * * * >>>> 25 * * * >>>> 26 * * * >>>> 27 * * * >>>> 28 * * * >>>> 29 * * * >>>> 30 * * * >>>> >>>> >>>> --- >>>> This email has been checked for viruses by AVG. >>>> https://www.avg.com >>>> >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users at lists.allstarlink.org >>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>>> >>>> To unsubscribe from this list please visit >>>> http://lists.allstarlink.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. >>>> >>> >>> >>> -- >>> Tim WD6AWP >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit >>> http://lists.allstarlink.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. >>> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. >> > > > -- > Tim WD6AWP > -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From tisawyer at gmail.com Mon Aug 13 19:55:35 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Mon, 13 Aug 2018 12:55:35 -0700 Subject: [App_rpt-users] cant ping or traceroute to register.allstarlink.org In-Reply-To: References: <00701d59-3689-4d71-402c-07fc02cb82f8@dyb.com> Message-ID: Never mind the resolver comment, that was wrong. What the IP of the station that can't ping. Is it on this list? http://lists.allstarlink.org/pipermail/app_rpt-users/2018-August/019206.html On Mon, Aug 13, 2018 at 12:20 PM Tim Sawyer wrote: > Maybe his resolver is messed up? > > On Mon, Aug 13, 2018 at 12:19 PM Tim Sawyer wrote: > >> I agree. However it is up and I can ping it: >> >> ping register.allstarlink.org >> PING register.regsvcs.allstarlink.org (44.98.254.145) 56(84) bytes of >> data. >> 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=1 >> ttl=53 time=59.5 ms >> 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=2 >> ttl=53 time=59.6 ms >> 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=3 >> ttl=53 time=59.7 ms >> 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=4 >> ttl=53 time=59.1 ms >> ^C >> --- register.regsvcs.allstarlink.org ping statistics --- >> 4 packets transmitted, 4 received, 0% packet loss, time 3004ms >> rtt min/avg/max/mdev = 59.151/59.521/59.731/0.375 ms >> >> >> On Mon, Aug 13, 2018 at 12:16 PM Pierre Martel >> wrote: >> >>> If he can traceroute out of his router (like we can see from his second >>> hops) he cant fix much on his side. Unless he have an ampr gateway badly >>> configured >>> >>> Le lun. 13 ao?t 2018 ? 15:09, Tim Sawyer a ?crit : >>> >>>> You'll need to fix ping to register.allstarlink.org. Maybe check if >>>> you can ping your router and go from there? >>>> >>>> On Mon, Aug 13, 2018 at 12:03 PM George Csahanin >>>> wrote: >>>> >>>>> OK, it wasn't in modules.conf, but had to add a dnsmgr.conf file now >>>>> shows "Y" but still no register. >>>>> >>>>> tried to ping the server, didn't work. >>>>> >>>>> Tried traceroute also no go, should I see it or does it block icmp? >>>>> >>>>> [root at 2360 asterisk]# traceroute 44.98.254.145 >>>>> traceroute to 44.98.254.145 (44.98.254.145), 30 hops max, 38 byte >>>>> packets >>>>> 1 homeportal (192.168.1.254) 7.593 ms 6.354 ms 9.444 ms >>>>> 2 108-198-88-1.lightspeed.rcsntx.sbcglobal.net (108.198.88.1) >>>>> 33.393 >>>>> ms 24.639 ms 23.120 ms >>>>> 3 71.155.112.230 (71.155.112.230) 28.088 ms 30.553 ms 26.064 ms >>>>> 4 * * 70.143.193.126 (70.143.193.126) 29.092 ms >>>>> 5 12.83.80.185 (12.83.80.185) 36.344 ms 12.83.80.189 >>>>> (12.83.80.189) 36.245 ms 12.83.80.185 (12.83.80.185) 29.868 ms >>>>> 6 gar25.dlstx.ip.att.net (12.122.85.233) 30.305 ms 30.601 ms >>>>> 31.341 ms >>>>> 7 192.205.36.222 (192.205.36.222) 29.046 ms 29.070 ms 29.989 ms >>>>> 8 be2764.ccr32.dfw01.atlas.cogentco.com (154.54.47.213) 32.496 ms >>>>> be2763.ccr31.dfw01.atlas.cogentco.com (154.54.28.73) 27.303 ms >>>>> 26.848 ms >>>>> 9 be2441.ccr41.iah01.atlas.cogentco.com (154.54.41.65) 35.356 ms >>>>> 33.722 ms 35.345 ms >>>>> 10 be3302.rcr21.msy01.atlas.cogentco.com (154.54.81.86) 40.227 ms >>>>> 41.719 ms 41.762 ms >>>>> 11 be3303.rcr21.tpa01.atlas.cogentco.com (154.54.81.89) 62.391 ms >>>>> 62.046 ms 58.817 ms >>>>> 12 be2578.nr12.b005666-1.tpa01.atlas.cogentco.com (154.24.16.98) >>>>> 71.652 ms 67.870 ms 64.507 ms >>>>> 13 38.140.225.146 (38.140.225.146) 66.960 ms 64.501 ms 67.099 ms >>>>> 14 66.216.50.34 (66.216.50.34) 59.505 ms 59.802 ms 60.373 ms >>>>> 15 ASL-hv.keekles.org (199.47.174.141) 63.397 ms 58.017 ms 57.555 >>>>> ms >>>>> 16 * * * >>>>> 17 * * * >>>>> 18 * * * >>>>> 19 * * * >>>>> 20 * * * >>>>> 21 * * * >>>>> 22 * * * >>>>> 23 * * * >>>>> 24 * * * >>>>> 25 * * * >>>>> 26 * * * >>>>> 27 * * * >>>>> 28 * * * >>>>> 29 * * * >>>>> 30 * * * >>>>> >>>>> >>>>> --- >>>>> This email has been checked for viruses by AVG. >>>>> https://www.avg.com >>>>> >>>>> _______________________________________________ >>>>> App_rpt-users mailing list >>>>> App_rpt-users at lists.allstarlink.org >>>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>>>> >>>>> To unsubscribe from this list please visit >>>>> http://lists.allstarlink.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. >>>>> >>>> >>>> >>>> -- >>>> Tim WD6AWP >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users at lists.allstarlink.org >>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>>> >>>> To unsubscribe from this list please visit >>>> http://lists.allstarlink.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. >>>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit >>> http://lists.allstarlink.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. >>> >> >> >> -- >> Tim WD6AWP >> > > > -- > Tim WD6AWP > -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From petem001 at gmail.com Mon Aug 13 20:33:21 2018 From: petem001 at gmail.com (Pierre Martel) Date: Mon, 13 Aug 2018 16:33:21 -0400 Subject: [App_rpt-users] cant ping or traceroute to register.allstarlink.org In-Reply-To: References: <00701d59-3689-4d71-402c-07fc02cb82f8@dyb.com> Message-ID: By the way the 2 nodes that I use to take care of are online and registering and they run on Acid. No reboot, no resolving stuff. The only thing I could think of that make bad registration are either cross port fowarding or bad router. I really dont get it if you have a service at port 4569 inside your network, why would you foward the traffic from port 4570 to it. Thats looking for trouble. The software can be configured to run on different port and it will react to it perfectly, why risk trouble and mess with the port? Le lun. 13 ao?t 2018 ? 15:55, Tim Sawyer a ?crit : > Never mind the resolver comment, that was wrong. What the IP of the > station that can't ping. Is it on this list? > http://lists.allstarlink.org/pipermail/app_rpt-users/2018-August/019206.html > > > On Mon, Aug 13, 2018 at 12:20 PM Tim Sawyer wrote: > >> Maybe his resolver is messed up? >> >> On Mon, Aug 13, 2018 at 12:19 PM Tim Sawyer wrote: >> >>> I agree. However it is up and I can ping it: >>> >>> ping register.allstarlink.org >>> PING register.regsvcs.allstarlink.org (44.98.254.145) 56(84) bytes of >>> data. >>> 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=1 >>> ttl=53 time=59.5 ms >>> 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=2 >>> ttl=53 time=59.6 ms >>> 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=3 >>> ttl=53 time=59.7 ms >>> 64 bytes from register-tpa.allstarlink.org (44.98.254.145): icmp_seq=4 >>> ttl=53 time=59.1 ms >>> ^C >>> --- register.regsvcs.allstarlink.org ping statistics --- >>> 4 packets transmitted, 4 received, 0% packet loss, time 3004ms >>> rtt min/avg/max/mdev = 59.151/59.521/59.731/0.375 ms >>> >>> >>> On Mon, Aug 13, 2018 at 12:16 PM Pierre Martel >>> wrote: >>> >>>> If he can traceroute out of his router (like we can see from his second >>>> hops) he cant fix much on his side. Unless he have an ampr gateway badly >>>> configured >>>> >>>> Le lun. 13 ao?t 2018 ? 15:09, Tim Sawyer a ?crit : >>>> >>>>> You'll need to fix ping to register.allstarlink.org. Maybe check if >>>>> you can ping your router and go from there? >>>>> >>>>> On Mon, Aug 13, 2018 at 12:03 PM George Csahanin >>>>> wrote: >>>>> >>>>>> OK, it wasn't in modules.conf, but had to add a dnsmgr.conf file now >>>>>> shows "Y" but still no register. >>>>>> >>>>>> tried to ping the server, didn't work. >>>>>> >>>>>> Tried traceroute also no go, should I see it or does it block icmp? >>>>>> >>>>>> [root at 2360 asterisk]# traceroute 44.98.254.145 >>>>>> traceroute to 44.98.254.145 (44.98.254.145), 30 hops max, 38 byte >>>>>> packets >>>>>> 1 homeportal (192.168.1.254) 7.593 ms 6.354 ms 9.444 ms >>>>>> 2 108-198-88-1.lightspeed.rcsntx.sbcglobal.net (108.198.88.1) >>>>>> 33.393 >>>>>> ms 24.639 ms 23.120 ms >>>>>> 3 71.155.112.230 (71.155.112.230) 28.088 ms 30.553 ms 26.064 ms >>>>>> 4 * * 70.143.193.126 (70.143.193.126) 29.092 ms >>>>>> 5 12.83.80.185 (12.83.80.185) 36.344 ms 12.83.80.189 >>>>>> (12.83.80.189) 36.245 ms 12.83.80.185 (12.83.80.185) 29.868 ms >>>>>> 6 gar25.dlstx.ip.att.net (12.122.85.233) 30.305 ms 30.601 ms >>>>>> 31.341 ms >>>>>> 7 192.205.36.222 (192.205.36.222) 29.046 ms 29.070 ms 29.989 ms >>>>>> 8 be2764.ccr32.dfw01.atlas.cogentco.com (154.54.47.213) 32.496 >>>>>> ms >>>>>> be2763.ccr31.dfw01.atlas.cogentco.com (154.54.28.73) 27.303 ms >>>>>> 26.848 ms >>>>>> 9 be2441.ccr41.iah01.atlas.cogentco.com (154.54.41.65) 35.356 >>>>>> ms >>>>>> 33.722 ms 35.345 ms >>>>>> 10 be3302.rcr21.msy01.atlas.cogentco.com (154.54.81.86) 40.227 ms >>>>>> 41.719 ms 41.762 ms >>>>>> 11 be3303.rcr21.tpa01.atlas.cogentco.com (154.54.81.89) 62.391 ms >>>>>> 62.046 ms 58.817 ms >>>>>> 12 be2578.nr12.b005666-1.tpa01.atlas.cogentco.com (154.24.16.98) >>>>>> 71.652 ms 67.870 ms 64.507 ms >>>>>> 13 38.140.225.146 (38.140.225.146) 66.960 ms 64.501 ms 67.099 ms >>>>>> 14 66.216.50.34 (66.216.50.34) 59.505 ms 59.802 ms 60.373 ms >>>>>> 15 ASL-hv.keekles.org (199.47.174.141) 63.397 ms 58.017 ms 57.555 >>>>>> ms >>>>>> 16 * * * >>>>>> 17 * * * >>>>>> 18 * * * >>>>>> 19 * * * >>>>>> 20 * * * >>>>>> 21 * * * >>>>>> 22 * * * >>>>>> 23 * * * >>>>>> 24 * * * >>>>>> 25 * * * >>>>>> 26 * * * >>>>>> 27 * * * >>>>>> 28 * * * >>>>>> 29 * * * >>>>>> 30 * * * >>>>>> >>>>>> >>>>>> --- >>>>>> This email has been checked for viruses by AVG. >>>>>> https://www.avg.com >>>>>> >>>>>> _______________________________________________ >>>>>> App_rpt-users mailing list >>>>>> App_rpt-users at lists.allstarlink.org >>>>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>>>>> >>>>>> To unsubscribe from this list please visit >>>>>> http://lists.allstarlink.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. >>>>>> >>>>> >>>>> >>>>> -- >>>>> Tim WD6AWP >>>>> _______________________________________________ >>>>> App_rpt-users mailing list >>>>> App_rpt-users at lists.allstarlink.org >>>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>>>> >>>>> To unsubscribe from this list please visit >>>>> http://lists.allstarlink.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. >>>>> >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users at lists.allstarlink.org >>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>>> >>>> To unsubscribe from this list please visit >>>> http://lists.allstarlink.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. >>>> >>> >>> >>> -- >>> Tim WD6AWP >>> >> >> >> -- >> Tim WD6AWP >> > > > -- > Tim WD6AWP > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From harvard5362 at yahoo.com Mon Aug 13 20:40:19 2018 From: harvard5362 at yahoo.com (C B) Date: Mon, 13 Aug 2018 20:40:19 +0000 (UTC) Subject: [App_rpt-users] [AllStar #602] 71.95.13.254 blacklisted In-Reply-To: References: <298037056.6640680.1534122388655.ref@mail.yahoo.com> <298037056.6640680.1534122388655@mail.yahoo.com> <306391641.6649599.1534125985556@mail.yahoo.com> <914788475.6649938.1534126157005@mail.yahoo.com> Message-ID: <166510248.7192992.1534192819422@mail.yahoo.com> I do not see how a failed attempt to register should result in being banned. Having checked all of the private nodes uncovered nothing new. i attempted to work with the all star team, however my request for more info and or guidance have gone unanswered other than to tell me to check every node as i have checked? the private nodes it could be a waist of time to check the 45 to 50 nodes behind my firewall as the problem may not be obvious. this leaves me to no longer worry about being registered with all star. i will just have those who need to connect add the correct line to their rpt.conf file that allows them to connect without utilizing the lookup table provided by all star. chris From: Bryan via RT To: harvard5362 at yahoo.com Sent: Monday, August 13, 2018 1:02 PM Subject: [AllStar #602] 71.95.13.254 blacklisted It's not registered, so we can't see any details on it, outside of the failed connection attempts.? Can you look at your nodes iax.conf files and ensure you have only public nodes pointed at the servers? Thanks,--? Bryan Fields, W9CR AllStarLink, Inc.?On Sun Aug 12 22:09:29 2018, N6LXX wrote: as most of my nodes have unique port numbers is there a way for you to tell the iax port number? ?From: Chris via RT To: harvard5362 at yahoo.com Sent: Sunday, August 12, 2018 7:06 PM Subject: Re: [AllStar #602] 71.95.13.254 blacklisted?i am not the best at wireshark (i do use it a little) any idea of a filter to look for it??thanks for your help ?From: Bryan via RT To: harvard5362 at yahoo.com Sent: Sunday, August 12, 2018 7:04 PM Subject: [AllStar #602] 71.95.13.254 blacklisted?idk, it's behind your IP.? tcpdump or wireshark? This is why I hate NAT :)--? Bryan Fields, W9CR AllStarLink, Inc.?On Sun Aug 12 22:02:30 2018, N6LXX wrote: Ok i must not have saved the changes on 1121 and 1123?they should be good now.?how am i going to find node xxxx? that has me stumped. ?From: Bryan via RT To: harvard5362 at yahoo.com Sent: Sunday, August 12, 2018 6:58 PM Subject: [AllStar #602] 71.95.13.254 blacklisted?[Aug 13 01:57:19] NOTICE[18339]: chan_iax2.c:8284 register_verify: No registration for peer 'xxxxx' (from? that's a new one too. Thanks,--? Bryan Fields, W9CR AllStarLink, Inc.?On Sun Aug 12 21:54:13 2018, N6LXX wrote: ok i will check again.?i must have made a mistake. ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From welfarecat at comcast.net Mon Aug 13 21:17:03 2018 From: welfarecat at comcast.net (Te Bussell) Date: Mon, 13 Aug 2018 17:17:03 -0400 Subject: [App_rpt-users] My location connected to IRLP? Message-ID: I used the installed WIN app on my iPad that now draws a line from my location to an IRLP node in Vancouver Canada. My node is connected to no other location, so I find this strange. I am running the standard approved software, and not Hamvoip. Stranger than science. Bill Bussell KB9WKR NODE 41514 Sent from my iPad From shawpbx at gmail.com Mon Aug 13 21:45:10 2018 From: shawpbx at gmail.com (David Shaw) Date: Mon, 13 Aug 2018 14:45:10 -0700 Subject: [App_rpt-users] Still Working on Migration In-Reply-To: References: Message-ID: Hello Tim, I'll wait patiently. I do like reading the emails around this. -- Thanks, David "Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one." Thomas Jefferson On Mon, Aug 13, 2018 at 12:17 PM Tim Sawyer wrote: > Hey Folks, > > The AllStar developer team knows there are still problems with the new > registration system. The are working on it. The goal continues to be to > make a better AllStar for everyone. Please be patient while they work out > the bugs. > > -- > Tim WD6AWP > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From app_rpt at marrold.co.uk Mon Aug 13 21:50:43 2018 From: app_rpt at marrold.co.uk (2E0SIP) Date: Mon, 13 Aug 2018 22:50:43 +0100 Subject: [App_rpt-users] Still Working on Migration In-Reply-To: References: Message-ID: Hi all, I'm curious, is this new registration system Asterisk based, or have you created your own? I'm following with interest. Thanks Matthew 2E0SIP On Mon, Aug 13, 2018 at 8:17 PM, Tim Sawyer wrote: > Hey Folks, > > The AllStar developer team knows there are still problems with the new > registration system. The are working on it. The goal continues to be to > make a better AllStar for everyone. Please be patient while they work out > the bugs. > > -- > Tim WD6AWP > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Mon Aug 13 22:42:56 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Mon, 13 Aug 2018 18:42:56 -0400 Subject: [App_rpt-users] [AllStar #602] 71.95.13.254 blacklisted In-Reply-To: <166510248.7192992.1534192819422@mail.yahoo.com> References: <298037056.6640680.1534122388655.ref@mail.yahoo.com> <298037056.6640680.1534122388655@mail.yahoo.com> <306391641.6649599.1534125985556@mail.yahoo.com> <914788475.6649938.1534126157005@mail.yahoo.com> <166510248.7192992.1534192819422@mail.yahoo.com> Message-ID: On 8/13/18 4:40 PM, C B wrote: > I do not see how a failed attempt to register should result in being > banned. You're IP is hitting the registration server, about 50 times per minute with many invalid registration attempts. As this never registers, it immediately starts again. This ties up resources on the server. > Having checked all of the private nodes uncovered nothing new. i > attempted to work with the all star team, however my request for more info > and or guidance have gone unanswered other than to tell me to check every > node as i have checked the private nodes it could be a waist of time to > check the 45 to 50 nodes behind my firewall as the problem may not be > obvious. "We've tried nothing and we're all out of ideas." God forbid you'd invest a scintilla of your own time in solving your own problems. Please, expect volunteers solve your problems for you, on your own network, with no charge. I've given you a bunch of pointers, yet you're still over here complaining about it. If you're going to run 30 servers behind NAT, you can't expect anyone external to tell you which one(s) is(are) broken. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From harvard5362 at yahoo.com Tue Aug 14 00:30:44 2018 From: harvard5362 at yahoo.com (C B) Date: Tue, 14 Aug 2018 00:30:44 +0000 (UTC) Subject: [App_rpt-users] [AllStar #602] 71.95.13.254 blacklisted In-Reply-To: References: <298037056.6640680.1534122388655.ref@mail.yahoo.com> <298037056.6640680.1534122388655@mail.yahoo.com> <306391641.6649599.1534125985556@mail.yahoo.com> <914788475.6649938.1534126157005@mail.yahoo.com> <166510248.7192992.1534192819422@mail.yahoo.com> Message-ID: <938870849.7321722.1534206644987@mail.yahoo.com> This attitude is unbelievable. go ahead and keep me blocked given your attitude i am finished with all star i did try looking for the obvious and it was not obvious The other 40 - 50 nodes are not private thus it is not the same issue and is beyond my knowledge to try to find and looking at them would be a waist of time as i do not know what i would be looking for. or it is a different issue on one of the private nodes, in any case i would not know what to look for. using tools such as wire-shark is an efficient way? to isolate an issue, however i lak the skils to do this job, so when i lack the skills i ask.? And i did ask and i received nothing that answered my question? just because you may have? knowledge of this works thus the ability to troubleshoot it clearly i do not as i would not ask for help if i did. As it is beyond my knowledge it is a waist of time to do so. if you would have helped to isolate to what node i could have rebuilt the node and hopefully eliminated the issue? if you represent the future of all star i want nothing to do with it. your holly than thou attitude is not welcome. From: Bryan Fields To: Users of Asterisk app_rpt Sent: Monday, August 13, 2018 3:43 PM Subject: Re: [App_rpt-users] [AllStar #602] 71.95.13.254 blacklisted On 8/13/18 4:40 PM, C B wrote: > I do not see how a failed attempt to register should result in being > banned. You're IP is hitting the registration server, about 50 times per minute with many invalid registration attempts.? As this never registers, it immediately starts again.? This ties up resources on the server. > Having checked all of the private nodes uncovered nothing new. i > attempted to work with the all star team, however my request for more info > and or guidance have gone unanswered other than to tell me to check every > node as i have checked? the private nodes it could be a waist of time to > check the 45 to 50 nodes behind my firewall as the problem may not be > obvious. "We've tried nothing and we're all out of ideas." God forbid you'd invest a scintilla of your own time in solving your own problems.? Please, expect volunteers solve your problems for you, on your own network, with no charge. I've given you a bunch of pointers, yet you're still over here complaining about it.? If you're going to run 30 servers behind NAT, you can't expect anyone external to tell you which one(s) is(are) broken. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at midnighteng.com Tue Aug 14 01:10:35 2018 From: mm at midnighteng.com (Mike) Date: Mon, 13 Aug 2018 21:10:35 -0400 Subject: [App_rpt-users] [AllStar #602] 71.95.13.254 blacklisted In-Reply-To: References: <298037056.6640680.1534122388655.ref@mail.yahoo.com> <298037056.6640680.1534122388655@mail.yahoo.com> <306391641.6649599.1534125985556@mail.yahoo.com> <914788475.6649938.1534126157005@mail.yahoo.com> <166510248.7192992.1534192819422@mail.yahoo.com> Message-ID: I think what some are seeing, thinking they are 'banned' comes down to a simple issue of the registration listing to the connectee via registration verification ? Could this be a possibility ? I'm not having any issues that I can verify this. Just thinking on it. Thank you to all that work to make things better. ...mike/kb8jnm On 8/13/2018 6:42 PM, Bryan Fields wrote: > On 8/13/18 4:40 PM, C B wrote: >> I do not see how a failed attempt to register should result in being >> banned. > > You're IP is hitting the registration server, about 50 times per minute with > many invalid registration attempts. As this never registers, it immediately > starts again. This ties up resources on the server. > >> Having checked all of the private nodes uncovered nothing new. i >> attempted to work with the all star team, however my request for more info >> and or guidance have gone unanswered other than to tell me to check every >> node as i have checked the private nodes it could be a waist of time to >> check the 45 to 50 nodes behind my firewall as the problem may not be >> obvious. > > "We've tried nothing and we're all out of ideas." > > God forbid you'd invest a scintilla of your own time in solving your own > problems. Please, expect volunteers solve your problems for you, on your own > network, with no charge. > > I've given you a bunch of pointers, yet you're still over here complaining > about it. If you're going to run 30 servers behind NAT, you can't expect > anyone external to tell you which one(s) is(are) broken. > > From Bryan at bryanfields.net Tue Aug 14 13:16:56 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Tue, 14 Aug 2018 09:16:56 -0400 Subject: [App_rpt-users] Update on registration Message-ID: We still have about ~200 nodes trying to register to the old server; please check your node and reboot it if it's not registering. Enabling dnsmgr will prevent this in the future and allow asterisk to failover to other servers. Please enable dnsmgr. We've tried to email most of these we can identify, but several have bounced back as the email on file is different. The vast majority of nodes (90%) came back up fine on Sunday, but we were having some serious issues with call number exhaustion from nodes which don't authenticate, and then hammer the server over and over again. Once you're out of call numbers on IAX, even valid nodes cannot authenticate. I think we've resolved this enough for now, there will be a better fix coming, but it's in test. As these are on a per IP basis, we didn't see this in testing as only about 200 hosts tested the cluster even though we had each host registering 100 nodes. The other unplanned event was nodes behind broken NAT. IAX requires a full cone nat to work and we tested with this, and everything worked. What was unplanned was when nat was broken, and Tim was able to come up with a fix to the nodes script for this. This script was completely rewritten and optimized with a 10 second cache, allowing us to generate it every 10 seconds across many servers. Previously the delta between the database and the nodes scripts was about 5 minutes, so this greatly speeds it up. If you look in /var/lib/asterisk/rpt-extnodes you'll see the cache info and which server generated it. Example: ;Generated 2574 records in 0.059 seconds. ;Served in 0.015 seconds. ;Served from cache: Yes ;Generated at 2018-08-14 13:01:26 UTC by register-ord.allstarlink.org In the above example there are 2574 nodes online, and it was served from cache by the Chicago server. The phone portal has been tweaked, and no longer reads back the invalid numbers at first call in. We've been doing much testing with it, and it's much much better as there are no longer 2900 nodes registering to it as well. I've yet to hear it stutter. 73's -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From flatpossum1231 at yahoo.com Tue Aug 14 13:31:20 2018 From: flatpossum1231 at yahoo.com (Mr. Possum (Bill)) Date: Tue, 14 Aug 2018 13:31:20 +0000 (UTC) Subject: [App_rpt-users] Update on registration In-Reply-To: References: Message-ID: <1085590553.6503504.1534253480531@mail.yahoo.com> Bryan, I went and looked at the /var/lib/asterisk/rpt_extnodes file and it had nothing in it...? Nada...? And my main hub node keeps registering as 209.112.233.252:1127 when it SHOULD be 209.112.233.252:4571... I've got a few nodes registering like this...? and the rpt_extnodes is a 1KB file dated 4/3/2015? Can you hand me a clue? Thanks! Bill - N5MBMwww.texasrepeaternetwork.net From: Bryan Fields To: Users of Asterisk app_rpt Sent: Tuesday, August 14, 2018 8:17 AM Subject: [App_rpt-users] Update on registration We still have about ~200 nodes trying to register to the old server; please check your node and reboot it if it's not registering.? Enabling dnsmgr will prevent this in the future and allow asterisk to failover to other servers. Please enable dnsmgr.? We've tried to email most of these we can identify, but several have bounced back as the email on file is different. The vast majority of nodes (90%) came back up fine on Sunday, but we were having some serious issues with call number exhaustion from nodes which don't authenticate, and then hammer the server over and over again.? Once you're out of call numbers on IAX, even valid nodes cannot authenticate.? I think we've resolved this enough for now, there will be a better fix coming, but it's in test.? As these are on a per IP basis, we didn't see this in testing as only about 200 hosts tested the cluster even though we had each host registering 100 nodes. The other unplanned event was nodes behind broken NAT.? IAX requires a full cone nat to work and we tested with this, and everything worked.? What was unplanned was when nat was broken, and Tim was able to come up with a fix to the nodes script for this.? This script was completely rewritten and optimized with a 10 second cache, allowing us to generate it every 10 seconds across many servers.? Previously the delta between the database and the nodes scripts was about 5 minutes, so this greatly speeds it up. If you look in /var/lib/asterisk/rpt-extnodes you'll see the cache info and which server generated it. Example: ;Generated 2574 records in 0.059 seconds. ;Served in 0.015 seconds. ;Served from cache: Yes ;Generated at 2018-08-14 13:01:26 UTC by register-ord.allstarlink.org In the above example there are 2574 nodes online, and it was served from cache by the Chicago server. The phone portal has been tweaked, and no longer reads back the invalid numbers at first call in.? We've been doing much testing with it, and it's much much better as there are no longer 2900 nodes registering to it as well. I've yet to hear it stutter. 73's -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kc8qch at gmail.com Tue Aug 14 13:44:44 2018 From: kc8qch at gmail.com (kc8qch at gmail.com) Date: Tue, 14 Aug 2018 09:44:44 -0400 Subject: [App_rpt-users] Update on registration In-Reply-To: References: Message-ID: <0c1801d433d4$f643aa60$e2caff20$@gmail.com> HI Bryan, How does one go about enabling dnsmgr or at least verify it is running or not.... Thanks, Jeff -----Original Message----- From: App_rpt-users On Behalf Of Bryan Fields Sent: Tuesday, August 14, 2018 09:17 To: Users of Asterisk app_rpt Subject: [App_rpt-users] Update on registration We still have about ~200 nodes trying to register to the old server; please check your node and reboot it if it's not registering. Enabling dnsmgr will prevent this in the future and allow asterisk to failover to other servers. Please enable dnsmgr. We've tried to email most of these we can identify, but several have bounced back as the email on file is different. The vast majority of nodes (90%) came back up fine on Sunday, but we were having some serious issues with call number exhaustion from nodes which don't authenticate, and then hammer the server over and over again. Once you're out of call numbers on IAX, even valid nodes cannot authenticate. I think we've resolved this enough for now, there will be a better fix coming, but it's in test. As these are on a per IP basis, we didn't see this in testing as only about 200 hosts tested the cluster even though we had each host registering 100 nodes. The other unplanned event was nodes behind broken NAT. IAX requires a full cone nat to work and we tested with this, and everything worked. What was unplanned was when nat was broken, and Tim was able to come up with a fix to the nodes script for this. This script was completely rewritten and optimized with a 10 second cache, allowing us to generate it every 10 seconds across many servers. Previously the delta between the database and the nodes scripts was about 5 minutes, so this greatly speeds it up. If you look in /var/lib/asterisk/rpt-extnodes you'll see the cache info and which server generated it. Example: ;Generated 2574 records in 0.059 seconds. ;Served in 0.015 seconds. ;Served from cache: Yes ;Generated at 2018-08-14 13:01:26 UTC by register-ord.allstarlink.org In the above example there are 2574 nodes online, and it was served from cache by the Chicago server. The phone portal has been tweaked, and no longer reads back the invalid numbers at first call in. We've been doing much testing with it, and it's much much better as there are no longer 2900 nodes registering to it as well. I've yet to hear it stutter. 73's -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. From Bryan at bryanfields.net Tue Aug 14 13:49:19 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Tue, 14 Aug 2018 09:49:19 -0400 Subject: [App_rpt-users] Update on registration In-Reply-To: <0c1801d433d4$f643aa60$e2caff20$@gmail.com> References: <0c1801d433d4$f643aa60$e2caff20$@gmail.com> Message-ID: <19da0c6e-9360-ca1f-49fb-e59f099dc5d7@bryanfields.net> On 8/14/18 9:44 AM, kc8qch at gmail.com wrote: > How does one go about enabling dnsmgr or at least verify it is running or > not.... 'iax2 show registry' Itchy*CLI> iax2 show registry Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 44233 44.98.249.6:4569 60 Registered 44.98.254.145:4569 Y 42032 44.98.249.6:4569 60 Registered 44.98.254.145:4569 Y 41618 44.98.249.6:4569 60 Registered 44.98.254.145:4569 Y 40821 44.98.249.6:4569 60 Registered If it says Y under dnsmgr, you're good. If it's an N, it's not running and it will not refresh DNS lookups until asterisk is restarted. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From kc8qch at gmail.com Tue Aug 14 13:52:49 2018 From: kc8qch at gmail.com (kc8qch at gmail.com) Date: Tue, 14 Aug 2018 09:52:49 -0400 Subject: [App_rpt-users] Update on registration In-Reply-To: <19da0c6e-9360-ca1f-49fb-e59f099dc5d7@bryanfields.net> References: <0c1801d433d4$f643aa60$e2caff20$@gmail.com> <19da0c6e-9360-ca1f-49fb-e59f099dc5d7@bryanfields.net> Message-ID: <0c3001d433d6$17262220$45726660$@gmail.com> Oh duh! I knew that....thanks for the refresher...... Jeff -----Original Message----- From: App_rpt-users On Behalf Of Bryan Fields Sent: Tuesday, August 14, 2018 09:49 To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] Update on registration On 8/14/18 9:44 AM, kc8qch at gmail.com wrote: > How does one go about enabling dnsmgr or at least verify it is running > or not.... 'iax2 show registry' Itchy*CLI> iax2 show registry Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 44233 44.98.249.6:4569 60 Registered 44.98.254.145:4569 Y 42032 44.98.249.6:4569 60 Registered 44.98.254.145:4569 Y 41618 44.98.249.6:4569 60 Registered 44.98.254.145:4569 Y 40821 44.98.249.6:4569 60 Registered If it says Y under dnsmgr, you're good. If it's an N, it's not running and it will not refresh DNS lookups until asterisk is restarted. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. From Bryan at bryanfields.net Tue Aug 14 13:54:24 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Tue, 14 Aug 2018 09:54:24 -0400 Subject: [App_rpt-users] Update on registration In-Reply-To: <1085590553.6503504.1534253480531@mail.yahoo.com> References: <1085590553.6503504.1534253480531@mail.yahoo.com> Message-ID: <05478e28-1496-2af3-ab90-cefcfc8de367@bryanfields.net> On 8/14/18 9:31 AM, Mr. Possum (Bill) wrote: > I went and looked at the /var/lib/asterisk/rpt_extnodes file and it had > nothing in it... Nada... Is rc.updatenodelist running? It doesn't sound like it is. Restart it or reboot the node to get it running again. > And my main hub node keeps registering as > 209.112.233.252:1127 when it SHOULD be 209.112.233.252:4571... I've got a > few nodes registering like this... and the rpt_extnodes is a 1KB file > dated 4/3/2015? Below is everything i see for your IP address: 42413=radio at 209.112.233.252:4572/42413,209.112.233.252 42414=radio at 209.112.233.252:4573/42414,209.112.233.252 42466=radio at 209.112.233.252:4573/42466,209.112.233.252 42471=radio at 209.112.233.252:4574/42471,209.112.233.252 42817=radio at 209.112.233.252:4571/42817,209.112.233.252 43033=radio at 209.112.233.252:4571/43033,209.112.233.252 43034=radio at 209.112.233.252:4571/43034,209.112.233.252 43035=radio at 209.112.233.252:4572/43035,209.112.233.252 45634=radio at 209.112.233.252:4571/45634,209.112.233.252 45635=radio at 209.112.233.252:4576/45635,209.112.233.252,y 45636=radio at 209.112.233.252:4576/45636,209.112.233.252,y 45638=radio at 209.112.233.252:4576/45638,209.112.233.252 45644=radio at 209.112.233.252:4575/45644,209.112.233.252 45645=radio at 209.112.233.252:4574/45645,209.112.233.252 45646=radio at 209.112.233.252:4575/45646,209.112.233.252 46902=radio at 209.112.233.252:4580/46902,209.112.233.252 I don't see port 1127 on any of them. 73's -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From flatpossum1231 at yahoo.com Tue Aug 14 14:06:58 2018 From: flatpossum1231 at yahoo.com (Mr. Possum (Bill)) Date: Tue, 14 Aug 2018 14:06:58 +0000 (UTC) Subject: [App_rpt-users] Update on registration In-Reply-To: <05478e28-1496-2af3-ab90-cefcfc8de367@bryanfields.net> References: <1085590553.6503504.1534253480531@mail.yahoo.com> <05478e28-1496-2af3-ab90-cefcfc8de367@bryanfields.net> Message-ID: <303483761.6571103.1534255618180@mail.yahoo.com> Thanks Bryan, When I reboot my main hub node I still get the same stuff... [root at RP1 /]# asterisk -rx "iax2 show registry" Host????????????????? dnsmgr? Username??????? Perceived???????????? Refresh? State 44.98.254.145:4569??? Y?????? 45634?????????? 209.112.233.252:1127?????? 60? Registered 44.98.254.145:4569??? Y?????? 42817?????????? 209.112.233.252:1127?????? 60? Registered 44.98.254.145:4569??? Y?????? 43034?????????? 209.112.233.252:1127?????? 60? Registered 44.98.254.145:4569??? Y?????? 43033?????????? 209.112.233.252:1127?????? 60? Registered [root at RP1 /]# When I reboot my Navasota node I get - [root at Navasota AUTOSKY]# asterisk -rx "iax2 show registry" Host????????????????? dnsmgr? Username??????? Perceived???????????? Refresh? State 44.98.254.145:4569??? Y?????? 46904?????????? 50.27.185.134:1027???????? 60? Registered 44.98.254.145:4569??? Y?????? 46901?????????? 50.27.185.134:1027???????? 60? Auth. Sent [root at Navasota AUTOSKY]# How do I kick rc.updatenodelist in the butt? Thanks,Bill - N5MBM From: Bryan Fields To: Users of Asterisk app_rpt Sent: Tuesday, August 14, 2018 8:54 AM Subject: Re: [App_rpt-users] Update on registration On 8/14/18 9:31 AM, Mr. Possum (Bill) wrote: > I went and looked at the /var/lib/asterisk/rpt_extnodes file and it had > nothing in it...? Nada...? Is rc.updatenodelist running?? It doesn't sound like it is.? Restart it or reboot the node to get it running again. > And my main hub node keeps registering as > 209.112.233.252:1127 when it SHOULD be 209.112.233.252:4571... I've got a > few nodes registering like this...? and the rpt_extnodes is a 1KB file > dated 4/3/2015? Below is everything i see for your IP address: 42413=radio at 209.112.233.252:4572/42413,209.112.233.252 42414=radio at 209.112.233.252:4573/42414,209.112.233.252 42466=radio at 209.112.233.252:4573/42466,209.112.233.252 42471=radio at 209.112.233.252:4574/42471,209.112.233.252 42817=radio at 209.112.233.252:4571/42817,209.112.233.252 43033=radio at 209.112.233.252:4571/43033,209.112.233.252 43034=radio at 209.112.233.252:4571/43034,209.112.233.252 43035=radio at 209.112.233.252:4572/43035,209.112.233.252 45634=radio at 209.112.233.252:4571/45634,209.112.233.252 45635=radio at 209.112.233.252:4576/45635,209.112.233.252,y 45636=radio at 209.112.233.252:4576/45636,209.112.233.252,y 45638=radio at 209.112.233.252:4576/45638,209.112.233.252 45644=radio at 209.112.233.252:4575/45644,209.112.233.252 45645=radio at 209.112.233.252:4574/45645,209.112.233.252 45646=radio at 209.112.233.252:4575/45646,209.112.233.252 46902=radio at 209.112.233.252:4580/46902,209.112.233.252 I don't see port 1127 on any of them. 73's -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Tue Aug 14 14:53:11 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Tue, 14 Aug 2018 10:53:11 -0400 Subject: [App_rpt-users] Update on registration In-Reply-To: <303483761.6571103.1534255618180@mail.yahoo.com> References: <1085590553.6503504.1534253480531@mail.yahoo.com> <05478e28-1496-2af3-ab90-cefcfc8de367@bryanfields.net> <303483761.6571103.1534255618180@mail.yahoo.com> Message-ID: <721fb693-a948-c6f6-1ca6-3310c86b57f9@bryanfields.net> On 8/14/18 10:06 AM, Mr. Possum (Bill) wrote: > Thanks Bryan, > When I reboot my main hub node I still get the same stuff... > [root at RP1 /]# asterisk -rx "iax2 show registry" > Host????????????????? dnsmgr? Username??????? Perceived???????????? Refresh? State > 44.98.254.145:4569??? Y?????? 45634?????????? 209.112.233.252:1127?????? 60? Registered > 44.98.254.145:4569??? Y?????? 42817?????????? 209.112.233.252:1127?????? 60? Registered > 44.98.254.145:4569??? Y?????? 43034?????????? 209.112.233.252:1127?????? 60? Registered > 44.98.254.145:4569??? Y?????? 43033?????????? 209.112.233.252:1127?????? 60? Registered > [root at RP1 /]# > When I reboot my Navasota node I get - > > [root at Navasota AUTOSKY]# asterisk -rx "iax2 show registry" > Host????????????????? dnsmgr? Username??????? Perceived???????????? Refresh? State > 44.98.254.145:4569??? Y?????? 46904?????????? 50.27.185.134:1027???????? 60? Registered > 44.98.254.145:4569??? Y?????? 46901?????????? 50.27.185.134:1027???????? 60? Auth. Sent Yea, it just means your NAT is not full cone. Your NAT box is not preserving the source port numbers of your node and the registration server is seeing you as 50.27.185.134 port 1027, rather than port 4569. You nodes are working just fine. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From flatpossum1231 at yahoo.com Tue Aug 14 15:29:17 2018 From: flatpossum1231 at yahoo.com (Mr. Possum (Bill)) Date: Tue, 14 Aug 2018 15:29:17 +0000 (UTC) Subject: [App_rpt-users] Update on registration In-Reply-To: <721fb693-a948-c6f6-1ca6-3310c86b57f9@bryanfields.net> References: <1085590553.6503504.1534253480531@mail.yahoo.com> <05478e28-1496-2af3-ab90-cefcfc8de367@bryanfields.net> <303483761.6571103.1534255618180@mail.yahoo.com> <721fb693-a948-c6f6-1ca6-3310c86b57f9@bryanfields.net> Message-ID: <671743217.6600145.1534260557229@mail.yahoo.com> Thanks for that tidbit of info Bryan...? And now that you mention it, BOTH of these addresses are behind Mikrotik routers...? And I don't have a clue as to how to "fix" it.? One belongs to me and the other to the site owner over in Navasota.? Mikrotik's are strange animals, I am more used to conguring Cisco, Nortel and of course the old LinkSys routers... Bill - N5MBM From: Bryan Fields To: Users of Asterisk app_rpt Sent: Tuesday, August 14, 2018 9:53 AM Subject: Re: [App_rpt-users] Update on registration On 8/14/18 10:06 AM, Mr. Possum (Bill) wrote: > Thanks Bryan, > When I reboot my main hub node I still get the same stuff... > [root at RP1 /]# asterisk -rx "iax2 show registry" > Host????????????????? dnsmgr? Username??????? Perceived???????????? Refresh? State > 44.98.254.145:4569??? Y?????? 45634?????????? 209.112.233.252:1127?????? 60? Registered > 44.98.254.145:4569??? Y?????? 42817?????????? 209.112.233.252:1127?????? 60? Registered > 44.98.254.145:4569??? Y?????? 43034?????????? 209.112.233.252:1127?????? 60? Registered > 44.98.254.145:4569??? Y?????? 43033?????????? 209.112.233.252:1127?????? 60? Registered > [root at RP1 /]# > When I reboot my Navasota node I get - > > [root at Navasota AUTOSKY]# asterisk -rx "iax2 show registry" > Host????????????????? dnsmgr? Username??????? Perceived???????????? Refresh? State > 44.98.254.145:4569??? Y?????? 46904?????????? 50.27.185.134:1027???????? 60? Registered > 44.98.254.145:4569??? Y?????? 46901?????????? 50.27.185.134:1027???????? 60? Auth. Sent Yea, it just means your NAT is not full cone.? Your NAT box is not preserving the source port numbers of your node and the registration server is seeing you as 50.27.185.134 port 1027, rather than port 4569. You nodes are working just fine. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at dyb.com Tue Aug 14 16:18:36 2018 From: george at dyb.com (George Csahanin) Date: Tue, 14 Aug 2018 11:18:36 -0500 Subject: [App_rpt-users] All back to normal Message-ID: All is normal here at Radio Ranch. Thanks to all for the efforts. Had a failure last night but that was AT&T (as usual) screwing up my gateway. Overnight it would not connect to anything. I am soooooo done with AT&T when this contract is up. Will go from this pitiful 25 Mbps service to 400 Mbps with Spectrum. GeorgeC W2DB nodes 2360, 28599 -- George Csahanin 10100 Carson Ranch Rd. Crowley, TX 76036 682-708-5716 home 401-338-0568 cel From flatpossum1231 at yahoo.com Tue Aug 14 16:25:13 2018 From: flatpossum1231 at yahoo.com (Mr. Possum (Bill)) Date: Tue, 14 Aug 2018 16:25:13 +0000 (UTC) Subject: [App_rpt-users] Update on registration In-Reply-To: <721fb693-a948-c6f6-1ca6-3310c86b57f9@bryanfields.net> References: <1085590553.6503504.1534253480531@mail.yahoo.com> <05478e28-1496-2af3-ab90-cefcfc8de367@bryanfields.net> <303483761.6571103.1534255618180@mail.yahoo.com> <721fb693-a948-c6f6-1ca6-3310c86b57f9@bryanfields.net> Message-ID: <132710226.6642635.1534263913817@mail.yahoo.com> Bryan, On a semi-unrelated note...? Do we have any idea when the bubble charts will start functioning properly again?? I go to http://stats.allstarlink.org/getstatus.cgi?46682 and it says I am not connected to anything?? That's my main HUB node that has a lot of connections...? You can see them all at http://n5mbm.net:81/supermon/link.php?nodes=46682,45634,43033,29503,43773 Thanks! Bill - N5MBM From: Bryan Fields To: Users of Asterisk app_rpt Sent: Tuesday, August 14, 2018 9:53 AM Subject: Re: [App_rpt-users] Update on registration On 8/14/18 10:06 AM, Mr. Possum (Bill) wrote: > Thanks Bryan, > When I reboot my main hub node I still get the same stuff... > [root at RP1 /]# asterisk -rx "iax2 show registry" > Host????????????????? dnsmgr? Username??????? Perceived???????????? Refresh? State > 44.98.254.145:4569??? Y?????? 45634?????????? 209.112.233.252:1127?????? 60? Registered > 44.98.254.145:4569??? Y?????? 42817?????????? 209.112.233.252:1127?????? 60? Registered > 44.98.254.145:4569??? Y?????? 43034?????????? 209.112.233.252:1127?????? 60? Registered > 44.98.254.145:4569??? Y?????? 43033?????????? 209.112.233.252:1127?????? 60? Registered > [root at RP1 /]# > When I reboot my Navasota node I get - > > [root at Navasota AUTOSKY]# asterisk -rx "iax2 show registry" > Host????????????????? dnsmgr? Username??????? Perceived???????????? Refresh? State > 44.98.254.145:4569??? Y?????? 46904?????????? 50.27.185.134:1027???????? 60? Registered > 44.98.254.145:4569??? Y?????? 46901?????????? 50.27.185.134:1027???????? 60? Auth. Sent Yea, it just means your NAT is not full cone.? Your NAT box is not preserving the source port numbers of your node and the registration server is seeing you as 50.27.185.134 port 1027, rather than port 4569. You nodes are working just fine. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bryan at bryanfields.net Tue Aug 14 16:29:13 2018 From: bryan at bryanfields.net (Bryan Fields) Date: Tue, 14 Aug 2018 11:29:13 -0500 (CDT) Subject: [App_rpt-users] Update on registration In-Reply-To: <132710226.6642635.1534263913817@mail.yahoo.com> References: <1085590553.6503504.1534253480531@mail.yahoo.com> <05478e28-1496-2af3-ab90-cefcfc8de367@bryanfields.net> <303483761.6571103.1534255618180@mail.yahoo.com> <721fb693-a948-c6f6-1ca6-3310c86b57f9@bryanfields.net> <132710226.6642635.1534263913817@mail.yahoo.com> Message-ID: It is working, your node isnt showing up for some reason. Can you check that its posting the http updates to http://stats.allstarlink.org/ ? -- Bryan Fields M: +1-727-409-1194 > On Aug 14, 2018, at 12:25, Mr. Possum (Bill) wrote: > > Bryan, > > On a semi-unrelated note... Do we have any idea when the bubble charts will start functioning properly again? > > I go to http://stats.allstarlink.org/getstatus.cgi?46682 and it says I am not connected to anything? That's my main HUB node that has a lot of connections... You can see them all at http://n5mbm.net:81/supermon/link.php?nodes=46682,45634,43033,29503,43773 > > Thanks! > > Bill - N5MBM > > > From: Bryan Fields > To: Users of Asterisk app_rpt > Sent: Tuesday, August 14, 2018 9:53 AM > Subject: Re: [App_rpt-users] Update on registration > > On 8/14/18 10:06 AM, Mr. Possum (Bill) wrote: > > Thanks Bryan, > > When I reboot my main hub node I still get the same stuff... > > [root at RP1 /]# asterisk -rx "iax2 show registry" > > Host dnsmgr Username Perceived Refresh State > > 44.98.254.145:4569 Y 45634 209.112.233.252:1127 60 Registered > > 44.98.254.145:4569 Y 42817 209.112.233.252:1127 60 Registered > > 44.98.254.145:4569 Y 43034 209.112.233.252:1127 60 Registered > > 44.98.254.145:4569 Y 43033 209.112.233.252:1127 60 Registered > > [root at RP1 /]# > > When I reboot my Navasota node I get - > > > > [root at Navasota AUTOSKY]# asterisk -rx "iax2 show registry" > > Host dnsmgr Username Perceived Refresh State > > 44.98.254.145:4569 Y 46904 50.27.185.134:1027 60 Registered > > 44.98.254.145:4569 Y 46901 50.27.185.134:1027 60 Auth. Sent > > Yea, it just means your NAT is not full cone. Your NAT box is not preserving > the source port numbers of your node and the registration server is seeing you > as 50.27.185.134 port 1027, rather than port 4569. > > You nodes are working just fine. > > -- > Bryan Fields > > 727-409-1194 - Voice > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From flatpossum1231 at yahoo.com Tue Aug 14 16:41:44 2018 From: flatpossum1231 at yahoo.com (Mr. Possum (Bill)) Date: Tue, 14 Aug 2018 16:41:44 +0000 (UTC) Subject: [App_rpt-users] Update on registration In-Reply-To: References: <1085590553.6503504.1534253480531@mail.yahoo.com> <05478e28-1496-2af3-ab90-cefcfc8de367@bryanfields.net> <303483761.6571103.1534255618180@mail.yahoo.com> <721fb693-a948-c6f6-1ca6-3310c86b57f9@bryanfields.net> <132710226.6642635.1534263913817@mail.yahoo.com> Message-ID: <956358785.6644223.1534264904754@mail.yahoo.com> I have three nodes at that particular remote repeater site - 45441 reports N/A for all the data, 46903 isn't showing up at all on the stats list and neither is the hub node 46682.? When I scroll through the list at http://stats.allstarlink.org/ I find 45441 with no data and the others just don't show up at all...? And I have the right statpost arguments in the rpt.conf file... ; *** Status Reporting *** statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null?????????????????????? statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates (scratches head) Uhhh... that oughta work right?? :) Bill - N5MBM From: Bryan Fields To: Users of Asterisk app_rpt Sent: Tuesday, August 14, 2018 11:29 AM Subject: Re: [App_rpt-users] Update on registration It is working, your node isnt showing up for some reason. ?Can you check that its posting the http updates to?http://stats.allstarlink.org/?? --Bryan FieldsM: +1-727-409-1194 On Aug 14, 2018, at 12:25, Mr. Possum (Bill) wrote: Bryan, On a semi-unrelated note...? Do we have any idea when the bubble charts will start functioning properly again?? I go to http://stats.allstarlink.org/getstatus.cgi?46682 and it says I am not connected to anything?? That's my main HUB node that has a lot of connections...? You can see them all at http://n5mbm.net:81/supermon/link.php?nodes=46682,45634,43033,29503,43773 Thanks! Bill - N5MBM From: Bryan Fields To: Users of Asterisk app_rpt Sent: Tuesday, August 14, 2018 9:53 AM Subject: Re: [App_rpt-users] Update on registration On 8/14/18 10:06 AM, Mr. Possum (Bill) wrote: > Thanks Bryan, > When I reboot my main hub node I still get the same stuff... > [root at RP1 /]# asterisk -rx "iax2 show registry" > Host????????????????? dnsmgr? Username??????? Perceived???????????? Refresh? State > 44.98.254.145:4569??? Y?????? 45634?????????? 209.112.233.252:1127?????? 60? Registered > 44.98.254.145:4569??? Y?????? 42817?????????? 209.112.233.252:1127?????? 60? Registered > 44.98.254.145:4569??? Y?????? 43034?????????? 209.112.233.252:1127?????? 60? Registered > 44.98.254.145:4569??? Y?????? 43033?????????? 209.112.233.252:1127?????? 60? Registered > [root at RP1 /]# > When I reboot my Navasota node I get - > > [root at Navasota AUTOSKY]# asterisk -rx "iax2 show registry" > Host????????????????? dnsmgr? Username??????? Perceived???????????? Refresh? State > 44.98.254.145:4569??? Y?????? 46904?????????? 50.27.185.134:1027???????? 60? Registered > 44.98.254.145:4569??? Y?????? 46901?????????? 50.27.185.134:1027???????? 60? Auth. Sent Yea, it just means your NAT is not full cone.? Your NAT box is not preserving the source port numbers of your node and the registration server is seeing you as 50.27.185.134 port 1027, rather than port 4569. You nodes are working just fine. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Tue Aug 14 16:56:07 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Tue, 14 Aug 2018 12:56:07 -0400 Subject: [App_rpt-users] Update on registration In-Reply-To: <956358785.6644223.1534264904754@mail.yahoo.com> References: <1085590553.6503504.1534253480531@mail.yahoo.com> <05478e28-1496-2af3-ab90-cefcfc8de367@bryanfields.net> <303483761.6571103.1534255618180@mail.yahoo.com> <721fb693-a948-c6f6-1ca6-3310c86b57f9@bryanfields.net> <132710226.6642635.1534263913817@mail.yahoo.com> <956358785.6644223.1534264904754@mail.yahoo.com> Message-ID: On 8/14/18 12:41 PM, Mr. Possum (Bill) wrote: > I have three nodes at that particular remote repeater site - 45441 reports > N/A for all the data, 46903 isn't showing up at all on the stats list and > neither is the hub node 46682. Bill, try it again. I actually found an issue with it, it was pulling the stats only for certain nodes, this was due to the db request not being pointed at the new db. Sorry for sending on a wild goose chase there, and many thanks for helping us troubleshoot it. 73's -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From flatpossum1231 at yahoo.com Tue Aug 14 16:59:45 2018 From: flatpossum1231 at yahoo.com (Mr. Possum (Bill)) Date: Tue, 14 Aug 2018 16:59:45 +0000 (UTC) Subject: [App_rpt-users] Update on registration In-Reply-To: References: <1085590553.6503504.1534253480531@mail.yahoo.com> <05478e28-1496-2af3-ab90-cefcfc8de367@bryanfields.net> <303483761.6571103.1534255618180@mail.yahoo.com> <721fb693-a948-c6f6-1ca6-3310c86b57f9@bryanfields.net> <132710226.6642635.1534263913817@mail.yahoo.com> <956358785.6644223.1534264904754@mail.yahoo.com> Message-ID: <2013790098.6695836.1534265985168@mail.yahoo.com> AHA!? So the fault did not lie in my set?!?? LOL Thanks for fixing it!? I think I am back to "normal" now... Bill - N5MBM From: Bryan Fields To: Users of Asterisk app_rpt Sent: Tuesday, August 14, 2018 11:56 AM Subject: Re: [App_rpt-users] Update on registration On 8/14/18 12:41 PM, Mr. Possum (Bill) wrote: > I have three nodes at that particular remote repeater site - 45441 reports > N/A for all the data, 46903 isn't showing up at all on the stats list and > neither is the hub node 46682. Bill, try it again.? I actually found an issue with it, it was pulling the stats only for certain nodes, this was due to the db request not being pointed at the new db. Sorry for sending on a wild goose chase there, and many thanks for helping us troubleshoot it. 73's -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcarl.griffith at gmail.com Tue Aug 14 18:02:02 2018 From: jcarl.griffith at gmail.com (John Griffith) Date: Tue, 14 Aug 2018 11:02:02 -0700 Subject: [App_rpt-users] Not working for me yet Message-ID: <01ec01d433f8$e87d78b0$b9786a10$@gmail.com> Greetings. Still having a problem registering. Here's my data: Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 29600 60 Request Sent If there's any more information I need to send, I can. John Griffith N7OKN Node 29600 WIN System affiliate From Bryan at bryanfields.net Tue Aug 14 18:06:17 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Tue, 14 Aug 2018 14:06:17 -0400 Subject: [App_rpt-users] Not working for me yet In-Reply-To: <01ec01d433f8$e87d78b0$b9786a10$@gmail.com> References: <01ec01d433f8$e87d78b0$b9786a10$@gmail.com> Message-ID: On 8/14/18 2:02 PM, John Griffith wrote: > Greetings. > > Still having a problem registering. > Here's my data: > > Host dnsmgr Username Perceived > Refresh State > 44.98.254.145:4569 Y 29600 > 60 Request Sent > > If there's any more information I need to send, I can. Need to know your IP address. Can you please post that too? -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From asonnesso at gmail.com Tue Aug 14 18:25:12 2018 From: asonnesso at gmail.com (Angelo T Sonnesso) Date: Tue, 14 Aug 2018 14:25:12 -0400 Subject: [App_rpt-users] Not working for me yet In-Reply-To: <01ec01d433f8$e87d78b0$b9786a10$@gmail.com> References: <01ec01d433f8$e87d78b0$b9786a10$@gmail.com> Message-ID: <00c301d433fc$24988ee0$6dc9aca0$@gmail.com> It seems that the only node I can connect with is 47288. If I try others I can't connect. Any suggestions? 73 N2DYN Angelo -----Original Message----- From: App_rpt-users On Behalf Of John Griffith Sent: Tuesday, August 14, 2018 2:02 PM To: 'Users of Asterisk app_rpt' Subject: [App_rpt-users] Not working for me yet Greetings. Still having a problem registering. Here's my data: Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 29600 60 Request Sent If there's any more information I need to send, I can. John Griffith N7OKN Node 29600 WIN System affiliate _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. From nhardman1428 at gmail.com Tue Aug 14 22:01:32 2018 From: nhardman1428 at gmail.com (Nate Hardman) Date: Tue, 14 Aug 2018 18:01:32 -0400 Subject: [App_rpt-users] Not working for me yet In-Reply-To: <00c301d433fc$24988ee0$6dc9aca0$@gmail.com> References: <01ec01d433f8$e87d78b0$b9786a10$@gmail.com> <00c301d433fc$24988ee0$6dc9aca0$@gmail.com> Message-ID: John, we will need to know the IP address that the node is using. You may email to helpdesk at allstarlink.org if you wish to keep you public IP address from being common knowledge. You can use the DIG command from the command line user at debian9:~ $ dig +short myip.opendns.com @resolver1.opendns.com to resolve the pubic IP the node is using. On Tue, Aug 14, 2018 at 2:25 PM, Angelo T Sonnesso wrote: > It seems that the only node I can connect with is 47288. > If I try others I can't connect. > Any suggestions? > > 73 N2DYN Angelo > > -----Original Message----- > From: App_rpt-users On > Behalf > Of John Griffith > Sent: Tuesday, August 14, 2018 2:02 PM > To: 'Users of Asterisk app_rpt' > Subject: [App_rpt-users] Not working for me yet > > > Greetings. > > Still having a problem registering. > Here's my data: > > Host dnsmgr Username > Perceived > Refresh State > 44.98.254.145:4569 Y 29600 > 60 Request Sent > > If there's any more information I need to send, I can. > > > John Griffith > N7OKN > > Node 29600 > WIN System affiliate > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > -- Nathan Hardman nhardman1428 at gmail.com N8THN at ARRL.NET -------------- next part -------------- An HTML attachment was scrubbed... URL: From tom at tomh.us Tue Aug 14 22:55:25 2018 From: tom at tomh.us (Tom Hayward) Date: Tue, 14 Aug 2018 15:55:25 -0700 Subject: [App_rpt-users] Not working for me yet In-Reply-To: References: <01ec01d433f8$e87d78b0$b9786a10$@gmail.com> <00c301d433fc$24988ee0$6dc9aca0$@gmail.com> Message-ID: On Tue, Aug 14, 2018 at 3:01 PM Nate Hardman wrote: > You can use the DIG command from the command line user at debian9:~ $ > dig +short myip.opendns.com @resolver1.opendns.com to resolve the pubic > IP the node is using. > I apologize for veering off topic here, but "curl http://checkip.amazonaws.com/" is another favorite of mine for checking public IP address of a server / headless system. Just SSH in and paste that into the shell. Tom KD7LXL -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcarl.griffith at gmail.com Tue Aug 14 23:01:27 2018 From: jcarl.griffith at gmail.com (John Griffith) Date: Tue, 14 Aug 2018 16:01:27 -0700 Subject: [App_rpt-users] Not working for me yet In-Reply-To: References: <01ec01d433f8$e87d78b0$b9786a10$@gmail.com> <00c301d433fc$24988ee0$6dc9aca0$@gmail.com> Message-ID: <029501d43422$bbe07990$33a16cb0$@gmail.com> We got the IP thank you. Been getting some private help, but will post back if needed. Real head scratcher. From: App_rpt-users On Behalf Of Tom Hayward Sent: Tuesday, August 14, 2018 3:55 PM To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] Not working for me yet On Tue, Aug 14, 2018 at 3:01 PM Nate Hardman > wrote: You can use the DIG command from the command line user at debian9:~ $ dig +short myip.opendns.com @resolver1.opendns.com to resolve the pubic IP the node is using. I apologize for veering off topic here, but "curl http://checkip.amazonaws.com/" is another favorite of mine for checking public IP address of a server / headless system. Just SSH in and paste that into the shell. Tom KD7LXL -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcarl.griffith at gmail.com Wed Aug 15 05:23:19 2018 From: jcarl.griffith at gmail.com (jcarl.griffith at gmail.com) Date: Tue, 14 Aug 2018 22:23:19 -0700 Subject: [App_rpt-users] Not working for me yet Message-ID: Finally got it working. Had to reset some settings in my router and clear the pipes. Thank you all. Sent from my T-Mobile 4G LTE device ------ Original message------From: Tom HaywardDate: Tue, Aug 14, 2018 3:56 PMTo: Users of Asterisk app_rpt;Cc: Subject:Re: [App_rpt-users] Not working for me yet On Tue, Aug 14, 2018 at 3:01 PM Nate Hardman wrote: You can use the DIG command? from the command line? ? user at debian9:~ $ dig +short myip.opendns.com @resolver1.opendns.com? ?to resolve the pubic IP the node is using. I apologize for veering off topic here, but "curl http://checkip.amazonaws.com/" is another favorite of mine for checking public IP address of a server / headless system. Just SSH in and paste that into the shell. Tom KD7LXL -------------- next part -------------- An HTML attachment was scrubbed... URL: From ky1u at gmx.com Wed Aug 15 12:42:06 2018 From: ky1u at gmx.com (Greg) Date: Wed, 15 Aug 2018 08:42:06 -0400 Subject: [App_rpt-users] tone decode, encode In-Reply-To: References: Message-ID: Is there a page with information of how to use allstar to decode and encode ctcss? I was hoping to do 2 different tones. Thanks Greg From kizzy at lusfiber.net Wed Aug 15 13:59:35 2018 From: kizzy at lusfiber.net (Steve Mahler) Date: Wed, 15 Aug 2018 08:59:35 -0500 Subject: [App_rpt-users] tone decode, encode In-Reply-To: References: Message-ID: <9be79298-33e5-1936-bdbd-82fde75158f5@lusfiber.net> Greg: Don't know about a page, but this works for me.? Must be usbradio.con (vice simpleusb I think). ; ; CTCSS / PL TONES ; txctcssdefault= 103.5?? ; default tx ctcss freq, any frequency permitted rxctcssfreqs= 67.0,88.5,136.5,192.8,250.3 ??????????????????????? ; rx ctcss freqs in floating point. must be in table ??????????????????????? ; the Nth position in rxctcssfreqs sends Nth position of txctcssfreqs txctcssfreqs= 67.0,88.5,103.5,192.8,250.3 ??????????????????????? ; tx ctcss freqs, any frequency permitted Each listed PL gives the same PL out (like a community repeater) EXCEPT 136.5 RX gives 103.5 TX.? [This exception is all about a multi-receiver/crossband system, see http://KF5VH.com for more details about the repeater.]? The default PL is used when the RX is inactive and an announcement or net audio uses the TX. ...STeve - KF5VH On 8/15/2018 7:42 AM, Greg wrote: > Is there a page with information of how to use allstar to decode and > encode ctcss? I was hoping to do 2 different tones. > Thanks > Greg > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From jcarl.griffith at gmail.com Wed Aug 15 15:42:48 2018 From: jcarl.griffith at gmail.com (John Griffith) Date: Wed, 15 Aug 2018 08:42:48 -0700 Subject: [App_rpt-users] Not working for me yet In-Reply-To: References: <01ec01d433f8$e87d78b0$b9786a10$@gmail.com> <00c301d433fc$24988ee0$6dc9aca0$@gmail.com> Message-ID: <031501d434ae$9f513440$ddf39cc0$@gmail.com> I didn?t see my post from earlier, so here it is again. Thank you all for your help, found out my router was at fault and its configuration needed to be refreshed. John Griffith N7OKN WIN System Affiliate. From: App_rpt-users On Behalf Of Nate Hardman Sent: Tuesday, August 14, 2018 3:02 PM To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] Not working for me yet John, we will need to know the IP address that the node is using. You may email to helpdesk at allstarlink.org if you wish to keep you public IP address from being common knowledge. You can use the DIG command from the command line user at debian9:~ $ dig +short myip.opendns.com @resolver1.opendns.com to resolve the pubic IP the node is using. On Tue, Aug 14, 2018 at 2:25 PM, Angelo T Sonnesso > wrote: It seems that the only node I can connect with is 47288. If I try others I can't connect. Any suggestions? 73 N2DYN Angelo -----Original Message----- From: App_rpt-users > On Behalf Of John Griffith Sent: Tuesday, August 14, 2018 2:02 PM To: 'Users of Asterisk app_rpt' > Subject: [App_rpt-users] Not working for me yet Greetings. Still having a problem registering. Here's my data: Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 29600 60 Request Sent If there's any more information I need to send, I can. John Griffith N7OKN Node 29600 WIN System affiliate _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -- Nathan Hardman nhardman1428 at gmail.com N8THN at ARRL.NET -------------- next part -------------- An HTML attachment was scrubbed... URL: From asonnesso at gmail.com Wed Aug 15 16:33:06 2018 From: asonnesso at gmail.com (Angelo T Sonnesso) Date: Wed, 15 Aug 2018 12:33:06 -0400 Subject: [App_rpt-users] Not working for me yet In-Reply-To: References: <01ec01d433f8$e87d78b0$b9786a10$@gmail.com> <00c301d433fc$24988ee0$6dc9aca0$@gmail.com> Message-ID: <033301d434b5$a577be00$f0673a00$@gmail.com> Well I didn?t notice my typo. The only node I can connect with is 41288. My node is 47931. 73 N2DYN Angelo -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at rainerbertsch.de Wed Aug 15 19:45:49 2018 From: info at rainerbertsch.de (info at rainerbertsch.de) Date: Wed, 15 Aug 2018 21:45:49 +0200 Subject: [App_rpt-users] register.allstarlink.org with ip 44.98.254.145 Message-ID: Hi there, can someone tell me why the server register.allstarlink.org give an answer with the IP 44.98.254.145 ? ping register.allstarlink.org PING register.regsvcs.allstarlink.org (44.98.254.145): 56 data bytes 64 bytes from 44.98.254.145: icmp_seq=0 ttl=51 time=151.827 ms 64 bytes from 44.98.254.145: icmp_seq=1 ttl=51 time=151.208 ms In our systems all ll IP-adresses with ip 44.x.x.x are routed to the HAMNET, never to the Internet. Therefore the system never can reach the registration server. Or is there something wrong in my thoughts ? 73 de Rainer, DF3SY Node 43024 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kd2nfc at gmail.com Wed Aug 15 20:13:03 2018 From: kd2nfc at gmail.com (Joe Puma) Date: Wed, 15 Aug 2018 16:13:03 -0400 Subject: [App_rpt-users] register.allstarlink.org with ip 44.98.254.145 In-Reply-To: References: Message-ID: <7CEC4F23-1D9E-47B7-A033-4FC1C018BCD0@gmail.com> 44/8 is still routable on the internet. I doubt you use all 16 million addresses locally you could just route a Class C 44.x.x.x/24 where you have your local resources so your not routing the whole 44/8 to a internal network. You could also add another hop with a higher metric to check your internet route for 44.0.0.0 hosts that are not in your network. Joe kd2nfc node 46596 > On Aug 15, 2018, at 3:45 PM, info at rainerbertsch.de wrote: > > Hi there, > can someone tell me why the server register.allstarlink.org give an answer with the IP 44.98.254.145 ? > > ping register.allstarlink.org > PING register.regsvcs.allstarlink.org (44.98.254.145): 56 data bytes > 64 bytes from 44.98.254.145: icmp_seq=0 ttl=51 time=151.827 ms > 64 bytes from 44.98.254.145: icmp_seq=1 ttl=51 time=151.208 ms > > In our systems all ll IP-adresses with ip 44.x.x.x are routed to the HAMNET, never to the Internet. > Therefore the system never can reach the registration server. > > Or is there something wrong in my thoughts ? > > 73 de Rainer, DF3SY > > Node 43024 > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tom at tomh.us Wed Aug 15 21:10:48 2018 From: tom at tomh.us (Tom Hayward) Date: Wed, 15 Aug 2018 14:10:48 -0700 Subject: [App_rpt-users] register.allstarlink.org with ip 44.98.254.145 In-Reply-To: References: Message-ID: On Wed, Aug 15, 2018 at 12:46 PM wrote: > Hi there, > can someone tell me why the server register.allstarlink.org give an > answer with the IP 44.98.254.145 ? > 44.98.254.145 is the address of one of the new Allstar registration servers. > In our systems all ll IP-adresses with ip 44.x.x.x are routed to the > HAMNET, never to the Internet. > Therefore the system never can reach the registration server. > 44.x.x.x is much bigger than just HAMNET. That seems like a mistake to configure your network to route the whole /8 to HAMNET. Tom KD7LXL -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bryan at bryanfields.net Wed Aug 15 21:30:33 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Wed, 15 Aug 2018 17:30:33 -0400 Subject: [App_rpt-users] register.allstarlink.org with ip 44.98.254.145 In-Reply-To: References: Message-ID: On 8/15/18 5:10 PM, Tom Hayward wrote: > ? > > In our systems all ll IP-adresses ?with ip 44.x.x.x are routed to the > HAMNET, never to the Internet. > Therefore the system never can reach the registration server. > > > 44.x.x.x is much bigger than just HAMNET. That seems like a mistake to > configure your network to route the whole /8 to HAMNET. Also, stats.allstarlink.org and dns has been on 44/8 for about 1 year now, so it's really important fix the routing on your end. We have some other servers in 44/8 which are announced to the global table from various ASN's. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From k5cg at hamoperator.org Wed Aug 15 21:35:20 2018 From: k5cg at hamoperator.org (Danny K5CG) Date: Wed, 15 Aug 2018 14:35:20 -0700 (PDT) Subject: [App_rpt-users] register.allstarlink.org with ip 44.98.254.145 In-Reply-To: References: Message-ID: <299472649.311235.1534368920246.JavaMail.zimbra@siminiuk.com> Looks like you'll need a much larger routing table :) https://hamnetdb.net/?m=subnet Danny K5CG ----- Original Message ----- From: "Bryan Fields" To: "Users of Asterisk app_rpt" Sent: Wednesday, August 15, 2018 4:30:33 PM Subject: Re: [App_rpt-users] register.allstarlink.org with ip 44.98.254.145 On 8/15/18 5:10 PM, Tom Hayward wrote: > ? > > In our systems all ll IP-adresses ?with ip 44.x.x.x are routed to the > HAMNET, never to the Internet. > Therefore the system never can reach the registration server. > > > 44.x.x.x is much bigger than just HAMNET. That seems like a mistake to > configure your network to route the whole /8 to HAMNET. Also, stats.allstarlink.org and dns has been on 44/8 for about 1 year now, so it's really important fix the routing on your end. We have some other servers in 44/8 which are announced to the global table from various ASN's. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. From tisawyer at gmail.com Wed Aug 15 23:19:31 2018 From: tisawyer at gmail.com (Tim Sawyer) Date: Wed, 15 Aug 2018 13:19:31 -1000 Subject: [App_rpt-users] Still Working on Migration In-Reply-To: References: Message-ID: I've received a couple of requests to up date the status of the new registration system. I'm a bit out of the know as I'm on a long planned vacation. I do know the Allstar team continues working on the new registration system. It appears the NAT issue is fixed. To review -- we attempted to switch the IAX port to the node provided port rather than the port configured in the Allstarlink portal. While that worked for the vast majority of folks, others would have had to reconfigure their network and still fewer could not be fixed period. We learned a thing or two from this process which will only make AllStar better. As Bryan has mentioned we switched the registration system from a single server in LA to three servers across the US. We updated to a later version of Asterisk and the database has been updated to the latest version. The goal is, of course, to eliminate a single point of failure. The old server was on its last legs. Asterisk was rebooting every 10 to 15 minutes. It was running CentOS 5.7. While some were insisting we switch back to the old server, it's end was near. Had that server crashed beyond repair things would have been really unacceptable. Security has also been improved. We've implemented IPSEC, firewalls and probably other security tools I know nothing about. I'm not a security guy so one of our other guys will need to talk to that as appropriate. My understanding is that the few remaining registration problems stem from the new Asterisk software. We are approaching 3000 nodes. It is unheard of in the Asterisk PBX world to have 3000 phones (read nodes) on a single server. It's the main reason our Asterisk was crashing so often. Our developers are working hard to overcome this limitation. We've been told it can't be done. As hams we have accomplished the impossible many times thought our history. I'm hopeful we can advance the art once again. Your continued patience is greatly appreciated. On Mon, Aug 13, 2018 at 9:17 AM Tim Sawyer wrote: > Hey Folks, > > The AllStar developer team knows there are still problems with the new > registration system. The are working on it. The goal continues to be to > make a better AllStar for everyone. Please be patient while they work out > the bugs. > > -- > Tim WD6AWP > -- Tim WD6AWP -------------- next part -------------- An HTML attachment was scrubbed... URL: From loren at lorentedford.com Thu Aug 16 00:02:50 2018 From: loren at lorentedford.com (Loren Tedford) Date: Wed, 15 Aug 2018 19:02:50 -0500 Subject: [App_rpt-users] Registration of '29928, 40875' rejected Message-ID: <5774222e-f06a-73f1-534c-ab14312a2b57@lorentedford.com> Ok so... Some one want to explain this? Really?? [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '40875' rejected: '' from: '44.98.254.145' [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '29925' rejected: '' from: '44.98.254.145' Just curious.. Loren Tedford KC9ZHV From loren at lorentedford.com Thu Aug 16 00:07:50 2018 From: loren at lorentedford.com (Loren Tedford) Date: Wed, 15 Aug 2018 19:07:50 -0500 Subject: [App_rpt-users] Registration of '29928, 40875' rejected In-Reply-To: <5774222e-f06a-73f1-534c-ab14312a2b57@lorentedford.com> References: <5774222e-f06a-73f1-534c-ab14312a2b57@lorentedford.com> Message-ID: <800540c5-929a-905f-dc93-a7df9d8663f1@lorentedford.com> Update might not all be registration issues still struggling with this ra35 that we got getting things working like they were with the uri.. root at repeater:/etc/asterisk# asterisk -r AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd Copyright (C) 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. and others. Created by Mark Spencer Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. This is free software, with components licensed under the GNU General Public License version 2 and other licenses; you are welcome to redistribute it under certain conditions. Type 'core show license' for details. ========================================================================= Connected to Asterisk GIT Version 004b9dd currently running on repeater (pid = 1556) [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 29925 [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 29925 [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 29925 [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 29925 [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 40875 [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 40875 [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 40875 [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 40875 [Aug 15 19:06:23] WARNING[1590]: channel.c:3051 ast_request: No channel type registered for 'Radio' [Aug 15 19:06:23] WARNING[1590]: channel.c:3051 ast_request: No channel type registered for 'Radio' [Aug 15 19:06:23] WARNING[1591]: channel.c:3051 ast_request: No channel type registered for 'Radio' [Aug 15 19:06:23] WARNING[1591]: channel.c:3051 ast_request: No channel type registered for 'Radio' [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 29925 [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 29925 [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 29925 [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 29925 [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 40875 [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 40875 [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 40875 [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 40875 [Aug 15 19:06:25] WARNING[1592]: channel.c:3051 ast_request: No channel type registered for 'Radio' [Aug 15 19:06:25] WARNING[1592]: channel.c:3051 ast_request: No channel type registered for 'Radio' [Aug 15 19:06:25] WARNING[1593]: channel.c:3051 ast_request: No channel type registered for 'Radio' [Aug 15 19:06:25] WARNING[1593]: channel.c:3051 ast_request: No channel type registered for 'Radio' [Aug 15 19:06:27] ERROR[1562]: app_rpt.c:22223 rpt_master: Continual RPT thread restarts, killing Asterisk [Aug 15 19:06:27] ERROR[1562]: app_rpt.c:22223 rpt_master: Continual RPT thread restarts, killing Asterisk repeater*CLI> Disconnected from Asterisk server root at repeater:/etc/asterisk# On 8/15/2018 7:02 PM, Loren Tedford wrote: > Ok so... Some one want to explain this? > > Really?? > > [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '40875' > rejected: '' from: '44.98.254.145' > [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '29925' > rejected: '' from: '44.98.254.145' > > > Just curious.. > > Loren Tedford KC9ZHV > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. From szingman at msgstor.com Thu Aug 16 00:09:30 2018 From: szingman at msgstor.com (Steve Zingman) Date: Wed, 15 Aug 2018 20:09:30 -0400 Subject: [App_rpt-users] Registration of '29928, 40875' rejected In-Reply-To: <800540c5-929a-905f-dc93-a7df9d8663f1@lorentedford.com> References: <5774222e-f06a-73f1-534c-ab14312a2b57@lorentedford.com> <800540c5-929a-905f-dc93-a7df9d8663f1@lorentedford.com> Message-ID: <2832cce2-3ff9-9b2a-2bf5-3bbe1d3d5373@msgstor.com> run Asterisk in the foreground so you see the errors at startup. On 08/15/2018 08:07 PM, Loren Tedford wrote: > Update might not all be registration issues still struggling with this > ra35 that we got getting things working like they were with the uri.. > > > root at repeater:/etc/asterisk# asterisk -r > > AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd > Copyright (C) 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. and > others. > Created by Mark Spencer > Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' > for details. > This is free software, with components licensed under the GNU General > Public > License version 2 and other licenses; you are welcome to redistribute > it under > certain conditions. Type 'core show license' for details. > ========================================================================= > Connected to Asterisk GIT Version 004b9dd currently running on > repeater (pid = 1556) > [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread > restarted on 29925 > [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread > restarted on 29925 > [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: > rpt_thread restarted on node 29925 > [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: > rpt_thread restarted on node 29925 > [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread > restarted on 40875 > [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread > restarted on 40875 > [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: > rpt_thread restarted on node 40875 > [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: > rpt_thread restarted on node 40875 > [Aug 15 19:06:23] WARNING[1590]: channel.c:3051 ast_request: No > channel type registered for 'Radio' > [Aug 15 19:06:23] WARNING[1590]: channel.c:3051 ast_request: No > channel type registered for 'Radio' > [Aug 15 19:06:23] WARNING[1591]: channel.c:3051 ast_request: No > channel type registered for 'Radio' > [Aug 15 19:06:23] WARNING[1591]: channel.c:3051 ast_request: No > channel type registered for 'Radio' > [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread > restarted on 29925 > [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread > restarted on 29925 > [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: > rpt_thread restarted on node 29925 > [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: > rpt_thread restarted on node 29925 > [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread > restarted on 40875 > [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread > restarted on 40875 > [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: > rpt_thread restarted on node 40875 > [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: > rpt_thread restarted on node 40875 > [Aug 15 19:06:25] WARNING[1592]: channel.c:3051 ast_request: No > channel type registered for 'Radio' > [Aug 15 19:06:25] WARNING[1592]: channel.c:3051 ast_request: No > channel type registered for 'Radio' > [Aug 15 19:06:25] WARNING[1593]: channel.c:3051 ast_request: No > channel type registered for 'Radio' > [Aug 15 19:06:25] WARNING[1593]: channel.c:3051 ast_request: No > channel type registered for 'Radio' > [Aug 15 19:06:27] ERROR[1562]: app_rpt.c:22223 rpt_master: Continual > RPT thread restarts, killing Asterisk > [Aug 15 19:06:27] ERROR[1562]: app_rpt.c:22223 rpt_master: Continual > RPT thread restarts, killing Asterisk > repeater*CLI> > Disconnected from Asterisk server > root at repeater:/etc/asterisk# > > > On 8/15/2018 7:02 PM, Loren Tedford wrote: >> Ok so... Some one want to explain this? >> >> Really?? >> >> [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '40875' >> rejected: '' from: '44.98.254.145' >> [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '29925' >> rejected: '' from: '44.98.254.145' >> >> >> Just curious.. >> >> Loren Tedford KC9ZHV >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. From loren at lorentedford.com Thu Aug 16 00:14:22 2018 From: loren at lorentedford.com (Loren Tedford) Date: Wed, 15 Aug 2018 19:14:22 -0500 Subject: [App_rpt-users] Registration of '29928, 40875' rejected In-Reply-To: <2832cce2-3ff9-9b2a-2bf5-3bbe1d3d5373@msgstor.com> References: <5774222e-f06a-73f1-534c-ab14312a2b57@lorentedford.com> <800540c5-929a-905f-dc93-a7df9d8663f1@lorentedford.com> <2832cce2-3ff9-9b2a-2bf5-3bbe1d3d5373@msgstor.com> Message-ID: <12f78ae4-6b4b-ae13-db21-4ee40a46fd47@lorentedford.com> Just to be on the safe side where is that script that i can redo my allstarlink config with the one you guys have premade through allstarlink.. Where is? it kept at it use to be nodesetup but its not working. On 8/15/2018 7:09 PM, Steve Zingman wrote: > run Asterisk in the foreground so you see the errors at startup. > > On 08/15/2018 08:07 PM, Loren Tedford wrote: >> Update might not all be registration issues still struggling with >> this ra35 that we got getting things working like they were with the >> uri.. >> >> >> root at repeater:/etc/asterisk# asterisk -r >> >> AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd >> Copyright (C) 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. >> and others. >> Created by Mark Spencer >> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' >> for details. >> This is free software, with components licensed under the GNU General >> Public >> License version 2 and other licenses; you are welcome to redistribute >> it under >> certain conditions. Type 'core show license' for details. >> ========================================================================= >> >> Connected to Asterisk GIT Version 004b9dd currently running on >> repeater (pid = 1556) >> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >> thread restarted on 29925 >> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >> thread restarted on 29925 >> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: >> rpt_thread restarted on node 29925 >> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: >> rpt_thread restarted on node 29925 >> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >> thread restarted on 40875 >> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >> thread restarted on 40875 >> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: >> rpt_thread restarted on node 40875 >> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: >> rpt_thread restarted on node 40875 >> [Aug 15 19:06:23] WARNING[1590]: channel.c:3051 ast_request: No >> channel type registered for 'Radio' >> [Aug 15 19:06:23] WARNING[1590]: channel.c:3051 ast_request: No >> channel type registered for 'Radio' >> [Aug 15 19:06:23] WARNING[1591]: channel.c:3051 ast_request: No >> channel type registered for 'Radio' >> [Aug 15 19:06:23] WARNING[1591]: channel.c:3051 ast_request: No >> channel type registered for 'Radio' >> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >> thread restarted on 29925 >> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >> thread restarted on 29925 >> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: >> rpt_thread restarted on node 29925 >> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: >> rpt_thread restarted on node 29925 >> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >> thread restarted on 40875 >> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >> thread restarted on 40875 >> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: >> rpt_thread restarted on node 40875 >> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: >> rpt_thread restarted on node 40875 >> [Aug 15 19:06:25] WARNING[1592]: channel.c:3051 ast_request: No >> channel type registered for 'Radio' >> [Aug 15 19:06:25] WARNING[1592]: channel.c:3051 ast_request: No >> channel type registered for 'Radio' >> [Aug 15 19:06:25] WARNING[1593]: channel.c:3051 ast_request: No >> channel type registered for 'Radio' >> [Aug 15 19:06:25] WARNING[1593]: channel.c:3051 ast_request: No >> channel type registered for 'Radio' >> [Aug 15 19:06:27] ERROR[1562]: app_rpt.c:22223 rpt_master: Continual >> RPT thread restarts, killing Asterisk >> [Aug 15 19:06:27] ERROR[1562]: app_rpt.c:22223 rpt_master: Continual >> RPT thread restarts, killing Asterisk >> repeater*CLI> >> Disconnected from Asterisk server >> root at repeater:/etc/asterisk# >> >> >> On 8/15/2018 7:02 PM, Loren Tedford wrote: >>> Ok so... Some one want to explain this? >>> >>> Really?? >>> >>> [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '40875' >>> rejected: '' from: '44.98.254.145' >>> [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '29925' >>> rejected: '' from: '44.98.254.145' >>> >>> >>> Just curious.. >>> >>> Loren Tedford KC9ZHV >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit >>> http://lists.allstarlink.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. >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. From nhardman1428 at gmail.com Thu Aug 16 00:30:47 2018 From: nhardman1428 at gmail.com (nhardman1428 at gmail.com) Date: Wed, 15 Aug 2018 20:30:47 -0400 Subject: [App_rpt-users] Registration of '29928, 40875' rejected In-Reply-To: <12f78ae4-6b4b-ae13-db21-4ee40a46fd47@lorentedford.com> References: <5774222e-f06a-73f1-534c-ab14312a2b57@lorentedford.com> <800540c5-929a-905f-dc93-a7df9d8663f1@lorentedford.com> <2832cce2-3ff9-9b2a-2bf5-3bbe1d3d5373@msgstor.com> <12f78ae4-6b4b-ae13-db21-4ee40a46fd47@lorentedford.com> Message-ID: <965C3D19-E824-4AD5-BD31-C0738B45638E@gmail.com> Access to the node setup script can be called from the asl-menu. All of those scripts are located in /usr/local/sbin Sent from my iPhone > On Aug 15, 2018, at 8:14 PM, Loren Tedford wrote: > > Just to be on the safe side where is that script that i can redo my allstarlink config with the one you guys have premade through allstarlink.. Where is it kept at it use to be nodesetup but its not working. > > >> On 8/15/2018 7:09 PM, Steve Zingman wrote: >> run Asterisk in the foreground so you see the errors at startup. >> >>> On 08/15/2018 08:07 PM, Loren Tedford wrote: >>> Update might not all be registration issues still struggling with this ra35 that we got getting things working like they were with the uri.. >>> >>> >>> root at repeater:/etc/asterisk# asterisk -r >>> >>> AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd >>> Copyright (C) 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. and others. >>> Created by Mark Spencer >>> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. >>> This is free software, with components licensed under the GNU General Public >>> License version 2 and other licenses; you are welcome to redistribute it under >>> certain conditions. Type 'core show license' for details. >>> ========================================================================= >>> Connected to Asterisk GIT Version 004b9dd currently running on repeater (pid = 1556) >>> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 29925 >>> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 29925 >>> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 29925 >>> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 29925 >>> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 40875 >>> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 40875 >>> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 40875 >>> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 40875 >>> [Aug 15 19:06:23] WARNING[1590]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>> [Aug 15 19:06:23] WARNING[1590]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>> [Aug 15 19:06:23] WARNING[1591]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>> [Aug 15 19:06:23] WARNING[1591]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 29925 >>> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 29925 >>> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 29925 >>> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 29925 >>> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 40875 >>> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 40875 >>> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 40875 >>> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 40875 >>> [Aug 15 19:06:25] WARNING[1592]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>> [Aug 15 19:06:25] WARNING[1592]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>> [Aug 15 19:06:25] WARNING[1593]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>> [Aug 15 19:06:25] WARNING[1593]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>> [Aug 15 19:06:27] ERROR[1562]: app_rpt.c:22223 rpt_master: Continual RPT thread restarts, killing Asterisk >>> [Aug 15 19:06:27] ERROR[1562]: app_rpt.c:22223 rpt_master: Continual RPT thread restarts, killing Asterisk >>> repeater*CLI> >>> Disconnected from Asterisk server >>> root at repeater:/etc/asterisk# >>> >>> >>>> On 8/15/2018 7:02 PM, Loren Tedford wrote: >>>> Ok so... Some one want to explain this? >>>> >>>> Really?? >>>> >>>> [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '40875' rejected: '' from: '44.98.254.145' >>>> [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '29925' rejected: '' from: '44.98.254.145' >>>> >>>> >>>> Just curious.. >>>> >>>> Loren Tedford KC9ZHV >>>> >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users at lists.allstarlink.org >>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>>> >>>> To unsubscribe from this list please visit http://lists.allstarlink.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. >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit http://lists.allstarlink.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. >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit http://lists.allstarlink.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. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. From loren at lorentedford.com Thu Aug 16 00:37:23 2018 From: loren at lorentedford.com (Loren Tedford) Date: Wed, 15 Aug 2018 19:37:23 -0500 Subject: [App_rpt-users] Registration of '29928, 40875' rejected In-Reply-To: <965C3D19-E824-4AD5-BD31-C0738B45638E@gmail.com> References: <5774222e-f06a-73f1-534c-ab14312a2b57@lorentedford.com> <800540c5-929a-905f-dc93-a7df9d8663f1@lorentedford.com> <2832cce2-3ff9-9b2a-2bf5-3bbe1d3d5373@msgstor.com> <12f78ae4-6b4b-ae13-db21-4ee40a46fd47@lorentedford.com> <965C3D19-E824-4AD5-BD31-C0738B45638E@gmail.com> Message-ID: <8efe0aff-47e9-bfea-ca22-7efe6283f7d4@lorentedford.com> Wow the new menu looks amazing i still don't see where i can enter my callsign and pasdword to download like the old days but this menu is good I will continue to look around since the menu's provided didn't have the option i was looking for. On 8/15/2018 7:30 PM, nhardman1428 at gmail.com wrote: > Access to the node setup script can be called from the asl-menu. All of those scripts are located in /usr/local/sbin > > Sent from my iPhone > >> On Aug 15, 2018, at 8:14 PM, Loren Tedford wrote: >> >> Just to be on the safe side where is that script that i can redo my allstarlink config with the one you guys have premade through allstarlink.. Where is it kept at it use to be nodesetup but its not working. >> >> >>> On 8/15/2018 7:09 PM, Steve Zingman wrote: >>> run Asterisk in the foreground so you see the errors at startup. >>> >>>> On 08/15/2018 08:07 PM, Loren Tedford wrote: >>>> Update might not all be registration issues still struggling with this ra35 that we got getting things working like they were with the uri.. >>>> >>>> >>>> root at repeater:/etc/asterisk# asterisk -r >>>> >>>> AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd >>>> Copyright (C) 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. and others. >>>> Created by Mark Spencer >>>> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. >>>> This is free software, with components licensed under the GNU General Public >>>> License version 2 and other licenses; you are welcome to redistribute it under >>>> certain conditions. Type 'core show license' for details. >>>> ========================================================================= >>>> Connected to Asterisk GIT Version 004b9dd currently running on repeater (pid = 1556) >>>> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 29925 >>>> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 29925 >>>> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 29925 >>>> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 29925 >>>> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 40875 >>>> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 40875 >>>> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 40875 >>>> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 40875 >>>> [Aug 15 19:06:23] WARNING[1590]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>>> [Aug 15 19:06:23] WARNING[1590]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>>> [Aug 15 19:06:23] WARNING[1591]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>>> [Aug 15 19:06:23] WARNING[1591]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>>> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 29925 >>>> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 29925 >>>> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 29925 >>>> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 29925 >>>> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 40875 >>>> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT thread restarted on 40875 >>>> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 40875 >>>> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: rpt_thread restarted on node 40875 >>>> [Aug 15 19:06:25] WARNING[1592]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>>> [Aug 15 19:06:25] WARNING[1592]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>>> [Aug 15 19:06:25] WARNING[1593]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>>> [Aug 15 19:06:25] WARNING[1593]: channel.c:3051 ast_request: No channel type registered for 'Radio' >>>> [Aug 15 19:06:27] ERROR[1562]: app_rpt.c:22223 rpt_master: Continual RPT thread restarts, killing Asterisk >>>> [Aug 15 19:06:27] ERROR[1562]: app_rpt.c:22223 rpt_master: Continual RPT thread restarts, killing Asterisk >>>> repeater*CLI> >>>> Disconnected from Asterisk server >>>> root at repeater:/etc/asterisk# >>>> >>>> >>>>> On 8/15/2018 7:02 PM, Loren Tedford wrote: >>>>> Ok so... Some one want to explain this? >>>>> >>>>> Really?? >>>>> >>>>> [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '40875' rejected: '' from: '44.98.254.145' >>>>> [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '29925' rejected: '' from: '44.98.254.145' >>>>> >>>>> >>>>> Just curious.. >>>>> >>>>> Loren Tedford KC9ZHV >>>>> >>>>> _______________________________________________ >>>>> App_rpt-users mailing list >>>>> App_rpt-users at lists.allstarlink.org >>>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>>>> >>>>> To unsubscribe from this list please visit http://lists.allstarlink.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. >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users at lists.allstarlink.org >>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>>> >>>> To unsubscribe from this list please visit http://lists.allstarlink.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. >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit http://lists.allstarlink.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. >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit http://lists.allstarlink.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. > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. From loren at lorentedford.com Thu Aug 16 00:48:44 2018 From: loren at lorentedford.com (Loren Tedford) Date: Wed, 15 Aug 2018 19:48:44 -0500 Subject: [App_rpt-users] Registration of '29928, 40875' rejected In-Reply-To: <8efe0aff-47e9-bfea-ca22-7efe6283f7d4@lorentedford.com> References: <5774222e-f06a-73f1-534c-ab14312a2b57@lorentedford.com> <800540c5-929a-905f-dc93-a7df9d8663f1@lorentedford.com> <2832cce2-3ff9-9b2a-2bf5-3bbe1d3d5373@msgstor.com> <12f78ae4-6b4b-ae13-db21-4ee40a46fd47@lorentedford.com> <965C3D19-E824-4AD5-BD31-C0738B45638E@gmail.com> <8efe0aff-47e9-bfea-ca22-7efe6283f7d4@lorentedford.com> Message-ID: <867cced8-7ad2-e9fa-3c4e-dd07bb814b7a@lorentedford.com> Also I noticed that for some reason allstarlink doesn't download the website configuration script from the site anymore at least for the last half hour it hasn't worked yet. On 8/15/2018 7:37 PM, Loren Tedford wrote: > Wow the new menu looks amazing i still don't see where i can enter my > callsign and pasdword to download like the old days but this menu is > good I will continue to look around since the menu's provided didn't > have the option i was looking for. > > > On 8/15/2018 7:30 PM, nhardman1428 at gmail.com wrote: >> Access to the node setup script can be called from the asl-menu.? All >> of those scripts are located in /usr/local/sbin >> >> Sent from my iPhone >> >>> On Aug 15, 2018, at 8:14 PM, Loren Tedford >>> wrote: >>> >>> Just to be on the safe side where is that script that i can redo my >>> allstarlink config with the one you guys have premade through >>> allstarlink.. Where is? it kept at it use to be nodesetup but its >>> not working. >>> >>> >>>> On 8/15/2018 7:09 PM, Steve Zingman wrote: >>>> run Asterisk in the foreground so you see the errors at startup. >>>> >>>>> On 08/15/2018 08:07 PM, Loren Tedford wrote: >>>>> Update might not all be registration issues still struggling with >>>>> this ra35 that we got getting things working like they were with >>>>> the uri.. >>>>> >>>>> >>>>> root at repeater:/etc/asterisk# asterisk -r >>>>> >>>>> AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd >>>>> Copyright (C) 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. >>>>> and others. >>>>> Created by Mark Spencer >>>>> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show >>>>> warranty' for details. >>>>> This is free software, with components licensed under the GNU >>>>> General Public >>>>> License version 2 and other licenses; you are welcome to >>>>> redistribute it under >>>>> certain conditions. Type 'core show license' for details. >>>>> ========================================================================= >>>>> >>>>> Connected to Asterisk GIT Version 004b9dd currently running on >>>>> repeater (pid = 1556) >>>>> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >>>>> thread restarted on 29925 >>>>> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >>>>> thread restarted on 29925 >>>>> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: >>>>> rpt_thread restarted on node 29925 >>>>> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: >>>>> rpt_thread restarted on node 29925 >>>>> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >>>>> thread restarted on 40875 >>>>> [Aug 15 19:06:23] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >>>>> thread restarted on 40875 >>>>> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: >>>>> rpt_thread restarted on node 40875 >>>>> [Aug 15 19:06:23] WARNING[1562]: app_rpt.c:22240 rpt_master: >>>>> rpt_thread restarted on node 40875 >>>>> [Aug 15 19:06:23] WARNING[1590]: channel.c:3051 ast_request: No >>>>> channel type registered for 'Radio' >>>>> [Aug 15 19:06:23] WARNING[1590]: channel.c:3051 ast_request: No >>>>> channel type registered for 'Radio' >>>>> [Aug 15 19:06:23] WARNING[1591]: channel.c:3051 ast_request: No >>>>> channel type registered for 'Radio' >>>>> [Aug 15 19:06:23] WARNING[1591]: channel.c:3051 ast_request: No >>>>> channel type registered for 'Radio' >>>>> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >>>>> thread restarted on 29925 >>>>> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >>>>> thread restarted on 29925 >>>>> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: >>>>> rpt_thread restarted on node 29925 >>>>> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: >>>>> rpt_thread restarted on node 29925 >>>>> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >>>>> thread restarted on 40875 >>>>> [Aug 15 19:06:25] NOTICE[1562]: app_rpt.c:22228 rpt_master: RPT >>>>> thread restarted on 40875 >>>>> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: >>>>> rpt_thread restarted on node 40875 >>>>> [Aug 15 19:06:25] WARNING[1562]: app_rpt.c:22240 rpt_master: >>>>> rpt_thread restarted on node 40875 >>>>> [Aug 15 19:06:25] WARNING[1592]: channel.c:3051 ast_request: No >>>>> channel type registered for 'Radio' >>>>> [Aug 15 19:06:25] WARNING[1592]: channel.c:3051 ast_request: No >>>>> channel type registered for 'Radio' >>>>> [Aug 15 19:06:25] WARNING[1593]: channel.c:3051 ast_request: No >>>>> channel type registered for 'Radio' >>>>> [Aug 15 19:06:25] WARNING[1593]: channel.c:3051 ast_request: No >>>>> channel type registered for 'Radio' >>>>> [Aug 15 19:06:27] ERROR[1562]: app_rpt.c:22223 rpt_master: >>>>> Continual RPT thread restarts, killing Asterisk >>>>> [Aug 15 19:06:27] ERROR[1562]: app_rpt.c:22223 rpt_master: >>>>> Continual RPT thread restarts, killing Asterisk >>>>> repeater*CLI> >>>>> Disconnected from Asterisk server >>>>> root at repeater:/etc/asterisk# >>>>> >>>>> >>>>>> On 8/15/2018 7:02 PM, Loren Tedford wrote: >>>>>> Ok so... Some one want to explain this? >>>>>> >>>>>> Really?? >>>>>> >>>>>> [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of >>>>>> '40875' rejected: '' from: '44.98.254.145' >>>>>> [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of >>>>>> '29925' rejected: '' from: '44.98.254.145' >>>>>> >>>>>> >>>>>> Just curious.. >>>>>> >>>>>> Loren Tedford KC9ZHV >>>>>> >>>>>> _______________________________________________ >>>>>> App_rpt-users mailing list >>>>>> App_rpt-users at lists.allstarlink.org >>>>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>>>>> >>>>>> To unsubscribe from this list please visit >>>>>> http://lists.allstarlink.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. >>>>> _______________________________________________ >>>>> App_rpt-users mailing list >>>>> App_rpt-users at lists.allstarlink.org >>>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>>>> >>>>> To unsubscribe from this list please visit >>>>> http://lists.allstarlink.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. >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users at lists.allstarlink.org >>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>>> >>>> To unsubscribe from this list please visit >>>> http://lists.allstarlink.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. >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit >>> http://lists.allstarlink.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. >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. From kd2nfc at gmail.com Thu Aug 16 01:32:57 2018 From: kd2nfc at gmail.com (Joe Puma) Date: Wed, 15 Aug 2018 21:32:57 -0400 Subject: [App_rpt-users] register.allstarlink.org with ip 44.98.254.145 In-Reply-To: <299472649.311235.1534368920246.JavaMail.zimbra@siminiuk.com> References: <299472649.311235.1534368920246.JavaMail.zimbra@siminiuk.com> Message-ID: I don?t get using the 44/8 space on a local natted network if thats what the OP is doing. was he assigned a 44 subnet? because if you use an IP in that space you don?t know if that IP is used on the internet. I?m wondering if he?s using 44.0.0.0 (255.0.0.0) in his network config and each machine 44.0.0.2, 3, 4? which is okay because I don?t see any pings in that space however 44.0.0.1 directs you to https://www.ampr.org/ . If you want to stay in the 44 IP space locally you can use something like 44.1.1.0/24 and you?ll have IP address range 44.1.1.1 - 254 with a subnet mask of 255.255.255.0 ?. If this is how you configure your router and assign IP?s to hosts on your network and its a natted local network then any traffic to this network will stay local and anything outside of 44.1.1.0/24 in the 44. IP space will go over the internet. Danny thats a cool link, how are subnets registered to this database, is this an official record of routable subnet assignment for hamnet? Joe kd2nfc > On Aug 15, 2018, at 5:35 PM, Danny K5CG wrote: > > Looks like you'll need a much larger routing table :) > > https://hamnetdb.net/?m=subnet > > Danny > K5CG > > ----- Original Message ----- > From: "Bryan Fields" > To: "Users of Asterisk app_rpt" > Sent: Wednesday, August 15, 2018 4:30:33 PM > Subject: Re: [App_rpt-users] register.allstarlink.org with ip 44.98.254.145 > > On 8/15/18 5:10 PM, Tom Hayward wrote: >> >> >> In our systems all ll IP-adresses with ip 44.x.x.x are routed to the >> HAMNET, never to the Internet. >> Therefore the system never can reach the registration server. >> >> >> 44.x.x.x is much bigger than just HAMNET. That seems like a mistake to >> configure your network to route the whole /8 to HAMNET. > > Also, stats.allstarlink.org and dns has been on 44/8 for about 1 year now, so > it's really important fix the routing on your end. We have some other servers > in 44/8 which are announced to the global table from various ASN's. > > -- > Bryan Fields > > 727-409-1194 - Voice > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From n3ssl at yahoo.com Thu Aug 16 14:36:11 2018 From: n3ssl at yahoo.com (Ryan Gross) Date: Thu, 16 Aug 2018 14:36:11 +0000 (UTC) Subject: [App_rpt-users] Node 27671 not registering References: <527056745.422071.1534430171378.ref@mail.yahoo.com> Message-ID: <527056745.422071.1534430171378@mail.yahoo.com> All: Up until about 3 weeks ago node 27671 was showing on stats.allstarlink.org site. the only error I am getting is Gps.conf is not pushing APRS out. Checked dnsmgr and is set correctly and nothing when checking iax2 registry. Can log in and confirmed ports ect. Ryan n3ssl From tgundo2003 at yahoo.com Thu Aug 16 21:09:36 2018 From: tgundo2003 at yahoo.com (TGundo 2003) Date: Thu, 16 Aug 2018 21:09:36 +0000 (UTC) Subject: [App_rpt-users] SSH Access References: <896372123.8698116.1534453776356.ref@mail.yahoo.com> Message-ID: <896372123.8698116.1534453776356@mail.yahoo.com> Hi all- I'm in the last lap of getting my first node online, still have a lot of learning to do. My setup consists of an S-Com 7330 that has repeaters on the first two ports and the Asterisk Pi on the third port for linking to a neighboring system. A few items I need some direction on: 1. SSH access. I can putty into the Pi and get to the login and password screen, but it rejects my username and password that I use to log into the machine on the local interface. Do I need to setup a different user account for SSH access? anyone with a good web link on how to accomplish this? 2.? CTCSS Invert. I am using USBRADIO for the driver. On the interface from the Repeater Builder USB-RIM Lite 7330 module it is lighting up my CTCSS light with no activity like its inverted. I can jumper the 7330 internally to invert it and make it go out, but not thru the driver. I changed CTCSS to USBINVERT but it didn't solve it. COS is working properly. What else should I be checking? Maybe a cabling issue? I used an off the shelf DB9 cable to connect the RIM to the 7330. 3. Are there any ports I need to open up on my router? I've looked far and wide and cannot seem to find this info. When the machine is fired up I see it is listed online on the website. Thank you all for the help! Tom W9SRV From mm at midnighteng.com Thu Aug 16 21:19:12 2018 From: mm at midnighteng.com (Mike) Date: Thu, 16 Aug 2018 17:19:12 -0400 Subject: [App_rpt-users] SSH Access In-Reply-To: <896372123.8698116.1534453776356@mail.yahoo.com> References: <896372123.8698116.1534453776356.ref@mail.yahoo.com> <896372123.8698116.1534453776356@mail.yahoo.com> Message-ID: Ssh Edit etc/ssh/sshd_config Enable web access = yes Save Restart ssh You should change the port number while u r at it Sorry t b brief Mobile Mike / Sent While Mobile > On Aug 16, 2018, at 5:09 PM, TGundo 2003 wrote: > > Hi all- > > I'm in the last lap of getting my first node online, still have a lot of learning to do. My setup consists of an S-Com 7330 that has repeaters on the first two ports and the Asterisk Pi on the third port for linking to a neighboring system. > > A few items I need some direction on: > > 1. SSH access. I can putty into the Pi and get to the login and password screen, but it rejects my username and password that I use to log into the machine on the local interface. Do I need to setup a different user account for SSH access? anyone with a good web link on how to accomplish this? > > 2. CTCSS Invert. I am using USBRADIO for the driver. On the interface from the Repeater Builder USB-RIM Lite 7330 module it is lighting up my CTCSS light with no activity like its inverted. I can jumper the 7330 internally to invert it and make it go out, but not thru the driver. I changed CTCSS to USBINVERT but it didn't solve it. COS is working properly. What else should I be checking? Maybe a cabling issue? I used an off the shelf DB9 cable to connect the RIM to the 7330. > > 3. Are there any ports I need to open up on my router? I've looked far and wide and cannot seem to find this info. When the machine is fired up I see it is listed online on the website. > > > Thank you all for the help! > Tom > W9SRV > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. From nessenj at jimsoffice.org Thu Aug 16 22:29:24 2018 From: nessenj at jimsoffice.org (Jim Nessen) Date: Thu, 16 Aug 2018 22:29:24 +0000 Subject: [App_rpt-users] SSH Access In-Reply-To: <896372123.8698116.1534453776356@mail.yahoo.com> References: <896372123.8698116.1534453776356.ref@mail.yahoo.com>, <896372123.8698116.1534453776356@mail.yahoo.com> Message-ID: 1. What username are you using to log into the local interface? If it's root, then chances are it may be blocked from logging in via ssh. Depending on what distribution you are using, the username may be 'pi'. Again, it depends on what distro you are using. 2. So, the CTCSS in the radio driver tells the node what signaling it should expect on the CTCSS pin from the radio, usb means that it when it senses the signal go active high, the radio has a valid PL, usbinvert is the flip of that and active low. That setting does not control what the node sends to the radio. If you don't plan on using that pin, it may be safe just to disconnect it (again, it depends on if you plan on using it). 3. Take a look at what you have set for bindport in /etc/asterisk/iax.conf. That port is what you need to open to allow people to connect in to your node (this is a udp port). If you want to allow remote access via ssh, you will also need to open tcp/22 or tcp/222 (again, depending on what distro you are using). Hope that helps! Jim, K6JWN ________________________________ From: App_rpt-users on behalf of TGundo 2003 Sent: Thursday, August 16, 2018 2:09 PM To: app_rpt-users at lists.allstarlink.org Subject: [App_rpt-users] SSH Access Hi all- I'm in the last lap of getting my first node online, still have a lot of learning to do. My setup consists of an S-Com 7330 that has repeaters on the first two ports and the Asterisk Pi on the third port for linking to a neighboring system. A few items I need some direction on: 1. SSH access. I can putty into the Pi and get to the login and password screen, but it rejects my username and password that I use to log into the machine on the local interface. Do I need to setup a different user account for SSH access? anyone with a good web link on how to accomplish this? 2. CTCSS Invert. I am using USBRADIO for the driver. On the interface from the Repeater Builder USB-RIM Lite 7330 module it is lighting up my CTCSS light with no activity like its inverted. I can jumper the 7330 internally to invert it and make it go out, but not thru the driver. I changed CTCSS to USBINVERT but it didn't solve it. COS is working properly. What else should I be checking? Maybe a cabling issue? I used an off the shelf DB9 cable to connect the RIM to the 7330. 3. Are there any ports I need to open up on my router? I've looked far and wide and cannot seem to find this info. When the machine is fired up I see it is listed online on the website. Thank you all for the help! Tom W9SRV _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users App_rpt-users Info Page - lists.allstarlink.org lists.allstarlink.org Your email address: Your name (optional): You may enter a privacy password below. This provides only mild security, but should prevent others from messing with your subscription. To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tgundo2003 at yahoo.com Fri Aug 17 01:24:02 2018 From: tgundo2003 at yahoo.com (TGundo 2003) Date: Fri, 17 Aug 2018 01:24:02 +0000 (UTC) Subject: [App_rpt-users] SSH Access In-Reply-To: References: <896372123.8698116.1534453776356.ref@mail.yahoo.com> <896372123.8698116.1534453776356@mail.yahoo.com> Message-ID: <281201230.8848359.1534469042843@mail.yahoo.com> Hi Mike- I went in, changed my port. However, I don't see Enable web access anywhere. Could it be called something else? ThanksTom On Thursday, August 16, 2018, 4:19:30 PM CDT, Mike wrote: Ssh Edit etc/ssh/sshd_config Enable web access = yes Save Restart ssh You should change the port number while u r at it Sorry t b brief Mobile Mike / Sent While Mobile > On Aug 16, 2018, at 5:09 PM, TGundo 2003 wrote: > > Hi all- > > I'm in the last lap of getting my first node online, still have a lot of learning to do. My setup consists of an S-Com 7330 that has repeaters on the first two ports and the Asterisk Pi on the third port for linking to a neighboring system. > > A few items I need some direction on: > > 1. SSH access. I can putty into the Pi and get to the login and password screen, but it rejects my username and password that I use to log into the machine on the local interface. Do I need to setup a different user account for SSH access? anyone with a good web link on how to accomplish this? > > 2.? CTCSS Invert. I am using USBRADIO for the driver. On the interface from the Repeater Builder USB-RIM Lite 7330 module it is lighting up my CTCSS light with no activity like its inverted. I can jumper the 7330 internally to invert it and make it go out, but not thru the driver. I changed CTCSS to USBINVERT but it didn't solve it. COS is working properly. What else should I be checking? Maybe a cabling issue? I used an off the shelf DB9 cable to connect the RIM to the 7330. > > 3. Are there any ports I need to open up on my router? I've looked far and wide and cannot seem to find this info. When the machine is fired up I see it is listed online on the website. > > > Thank you all for the help! > Tom > W9SRV > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tgundo2003 at yahoo.com Fri Aug 17 01:26:48 2018 From: tgundo2003 at yahoo.com (TGundo 2003) Date: Fri, 17 Aug 2018 01:26:48 +0000 (UTC) Subject: [App_rpt-users] SSH Access In-Reply-To: References: <896372123.8698116.1534453776356.ref@mail.yahoo.com> <896372123.8698116.1534453776356@mail.yahoo.com> Message-ID: <1050468582.8797468.1534469208130@mail.yahoo.com> Hi Jim- 1. Yes, it is root. Should I change that or create another user? 2. Ok on CTCSS. I really will not be using it, I might just leave it the way it is, gives me a visual indicator the RIM is on and loaded. 3. Checking IAX now. I'm just trying to SSH in locally at this point on the same network though. Thanks!Tom On Thursday, August 16, 2018, 5:29:41 PM CDT, Jim Nessen wrote: - ?What username are you using to log into the local interface?? If it's root, then chances are it may be blocked from logging in via ssh.? Depending on what distribution you are using, the username may be 'pi'.? Again, it depends on what distro you are using. - So, the CTCSS in the radio driver tells the node what signaling it should expect on the CTCSS pin from the radio, usb means that it when it senses the signal go active high, the radio has a valid PL, usbinvert is the flip of that and active low.? That setting does not control what the node sends to the radio.? If you don't plan on using that pin, it may be safe just to disconnect it (again, it depends on if you plan on using it). - Take a look at what you have set for bindport in /etc/asterisk/iax.conf.? That port is what you need to open to allow people to connect in to your node (this is a udp port).? If you want to allow remote access via ssh, you will also need to open tcp/22 or tcp/222 (again, depending on what distro you are using). Hope that helps! Jim, K6JWN From: App_rpt-users on behalf of TGundo 2003 Sent: Thursday, August 16, 2018 2:09 PM To: app_rpt-users at lists.allstarlink.org Subject: [App_rpt-users] SSH Access?Hi all- I'm in the last lap of getting my first node online, still have a lot of learning to do. My setup consists of an S-Com 7330 that has repeaters on the first two ports and the Asterisk Pi on the third port for linking to a neighboring system. A few items I need some direction on: 1. SSH access. I can putty into the Pi and get to the login and password screen, but it rejects my username and password that I use to log into the machine on the local interface. Do I need to setup a different user account for SSH access? anyone with a good web link on how to accomplish this? 2.? CTCSS Invert. I am using USBRADIO for the driver. On the interface from the Repeater Builder USB-RIM Lite 7330 module it is lighting up my CTCSS light with no activity like its inverted. I can jumper the 7330 internally to invert it and make it go out, but not thru the driver. I changed CTCSS to USBINVERT but it didn't solve it. COS is working properly. What else should I be checking? Maybe a cabling issue? I used an off the shelf DB9 cable to connect the RIM to the 7330. 3. Are there any ports I need to open up on my router? I've looked far and wide and cannot seem to find this info. When the machine is fired up I see it is listed online on the website. Thank you all for the help! Tom W9SRV _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users | App_rpt-users Info Page - lists.allstarlink.orglists.allstarlink.orgYour email address: Your name (optional): You may enter a privacy password below. This provides only mild security, but should prevent others from messing with your subscription. | To unsubscribe from this list please visit http://lists.allstarlink.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. _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at midnighteng.com Fri Aug 17 01:38:51 2018 From: mm at midnighteng.com (Mike) Date: Thu, 16 Aug 2018 21:38:51 -0400 Subject: [App_rpt-users] SSH Access In-Reply-To: <281201230.8848359.1534469042843@mail.yahoo.com> References: <896372123.8698116.1534453776356.ref@mail.yahoo.com> <896372123.8698116.1534453776356@mail.yahoo.com> <281201230.8848359.1534469042843@mail.yahoo.com> Message-ID: Well, sorry, that's my poor memory getting the best of me again... confusing it with something else ! PermitRootLogin yes That should do it, but it may be commented out and say something other than yes/no by default. ...mike/kb8jnm On 8/16/2018 9:24 PM, TGundo 2003 wrote: > Hi Mike- > I went in, changed my port. However, I don't see Enable web access anywhere. Could it be called something else? > ThanksTom > On Thursday, August 16, 2018, 4:19:30 PM CDT, Mike wrote: > > Ssh > Edit etc/ssh/sshd_config > Enable web access = yes > > Save > Restart ssh > > You should change the port number while u r at it > > Sorry t b brief > Mobile > > Mike / Sent While Mobile > >> On Aug 16, 2018, at 5:09 PM, TGundo 2003 wrote: >> >> Hi all- >> >> I'm in the last lap of getting my first node online, still have a lot of learning to do. My setup consists of an S-Com 7330 that has repeaters on the first two ports and the Asterisk Pi on the third port for linking to a neighboring system. >> >> A few items I need some direction on: >> >> 1. SSH access. I can putty into the Pi and get to the login and password screen, but it rejects my username and password that I use to log into the machine on the local interface. Do I need to setup a different user account for SSH access? anyone with a good web link on how to accomplish this? >> >> 2.? CTCSS Invert. I am using USBRADIO for the driver. On the interface from the Repeater Builder USB-RIM Lite 7330 module it is lighting up my CTCSS light with no activity like its inverted. I can jumper the 7330 internally to invert it and make it go out, but not thru the driver. I changed CTCSS to USBINVERT but it didn't solve it. COS is working properly. What else should I be checking? Maybe a cabling issue? I used an off the shelf DB9 cable to connect the RIM to the 7330. >> >> 3. Are there any ports I need to open up on my router? I've looked far and wide and cannot seem to find this info. When the machine is fired up I see it is listed online on the website. >> >> >> Thank you all for the help! >> Tom >> W9SRV >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit http://lists.allstarlink.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. > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > From tgundo2003 at yahoo.com Fri Aug 17 03:24:43 2018 From: tgundo2003 at yahoo.com (TGundo 2003) Date: Fri, 17 Aug 2018 03:24:43 +0000 (UTC) Subject: [App_rpt-users] SSH Access In-Reply-To: References: <896372123.8698116.1534453776356.ref@mail.yahoo.com> <896372123.8698116.1534453776356@mail.yahoo.com> <281201230.8848359.1534469042843@mail.yahoo.com> Message-ID: <1026200523.8143037.1534476283514@mail.yahoo.com> Ok, I found that and edited. Wrote it out, rebooted, and it doesn't seem to take affect, I went back in and my changes are there, both that and the new port, but its still listening on port 22. Is there somewhere I have to change which SSH config to load? Thanks again Tom On Thursday, August 16, 2018, 8:39:04 PM CDT, Mike wrote: Well, sorry,? that's my poor memory getting the best of me again... confusing it with something else ! PermitRootLogin yes That should do it, but it may be commented out and say something other than yes/no by default. ...mike/kb8jnm On 8/16/2018 9:24 PM, TGundo 2003 wrote: >? Hi Mike- > I went in, changed my port. However, I don't see Enable web access anywhere. Could it be called something else? > ThanksTom >? ? ? On Thursday, August 16, 2018, 4:19:30 PM CDT, Mike wrote: >? >? Ssh > Edit etc/ssh/sshd_config > Enable web access = yes > > Save > Restart ssh > > You should change the port number while u r at it > > Sorry t b brief > Mobile > > Mike / Sent While Mobile > >> On Aug 16, 2018, at 5:09 PM, TGundo 2003 wrote: >> >> Hi all- >> >> I'm in the last lap of getting my first node online, still have a lot of learning to do. My setup consists of an S-Com 7330 that has repeaters on the first two ports and the Asterisk Pi on the third port for linking to a neighboring system. >> >> A few items I need some direction on: >> >> 1. SSH access. I can putty into the Pi and get to the login and password screen, but it rejects my username and password that I use to log into the machine on the local interface. Do I need to setup a different user account for SSH access? anyone with a good web link on how to accomplish this? >> >> 2.? CTCSS Invert. I am using USBRADIO for the driver. On the interface from the Repeater Builder USB-RIM Lite 7330 module it is lighting up my CTCSS light with no activity like its inverted. I can jumper the 7330 internally to invert it and make it go out, but not thru the driver. I changed CTCSS to USBINVERT but it didn't solve it. COS is working properly. What else should I be checking? Maybe a cabling issue? I used an off the shelf DB9 cable to connect the RIM to the 7330. >> >> 3. Are there any ports I need to open up on my router? I've looked far and wide and cannot seem to find this info. When the machine is fired up I see it is listed online on the website. >> >> >> Thank you all for the help! >> Tom >> W9SRV >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit http://lists.allstarlink.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. > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. >? ? > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lengriff at optimum.net Fri Aug 17 12:09:50 2018 From: lengriff at optimum.net (lengriff at optimum.net) Date: Fri, 17 Aug 2018 08:09:50 -0400 (Eastern Daylight Time) Subject: [App_rpt-users] Registration refused Message-ID: <5B76BB0D.00000D.10772@LEAPER-PC> On both my local system and our club systems, registration is refused from server 44.98.254.145. The others servers are OK, and the nodes list shows us all active. Any reason for the refusal? Message log shows: [Aug 16 10:20:06] NOTICE[457] Chan_iax2.c: Registration of '42690' rejected: '' from: '44.98.254.145' [Aug 16 13:20:08] NOTICE[452] Chan_iax2.c: Registration of '42690' rejected: '' from: '44.98.254.145' [Aug 16 21:28:20] NOTICE[461] chan_iax2.c: Registration of '42690' rejected: 'Registration Refused' from: '44.98.254.145' Len WB2HKK ? From mm at midnighteng.com Fri Aug 17 12:10:43 2018 From: mm at midnighteng.com (Mike) Date: Fri, 17 Aug 2018 08:10:43 -0400 Subject: [App_rpt-users] SSH Access In-Reply-To: <1026200523.8143037.1534476283514@mail.yahoo.com> References: <896372123.8698116.1534453776356.ref@mail.yahoo.com> <896372123.8698116.1534453776356@mail.yahoo.com> <281201230.8848359.1534469042843@mail.yahoo.com> <1026200523.8143037.1534476283514@mail.yahoo.com> Message-ID: <05d37c29-79f2-177b-f9be-5787a0540928@midnighteng.com> Have you set ROOT password ? Edit the file as root from console Restart the ssh service ...mike/kb8jnm On 8/16/2018 11:24 PM, TGundo 2003 wrote: > Ok, I found that and edited. Wrote it out, rebooted, and it doesn't seem to take affect, I went back in and my changes are there, both that and the new port, but its still listening on port 22. Is there somewhere I have to change which SSH config to load? > Thanks again > Tom > On Thursday, August 16, 2018, 8:39:04 PM CDT, Mike wrote: > > Well, sorry,? that's my poor memory getting the best of me again... > confusing it with something else ! > > PermitRootLogin yes > > That should do it, but it may be commented out and say something other > than yes/no by default. > > ...mike/kb8jnm > > On 8/16/2018 9:24 PM, TGundo 2003 wrote: >> ? Hi Mike- >> I went in, changed my port. However, I don't see Enable web access anywhere. Could it be called something else? >> ThanksTom >> ? ? ? On Thursday, August 16, 2018, 4:19:30 PM CDT, Mike wrote: >> >> ? Ssh >> Edit etc/ssh/sshd_config >> Enable web access = yes >> >> Save >> Restart ssh >> >> You should change the port number while u r at it >> >> Sorry t b brief >> Mobile >> >> Mike / Sent While Mobile >> >>> On Aug 16, 2018, at 5:09 PM, TGundo 2003 wrote: >>> >>> Hi all- >>> >>> I'm in the last lap of getting my first node online, still have a lot of learning to do. My setup consists of an S-Com 7330 that has repeaters on the first two ports and the Asterisk Pi on the third port for linking to a neighboring system. >>> >>> A few items I need some direction on: >>> >>> 1. SSH access. I can putty into the Pi and get to the login and password screen, but it rejects my username and password that I use to log into the machine on the local interface. Do I need to setup a different user account for SSH access? anyone with a good web link on how to accomplish this? >>> >>> 2.? CTCSS Invert. I am using USBRADIO for the driver. On the interface from the Repeater Builder USB-RIM Lite 7330 module it is lighting up my CTCSS light with no activity like its inverted. I can jumper the 7330 internally to invert it and make it go out, but not thru the driver. I changed CTCSS to USBINVERT but it didn't solve it. COS is working properly. What else should I be checking? Maybe a cabling issue? I used an off the shelf DB9 cable to connect the RIM to the 7330. >>> >>> 3. Are there any ports I need to open up on my router? I've looked far and wide and cannot seem to find this info. When the machine is fired up I see it is listed online on the website. >>> >>> >>> Thank you all for the help! >>> Tom >>> W9SRV >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit http://lists.allstarlink.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. >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit http://lists.allstarlink.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. >> >> >> >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit http://lists.allstarlink.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. >> > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > From Bryan at bryanfields.net Fri Aug 17 12:21:27 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Fri, 17 Aug 2018 08:21:27 -0400 Subject: [App_rpt-users] Registration refused In-Reply-To: <5B76BB0D.00000D.10772@LEAPER-PC> References: <5B76BB0D.00000D.10772@LEAPER-PC> Message-ID: <862116e4-7458-c2a9-25c9-ac204be6f485@bryanfields.net> On 8/17/18 8:09 AM, lengriff at optimum.net wrote: > On both my local system and our club systems, registration is refused from > server 44.98.254.145. > The others servers are OK, and the nodes list shows us all active. Any > reason for the refusal? > Message log shows: > [Aug 16 10:20:06] NOTICE[457] Chan_iax2.c: Registration of '42690' rejected: > '' from: '44.98.254.145' > [Aug 16 13:20:08] NOTICE[452] Chan_iax2.c: Registration of '42690' rejected: > '' from: '44.98.254.145' > [Aug 16 21:28:20] NOTICE[461] chan_iax2.c: Registration of '42690' rejected: > 'Registration Refused' from: '44.98.254.145' > Len > WB2HKK What time zone is that, I'd like to correlate it with our logs in UTC. We see some logs here: [Aug 16 17:20:08] WARNING[30259] chan_iax2.c: Address 68.195.113.15:4569 failed CallToken hash inspection You're registered currently, and so long as you register once every 5 min, you're node is in the list. > 42690 68.195.113.15 (D) (null) 4569 Unmonitored Can you send a message to helpdesk at allstarlink.org with this? I'd like to have the dev team look at it. Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From tgundo2003 at yahoo.com Fri Aug 17 13:53:51 2018 From: tgundo2003 at yahoo.com (TGundo 2003) Date: Fri, 17 Aug 2018 13:53:51 +0000 (UTC) Subject: [App_rpt-users] SSH Access In-Reply-To: <05d37c29-79f2-177b-f9be-5787a0540928@midnighteng.com> References: <896372123.8698116.1534453776356.ref@mail.yahoo.com> <896372123.8698116.1534453776356@mail.yahoo.com> <281201230.8848359.1534469042843@mail.yahoo.com> <1026200523.8143037.1534476283514@mail.yahoo.com> <05d37c29-79f2-177b-f9be-5787a0540928@midnighteng.com> Message-ID: <1944297353.966802.1534514031752@mail.yahoo.com> >Have you set ROOT password ? >Edit the file as root from console >Restart the ssh service My password is not the default password, but is there a separate password for root via ssh? ThanksTomW9SRV -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at midnighteng.com Fri Aug 17 14:37:46 2018 From: mm at midnighteng.com (Mike) Date: Fri, 17 Aug 2018 10:37:46 -0400 Subject: [App_rpt-users] SSH Access In-Reply-To: <1944297353.966802.1534514031752@mail.yahoo.com> References: <896372123.8698116.1534453776356.ref@mail.yahoo.com> <896372123.8698116.1534453776356@mail.yahoo.com> <281201230.8848359.1534469042843@mail.yahoo.com> <1026200523.8143037.1534476283514@mail.yahoo.com> <05d37c29-79f2-177b-f9be-5787a0540928@midnighteng.com> <1944297353.966802.1534514031752@mail.yahoo.com> Message-ID: Not sure why you are having issues Root has it's own password SSH or not.(user) Perhaps the service has not been enabled which would have happened if you restarted ssh and not rebooted. Rebooting will not start a service that has not been told to start in the first place. Restarting a service will start the service if not already started, and restart it if already running. systemctl enable ssh systemctl restart ssh ...mike/kb8jnm On 8/17/2018 9:53 AM, TGundo 2003 wrote: > >Have you set ROOT password ? >> Edit the file as root from console >> Restart the ssh service > > My password is not the default password, but is there a separate password for root via ssh? > ThanksTomW9SRV > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > From k6ecm1 at gmail.com Sun Aug 19 04:53:45 2018 From: k6ecm1 at gmail.com (Bob Pyke) Date: Sat, 18 Aug 2018 21:53:45 -0700 Subject: [App_rpt-users] Setting Up a Chicken Link With ASL Message-ID: <16086D6D-43F5-410A-87FF-1EB7447ED6B0@gmail.com> The local club wants to link two repeaters (local and remote) using a 440 link. I?d like to see just how serious folks are about this before we go to all that expense. I?m looking for some pointers as I attempt to setup a ?chicken link? with our remote repeater using a local radio attached to an Allstarlink node. The radio operates in half-duplex with the receive audio out over the internet, and the audio coming in from the internet is transmitted to the remote repeater. My first attempt resulted in ping ponging between the repeater and my local radio. I?m certainly missing something. I?m looking for some added insights. I started by using duplex=0 in rpt.conf Thanks, Bob K6ECM Sent from iPad From mm at midnighteng.com Sun Aug 19 14:08:58 2018 From: mm at midnighteng.com (Mike) Date: Sun, 19 Aug 2018 10:08:58 -0400 Subject: [App_rpt-users] Setting Up a Chicken Link With ASL In-Reply-To: <16086D6D-43F5-410A-87FF-1EB7447ED6B0@gmail.com> References: <16086D6D-43F5-410A-87FF-1EB7447ED6B0@gmail.com> Message-ID: There are many methods for doing this. The one I prefer is to use ctcss on link radios and use the tone for COS So if you can 'pass' pl on the system OR generate a pl only when the repeater has a active cos, works. You can't listen to the repeater 'tail' on your cos. It's the same mistake most make when doing radio remote echolink set-ups. ...mike/kb8jnm On 8/19/2018 12:53 AM, Bob Pyke wrote: > The local club wants to link two repeaters (local and remote) using a 440 link. I?d like to see just how serious folks are about this before we go to all that expense. I?m looking for some pointers as I attempt to setup a ?chicken link? with our remote repeater using a local radio attached to an Allstarlink node. The radio operates in half-duplex with the receive audio out over the internet, and the audio coming in from the internet is transmitted to the remote repeater. My first attempt resulted in ping ponging between the repeater and my local radio. I?m certainly missing something. I?m looking for some added insights. I started by using duplex=0 in rpt.conf > > Thanks, > Bob > K6ECM > > Sent from iPad > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > From dobbins125 at yahoo.com Sun Aug 19 17:07:36 2018 From: dobbins125 at yahoo.com (Keith Dobbins) Date: Sun, 19 Aug 2018 17:07:36 +0000 (UTC) Subject: [App_rpt-users] Issue with Node 45467 No PTT on node actions References: <233191654.10561124.1534698456294.ref@mail.yahoo.com> Message-ID: <233191654.10561124.1534698456294@mail.yahoo.com> I'm having an issue with my node that just started recently. It appears to be dead from the perspective that no action will cause a PTT to occur. I can execute susb key and it works fine from asterisk -rv but when I issue a rpt fun 45467 *722 to speak the time, I see the commands in the asterisk console, BUT no PTT action takes place and my node doesn't key up. Anywhere I can look to find out what the heck is going on? This a weird problem to me and like I said it has been working fine for months. I did a full re-install and it worked fine for a day or so then it's right back to where it was before. Latest version of the 1.1 install. DMK URI and Intel D525 Atom Board. Thanks for any guidance! Keith DobbinsSr. IT Systems EngineerManaged File Transfer/Mainframe Networks3402 Linden Street Parkersburg, WV 26104-1608 ??Amateur Radio Call Sign: N8KLD -------------- next part -------------- An HTML attachment was scrubbed... URL: From jh0932 at gmail.com Sun Aug 19 18:37:35 2018 From: jh0932 at gmail.com (John Heron) Date: Sun, 19 Aug 2018 14:37:35 -0400 Subject: [App_rpt-users] Setting Up a Chicken Link With ASL In-Reply-To: <16086D6D-43F5-410A-87FF-1EB7447ED6B0@gmail.com> References: <16086D6D-43F5-410A-87FF-1EB7447ED6B0@gmail.com> Message-ID: <2140374C-5B22-491B-8E71-FC9256D1767F@gmail.com> Just have to ask? Is it close enough for an RF link? Just treat it as a remove base. All the best, John Heron WA4FAP 678-701-4845 jh0932 at gmail.com > On Aug 19, 2018, at 12:53 AM, Bob Pyke wrote: > > The local club wants to link two repeaters (local and remote) using a 440 link. I?d like to see just how serious folks are about this before we go to all that expense. I?m looking for some pointers as I attempt to setup a ?chicken link? with our remote repeater using a local radio attached to an Allstarlink node. The radio operates in half-duplex with the receive audio out over the internet, and the audio coming in from the internet is transmitted to the remote repeater. My first attempt resulted in ping ponging between the repeater and my local radio. I?m certainly missing something. I?m looking for some added insights. I started by using duplex=0 in rpt.conf > > Thanks, > Bob > K6ECM > > Sent from iPad > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. From k6ecm1 at gmail.com Sun Aug 19 19:51:56 2018 From: k6ecm1 at gmail.com (Bob Pyke) Date: Sun, 19 Aug 2018 12:51:56 -0700 Subject: [App_rpt-users] Setting Up a Chicken Link With ASL In-Reply-To: References: <16086D6D-43F5-410A-87FF-1EB7447ED6B0@gmail.com> Message-ID: <13C7774B-2F98-4105-927F-B3D32A77914E@gmail.com> Doesn't ASL send PL till the end of the tail? Thanks, Bob K6ECM Sent from iPad > On Aug 19, 2018, at 7:08 AM, Mike wrote: > > There are many methods for doing this. > The one I prefer is to use ctcss on link radios and use the tone for COS > So if you can 'pass' pl on the system OR generate a pl only when the repeater has a active cos, works. > You can't listen to the repeater 'tail' on your cos. > It's the same mistake most make when doing radio remote echolink set-ups. > > ...mike/kb8jnm > >> On 8/19/2018 12:53 AM, Bob Pyke wrote: >> The local club wants to link two repeaters (local and remote) using a 440 link. I?d like to see just how serious folks are about this before we go to all that expense. I?m looking for some pointers as I attempt to setup a ?chicken link? with our remote repeater using a local radio attached to an Allstarlink node. The radio operates in half-duplex with the receive audio out over the internet, and the audio coming in from the internet is transmitted to the remote repeater. My first attempt resulted in ping ponging between the repeater and my local radio. I?m certainly missing something. I?m looking for some added insights. I started by using duplex=0 in rpt.conf >> Thanks, >> Bob >> K6ECM >> Sent from iPad >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> To unsubscribe from this list please visit http://lists.allstarlink.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. > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. From mm at midnighteng.com Sun Aug 19 21:30:00 2018 From: mm at midnighteng.com (Mike) Date: Sun, 19 Aug 2018 17:30:00 -0400 Subject: [App_rpt-users] Setting Up a Chicken Link With ASL In-Reply-To: <13C7774B-2F98-4105-927F-B3D32A77914E@gmail.com> References: <16086D6D-43F5-410A-87FF-1EB7447ED6B0@gmail.com> <13C7774B-2F98-4105-927F-B3D32A77914E@gmail.com> Message-ID: <9ab4d05e-af1e-516c-bc4e-e053e9feb4a0@midnighteng.com> That depends on how you set it up as I remember it. Perhaps my memory is failing me again, but, I thought you were looking for a method. You may have to resort to a hardware 'encoder' that is set to come 'on with COS' . Not knowing what the uhf link radios are and assuming that they do not themselves have ctcss capability... (would make it easy) I think if the neither naked settings are there , you should be able to generate it with 'ON EVENT' type scripting in ASL. Best advise... The truly easiest is to use a remote trx on a simplex freq at both locations with or without ctcss on the remote radios. Configured as a remote base in app_rpt... no ping pong, no listening to the others tail. But, remote must be on at both locations. But perhaps your remote radios are not 'freq agile'. No matter the method, if the others tail is present through the link, it's not going to work right. The link COS must end with RX activity. And the easiest to do that is CTCSS. You might also just set a remote TX'rs to the other systems RXrs as a remote base. There is no need to 'listen' to the other system "but only if this is a full time link". Your exact set-up and needs would determine what's best. It's the best I can advise not knowing how the remote radios are config'd in the system or what they are capable of. ...mike/kb8jnm On 8/19/2018 3:51 PM, Bob Pyke wrote: > Doesn't ASL send PL till the end of the tail? > > Thanks, > Bob > K6ECM > > Sent from iPad > > >> On Aug 19, 2018, at 7:08 AM, Mike wrote: >> >> There are many methods for doing this. >> The one I prefer is to use ctcss on link radios and use the tone for COS >> So if you can 'pass' pl on the system OR generate a pl only when the repeater has a active cos, works. >> You can't listen to the repeater 'tail' on your cos. >> It's the same mistake most make when doing radio remote echolink set-ups. >> >> ...mike/kb8jnm >> >>> On 8/19/2018 12:53 AM, Bob Pyke wrote: >>> The local club wants to link two repeaters (local and remote) using a 440 link. I?d like to see just how serious folks are about this before we go to all that expense. I?m looking for some pointers as I attempt to setup a ?chicken link? with our remote repeater using a local radio attached to an Allstarlink node. The radio operates in half-duplex with the receive audio out over the internet, and the audio coming in from the internet is transmitted to the remote repeater. My first attempt resulted in ping ponging between the repeater and my local radio. I?m certainly missing something. I?m looking for some added insights. I started by using duplex=0 in rpt.conf >>> Thanks, >>> Bob >>> K6ECM >>> Sent from iPad >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> To unsubscribe from this list please visit http://lists.allstarlink.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. >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit http://lists.allstarlink.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. > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > From mm at midnighteng.com Sun Aug 19 21:35:29 2018 From: mm at midnighteng.com (Mike) Date: Sun, 19 Aug 2018 17:35:29 -0400 Subject: [App_rpt-users] Setting Up a Chicken Link With ASL In-Reply-To: <9ab4d05e-af1e-516c-bc4e-e053e9feb4a0@midnighteng.com> References: <16086D6D-43F5-410A-87FF-1EB7447ED6B0@gmail.com> <13C7774B-2F98-4105-927F-B3D32A77914E@gmail.com> <9ab4d05e-af1e-516c-bc4e-e053e9feb4a0@midnighteng.com> Message-ID: <731a866b-1695-ff73-a335-5f605e4271f8@midnighteng.com> I believe 'NO' is the setting you are looking for... I could be wrong ! ...mike/kb8jnm http://docs.allstarlink.org/drupal/node/69 txtoctype=notone ; Transmit tone control type: no,phase,notone ; no - CTCSS tone encoding with no hang time ; phase - encode CTCSS and reverse phase ; AKA ("reverse burst") before unkeying TX ; notone - encode CTCSS and stop sending tone before unkeying TX ; AKA ("chicken burst") On 8/19/2018 5:30 PM, Mike wrote: > That depends on how you set it up as I remember it. Perhaps my memory is > failing me again, but, I thought you were looking for a method. > > You may have to resort to a hardware 'encoder' that is set to come 'on > with COS' . Not knowing what the uhf link radios are and assuming that > they do not themselves have ctcss capability... (would make it easy) > > I think if the neither naked settings are there , you should be able to > generate it with 'ON EVENT' type scripting in ASL. > > Best advise... > The truly easiest is to use a remote trx on a simplex freq at both > locations with or without ctcss on the remote radios. Configured as a > remote base in app_rpt... no ping pong, no listening to the others tail. > But, remote must be on at both locations. But perhaps your remote radios > are not 'freq agile'. > > No matter the method, if the others tail is present through the link, > it's not going to work right. The link COS must end with RX activity. > And the easiest to do that is CTCSS. > > You might also just set a remote TX'rs to the other systems RXrs as a > remote base. There is no need to 'listen' to the other system "but only > if this is a full time link". > > Your exact set-up and needs would determine what's best. It's the best I > can advise not knowing how the remote radios are config'd in the system > or what they are capable of. > > ...mike/kb8jnm > > > > > > On 8/19/2018 3:51 PM, Bob Pyke wrote: >> Doesn't ASL send PL till the end of the tail? >> >> Thanks, >> Bob >> K6ECM >> >> Sent from iPad >> >> >>> On Aug 19, 2018, at 7:08 AM, Mike wrote: >>> >>> There are many methods for doing this. >>> The one I prefer is to use ctcss on link radios and use the tone for COS >>> So if you can 'pass' pl on the system OR generate a pl only when the >>> repeater has a active cos, works. >>> You can't listen to the repeater 'tail' on your cos. >>> It's the same mistake most make when doing radio remote echolink >>> set-ups. >>> >>> ...mike/kb8jnm >>> >>>> On 8/19/2018 12:53 AM, Bob Pyke wrote: >>>> The local club wants to link two repeaters (local and remote) using >>>> a 440 link. I?d like to see just how serious folks are about this >>>> before we go to all that expense. I?m looking for some pointers as I >>>> attempt to setup a ?chicken link? with our remote repeater using a >>>> local radio attached to an Allstarlink node. The radio operates in >>>> half-duplex with the receive audio out over the internet, and the >>>> audio coming in from the internet is transmitted to the remote >>>> repeater. My first attempt resulted in ping ponging between the >>>> repeater and my local radio. I?m certainly missing something. I?m >>>> looking for some added insights. I started by using duplex=0 in >>>> rpt.conf >>>> Thanks, >>>> Bob >>>> K6ECM >>>> Sent from iPad >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users at lists.allstarlink.org >>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>>> To unsubscribe from this list please visit >>>> http://lists.allstarlink.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. >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit >>> http://lists.allstarlink.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. >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. >> > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. From tgundo2003 at yahoo.com Mon Aug 20 02:57:20 2018 From: tgundo2003 at yahoo.com (TGundo 2003) Date: Mon, 20 Aug 2018 02:57:20 +0000 (UTC) Subject: [App_rpt-users] SSH Access In-Reply-To: References: <896372123.8698116.1534453776356.ref@mail.yahoo.com> <896372123.8698116.1534453776356@mail.yahoo.com> <281201230.8848359.1534469042843@mail.yahoo.com> <1026200523.8143037.1534476283514@mail.yahoo.com> <05d37c29-79f2-177b-f9be-5787a0540928@midnighteng.com> <1944297353.966802.1534514031752@mail.yahoo.com> Message-ID: <882704386.9929361.1534733840584@mail.yahoo.com> Mike- Thanks again for the help. I figured out what I did wrong. When I edited the SSHD_CONFIG file, me being a newbe forgot to take the # off the front of the line so it was commented out. Fixed it and I now have SSH access on a different port than default. one step at a time... Thanks!TomW9SRV On Friday, August 17, 2018, 9:37:50 AM CDT, Mike wrote: Not sure why you are having issues Root has it's own password SSH or not.(user) Perhaps the service has not been enabled which would have happened if you restarted ssh and not rebooted. Rebooting will not start a service that has not been told to start in the first place. Restarting a service will start the service if not already started, and restart it if already running. systemctl enable ssh systemctl restart ssh ...mike/kb8jnm On 8/17/2018 9:53 AM, TGundo 2003 wrote: >? >Have you set ROOT password ? >> Edit the file as root from console >> Restart the ssh service > > My password is not the default password, but is there a separate password for root via ssh? > ThanksTomW9SRV > >? ? > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at midnighteng.com Mon Aug 20 03:28:32 2018 From: mm at midnighteng.com (Mike) Date: Sun, 19 Aug 2018 23:28:32 -0400 Subject: [App_rpt-users] SSH Access In-Reply-To: <882704386.9929361.1534733840584@mail.yahoo.com> References: <896372123.8698116.1534453776356.ref@mail.yahoo.com> <896372123.8698116.1534453776356@mail.yahoo.com> <281201230.8848359.1534469042843@mail.yahoo.com> <1026200523.8143037.1534476283514@mail.yahoo.com> <05d37c29-79f2-177b-f9be-5787a0540928@midnighteng.com> <1944297353.966802.1534514031752@mail.yahoo.com> <882704386.9929361.1534733840584@mail.yahoo.com> Message-ID: <46779cc1-2a09-2f1f-f957-bd9afdcaa34a@midnighteng.com> ...LOL... been there...done that... It's always something ... hey ! Glad you figured it out. hope there is still some hair on your head ! I'm pulling on some myself on some other matter with ssh & ipv6 LOL ...mike/kb8jnm On 8/19/2018 10:57 PM, TGundo 2003 wrote: > Mike- > Thanks again for the help. I figured out what I did wrong. When I edited the SSHD_CONFIG file, me being a newbe forgot to take the # off the front of the line so it was commented out. Fixed it and I now have SSH access on a different port than default. > one step at a time... > Thanks!TomW9SRV > On Friday, August 17, 2018, 9:37:50 AM CDT, Mike wrote: > > Not sure why you are having issues > Root has it's own password SSH or not.(user) > Perhaps the service has not been enabled which would have happened if > you restarted ssh and not rebooted. > > Rebooting will not start a service that has not been told to start in > the first place. > Restarting a service will start the service if not already started, and > restart it if already running. > > systemctl enable ssh > systemctl restart ssh > > ...mike/kb8jnm > > On 8/17/2018 9:53 AM, TGundo 2003 wrote: >> ? >Have you set ROOT password ? >>> Edit the file as root from console >>> Restart the ssh service >> >> My password is not the default password, but is there a separate password for root via ssh? >> ThanksTomW9SRV >> >> >> >> >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit http://lists.allstarlink.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. >> > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > From mm at midnighteng.com Mon Aug 20 14:43:17 2018 From: mm at midnighteng.com (Mike) Date: Mon, 20 Aug 2018 10:43:17 -0400 Subject: [App_rpt-users] Issue with Node 45467 No PTT on node actions In-Reply-To: <233191654.10561124.1534698456294@mail.yahoo.com> References: <233191654.10561124.1534698456294.ref@mail.yahoo.com> <233191654.10561124.1534698456294@mail.yahoo.com> Message-ID: <0ca4342f-aa57-1b6f-e6b8-d462fcf6ce24@midnighteng.com> Keith, I let this fester in my head a while, While not being familiar with the DMK, and my only thoughts are to check the DMK and be sure the PTT transistor buffer isn't 'wimping-out" Outside of that, look for corruptions in your usbradio file with notepad++ or similar to 'see all characters'. But you might take a peak at app_rpt vars while this is happening to give you a better clue where to look... asterisk -rx rpt showvars NODE# This should tell you a bit closer to look at software or hardware first. See if the TX is up at that point AND when the cos is active which is the other half of what you should be looking at. Hope it helps and you find it. ...mike/kb8jnm On 8/19/2018 1:07 PM, Keith Dobbins wrote: > I'm having an issue with my node that just started recently. It appears to be dead from the perspective that no action will cause a PTT to occur. I can execute susb key and it works fine from asterisk -rv but when I issue a rpt fun 45467 *722 to speak the time, I see the commands in the asterisk console, BUT no PTT action takes place and my node doesn't key up. Anywhere I can look to find out what the heck is going on? This a weird problem to me and like I said it has been working fine for months. I did a full re-install and it worked fine for a day or so then it's right back to where it was before. Latest version of the 1.1 install. DMK URI and Intel D525 Atom Board. > Thanks for any guidance! > Keith DobbinsSr. IT Systems EngineerManaged File Transfer/Mainframe Networks3402 Linden Street Parkersburg, WV 26104-1608 ??Amateur Radio Call Sign: N8KLD > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > From wllmbecks at gmail.com Mon Aug 20 15:17:08 2018 From: wllmbecks at gmail.com (William Becks) Date: Mon, 20 Aug 2018 10:17:08 -0500 Subject: [App_rpt-users] Issue with Node 45467 No PTT on node actions In-Reply-To: <0ca4342f-aa57-1b6f-e6b8-d462fcf6ce24@midnighteng.com> References: <233191654.10561124.1534698456294.ref@mail.yahoo.com> <233191654.10561124.1534698456294@mail.yahoo.com> <0ca4342f-aa57-1b6f-e6b8-d462fcf6ce24@midnighteng.com> Message-ID: <000701d43898$dcc8f950$965aebf0$@gmail.com> Keith, You might also want to build the loopback fixture for the URIx and run uridiag. The various GPIO lines of the URIx are chained or looped to facilitate a quick I/O test. Bill, WA8WG -----Original Message----- From: App_rpt-users On Behalf Of Mike Sent: Monday, August 20, 2018 9:43 AM To: app_rpt-users at lists.allstarlink.org Subject: Re: [App_rpt-users] Issue with Node 45467 No PTT on node actions Keith, I let this fester in my head a while, While not being familiar with the DMK, and my only thoughts are to check the DMK and be sure the PTT transistor buffer isn't 'wimping-out" Outside of that, look for corruptions in your usbradio file with notepad++ or similar to 'see all characters'. But you might take a peak at app_rpt vars while this is happening to give you a better clue where to look... asterisk -rx rpt showvars NODE# This should tell you a bit closer to look at software or hardware first. See if the TX is up at that point AND when the cos is active which is the other half of what you should be looking at. Hope it helps and you find it. ...mike/kb8jnm On 8/19/2018 1:07 PM, Keith Dobbins wrote: > I'm having an issue with my node that just started recently. It appears to be dead from the perspective that no action will cause a PTT to occur. I can execute susb key and it works fine from asterisk -rv but when I issue a rpt fun 45467 *722 to speak the time, I see the commands in the asterisk console, BUT no PTT action takes place and my node doesn't key up. Anywhere I can look to find out what the heck is going on? This a weird problem to me and like I said it has been working fine for months. I did a full re-install and it worked fine for a day or so then it's right back to where it was before. Latest version of the 1.1 install. DMK URI and Intel D525 Atom Board. > Thanks for any guidance! > Keith DobbinsSr. IT Systems EngineerManaged File Transfer/Mainframe > Networks3402 Linden Street Parkersburg, WV 26104-1608 Amateur Radio > Call Sign: N8KLD > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. From k2dls at k2dls.net Tue Aug 21 22:50:12 2018 From: k2dls at k2dls.net (Dan Srebnick) Date: Tue, 21 Aug 2018 18:50:12 -0400 Subject: [App_rpt-users] UPS for a PI 3 B+ In-Reply-To: References: Message-ID: <4ac7eaed5b902c0292ebc52a6a2c0d22313e91c4.camel@k2dls.net> I have an older model on a RPi B+ (not 2 or 3) and it works fine. On Sat, 2018-08-04 at 08:03 -0400, Ramesh Dhami wrote: > Hi All: > > This topic comes up from time-to-time! > > Does anyone have experience with the following UPS HAT: > > http://www.pimodulescart.com/shop/item.aspx?itemid=50 > > The ordering options seems to be a little confusing! > > Additionally, what I am looking for is: > > 1. Does this fully restore power once the battery has been > discharged > and the AC power is restored? - i.e., no buttons to press (my > application is in an unattended / remote location) > > 2. Is this the s/w that I need to install: > https://github.com/modmypi/PiModules/wiki/UPS-PIco-Installation -> > Any > incompatibility / will it break a DIAL install? > > > Thanks, > > Ramesh. > > VA3UV / KN4RSD > > #27919 (and others!) > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. From tom at tomh.us Tue Aug 21 23:56:47 2018 From: tom at tomh.us (Tom Hayward) Date: Tue, 21 Aug 2018 16:56:47 -0700 Subject: [App_rpt-users] UPS for a PI 3 B+ In-Reply-To: References: Message-ID: I went a bit different direction to solve this problem. I already have a 12V power system with battery backup, so I decided to run the Pi from that. I used the SleepyPi https://spellfoundry.com/product/sleepy-pi-2/ to safely shutdown the Pi when the battery voltage drops below the threshold I programmed. When the voltage recovers above another (higher) threshold, it boots up again. I can also read the current voltage over serial for logging, alerting, etc. Here is the code I wrote to do it: https://github.com/SpellFoundry/SleepyPi2/blob/master/examples/LowVoltageShutdown/LowVoltageShutdown.ino If you have a slightly different application, you could modify the code to suit it. Tom KD7LXL -------------- next part -------------- An HTML attachment was scrubbed... URL: From cnovey at gmail.com Wed Aug 22 00:41:09 2018 From: cnovey at gmail.com (Clifford Novey) Date: Tue, 21 Aug 2018 17:41:09 -0700 Subject: [App_rpt-users] Fwd: ASL DAHDI error- asterisk not working In-Reply-To: References: <003f01d439a3$f489efc0$dd9dcf40$@gmail.com> Message-ID: Subject: DAHDI error- asterisk not working RPi3 and stock Allstar (not hamvoip/Crompton etc.) I just did apt-get upgrade then update. Looked like there were some big kernel updates possibly. Asterisk stopped working. 3 blocks of info below- 1- output of "service asterisk status" 2- output of "service asterisk start" 3- output of "journalctl -xe" Any suggestions appreciated- thanks very much. Clifford KK6QMS pi at KK6QMS-ASL-48654:~ $ sudo su root at KK6QMS-ASL-48654:/home/pi# service asterisk status ? asterisk.service - Asterisk PBX and telephony daemon Loaded: loaded (/lib/systemd/system/asterisk.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:asterisk(8) Aug 21 01:08:41 KK6QMS-ASL-48654 systemd[1]: Dependency failed for Asterisk PBX and telephony daemon. Aug 21 01:08:41 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job asterisk.service/start failed with result 'dependency'. Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Dependency failed for Asterisk PBX and telephony daemon. Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job asterisk.service/start failed with result 'dependency'. root at KK6QMS-ASL-48654:/home/pi# then------------------------------>>>>> root at KK6QMS-ASL-48654:/home/pi# service asterisk start A dependency job for asterisk.service failed. See 'journalctl -xe' for details. root at KK6QMS-ASL-48654:/home/pi# ----------------------------------------------- > > > pi at KK6QMS-ASL-48654:~ $ sudo su > > root at KK6QMS-ASL-48654:/home/pi# journalctl -xe > > Aug 21 12:40:02 KK6QMS-ASL-48654 CRON[4240]: pam_unix(cron:session): > session closed for user smmsp > > Aug 21 12:42:37 KK6QMS-ASL-48654 vncserver-x11[391]: Connections: > connected: 192.168.0.6::51946 > > Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: session started: user > pi permissions f > > Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: Connections: > authenticated: 192.168.0.6::51946, as pi (f permissions) > > Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: SPrintConnMgr: Failed > to add printer: server-error-service-unavailable > > Aug 21 12:43:26 KK6QMS-ASL-48654 sudo[4295]: pi : TTY=pts/1 ; > PWD=/home/pi ; USER=root ; COMMAND=/bin/su > > Aug 21 12:43:26 KK6QMS-ASL-48654 sudo[4295]: pam_unix(sudo:session): > session opened for user root by (uid=0) > > Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: Successful su for root by root > > Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: + /dev/pts/1 root:root > > Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: pam_unix(su:session): session > opened for user root by (uid=0) > > Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: pam_systemd(su:session): Cannot > create session: Already running in a session > > Aug 21 12:43:40 KK6QMS-ASL-48654 su[3496]: pam_unix(su:session): session > closed for user root > > Aug 21 12:43:40 KK6QMS-ASL-48654 sudo[3492]: pam_unix(sudo:session): > session closed for user root > > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: dev-dahdi-pseudo.device: Job > dev-dahdi-pseudo.device/start timed out. > > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Timed out waiting for device > dev-dahdi-pseudo.device. > > -- Subject: Unit dev-dahdi-pseudo.device has failed > > -- Defined-By: systemd > > -- Support: https://www.debian.org/support > > -- > > -- Unit dev-dahdi-pseudo.device has failed. > > -- > > -- The result is timeout. > > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Dependency failed for > Asterisk PBX and telephony daemon. > > -- Subject: Unit asterisk.service has failed > > -- Defined-By: systemd > > -- Support: https://www.debian.org/support > > -- > > -- Unit asterisk.service has failed. > > -- > > -- The result is dependency. > > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job > asterisk.service/start failed with result 'dependency'. > > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: dev-dahdi-pseudo.device: Job > dev-dahdi-pseudo.device/start failed with result 'timeout'. > > Aug 21 12:45:57 KK6QMS-ASL-48654 sudo[4394]: pi : TTY=pts/0 ; > PWD=/home/pi ; USER=root ; COMMAND=/bin/su > > Aug 21 12:45:57 KK6QMS-ASL-48654 sudo[4394]: pam_unix(sudo:session): > session opened for user root by (uid=0) > > Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: Successful su for root by root > > Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: + /dev/pts/0 root:root > > Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: pam_unix(su:session): session > opened for user root by (uid=0) > > Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: pam_systemd(su:session): Cannot > create session: Already running in a session > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bryan at k6cbr.us Wed Aug 22 00:46:14 2018 From: bryan at k6cbr.us (Bryan St Clair) Date: Tue, 21 Aug 2018 17:46:14 -0700 Subject: [App_rpt-users] Fwd: ASL DAHDI error- asterisk not working In-Reply-To: References: <003f01d439a3$f489efc0$dd9dcf40$@gmail.com> Message-ID: In the readme instructions it had you put some on hold, did you perform the command: sudo apt-mark hold raspberrypi-kernel-headers raspberrypi-kernel On Tue, Aug 21, 2018 at 5:41 PM, Clifford Novey wrote: > > Subject: DAHDI error- asterisk not working > RPi3 and stock Allstar (not hamvoip/Crompton etc.) > I just did apt-get upgrade then update. Looked like there were some big > kernel updates possibly. Asterisk stopped working. 3 blocks of info below- > 1- output of "service asterisk status" > 2- output of "service asterisk start" > 3- output of "journalctl -xe" > Any suggestions appreciated- thanks very much. > Clifford KK6QMS > > pi at KK6QMS-ASL-48654:~ $ sudo su > root at KK6QMS-ASL-48654:/home/pi# service asterisk status > ? asterisk.service - Asterisk PBX and telephony daemon > Loaded: loaded (/lib/systemd/system/asterisk.service; enabled; vendor > preset: enabled) > Active: inactive (dead) > Docs: man:asterisk(8) > > Aug 21 01:08:41 KK6QMS-ASL-48654 systemd[1]: Dependency failed for Asterisk > PBX and telephony daemon. > Aug 21 01:08:41 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job > asterisk.service/start failed with result 'dependency'. > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Dependency failed for Asterisk > PBX and telephony daemon. > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job > asterisk.service/start failed with result 'dependency'. > root at KK6QMS-ASL-48654:/home/pi# > > then------------------------------>>>>> > root at KK6QMS-ASL-48654:/home/pi# service asterisk start > A dependency job for asterisk.service failed. See 'journalctl -xe' for > details. > root at KK6QMS-ASL-48654:/home/pi# > ----------------------------------------------- > > > >> >> >> >> pi at KK6QMS-ASL-48654:~ $ sudo su >> >> root at KK6QMS-ASL-48654:/home/pi# journalctl -xe >> >> Aug 21 12:40:02 KK6QMS-ASL-48654 CRON[4240]: pam_unix(cron:session): >> session closed for user smmsp >> >> Aug 21 12:42:37 KK6QMS-ASL-48654 vncserver-x11[391]: Connections: >> connected: 192.168.0.6::51946 >> >> Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: session started: user >> pi permissions f >> >> Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: Connections: >> authenticated: 192.168.0.6::51946, as pi (f permissions) >> >> Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: SPrintConnMgr: Failed >> to add printer: server-error-service-unavailable >> >> Aug 21 12:43:26 KK6QMS-ASL-48654 sudo[4295]: pi : TTY=pts/1 ; >> PWD=/home/pi ; USER=root ; COMMAND=/bin/su >> >> Aug 21 12:43:26 KK6QMS-ASL-48654 sudo[4295]: pam_unix(sudo:session): >> session opened for user root by (uid=0) >> >> Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: Successful su for root by root >> >> Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: + /dev/pts/1 root:root >> >> Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: pam_unix(su:session): session >> opened for user root by (uid=0) >> >> Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: pam_systemd(su:session): Cannot >> create session: Already running in a session >> >> Aug 21 12:43:40 KK6QMS-ASL-48654 su[3496]: pam_unix(su:session): session >> closed for user root >> >> Aug 21 12:43:40 KK6QMS-ASL-48654 sudo[3492]: pam_unix(sudo:session): >> session closed for user root >> >> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: dev-dahdi-pseudo.device: Job >> dev-dahdi-pseudo.device/start timed out. >> >> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Timed out waiting for device >> dev-dahdi-pseudo.device. >> >> -- Subject: Unit dev-dahdi-pseudo.device has failed >> >> -- Defined-By: systemd >> >> -- Support: https://www.debian.org/support >> >> -- >> >> -- Unit dev-dahdi-pseudo.device has failed. >> >> -- >> >> -- The result is timeout. >> >> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Dependency failed for >> Asterisk PBX and telephony daemon. >> >> -- Subject: Unit asterisk.service has failed >> >> -- Defined-By: systemd >> >> -- Support: https://www.debian.org/support >> >> -- >> >> -- Unit asterisk.service has failed. >> >> -- >> >> -- The result is dependency. >> >> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job >> asterisk.service/start failed with result 'dependency'. >> >> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: dev-dahdi-pseudo.device: Job >> dev-dahdi-pseudo.device/start failed with result 'timeout'. >> >> Aug 21 12:45:57 KK6QMS-ASL-48654 sudo[4394]: pi : TTY=pts/0 ; >> PWD=/home/pi ; USER=root ; COMMAND=/bin/su >> >> Aug 21 12:45:57 KK6QMS-ASL-48654 sudo[4394]: pam_unix(sudo:session): >> session opened for user root by (uid=0) >> >> Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: Successful su for root by root >> >> Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: + /dev/pts/0 root:root >> >> Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: pam_unix(su:session): session >> opened for user root by (uid=0) >> >> Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: pam_systemd(su:session): Cannot >> create session: Already running in a session > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Bryan K6CBR bryan at k6cbr.us Allstar Base: 43918, 43991 Allstar Hubs: 43919, 47036, 47061(Testing) www.k6cbr.us QRZ From cummingsj at gmail.com Wed Aug 22 01:23:02 2018 From: cummingsj at gmail.com (JJC) Date: Tue, 21 Aug 2018 20:23:02 -0500 Subject: [App_rpt-users] Fwd: ASL DAHDI error- asterisk not working In-Reply-To: References: <003f01d439a3$f489efc0$dd9dcf40$@gmail.com> Message-ID: You can also look in the mailer archives, I provided a solution to allow kernel updates etc... Sent from the iRoad > On Aug 21, 2018, at 19:46, Bryan St Clair wrote: > > In the readme instructions it had you put some on hold, did you > perform the command: > > sudo apt-mark hold raspberrypi-kernel-headers raspberrypi-kernel > > > >> On Tue, Aug 21, 2018 at 5:41 PM, Clifford Novey wrote: >> >> Subject: DAHDI error- asterisk not working >> RPi3 and stock Allstar (not hamvoip/Crompton etc.) >> I just did apt-get upgrade then update. Looked like there were some big >> kernel updates possibly. Asterisk stopped working. 3 blocks of info below- >> 1- output of "service asterisk status" >> 2- output of "service asterisk start" >> 3- output of "journalctl -xe" >> Any suggestions appreciated- thanks very much. >> Clifford KK6QMS >> >> pi at KK6QMS-ASL-48654:~ $ sudo su >> root at KK6QMS-ASL-48654:/home/pi# service asterisk status >> ? asterisk.service - Asterisk PBX and telephony daemon >> Loaded: loaded (/lib/systemd/system/asterisk.service; enabled; vendor >> preset: enabled) >> Active: inactive (dead) >> Docs: man:asterisk(8) >> >> Aug 21 01:08:41 KK6QMS-ASL-48654 systemd[1]: Dependency failed for Asterisk >> PBX and telephony daemon. >> Aug 21 01:08:41 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job >> asterisk.service/start failed with result 'dependency'. >> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Dependency failed for Asterisk >> PBX and telephony daemon. >> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job >> asterisk.service/start failed with result 'dependency'. >> root at KK6QMS-ASL-48654:/home/pi# >> >> then------------------------------>>>>> >> root at KK6QMS-ASL-48654:/home/pi# service asterisk start >> A dependency job for asterisk.service failed. See 'journalctl -xe' for >> details. >> root at KK6QMS-ASL-48654:/home/pi# >> ----------------------------------------------- >> >> >> >>> >>> >>> >>> pi at KK6QMS-ASL-48654:~ $ sudo su >>> >>> root at KK6QMS-ASL-48654:/home/pi# journalctl -xe >>> >>> Aug 21 12:40:02 KK6QMS-ASL-48654 CRON[4240]: pam_unix(cron:session): >>> session closed for user smmsp >>> >>> Aug 21 12:42:37 KK6QMS-ASL-48654 vncserver-x11[391]: Connections: >>> connected: 192.168.0.6::51946 >>> >>> Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: session started: user >>> pi permissions f >>> >>> Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: Connections: >>> authenticated: 192.168.0.6::51946, as pi (f permissions) >>> >>> Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: SPrintConnMgr: Failed >>> to add printer: server-error-service-unavailable >>> >>> Aug 21 12:43:26 KK6QMS-ASL-48654 sudo[4295]: pi : TTY=pts/1 ; >>> PWD=/home/pi ; USER=root ; COMMAND=/bin/su >>> >>> Aug 21 12:43:26 KK6QMS-ASL-48654 sudo[4295]: pam_unix(sudo:session): >>> session opened for user root by (uid=0) >>> >>> Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: Successful su for root by root >>> >>> Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: + /dev/pts/1 root:root >>> >>> Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: pam_unix(su:session): session >>> opened for user root by (uid=0) >>> >>> Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: pam_systemd(su:session): Cannot >>> create session: Already running in a session >>> >>> Aug 21 12:43:40 KK6QMS-ASL-48654 su[3496]: pam_unix(su:session): session >>> closed for user root >>> >>> Aug 21 12:43:40 KK6QMS-ASL-48654 sudo[3492]: pam_unix(sudo:session): >>> session closed for user root >>> >>> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: dev-dahdi-pseudo.device: Job >>> dev-dahdi-pseudo.device/start timed out. >>> >>> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Timed out waiting for device >>> dev-dahdi-pseudo.device. >>> >>> -- Subject: Unit dev-dahdi-pseudo.device has failed >>> >>> -- Defined-By: systemd >>> >>> -- Support: https://www.debian.org/support >>> >>> -- >>> >>> -- Unit dev-dahdi-pseudo.device has failed. >>> >>> -- >>> >>> -- The result is timeout. >>> >>> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Dependency failed for >>> Asterisk PBX and telephony daemon. >>> >>> -- Subject: Unit asterisk.service has failed >>> >>> -- Defined-By: systemd >>> >>> -- Support: https://www.debian.org/support >>> >>> -- >>> >>> -- Unit asterisk.service has failed. >>> >>> -- >>> >>> -- The result is dependency. >>> >>> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job >>> asterisk.service/start failed with result 'dependency'. >>> >>> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: dev-dahdi-pseudo.device: Job >>> dev-dahdi-pseudo.device/start failed with result 'timeout'. >>> >>> Aug 21 12:45:57 KK6QMS-ASL-48654 sudo[4394]: pi : TTY=pts/0 ; >>> PWD=/home/pi ; USER=root ; COMMAND=/bin/su >>> >>> Aug 21 12:45:57 KK6QMS-ASL-48654 sudo[4394]: pam_unix(sudo:session): >>> session opened for user root by (uid=0) >>> >>> Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: Successful su for root by root >>> >>> Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: + /dev/pts/0 root:root >>> >>> Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: pam_unix(su:session): session >>> opened for user root by (uid=0) >>> >>> Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: pam_systemd(su:session): Cannot >>> create session: Already running in a session >> >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. >> > > > > -- > Bryan > K6CBR > bryan at k6cbr.us > Allstar Base: 43918, 43991 > Allstar Hubs: 43919, 47036, 47061(Testing) > > www.k6cbr.us > QRZ > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. From cnovey at gmail.com Wed Aug 22 01:24:59 2018 From: cnovey at gmail.com (cnovey) Date: Tue, 21 Aug 2018 18:24:59 -0700 Subject: [App_rpt-users] Fwd: ASL DAHDI error- asterisk not working In-Reply-To: References: <003f01d439a3$f489efc0$dd9dcf40$@gmail.com> Message-ID: <005201d439b6$f1bfd8a0$d53f89e0$@gmail.com> I was able to fix it w help of a friend who had old posts to search- the answer is listed below in quoted post. Re instructions, no I do not think that command string was involved- I used these instructions: https://wiki.allstarlink.org/wiki/ASL_FAQ Thanks Clifford KK6QMS =quote= "---------- Forwarded message --------- From: Steve Zingman Date: Wed, Jul 25, 2018 at 2:58 AM Subject: Re: [App_rpt-users] NanoPi To: Users of Asterisk app_rpt Bob, It looks like DKMS did not rebuild DAHDI properly. Please do as root: dpkg-reconfigure asl-dahdi-linux-dkms reboot Should now be fixed. Check DAHDI is running by: lsmod | grep dahdi 73, Steve N4IRS" =end quote= -----Original Message----- From: App_rpt-users On Behalf Of Bryan St Clair Sent: Tuesday, August 21, 2018 5:46 PM To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] Fwd: ASL DAHDI error- asterisk not working In the readme instructions it had you put some on hold, did you perform the command: sudo apt-mark hold raspberrypi-kernel-headers raspberrypi-kernel On Tue, Aug 21, 2018 at 5:41 PM, Clifford Novey wrote: > > Subject: DAHDI error- asterisk not working > RPi3 and stock Allstar (not hamvoip/Crompton etc.) I just did apt-get > upgrade then update. Looked like there were some big kernel updates > possibly. Asterisk stopped working. 3 blocks of info below- > 1- output of "service asterisk status" > 2- output of "service asterisk start" > 3- output of "journalctl -xe" > Any suggestions appreciated- thanks very much. > Clifford KK6QMS > > pi at KK6QMS-ASL-48654:~ $ sudo su > root at KK6QMS-ASL-48654:/home/pi# service asterisk status ? > asterisk.service - Asterisk PBX and telephony daemon > Loaded: loaded (/lib/systemd/system/asterisk.service; enabled; > vendor > preset: enabled) > Active: inactive (dead) > Docs: man:asterisk(8) > > Aug 21 01:08:41 KK6QMS-ASL-48654 systemd[1]: Dependency failed for > Asterisk PBX and telephony daemon. > Aug 21 01:08:41 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job > asterisk.service/start failed with result 'dependency'. > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Dependency failed for > Asterisk PBX and telephony daemon. > Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job > asterisk.service/start failed with result 'dependency'. > root at KK6QMS-ASL-48654:/home/pi# > > then------------------------------>>>>> > root at KK6QMS-ASL-48654:/home/pi# service asterisk start A dependency > job for asterisk.service failed. See 'journalctl -xe' for details. > root at KK6QMS-ASL-48654:/home/pi# > ----------------------------------------------- > > > >> >> >> >> pi at KK6QMS-ASL-48654:~ $ sudo su >> >> root at KK6QMS-ASL-48654:/home/pi# journalctl -xe >> >> Aug 21 12:40:02 KK6QMS-ASL-48654 CRON[4240]: pam_unix(cron:session): >> session closed for user smmsp >> >> Aug 21 12:42:37 KK6QMS-ASL-48654 vncserver-x11[391]: Connections: >> connected: 192.168.0.6::51946 >> >> Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: session started: >> user pi permissions f >> >> Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: Connections: >> authenticated: 192.168.0.6::51946, as pi (f permissions) >> >> Aug 21 12:42:38 KK6QMS-ASL-48654 vncserver-x11[391]: SPrintConnMgr: >> Failed to add printer: server-error-service-unavailable >> >> Aug 21 12:43:26 KK6QMS-ASL-48654 sudo[4295]: pi : TTY=pts/1 ; >> PWD=/home/pi ; USER=root ; COMMAND=/bin/su >> >> Aug 21 12:43:26 KK6QMS-ASL-48654 sudo[4295]: pam_unix(sudo:session): >> session opened for user root by (uid=0) >> >> Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: Successful su for root by >> root >> >> Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: + /dev/pts/1 root:root >> >> Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: pam_unix(su:session): >> session opened for user root by (uid=0) >> >> Aug 21 12:43:26 KK6QMS-ASL-48654 su[4299]: pam_systemd(su:session): >> Cannot create session: Already running in a session >> >> Aug 21 12:43:40 KK6QMS-ASL-48654 su[3496]: pam_unix(su:session): >> session closed for user root >> >> Aug 21 12:43:40 KK6QMS-ASL-48654 sudo[3492]: pam_unix(sudo:session): >> session closed for user root >> >> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: dev-dahdi-pseudo.device: >> Job dev-dahdi-pseudo.device/start timed out. >> >> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Timed out waiting for >> device dev-dahdi-pseudo.device. >> >> -- Subject: Unit dev-dahdi-pseudo.device has failed >> >> -- Defined-By: systemd >> >> -- Support: https://www.debian.org/support >> >> -- >> >> -- Unit dev-dahdi-pseudo.device has failed. >> >> -- >> >> -- The result is timeout. >> >> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: Dependency failed for >> Asterisk PBX and telephony daemon. >> >> -- Subject: Unit asterisk.service has failed >> >> -- Defined-By: systemd >> >> -- Support: https://www.debian.org/support >> >> -- >> >> -- Unit asterisk.service has failed. >> >> -- >> >> -- The result is dependency. >> >> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: asterisk.service: Job >> asterisk.service/start failed with result 'dependency'. >> >> Aug 21 12:45:02 KK6QMS-ASL-48654 systemd[1]: dev-dahdi-pseudo.device: >> Job dev-dahdi-pseudo.device/start failed with result 'timeout'. >> >> Aug 21 12:45:57 KK6QMS-ASL-48654 sudo[4394]: pi : TTY=pts/0 ; >> PWD=/home/pi ; USER=root ; COMMAND=/bin/su >> >> Aug 21 12:45:57 KK6QMS-ASL-48654 sudo[4394]: pam_unix(sudo:session): >> session opened for user root by (uid=0) >> >> Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: Successful su for root by >> root >> >> Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: + /dev/pts/0 root:root >> >> Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: pam_unix(su:session): >> session opened for user root by (uid=0) >> >> Aug 21 12:45:57 KK6QMS-ASL-48654 su[4398]: pam_systemd(su:session): >> Cannot create session: Already running in a session > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -- Bryan K6CBR bryan at k6cbr.us Allstar Base: 43918, 43991 Allstar Hubs: 43919, 47036, 47061(Testing) www.k6cbr.us QRZ _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. From Bryan at bryanfields.net Thu Aug 23 04:44:51 2018 From: Bryan at bryanfields.net (Bryan Fields) Date: Thu, 23 Aug 2018 00:44:51 -0400 Subject: [App_rpt-users] Web Transceiver Update Message-ID: Wanted to give a quick update as the ops team believes we have this licked. If you're able to get it to run in your browser, it should work now. If you have Java issues, that sadly between you and the PC, but I've tested the in a windows 7 VM in IE (ick) and it works. I'd give out a special thanks to the team members who re-coded the undocumented server-side program to make this work in a very short time. Reminder, not all nodes support this, they must allow it. Please reach out to helpdesk at allstarlink.org if you have issues that are not java related. 73s -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net From waynehale at mac.com Thu Aug 23 06:03:22 2018 From: waynehale at mac.com (wayne hale) Date: Wed, 22 Aug 2018 23:03:22 -0700 Subject: [App_rpt-users] Web Transceiver Update In-Reply-To: References: Message-ID: <16D85AC9-07A2-4FF0-BC38-2F3C03BBEB8D@mac.com> Thank you, thank you. Just verified I can now connect normally to my remote base 28146 via webtranceiver. There are lingering issues of course like it stops responding to commands after a few minutes until you disconnect then reconnect but I can live with that. Sometimes the audio stutters but that is not a show stopper either. Firefox ESR (extended service release), 32 bit for Windows, works under Windows 7 and Mac OSX for me, Linux Mint 18.3 and Palemoon browser and the IcedTea java replacement works for me also. Windows 10 is hit and miss to run Java, sometimes it works, other times not even with the proper security exception in the java control panel. 73 and thanks Wayne W6IZK > On Aug 22, 2018, at 9:44 PM, Bryan Fields wrote: > > Wanted to give a quick update as the ops team believes we have this licked. > If you're able to get it to run in your browser, it should work now. If you > have Java issues, that sadly between you and the PC, but I've tested the in a > windows 7 VM in IE (ick) and it works. > > I'd give out a special thanks to the team members who re-coded the > undocumented server-side program to make this work in a very short time. > > Reminder, not all nodes support this, they must allow it. > > Please reach out to helpdesk at allstarlink.org if you have issues that are not > java related. > > 73s > -- > Bryan Fields > > 727-409-1194 - Voice > http://bryanfields.net > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. From george at dyb.com Sat Aug 25 16:55:47 2018 From: george at dyb.com (George Csahanin) Date: Sat, 25 Aug 2018 11:55:47 -0500 Subject: [App_rpt-users] Pi Zero Message-ID: <93D48B76-69BD-4546-9F6A-DCFA9B15F360@dyb.com> Tried DIAL on s Pi Zero with WiFi. The os runs ok, WiFi ok asterisk gives a segmentation fault snd just sits retrying every ten seconds. Am I trying the impossible with the Pi Zero? Aug 24 14:53:35 repeater systemd[1]: asterisk.service: Failed with result 'signal'. Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart. Aug 24 14:53:45 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon. Aug 24 14:53:45 repeater systemd[1]: Started Asterisk PBX and telephony daemon. Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Main process exited, code=killed, status=11/SEGV Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Control process exited, code=killed status=11 Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Unit entered failed state. Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Failed with result 'signal'. -- George Csahanin 10100 Carson Ranch Rd. Crowley, TX 76036 682-708-5716 home 401-338-0568 cel -------------- next part -------------- An HTML attachment was scrubbed... URL: From cnovey at gmail.com Sat Aug 25 21:54:55 2018 From: cnovey at gmail.com (Clifford Novey) Date: Sat, 25 Aug 2018 14:54:55 -0700 Subject: [App_rpt-users] Pi Zero In-Reply-To: <93D48B76-69BD-4546-9F6A-DCFA9B15F360@dyb.com> References: <93D48B76-69BD-4546-9F6A-DCFA9B15F360@dyb.com> Message-ID: I had similar error yesterday but in my case it had to do with needing to enable simple USB in both rpt.cfg and in modules cfg. Clifford KK6QMS On Sat, Aug 25, 2018, 9:55 AM George Csahanin wrote: > Tried DIAL on s Pi Zero with WiFi. The os runs ok, WiFi ok asterisk gives > a segmentation fault snd just sits retrying every ten seconds. > > Am I trying the impossible with the Pi Zero? > > > Aug 24 14:53:35 repeater systemd[1]: asterisk.service: Failed with result > 'signal'. > Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Service hold-off > time over, scheduling restart. > Aug 24 14:53:45 repeater systemd[1]: Stopped Asterisk PBX and telephony > daemon. > Aug 24 14:53:45 repeater systemd[1]: Started Asterisk PBX and telephony > daemon. > Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Main process > exited, code=killed, status=11/SEGV > Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Control process > exited, code=killed status=11 > Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Unit entered failed > state. > Aug 24 14:53:45 repeater systemd[1]: asterisk.service: Failed with result > 'signal'. > > -- > George Csahanin > 10100 Carson Ranch Rd. > Crowley, TX 76036 > 682-708-5716 home > 401-338-0568 cel > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dpk at randomnotes.org Sun Aug 26 00:22:24 2018 From: dpk at randomnotes.org (Doug Kingston) Date: Sat, 25 Aug 2018 17:22:24 -0700 Subject: [App_rpt-users] Integrating Echolink (and IRLP?) to an Allstar based repeater Message-ID: One suggestion that has been made in some of the howto's is to put the Echolink to a pseudo node and then permanently link that to the primary Allstar node at startup so its easier to disconnect if needed. I have not see a good sample rpt.conf file that implements that. Does someone run in that configuration would would be willing to share a suitably redacted version of their config file(s)? Should we do the same thing with IRLP? -Doug-, KD7DK -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at midnighteng.com Sun Aug 26 12:23:13 2018 From: mm at midnighteng.com (Mike) Date: Sun, 26 Aug 2018 08:23:13 -0400 Subject: [App_rpt-users] Integrating Echolink (and IRLP?) to an Allstar based repeater In-Reply-To: References: Message-ID: The 'generic' node/hub is all you need for a independent echolink. That is a node using rxchannel = dahdi/pseudo for your rxchannel driver. The rest is the echolink config to say that node # xxxxx is the node connections are directed to (astnode=xxxxx). Your generic node can be public or private depending on if you want it to be able to independently have incoming asterisk connections to anywhere else (public listings). Don't forget to set that generic hub/node in iax and extensions if you want to be publicly independent. ...mike/kb8jnm On 8/25/2018 8:22 PM, Doug Kingston wrote: > One suggestion that has been made in some of the howto's is to put the > Echolink to a pseudo node and then permanently link that to the primary > Allstar node at startup so its easier to disconnect if needed. I have not > see a good sample rpt.conf file that implements that. Does someone run in > that configuration would would be willing to share a suitably redacted > version of their config file(s)? > > Should we do the same thing with IRLP? > > -Doug-, KD7DK > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > From k2krs at arrl.net Sun Aug 26 14:03:20 2018 From: k2krs at arrl.net (K2KRS Ken) Date: Sun, 26 Aug 2018 09:03:20 -0500 Subject: [App_rpt-users] Integrating Echolink (and IRLP?) to an Allstar based repeater In-Reply-To: References: Message-ID: <88890ee38dd05af005bb8c245691bb3d@stoneblue.com> I have two nodes, one local from Mark nano ae and one I run on a Vultr server. My local internet is not reliable and usually can not take incoming connections and I can't even get outgoing echolink to work locally which is the reason I setup the second node on vultr. Then I dialup a permanent connection between the two. https://youtu.be/zGqdTvyObIU Allstar Node on Virtual Server https://www.youtube.com/watch?v=IsxVPh1ms3o How To Setup Echolink on your AllStar Node Sorry I don't know anything about setting up IRLP currently. --- AllStar: 48715 EchoLink: 207841 On 2018-08-25 07:22 PM, Doug Kingston wrote: > One suggestion that has been made in some of the howto's is to put the > Echolink to a pseudo node and then permanently link that to the primary > Allstar node at startup so its easier to disconnect if needed. I have > not > see a good sample rpt.conf file that implements that. Does someone run > in > that configuration would would be willing to share a suitably redacted > version of their config file(s)? > > Should we do the same thing with IRLP? > > -Doug-, KD7DK > From dcarlet_2000 at yahoo.com Mon Aug 27 02:40:13 2018 From: dcarlet_2000 at yahoo.com (Darren Carleton) Date: Mon, 27 Aug 2018 02:40:13 +0000 (UTC) Subject: [App_rpt-users] localplay / local time References: <1742967311.3541001.1535337613488.ref@mail.yahoo.com> Message-ID: <1742967311.3541001.1535337613488@mail.yahoo.com> Is this a bug or by design? localplay and time functions do not seem to work when rpt.config is configured with duplex = 0 Execution of these:rpt localplay #### digits/2711 = status,11? ? ? ? ?; Force ID (local only)712 = status,12? ? ? ? ?; Give Time of Day (local only) Results in playback without PTT. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tgundo2003 at yahoo.com Mon Aug 27 03:10:27 2018 From: tgundo2003 at yahoo.com (TGundo 2003) Date: Mon, 27 Aug 2018 03:10:27 +0000 (UTC) Subject: [App_rpt-users] Cannot get node to execute commands via CLI References: <1067589670.2986931.1535339427112.ref@mail.yahoo.com> Message-ID: <1067589670.2986931.1535339427112@mail.yahoo.com> I had my node working and was able to connect to another node about a week ago using the CLI interface in asterisk.? Since then the things I have changed: -Configured iax client so I can monitor with iaxrpt on my PC. -Removed ID's the and hang times from the rpt.conf file. Not much else than that. If I go to radio-tune-menu and enable echo mode I hear myself back. I show online on the node list. I'm really thinking I may have messed something up when I configured for the iax client. Any suggestions? Thanks! TomW9SRV -------------- next part -------------- An HTML attachment was scrubbed... URL: From ji1bqw at mbr.nifty.com Tue Aug 28 09:55:21 2018 From: ji1bqw at mbr.nifty.com (K. Ishikawa) Date: Tue, 28 Aug 2018 18:55:21 +0900 Subject: [App_rpt-users] rxctcssdecode = -1 Message-ID: <984eb781-0405-b6a3-7479-e28ca4fe6e91@mbr.nifty.com> Hi to the group, When I set "radio set debug" in CLI, the screen is inundated with a flow the following message. It keeps printing the same message so fast that I can't catch other debug messages. Can anyone advise how I can eliminate this, please? [Aug 28 18:32:39] NOTICE[3013]: chan_usbradio.c:2913 usbradio_read: rxctcssdecode = -1, chan Radio/usb_2132 The node itself is working well, as far as I can tell. It's on R-Pi 3 with URI. Thanks, K -- JI1BQW - #2132 From ji1bqw at mbr.nifty.com Tue Aug 28 10:19:58 2018 From: ji1bqw at mbr.nifty.com (K. Ishikawa) Date: Tue, 28 Aug 2018 19:19:58 +0900 Subject: [App_rpt-users] rxctcssdecode = -1 In-Reply-To: References: Message-ID: <9d1a031b-f00f-0488-0210-45b94d3937c3@mbr.nifty.com> (Let me go again as the format was broken in the previous post.) Hi to the group, When I set "radio set debug" in CLI, the screen is inundated with a flow the following message.? It keeps printing the same message so fast that I can't catch other debug messages.? Can anyone advise how I can eliminate this, please? [Aug 28 18:32:39] NOTICE[3013]: chan_usbradio.c:2913 usbradio_read: rxctcssdecode = -1, chan Radio/usb_2132 The node itself is working well, as far as I can tell.? It's on R-Pi 3 with URI. Thanks, K -- JI1BQW - #2132 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at midnighteng.com Tue Aug 28 12:52:00 2018 From: mm at midnighteng.com (Mike) Date: Tue, 28 Aug 2018 08:52:00 -0400 Subject: [App_rpt-users] rxctcssdecode = -1 In-Reply-To: <984eb781-0405-b6a3-7479-e28ca4fe6e91@mbr.nifty.com> References: <984eb781-0405-b6a3-7479-e28ca4fe6e91@mbr.nifty.com> Message-ID: <7a4d397a-521f-2bc5-f792-de998eb6600e@midnighteng.com> While I can't answer your debug question, I run asterisk in the foreground and set verbosity to a desirable level to see what I want to see. asterisk -r -vvv - The more v's the more verbose Perhaps that may help... But, what is the issue with "rxctcssdecode = -1" your tracking ? ...mike/kb8jnm On 8/28/2018 5:55 AM, K. Ishikawa wrote: > Hi to the group, When I set "radio set debug" in CLI, the screen is > inundated with a flow the following message. It keeps printing the same > message so fast that I can't catch other debug messages. Can anyone > advise how I can eliminate this, please? [Aug 28 18:32:39] NOTICE[3013]: > chan_usbradio.c:2913 usbradio_read: rxctcssdecode = -1, chan > Radio/usb_2132 The node itself is working well, as far as I can tell. > It's on R-Pi 3 with URI. Thanks, K > From ji1bqw at mbr.nifty.com Tue Aug 28 14:05:42 2018 From: ji1bqw at mbr.nifty.com (K. Ishikawa) Date: Tue, 28 Aug 2018 23:05:42 +0900 Subject: [App_rpt-users] rxctcssdecode = -1 In-Reply-To: <7a4d397a-521f-2bc5-f792-de998eb6600e@midnighteng.com> References: <984eb781-0405-b6a3-7479-e28ca4fe6e91@mbr.nifty.com> <7a4d397a-521f-2bc5-f792-de998eb6600e@midnighteng.com> Message-ID: Mike, -vv .. doesn't make a difference.? Even without -v, it generates the message.? Well it's not a big deal, but when I want to see radio related debug messages (e.g., keyed, carrier detect, etc.), they are buried in this particular message and scrolled out of screen instantly.? Since it generates 50+ same messages in a second(!), I just feel something maybe minor (I hope) is not working as it should be.? I just wondered someone in the group had any clue. K On 2018/08/28 21:52, Mike wrote: > While I can't answer your debug question, > I run asterisk in the foreground and set verbosity to a desirable > level to see what I want to see. > > asterisk -r -vvv???? -? The more v's the more verbose > > Perhaps that may help... > > But, what is the issue with "rxctcssdecode = -1" your tracking ? > > ...mike/kb8jnm > > On 8/28/2018 5:55 AM, K. Ishikawa wrote: >> Hi to the group, When I set "radio set debug" in CLI, the screen is >> inundated with a flow the following message. It keeps printing the >> same message so fast that I can't catch other debug messages. Can >> anyone advise how I can eliminate this, please? [Aug 28 18:32:39] >> NOTICE[3013]: chan_usbradio.c:2913 usbradio_read: rxctcssdecode = -1, >> chan Radio/usb_2132 The node itself is working well, as far as I can >> tell. It's on R-Pi 3 with URI. Thanks, K >> > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. -- JI1BQW From k2krs at arrl.net Tue Aug 28 14:20:36 2018 From: k2krs at arrl.net (K2KRS Ken) Date: Tue, 28 Aug 2018 09:20:36 -0500 Subject: [App_rpt-users] rxctcssdecode = -1 In-Reply-To: References: <984eb781-0405-b6a3-7479-e28ca4fe6e91@mbr.nifty.com> <7a4d397a-521f-2bc5-f792-de998eb6600e@midnighteng.com> Message-ID: <7092adb86f1bdb265913ad919e7628e5@arrl.net> This is just a wild guess but chan_usbradio.c:2913 usbradio_read: rxctcssdecode = -1, this may be a debug message pertaining to decoding or not decoding (-1) the continuous tone on the receive. I imagine decoding that tone is a continuous thus continuous flow of messages if debug is enabled to your screen. Do you have the chan_usbradio.c file ? You could look at line 2913 to see what's up. On 2018-08-28 09:05 AM, K. Ishikawa wrote: > Mike, > > -vv .. doesn't make a difference.? Even without -v, it generates the > message.? Well it's not a big deal, but when I want to see radio > related debug messages (e.g., keyed, carrier detect, etc.), they are > buried in this particular message and scrolled out of screen > instantly.? Since it generates 50+ same messages in a second(!), I > just feel something maybe minor (I hope) is not working as it should > be.? I just wondered someone in the group had any clue. > > K > > > On 2018/08/28 21:52, Mike wrote: >> While I can't answer your debug question, >> I run asterisk in the foreground and set verbosity to a desirable >> level to see what I want to see. >> >> asterisk -r -vvv???? -? The more v's the more verbose >> >> Perhaps that may help... >> >> But, what is the issue with "rxctcssdecode = -1" your tracking ? >> >> ...mike/kb8jnm >> >> On 8/28/2018 5:55 AM, K. Ishikawa wrote: >>> Hi to the group, When I set "radio set debug" in CLI, the screen is >>> inundated with a flow the following message. It keeps printing the >>> same message so fast that I can't catch other debug messages. Can >>> anyone advise how I can eliminate this, please? [Aug 28 18:32:39] >>> NOTICE[3013]: chan_usbradio.c:2913 usbradio_read: rxctcssdecode = -1, >>> chan Radio/usb_2132 The node itself is working well, as far as I can >>> tell. It's on R-Pi 3 with URI. Thanks, K >>> From mm at midnighteng.com Tue Aug 28 15:15:10 2018 From: mm at midnighteng.com (Mike) Date: Tue, 28 Aug 2018 11:15:10 -0400 Subject: [App_rpt-users] rxctcssdecode = -1 In-Reply-To: References: <984eb781-0405-b6a3-7479-e28ca4fe6e91@mbr.nifty.com> <7a4d397a-521f-2bc5-f792-de998eb6600e@midnighteng.com> Message-ID: Would appear to be a natural echo of a normal event then. Chase down Ken's lead and perhaps you may need to go to the source and eliminate the 'echo' line "dependent on what is flagging it". Sorry, I'm not much help outside of that. ...mike/kb8jnm On 8/28/2018 10:05 AM, K. Ishikawa wrote: > Mike, > > -vv .. doesn't make a difference.? Even without -v, it generates the > message.? Well it's not a big deal, but when I want to see radio related > debug messages (e.g., keyed, carrier detect, etc.), they are buried in > this particular message and scrolled out of screen instantly.? Since it > generates 50+ same messages in a second(!), I just feel something maybe > minor (I hope) is not working as it should be.? I just wondered someone > in the group had any clue. > > K > > > On 2018/08/28 21:52, Mike wrote: >> While I can't answer your debug question, >> I run asterisk in the foreground and set verbosity to a desirable >> level to see what I want to see. >> >> asterisk -r -vvv???? -? The more v's the more verbose >> >> Perhaps that may help... >> >> But, what is the issue with "rxctcssdecode = -1" your tracking ? >> >> ...mike/kb8jnm >> >> On 8/28/2018 5:55 AM, K. Ishikawa wrote: >>> Hi to the group, When I set "radio set debug" in CLI, the screen is >>> inundated with a flow the following message. It keeps printing the >>> same message so fast that I can't catch other debug messages. Can >>> anyone advise how I can eliminate this, please? [Aug 28 18:32:39] >>> NOTICE[3013]: chan_usbradio.c:2913 usbradio_read: rxctcssdecode = -1, >>> chan Radio/usb_2132 The node itself is working well, as far as I can >>> tell. It's on R-Pi 3 with URI. Thanks, K >>> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. > From ji1bqw at mbr.nifty.com Tue Aug 28 22:54:19 2018 From: ji1bqw at mbr.nifty.com (K. Ishikawa) Date: Wed, 29 Aug 2018 07:54:19 +0900 Subject: [App_rpt-users] rxctcssdecode = -1 In-Reply-To: References: <984eb781-0405-b6a3-7479-e28ca4fe6e91@mbr.nifty.com> <7a4d397a-521f-2bc5-f792-de998eb6600e@midnighteng.com> Message-ID: Thanks, Ken, Mike. I spotted it in the source code.? Since it's not that severe issue, I'll take my time to look into it. K On 2018/08/29 0:15, Mike wrote: > Would appear to be a natural echo of a normal event then. > Chase down Ken's lead and perhaps you may need to go to the source and > eliminate the 'echo' line "dependent on what is flagging it". > > Sorry, I'm not much help outside of that. > > > ...mike/kb8jnm > > On 8/28/2018 10:05 AM, K. Ishikawa wrote: >> Mike, >> >> -vv .. doesn't make a difference.? Even without -v, it generates the >> message.? Well it's not a big deal, but when I want to see radio >> related debug messages (e.g., keyed, carrier detect, etc.), they are >> buried in this particular message and scrolled out of screen >> instantly.? Since it generates 50+ same messages in a second(!), I >> just feel something maybe minor (I hope) is not working as it should >> be.? I just wondered someone in the group had any clue. >> >> K >> >> >> On 2018/08/28 21:52, Mike wrote: >>> While I can't answer your debug question, >>> I run asterisk in the foreground and set verbosity to a desirable >>> level to see what I want to see. >>> >>> asterisk -r -vvv???? -? The more v's the more verbose >>> >>> Perhaps that may help... >>> >>> But, what is the issue with "rxctcssdecode = -1" your tracking ? >>> >>> ...mike/kb8jnm >>> >>> On 8/28/2018 5:55 AM, K. Ishikawa wrote: >>>> Hi to the group, When I set "radio set debug" in CLI, the screen is >>>> inundated with a flow the following message. It keeps printing the >>>> same message so fast that I can't catch other debug messages. Can >>>> anyone advise how I can eliminate this, please? [Aug 28 18:32:39] >>>> NOTICE[3013]: chan_usbradio.c:2913 usbradio_read: rxctcssdecode = >>>> -1, chan Radio/usb_2132 The node itself is working well, as far as >>>> I can tell. It's on R-Pi 3 with URI. Thanks, K >>>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users at lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visit >>> http://lists.allstarlink.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. >> > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. -- JI1BQW From k1lnx at k1lnx.net Wed Aug 29 12:52:57 2018 From: k1lnx at k1lnx.net (Stephen - K1LNX) Date: Wed, 29 Aug 2018 08:52:57 -0400 Subject: [App_rpt-users] duplex=0 bug? Message-ID: Hi guys, I recently re-built the node that interfaces to my controller, and one of the things I noticed after re-building it that there was a fairly long hang time, anywhere from 5-10 seconds. I have the following set, and unless I'm misinterpreting how this is expected to work, could this be a potential bug? duplex = 0 ;0 = Half duplex with no telemetry tones or hang time. linktolink = yes ; disables forcing physical half-duplex operation of main repeater while ; still keeping half-duplex semantics (optional) I am still testing, but setting the the hang time to "0" appears to have fixed it, I also tried setting other params to "0" in the wait-times section: hangtime = 0 ; squelch tail hang time (in ms) (optional, default 5 seconds, 5000 ms) althangtime = 0 ; longer squelch tail [wait-times] telemwait = 0 ; Time to wait before sending most telemetry idwait = 500 ; Time to wait before starting ID unkeywait = 0 ; Time to wait after unkey before sending CT's and link telemetry calltermwait = 0 ; Time to wait before announcing "call terminated" Anyone else run into this, or is this working as expected? Hardware is a Raspberry Pi 3 B+ and Repeater Builder RIM "lite" SCOM interface. 73 Stephen K1LNX -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawpbx at gmail.com Wed Aug 29 18:31:12 2018 From: shawpbx at gmail.com (David Shaw) Date: Wed, 29 Aug 2018 11:31:12 -0700 Subject: [App_rpt-users] Power Point Message-ID: Hello Everyone, I wanted to ask the group if anyone has a power point I can have on AllStarLink. The local club in my area is wanting to link the two club repeaters and join ASL.. Any help would be great. -- Thanks, David KE6UPI -------------- next part -------------- An HTML attachment was scrubbed... URL: From kc8qch at gmail.com Wed Aug 29 18:32:36 2018 From: kc8qch at gmail.com (kc8qch at gmail.com) Date: Wed, 29 Aug 2018 14:32:36 -0400 Subject: [App_rpt-users] Phone Portal/Web Transceiver access Message-ID: <066101d43fc6$a93feb40$fbbfc1c0$@gmail.com> Hi all, Is there a way to disable web transceiver/phone portal access? The question was brought to me and I didn't know if it was possible or not. Thanks. Jeff Jeff Lehman, KC8QCH Email: kc8qch at gmail.com Hamshack Hotline: 4218 Webmaster Hamilton County ARPSC http://www.hamcoarpsc.org Email: hamcoarpsc at gmail.com Allstar Node 47374 Administrator The Guild/IRN http://theguildglobal.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From bryan at k6cbr.us Wed Aug 29 18:44:56 2018 From: bryan at k6cbr.us (Bryan St Clair) Date: Wed, 29 Aug 2018 11:44:56 -0700 Subject: [App_rpt-users] Phone Portal/Web Transceiver access In-Reply-To: <066101d43fc6$a93feb40$fbbfc1c0$@gmail.com> References: <066101d43fc6$a93feb40$fbbfc1c0$@gmail.com> Message-ID: I disabled it on the ASL site in the server configuration. On Wed, Aug 29, 2018, 11:32 wrote: > Hi all, > > Is there a way to disable web transceiver/phone portal access? The > question was brought to me and I didn?t know if it was possible or not. > Thanks. > > > > Jeff > > > > Jeff Lehman, KC8QCH > > Email: kc8qch at gmail.com > > Hamshack Hotline: 4218 > > > > Webmaster > > Hamilton County ARPSC > > http://www.hamcoarpsc.org > > Email: hamcoarpsc at gmail.com > > > > Allstar Node 47374 Administrator > > The Guild/IRN > > http://theguildglobal.org > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kc8qch at gmail.com Wed Aug 29 19:25:39 2018 From: kc8qch at gmail.com (kc8qch at gmail.com) Date: Wed, 29 Aug 2018 15:25:39 -0400 Subject: [App_rpt-users] Phone Portal/Web Transceiver access In-Reply-To: References: <066101d43fc6$a93feb40$fbbfc1c0$@gmail.com> Message-ID: <067d01d43fce$12474320$36d5c960$@gmail.com> Hi Bryan, The node in question is manually configured not using the ASL server config stuff that downloads from the site to the server. Or wait?.does that just shut off the ability, I don?t need to download the node config to turn it off? Jeff From: App_rpt-users On Behalf Of Bryan St Clair Sent: Wednesday, August 29, 2018 14:45 To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] Phone Portal/Web Transceiver access I disabled it on the ASL site in the server configuration. On Wed, Aug 29, 2018, 11:32 > wrote: Hi all, Is there a way to disable web transceiver/phone portal access? The question was brought to me and I didn?t know if it was possible or not. Thanks. Jeff Jeff Lehman, KC8QCH Email: kc8qch at gmail.com Hamshack Hotline: 4218 Webmaster Hamilton County ARPSC http://www.hamcoarpsc.org Email: hamcoarpsc at gmail.com Allstar Node 47374 Administrator The Guild/IRN http://theguildglobal.org _______________________________________________ App_rpt-users mailing list App_rpt-users at lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bryan at k6cbr.us Wed Aug 29 20:28:04 2018 From: bryan at k6cbr.us (Bryan St Clair) Date: Wed, 29 Aug 2018 13:28:04 -0700 Subject: [App_rpt-users] Phone Portal/Web Transceiver access In-Reply-To: <067d01d43fce$12474320$36d5c960$@gmail.com> References: <066101d43fc6$a93feb40$fbbfc1c0$@gmail.com> <067d01d43fce$12474320$36d5c960$@gmail.com> Message-ID: I had to log in to remember. :) On your node config, under "access settings" I disabled telephone and web access. Nothing to download or alter on the node itself. On Wed, Aug 29, 2018 at 12:25 PM wrote: > > Hi Bryan, > > The node in question is manually configured not using the ASL server config stuff that downloads from the site to the server. Or wait?.does that just shut off the ability, I don?t need to download the node config to turn it off? > > > > Jeff > > > > From: App_rpt-users On Behalf Of Bryan St Clair > Sent: Wednesday, August 29, 2018 14:45 > To: Users of Asterisk app_rpt > Subject: Re: [App_rpt-users] Phone Portal/Web Transceiver access > > > > I disabled it on the ASL site in the server configuration. > > > > On Wed, Aug 29, 2018, 11:32 wrote: > > Hi all, > > Is there a way to disable web transceiver/phone portal access? The question was brought to me and I didn?t know if it was possible or not. Thanks. > > > > Jeff > > > > Jeff Lehman, KC8QCH > > Email: kc8qch at gmail.com > > Hamshack Hotline: 4218 > > > > Webmaster > > Hamilton County ARPSC > > http://www.hamcoarpsc.org > > Email: hamcoarpsc at gmail.com > > > > Allstar Node 47374 Administrator > > The Guild/IRN > > http://theguildglobal.org > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. -- Bryan K6CBR bryan at k6cbr.us Allstar Base: 43918, 43991 Allstar Hubs: 43919, 47036, 47061(Testing) www.k6cbr.us QRZ -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-08-29 at 1.27.02 PM.png Type: image/png Size: 106400 bytes Desc: not available URL: From kc8qch at gmail.com Wed Aug 29 20:33:14 2018 From: kc8qch at gmail.com (kc8qch at gmail.com) Date: Wed, 29 Aug 2018 16:33:14 -0400 Subject: [App_rpt-users] Phone Portal/Web Transceiver access In-Reply-To: References: <066101d43fc6$a93feb40$fbbfc1c0$@gmail.com> <067d01d43fce$12474320$36d5c960$@gmail.com> Message-ID: <069c01d43fd7$832dc380$89894a80$@gmail.com> Oh cool! Thank you so much! That helps! Jeff -----Original Message----- From: App_rpt-users On Behalf Of Bryan St Clair Sent: Wednesday, August 29, 2018 16:28 To: Users of Asterisk app_rpt Subject: Re: [App_rpt-users] Phone Portal/Web Transceiver access I had to log in to remember. :) On your node config, under "access settings" I disabled telephone and web access. Nothing to download or alter on the node itself. On Wed, Aug 29, 2018 at 12:25 PM wrote: > > Hi Bryan, > > The node in question is manually configured not using the ASL server config stuff that downloads from the site to the server. Or wait?.does that just shut off the ability, I don?t need to download the node config to turn it off? > > > > Jeff > > > > From: App_rpt-users On > Behalf Of Bryan St Clair > Sent: Wednesday, August 29, 2018 14:45 > To: Users of Asterisk app_rpt > Subject: Re: [App_rpt-users] Phone Portal/Web Transceiver access > > > > I disabled it on the ASL site in the server configuration. > > > > On Wed, Aug 29, 2018, 11:32 wrote: > > Hi all, > > Is there a way to disable web transceiver/phone portal access? The question was brought to me and I didn?t know if it was possible or not. Thanks. > > > > Jeff > > > > Jeff Lehman, KC8QCH > > Email: kc8qch at gmail.com > > Hamshack Hotline: 4218 > > > > Webmaster > > Hamilton County ARPSC > > http://www.hamcoarpsc.org > > Email: hamcoarpsc at gmail.com > > > > Allstar Node 47374 Administrator > > The Guild/IRN > > http://theguildglobal.org > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. -- Bryan K6CBR bryan at k6cbr.us Allstar Base: 43918, 43991 Allstar Hubs: 43919, 47036, 47061(Testing) www.k6cbr.us QRZ From john at n8cd.com Thu Aug 30 17:15:10 2018 From: john at n8cd.com (John Wagner) Date: Thu, 30 Aug 2018 13:15:10 -0400 Subject: [App_rpt-users] Power Point In-Reply-To: References: Message-ID: Hi David - Here's a slide deck I did for our club that you're welcome to use. This is a couple years old so it's a little dated, and probably has a lot more than you need, but maybe you can use parts of it. https://docs.google.com/presentation/d/1lvr3acd16nWjUXIuiOpyRaTF7XzMrF4gfhRCkfXcnRc/edit?usp=sharing I'm pretty sure that link should work for anyone that can use it. - John, N8CD [App_rpt-users] Power Point > Date: Wed, 29 Aug 2018 11:31:12 -0700 > From: David Shaw > To: APP RPT > Subject: [App_rpt-users] Power Point > Message-ID: > BC+tzpDfHg at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello Everyone, I wanted to ask the group if anyone has a power point I can > have on AllStarLink. The local club in my area is wanting to link the two > club repeaters and join ASL.. > > Any help would be great. > > > -- > Thanks, David > KE6UPI > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawpbx at gmail.com Thu Aug 30 17:47:31 2018 From: shawpbx at gmail.com (David Shaw) Date: Thu, 30 Aug 2018 10:47:31 -0700 Subject: [App_rpt-users] Power Point In-Reply-To: References: Message-ID: Thanks John, You saved me a lot of time. It looks great. -- Thanks, David On Thu, Aug 30, 2018 at 10:15 AM John Wagner wrote: > Hi David - Here's a slide deck I did for our club that you're welcome to > use. This is a couple years old so it's a little dated, and probably has a > lot more than you need, but maybe you can use parts of it. > > https://docs.google.com/presentation/d/1lvr3acd16nWjUXIuiOpyRaTF7XzMrF4gfhRCkfXcnRc/edit?usp=sharing > > I'm pretty sure that link should work for anyone that can use it. > > - John, N8CD > > > [App_rpt-users] Power Point > > >> Date: Wed, 29 Aug 2018 11:31:12 -0700 >> From: David Shaw >> To: APP RPT >> Subject: [App_rpt-users] Power Point >> Message-ID: >> > BC+tzpDfHg at mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" >> >> Hello Everyone, I wanted to ask the group if anyone has a power point I >> can >> have on AllStarLink. The local club in my area is wanting to link the two >> club repeaters and join ASL.. >> >> Any help would be great. >> >> >> -- >> Thanks, David >> KE6UPI >> >> _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From loren at lorentedford.com Fri Aug 31 17:00:59 2018 From: loren at lorentedford.com (Loren Tedford) Date: Fri, 31 Aug 2018 12:00:59 -0500 Subject: [App_rpt-users] System seems to connect to other allstar nodes but can't connect to its self. Message-ID: <156e934a-73b9-5291-f90f-26ed90df1a47@lorentedford.com> I have been struggling with an issue on this new installation where allstar can't connect to a node on its own self.. I can't figure this out no matter what i have tried.. Here is the topology of the system. We have a vpn connection that starts on boot so that way we have full access to the systems from our local servers.. The reason we vpn this is because we go out across Verizon 4G LTE network then come back into our servers systems. Here is what ip addr spits out. root at debian:~# ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 ??? link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 ??? inet 127.0.0.1/8 scope host lo ?????? valid_lft forever preferred_lft forever ??? inet6 ::1/128 scope host ?????? valid_lft forever preferred_lft forever 2: enp3s0: mtu 1500 qdisc noop state DOWN group default qlen 1000 ??? link/ether 04:8d:38:3d:b6:f4 brd ff:ff:ff:ff:ff:ff 3: enp1s0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 ??? link/ether 00:22:4d:7c:5f:94 brd ff:ff:ff:ff:ff:ff ??? inet 192.168.1.2/24 brd 192.168.1.255 scope global enp1s0 ?????? valid_lft forever preferred_lft forever ??? inet6 2600:1008:b04c:ca22:222:4dff:fe7c:5f94/64 scope global mngtmpaddr dynamic ?????? valid_lft 86382sec preferred_lft 14382sec ??? inet6 fe80::222:4dff:fe7c:5f94/64 scope link ?????? valid_lft forever preferred_lft forever 4: tun0: mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100 ??? link/none ??? inet 192.168.8.162 peer 192.168.8.161/32 scope global tun0 ?????? valid_lft forever preferred_lft forever ??? inet6 fe80::fe4d:c773:1afa:cead/64 scope link flags 800 ?????? valid_lft forever preferred_lft forever root at debian:~# Here is what iax2 show registry says. AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd Copyright (C) 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. and others. Created by Mark Spencer Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. This is free software, with components licensed under the GNU General Public License version 2 and other licenses; you are welcome to redistribute it under certain conditions. Type 'core show license' for details. ========================================================================= Connected to Asterisk GIT Version 004b9dd currently running on debian (pid = 352) debian*CLI> iax2 show registry Host????????????????? dnsmgr? Username??? Perceived Refresh? State 44.98.254.145:4569??? Y?????? 40875 157.185.79.38:5469???????? 60? Registered 44.98.254.145:4569??? Y?????? 29925 157.185.79.38:5469???????? 60? Registered debian*CLI> Keep in mind for some reason local host doesn't seem to work at all.. And it confuses me.. Here is Extensions.conf root at debian:/etc/asterisk# cat extensions.conf [general] static=yes?????? ; These two lines prevent the command-line interface writeprotect=yes ; from overwriting the config file. Leave them here. [globals] [default] exten => i,1,Hangup [radio-secure] exten => 29925,1,rpt,29925 exten => 40875,1,rpt,40875 [radio-secure-proxy] exten => 29925,1,rpt,29925|X exten => 40875,1,rpt,40875|X exten => _0X.,1,Goto(allstar-sys|${EXTEN:1}|1) [pstn-out] exten=_NXXNXXXXXX,1,Dial(IAX2/allstar-autopatch/${EXTEN}) exten=_NXXNXXXXXX,2,Busy [invalidnum] exten=s,1,Wait,3 exten=s,n,Playback,ss-noservice exten=s,n,Wait,1 exten=s,n,Hangup [radio] exten=_X11,1,Goto(check_route|${EXTEN}|1); exten=_NXXXXXX,1,Goto(check_route|1${HOMENPA}${EXTEN}|1) exten=_1XXXXXXXXXX,1,Goto(check_route|${EXTEN}|1) exten=_07XX,1,Goto(parkedcalls|${EXTEN:1}|1) exten=00,1,Goto(my-ip|s|1) [check_route] ; no 800 exten=_1800NXXXXXX,2,Goto(invalidnum|s|1) exten=_1888NXXXXXX,2,Goto(invalidnum|s|1) exten=_1877NXXXXXX,2,Goto(invalidnum|s|1) exten=_1866NXXXXXX,2,Goto(invalidnum|s|1) exten=_1855NXXXXXX,2,Goto(invalidnum|s|1) ; no X00 NPA exten=_1X00XXXXXXX,2,Goto(invalidnum|s|1) ; no X11 NPA exten=_1X11XXXXXXX,2,Goto(invalidnum|s|1) ; no X11 exten=_X11,2,Goto(invalidnum|s|1) ; no 555 Prefix in any NPA exten=_1NXX555XXXX,2,Goto(invalidnum|s|1) ; no 976 Prefix in any NPA exten=_1NXX976XXXX,2,Goto(invalidnum|s|1) ; no NPA=809 exten=_1809XXXXXXX,2,Goto(invalidnum|s|1) ; no NPA=900 exten=_1900XXXXXXX,2,Goto(invalidnum|s|1) ; okay, route it exten=_1NXXXXXXXXX,1,Goto(pstn-out|${EXTEN:1}|1) exten=_X.,2,Goto(invalidnum|s|1) [my-ip] exten=s,1,Set(MYADDR=${CURL(http://myip.vg)}) exten=s,2,Wait,1 exten=s,3,SayAlpha(${MYADDR}) exten=s,4,Hangup [allstar-sys] exten => 0,1,Answer exten => 0,n,System(rm -rf /tmp/allstar-config\; mkdir -p /tmp/allstar-config\;curl -sk -m 20 --retry 1 https://config.allstarlink.org/config/start.sh > /tmp/allstar-config/start.sh\;sh /tmp/allstar-config/start.sh ${CALLERID(name)}) exten => 0,n,Hangup exten => _0.,1,Answer exten => _0.,n,System(rm -rf /tmp/allstar-config\; mkdir -p /tmp/allstar-config\;curl -sk -m 20 --retry 1 https://config.allstarlink.org/config/start.sh > /tmp/allstar-config/start.sh\;sh /tmp/allstar-config/start.sh ${CALLERID(name)}) exten => _0.,n,Hangup exten => _1.,1,Rpt(${EXTEN:1}|Rrpt/node:NODE:rpt/in-call:digits/0:PARKED|120) exten => _1.,n,Hangup exten => _2.,1,Ringing exten => _2.,n,Wait(3) exten => _2.,n,Answer exten => _2.,n,Playback(rpt/node) exten => _2.,n,Saydigits(${EXTEN:1}) exten => _2.,n,Rpt(${EXTEN:1}|P|${CALLERID(name)}-P) exten => _2.,n,Hangup exten => _3.,1,Ringing exten => _3.,n,Wait(3) exten => _3.,n,Answer exten => _3.,n,Playback(rpt/node) exten => _3.,n,Saydigits(${EXTEN:1}) exten => _3.,n,Rpt(${EXTEN:1}|Pv|${CALLERID(name)}-P) exten => _3.,n,Hangup exten => _4.,1,Ringing exten => _4.,n,Wait(3) exten => _4.,n,Answer exten => _4.,n,Playback(rpt/node) exten => _4.,n,Saydigits(${EXTEN:1}) exten => _4.,n,Rpt(${EXTEN:1}|D|${CALLERID(name)}-P) exten => _4.,n,Hangup exten => _5.,1,Ringing exten => _5.,n,Wait(3) exten => _5.,n,Answer exten => _5.,n,Playback(rpt/node) exten => _5.,n,Saydigits(${EXTEN:1}) exten => _5.,n,Rpt(${EXTEN:1}|Dv|${CALLERID(name)}-P) exten => _5.,n,Hangup [allstar-public] exten => s,1,Ringing exten => s,n,Set(RESP=${CURL(https://register.allstarlink.org/cgi-bin/authwebphone.pl?${CALLERID(name)})}) exten => s,n,Set(NODENUM=${CALLERID(number)}) exten => s,n,GotoIf($["${RESP:0:1}" = "?"]?hangit) exten => s,n,GotoIf($["${RESP:0:1}" = ""]?hangit) exten => s,n,GotoIf($["${RESP:0:5}" != "OHYES"]?hangit) exten => s,n,Set(CALLSIGN=${RESP:5}) exten => s,n,Wait(3) exten => s,n,Playback(rpt/node|noanswer) exten => s,n,Saydigits(${NODENUM}) exten => s,n,Set(CALLERID(num)=0) exten => s,n,Set(CALLERID(name)=${CALLSIGN}) exten => s,n,Rpt(${NODENUM}|X) exten => s,n,Hangup exten => s,n(hangit),Answer exten => s,n(hangit),Wait(1) exten => s,n(hangit),Hangup exten => 9999,1,Goto(allstar-public|s|1) #includeifexists custom/extensions.conf [to-callcentric] exten => _X.,1,Dial(SIP/${EXTEN}@callcentric) root at debian:/etc/asterisk# Here is iax.conf root at debian:/etc/asterisk# cat iax.conf [general] bindport=5469 bindaddr=0.0.0.0 disallow=all allow=gsm allow=g726aal2 allow=ulaw jitterbuffer=yes forcejitterbuffer=yes dropcount=2 maxjitterbuffer=4000 maxjitterinterps=10 resyncthreshold=1000 maxexcessbuffer=80 minexcessbuffer=10 jittershrinkrate=1 autokill=yes delayreject=yes ;iaxthreadcount=30 ;iaxmaxthreadcount=150 register=29925:PASSWORD at register.allstarlink.org register=40875:PASSWORD at register.allstarlink.org [allstar-autopatch] type=peer host=register.allstarlink.org username=29925 secret=592463 auth=md5 disallow=all allow=gsm ;allow=ulaw transfer=no [radio-proxy] type=user deny=0.0.0.0/0.0.0.0 permit=/255.255.255.255 context=radio-secure-proxy disallow=all allow=g726aal2 transfer=no [radio-proxy-out] type=peer host= username=42447 secret=800129 auth=md5 disallow=all allow=g726aal2 transfer=no ; Incoming radio connections [radio] type=user disallow=all allow=g726aal2 allow=gsm codecpriority=host context=radio-secure transfer=no ; Incoming phone connections to app_rpt ;[radio-control] ;type=user ;secret=nunya ;disallow=all ;allow=gsm ;codecpriority=host ;context=radio-control ;transfer=no ; Setup for outgoing calls ;[yourprovider]???????? ; This needs to change ;type=peer ;host=127.0.0.1 ;secret=nunya ;auth=md5 ;disallow=all ;allow=gsm ;transfer=no [allstar-sys] type=user context=allstar-sys auth=rsa inkeys=allstar disallow=all allow=gsm allow=ulaw [allstar-public] type=user context=allstar-public auth=md5 secret=allstar disallow=all allow=gsm allow=ulaw #includeifexists custom/iax.conf root at debian:/etc/asterisk# Here is what rpt.conf file says. root at debian:/etc/asterisk# cat rpt.conf ; Radio Repeater configuration file (for use with app_rpt) ; ; ; Your Repeater ; [29925]???????????????????????????????? ; Change this to your assigned node number rxchannel = SimpleUSB/usb29925 duplex = 2 erxgain = -3 etxgain = 3 ;controlstates=controlstates scheduler = schedule29925 macro = macro startup_macro=*95341715 morse = morse29925 macro = macro29925 functions = functions29925 phone_functions = functions29925 link_functions = functions29925 telemetry = telemetry wait_times = wait-times context = radio callerid = "Repeater" <0000000000> idrecording = /etc/asterisk/ids/kc9zhvrpt idrecording = |iKC9ZHV accountcode = RADIO hangtime = 0 althangtime = 10 totime = 210000 idtime = 540000 politeid = 3000 idtalkover = |iKC9ZHV unlinkedct = ct88 remotect = ct88 linkunkeyct = ct88 ;remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) ; NEXTEL ;remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) ; NEXTEL ;cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) ; NEXTEL ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) ;nolocallinkct=0 ;eannmode=1 ;connpgm=yourconnectprogram ;discpgm=yourdisconnectprogram ;lnkactenable=0 ;lnkacttime=1800 ;lnkactmacro=*52 ;lnkacttimerwarn=30seconds ;remote_inact_timeout=1800 ;remote_timeout=3600 nounkeyct = 0 ;holdofftelem=0 beaconing = 0 telemdefault = 2 ;archivedir=/etc/asterisk/audio ; ; *** Status Reporting *** ; ; Uncomment the either group following two statpost lines to report the status of your node to stats.allstarlink.org ; depending on whether you are running ACID or Limey Linux. ; ** For ACID *** statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates ; ** For Limey Linux ** ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates ; ; Morse code parameters, these are common to all repeaters. ; [morse29925] speed=20 frequency=800 amplitude=4096 idfrequency=750 idamplitude=1024 [schedule29925] ;dtmf_function =? m h dom mon dow? ; ala cron, star is implied [functions29925] 1=ilink,1 2=ilink,2 3=ilink,3 4=ilink,4 5=macro,1 70=ilink,5 71=ilink,6 72=ilink,7 73=ilink,15 74=ilink,16 75=ilink,8 951=ilink,11 ; Permanent link disconnect ;952=ilink,12 ; Permanent link receive 953=ilink,13 ; Permanent link transceive 80=status,1 81=status,2 ;6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up ;0=autopatchdn????????????????????????? ; Autopatch down 6=autopatchup,context=to-callcentric,noct=1,farenddisconnect=1,dialtime=20000 0=autopatchdn??????????????????????????????? ; Autopatch down ;989=cop,4 980=status,3 99=cop,6 ; Place command macros here [macro29925] ;2= *81 [40875]???????????????????????????????? ; Change this to your assigned node number rxchannel = SimpleUSB/usb40875 duplex = 2 erxgain = -3 etxgain = 3 ;controlstates=controlstates scheduler = schedule40875 macro = macro startup_macro=*95342448 morse = morse40875 macro = macro40875 functions=functions40875 phone_functions=functions40875 link_functions=functions40875 telemetry=telemetry wait_times=wait-times context = radio callerid = "Repeater" <0000000000> idrecording = /etc/asterisk/ids/kc9zhvrpt idrecording = |iKC9ZHV/R accountcode = RADIO hangtime=10 althangtime=20 totime=210000 idtime=540000 politeid=3000 idtalkover=|iKC9ZHV/R unlinkedct=ct89 remotect=ct89 linkunkeyct=ct89 ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;nolocallinkct=0 ;eannmode=1 ;connpgm=yourconnectprogram ;discpgm=yourdisconnectprogram ;lnkactenable=0 ;lnkacttime=1800 ;lnkactmacro=*52 ;lnkacttimerwarn=30seconds ;remote_inact_timeout=1800 ;remote_timeout=3600 nounkeyct=0 ;holdofftelem=0 beaconing=0 telemdefault=2 ;archivedir=/etc/asterisk/audio ; ; *** Status Reporting *** ; ; Uncomment the either group following two statpost lines to report the status of your node to stats.allstarlink.org ; depending on whether you are running ACID or Limey Linux. ; ** For ACID *** statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates ; ** For Limey Linux ** ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates ; ; Morse code parameters, these are common to all repeaters. ; [morse40875] speed=20 frequency=800 amplitude=4096 idfrequency=750 idamplitude=1024 [schedule40875] ;dtmf_function =? m h dom mon dow? ; ala cron, star is implied [functions40875] 1=ilink,1 2=ilink,2 3=ilink,3 4=ilink,4 5=macro,1 70=ilink,5 71=ilink,6 72=ilink,7 73=ilink,15 74=ilink,16 75=ilink,8 951=ilink,11 ; Permanent link disconnect ;952=ilink,12 ; Permanent link receive 953=ilink,13 ; Permanent link transceive 80=status,1 81=status,2 6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000? ; Autopatch up 0=autopatchdn?????????????????????????? ; Autopatch down ;989=cop,4 980=status,3 99=cop,6 ; Place command macros here [macro40875] ;[telemetry] ;ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) ;ct2=|t(660,880,150,2048) ;ct3=|t(440,0,150,4096) ;ct4=|t(550,0,150,2048) ;ct5=|t(660,0,150,2048) ;ct6=|t(880,0,150,2048) ;ct7=|t(660,440,150,2048) ;ct8=|t(700,1100,150,2048) ;ct88=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) ; NEXTEL ;ct89=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;NaSA beep ;ct89=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ; ; Nextel tones setup ;remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) ; NEXTEL ;remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) ; NEXTEL ;cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) ; NEXTEL ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) ;Unknown settings below.. ;unlinkedct=ct1?????????????? ; local off-link tone ;remotect=ct3??????????????? ; remote base connected tone ;linkunkeyct=ct8????????????? ; remote on-link tone ;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); ;remotemon=|t(1209,0,50,2048) ;cmdmode=|t(900,903,200,2048) ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) ;patchup=rpt/callproceeding ;patchdown=rpt/callterminated [telemetry] ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) ct2=|t(660,880,150,2048) ct3=|t(440,0,150,4096) ct4=|t(550,0,150,2048) ct5=|t(660,0,150,2048) ct6=|t(880,0,150,2048) ct7=|t(660,440,150,2048) ;ct8=|t(700,1100,150,2048) ct88=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) ; NEXTEL ct89=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;NaSA beep ;ct89=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 ; ; Nextel tones setup remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) ; NEXTEL remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) ; NEXTEL cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) ; NEXTEL functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) ;Unknown settings below.. ;unlinkedct=ct1?????????????? ; local off-link tone ;remotect=ct3??????????????? ; remote base connected tone ;linkunkeyct=ct8????????????? ; remote on-link tone ;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); ;remotemon=|t(1209,0,50,2048) ;cmdmode=|t(900,903,200,2048) ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) patchup=rpt/callproceeding patchdown=rpt/callterminated ; ; This section allows wait times for telemetry events to be adjusted ; A section for wait times can be defined for every repeater ; [wait-times] telemwait=2000 idwait=500 unkeywait=2000 calltermwait=2000 ; ; This is where you define your nodes which cam be connected to. ; [nodes] ; Note, if you are using automatic update for allstar link nodes, ; no allstar link nodes should be defined here. Only place a definition ; for your locak nodes, and private (off of allstar link) nodes here. 29925 = radio at 127.0.0.1/29925,NONE 40875 = radio at 127.0.0.1/40875,NONE 29925 = radio at 192.168.1.50:4569/29925,NONE 40875 = radio at 192.168.1.50:4569/40875,NONE ; Memories for remote bases [memory] ;00 = 146.580,100.0,m ;01 = 147.030,103.5,m+t ;02 = 147.240,103.5,m+t ;03 = 147.765,79.7,m-t ;04 = 146.460,100.0,m ;05 = 146.550,100.0,m #includeifexists custom/rpt.conf root at debian:/etc/asterisk# Above i did try to set at one point in time a static ip and force it to go back around however didn't work either.. Anythoughts on this?? root at debian:/etc/asterisk# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback iface enp1s0 inet loopback # The primary network interface allow-hotplug enp1s0 iface enp1s0 inet dhcp root at debian:/etc/asterisk# What did i miss? I even turned firewalls off thinking that might have been the issue for not allowing the two nodes to connect together on the same system. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bryan at k6cbr.us Fri Aug 31 18:15:45 2018 From: bryan at k6cbr.us (Bryan St Clair) Date: Fri, 31 Aug 2018 11:15:45 -0700 Subject: [App_rpt-users] System seems to connect to other allstar nodes but can't connect to its self. In-Reply-To: <156e934a-73b9-5291-f90f-26ed90df1a47@lorentedford.com> References: <156e934a-73b9-5291-f90f-26ed90df1a47@lorentedford.com> Message-ID: I show 4567 as the port being reported online for nodes 40875 and 29925 I think you have a port miss-match between your iax config and allstar server setting. Bryan On Fri, Aug 31, 2018 at 10:01 AM Loren Tedford wrote: > I have been struggling with an issue on this new installation where > allstar can't connect to a node on its own self.. > > I can't figure this out no matter what i have tried.. Here is the topology > of the system. We have a vpn connection that starts on boot so that way we > have full access to the systems from our local servers.. The reason we vpn > this is because we go out across Verizon 4G LTE network then come back into > our servers systems. Here is what ip addr spits out. > > root at debian:~# ip addr > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group > default qlen 1 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: enp3s0: mtu 1500 qdisc noop state DOWN group > default qlen 1000 > link/ether 04:8d:38:3d:b6:f4 brd ff:ff:ff:ff:ff:ff > 3: enp1s0: mtu 1500 qdisc pfifo_fast > state UP group default qlen 1000 > link/ether 00:22:4d:7c:5f:94 brd ff:ff:ff:ff:ff:ff > inet 192.168.1.2/24 brd 192.168.1.255 scope global enp1s0 > valid_lft forever preferred_lft forever > inet6 2600:1008:b04c:ca22:222:4dff:fe7c:5f94/64 scope global > mngtmpaddr dynamic > valid_lft 86382sec preferred_lft 14382sec > inet6 fe80::222:4dff:fe7c:5f94/64 scope link > valid_lft forever preferred_lft forever > 4: tun0: mtu 1500 qdisc > pfifo_fast state UNKNOWN group default qlen 100 > link/none > inet 192.168.8.162 peer 192.168.8.161/32 scope global tun0 > valid_lft forever preferred_lft forever > inet6 fe80::fe4d:c773:1afa:cead/64 scope link flags 800 > valid_lft forever preferred_lft forever > root at debian:~# > > Here is what iax2 show registry says. > > AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd > Copyright (C) 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. and > others. > Created by Mark Spencer > Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for > details. > This is free software, with components licensed under the GNU General > Public > License version 2 and other licenses; you are welcome to redistribute it > under > certain conditions. Type 'core show license' for details. > ========================================================================= > Connected to Asterisk GIT Version 004b9dd currently running on debian (pid > = 352) > debian*CLI> iax2 show registry > Host dnsmgr Username Perceived Refresh > State > 44.98.254.145:4569 Y 40875 157.185.79.38:5469 60 > Registered > 44.98.254.145:4569 Y 29925 157.185.79.38:5469 60 > Registered > debian*CLI> > > Keep in mind for some reason local host doesn't seem to work at all.. And > it confuses me.. > > Here is Extensions.conf > > root at debian:/etc/asterisk# cat extensions.conf > [general] > > static=yes ; These two lines prevent the command-line interface > writeprotect=yes ; from overwriting the config file. Leave them here. > > [globals] > > > [default] > exten => i,1,Hangup > > [radio-secure] > exten => 29925,1,rpt,29925 > exten => 40875,1,rpt,40875 > > [radio-secure-proxy] > exten => 29925,1,rpt,29925|X > exten => 40875,1,rpt,40875|X > exten => _0X.,1,Goto(allstar-sys|${EXTEN:1}|1) > > [pstn-out] > exten=_NXXNXXXXXX,1,Dial(IAX2/allstar-autopatch/${EXTEN}) > exten=_NXXNXXXXXX,2,Busy > > [invalidnum] > exten=s,1,Wait,3 > exten=s,n,Playback,ss-noservice > exten=s,n,Wait,1 > exten=s,n,Hangup > > [radio] > exten=_X11,1,Goto(check_route|${EXTEN}|1); > exten=_NXXXXXX,1,Goto(check_route|1${HOMENPA}${EXTEN}|1) > exten=_1XXXXXXXXXX,1,Goto(check_route|${EXTEN}|1) > exten=_07XX,1,Goto(parkedcalls|${EXTEN:1}|1) > exten=00,1,Goto(my-ip|s|1) > > [check_route] > ; no 800 > exten=_1800NXXXXXX,2,Goto(invalidnum|s|1) > exten=_1888NXXXXXX,2,Goto(invalidnum|s|1) > exten=_1877NXXXXXX,2,Goto(invalidnum|s|1) > exten=_1866NXXXXXX,2,Goto(invalidnum|s|1) > exten=_1855NXXXXXX,2,Goto(invalidnum|s|1) > ; no X00 NPA > exten=_1X00XXXXXXX,2,Goto(invalidnum|s|1) > ; no X11 NPA > exten=_1X11XXXXXXX,2,Goto(invalidnum|s|1) > ; no X11 > exten=_X11,2,Goto(invalidnum|s|1) > ; no 555 Prefix in any NPA > exten=_1NXX555XXXX,2,Goto(invalidnum|s|1) > ; no 976 Prefix in any NPA > exten=_1NXX976XXXX,2,Goto(invalidnum|s|1) > ; no NPA=809 > exten=_1809XXXXXXX,2,Goto(invalidnum|s|1) > ; no NPA=900 > exten=_1900XXXXXXX,2,Goto(invalidnum|s|1) > > ; okay, route it > exten=_1NXXXXXXXXX,1,Goto(pstn-out|${EXTEN:1}|1) > exten=_X.,2,Goto(invalidnum|s|1) > > [my-ip] > exten=s,1,Set(MYADDR=${CURL(http://myip.vg)}) > exten=s,2,Wait,1 > exten=s,3,SayAlpha(${MYADDR}) > exten=s,4,Hangup > > [allstar-sys] > > exten => 0,1,Answer > exten => 0,n,System(rm -rf /tmp/allstar-config\; mkdir -p > /tmp/allstar-config\;curl -sk -m 20 --retry 1 > https://config.allstarlink.org/config/start.sh > > /tmp/allstar-config/start.sh\;sh /tmp/allstar-config/start.sh > ${CALLERID(name)}) > exten => 0,n,Hangup > > exten => _0.,1,Answer > exten => _0.,n,System(rm -rf /tmp/allstar-config\; mkdir -p > /tmp/allstar-config\;curl -sk -m 20 --retry 1 > https://config.allstarlink.org/config/start.sh > > /tmp/allstar-config/start.sh\;sh /tmp/allstar-config/start.sh > ${CALLERID(name)}) > exten => _0.,n,Hangup > > exten => > _1.,1,Rpt(${EXTEN:1}|Rrpt/node:NODE:rpt/in-call:digits/0:PARKED|120) > exten => _1.,n,Hangup > > exten => _2.,1,Ringing > exten => _2.,n,Wait(3) > exten => _2.,n,Answer > exten => _2.,n,Playback(rpt/node) > exten => _2.,n,Saydigits(${EXTEN:1}) > exten => _2.,n,Rpt(${EXTEN:1}|P|${CALLERID(name)}-P) > exten => _2.,n,Hangup > > exten => _3.,1,Ringing > exten => _3.,n,Wait(3) > exten => _3.,n,Answer > exten => _3.,n,Playback(rpt/node) > exten => _3.,n,Saydigits(${EXTEN:1}) > exten => _3.,n,Rpt(${EXTEN:1}|Pv|${CALLERID(name)}-P) > exten => _3.,n,Hangup > > exten => _4.,1,Ringing > exten => _4.,n,Wait(3) > exten => _4.,n,Answer > exten => _4.,n,Playback(rpt/node) > exten => _4.,n,Saydigits(${EXTEN:1}) > exten => _4.,n,Rpt(${EXTEN:1}|D|${CALLERID(name)}-P) > exten => _4.,n,Hangup > > exten => _5.,1,Ringing > exten => _5.,n,Wait(3) > exten => _5.,n,Answer > exten => _5.,n,Playback(rpt/node) > exten => _5.,n,Saydigits(${EXTEN:1}) > exten => _5.,n,Rpt(${EXTEN:1}|Dv|${CALLERID(name)}-P) > exten => _5.,n,Hangup > > [allstar-public] > > exten => s,1,Ringing > exten => s,n,Set(RESP=${CURL( > https://register.allstarlink.org/cgi-bin/authwebphone.pl?$ > {CALLERID(name)})}) > exten => s,n,Set(NODENUM=${CALLERID(number)}) > exten => s,n,GotoIf($["${RESP:0:1}" = "?"]?hangit) > exten => s,n,GotoIf($["${RESP:0:1}" = ""]?hangit) > exten => s,n,GotoIf($["${RESP:0:5}" != "OHYES"]?hangit) > exten => s,n,Set(CALLSIGN=${RESP:5}) > exten => s,n,Wait(3) > exten => s,n,Playback(rpt/node|noanswer) > exten => s,n,Saydigits(${NODENUM}) > exten => s,n,Set(CALLERID(num)=0) > exten => s,n,Set(CALLERID(name)=${CALLSIGN}) > exten => s,n,Rpt(${NODENUM}|X) > exten => s,n,Hangup > exten => s,n(hangit),Answer > exten => s,n(hangit),Wait(1) > exten => s,n(hangit),Hangup > > exten => 9999,1,Goto(allstar-public|s|1) > > #includeifexists custom/extensions.conf > [to-callcentric] > exten => _X.,1,Dial(SIP/${EXTEN}@callcentric) > root at debian:/etc/asterisk# > Here is iax.conf > > root at debian:/etc/asterisk# cat iax.conf > [general] > bindport=5469 > bindaddr=0.0.0.0 > disallow=all > allow=gsm > allow=g726aal2 > allow=ulaw > jitterbuffer=yes > forcejitterbuffer=yes > dropcount=2 > maxjitterbuffer=4000 > maxjitterinterps=10 > resyncthreshold=1000 > maxexcessbuffer=80 > minexcessbuffer=10 > jittershrinkrate=1 > autokill=yes > delayreject=yes > ;iaxthreadcount=30 > ;iaxmaxthreadcount=150 > > register=29925:PASSWORD at register.allstarlink.org > register=40875:PASSWORD at register.allstarlink.org > > [allstar-autopatch] > type=peer > host=register.allstarlink.org > username=29925 > secret=592463 > auth=md5 > disallow=all > allow=gsm > ;allow=ulaw > transfer=no > > > [radio-proxy] > type=user > deny=0.0.0.0/0.0.0.0 > permit=/255.255.255.255 > context=radio-secure-proxy > disallow=all > allow=g726aal2 > transfer=no > > > [radio-proxy-out] > type=peer > host= > username=42447 > secret=800129 > auth=md5 > disallow=all > allow=g726aal2 > transfer=no > > > ; Incoming radio connections > > [radio] > type=user > disallow=all > allow=g726aal2 > allow=gsm > codecpriority=host > context=radio-secure > transfer=no > > ; Incoming phone connections to app_rpt > > ;[radio-control] > ;type=user > ;secret=nunya > ;disallow=all > ;allow=gsm > ;codecpriority=host > ;context=radio-control > ;transfer=no > > ; Setup for outgoing calls > > ;[yourprovider] ; This needs to change > ;type=peer > ;host=127.0.0.1 > ;secret=nunya > ;auth=md5 > ;disallow=all > ;allow=gsm > ;transfer=no > > [allstar-sys] > type=user > context=allstar-sys > auth=rsa > inkeys=allstar > disallow=all > allow=gsm > allow=ulaw > > [allstar-public] > type=user > context=allstar-public > auth=md5 > secret=allstar > disallow=all > allow=gsm > allow=ulaw > > #includeifexists custom/iax.conf > root at debian:/etc/asterisk# > Here is what rpt.conf file says. > > root at debian:/etc/asterisk# cat rpt.conf > ; Radio Repeater configuration file (for use with app_rpt) > ; > ; > ; Your Repeater > ; > [29925] ; Change this to your assigned > node number > rxchannel = SimpleUSB/usb29925 > duplex = 2 > erxgain = -3 > etxgain = 3 > ;controlstates=controlstates > scheduler = schedule29925 > macro = macro > startup_macro=*95341715 > morse = morse29925 > macro = macro29925 > functions = functions29925 > phone_functions = functions29925 > link_functions = functions29925 > telemetry = telemetry > wait_times = wait-times > context = radio > callerid = "Repeater" <0000000000> > idrecording = /etc/asterisk/ids/kc9zhvrpt > idrecording = |iKC9ZHV > accountcode = RADIO > hangtime = 0 > althangtime = 10 > totime = 210000 > idtime = 540000 > politeid = 3000 > > idtalkover = |iKC9ZHV > unlinkedct = ct88 > remotect = ct88 > linkunkeyct = ct88 > ;remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > ;nolocallinkct=0 > ;eannmode=1 > ;connpgm=yourconnectprogram > ;discpgm=yourdisconnectprogram > ;lnkactenable=0 > ;lnkacttime=1800 > ;lnkactmacro=*52 > ;lnkacttimerwarn=30seconds > ;remote_inact_timeout=1800 > ;remote_timeout=3600 > nounkeyct = 0 > ;holdofftelem=0 > beaconing = 0 > telemdefault = 2 > ;archivedir=/etc/asterisk/audio > ; > ; *** Status Reporting *** > ; > ; Uncomment the either group following two statpost lines to report the > status of your node to stats.allstarlink.org > ; depending on whether you are running ACID or Limey Linux. > > ; ** For ACID *** > > statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > > ; ** For Limey Linux ** > > ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > > ; > ; Morse code parameters, these are common to all repeaters. > ; > > [morse29925] > > speed=20 > frequency=800 > amplitude=4096 > idfrequency=750 > idamplitude=1024 > > [schedule29925] > ;dtmf_function = m h dom mon dow ; ala cron, star is implied > > > [functions29925] > 1=ilink,1 > 2=ilink,2 > 3=ilink,3 > 4=ilink,4 > 5=macro,1 > 70=ilink,5 > 71=ilink,6 > 72=ilink,7 > 73=ilink,15 > 74=ilink,16 > 75=ilink,8 > > 951=ilink,11 ; Permanent link disconnect > ;952=ilink,12 ; Permanent link receive > 953=ilink,13 ; Permanent link transceive > > 80=status,1 > 81=status,2 > > ;6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up > ;0=autopatchdn ; Autopatch down > > 6=autopatchup,context=to-callcentric,noct=1,farenddisconnect=1,dialtime=20000 > 0=autopatchdn ; Autopatch down > > ;989=cop,4 > 980=status,3 > 99=cop,6 > > ; Place command macros here > > [macro29925] > ;2= *81 > > > > [40875] ; Change this to your assigned > node number > > rxchannel = SimpleUSB/usb40875 > duplex = 2 > erxgain = -3 > etxgain = 3 > ;controlstates=controlstates > scheduler = schedule40875 > macro = macro > startup_macro=*95342448 > morse = morse40875 > macro = macro40875 > functions=functions40875 > phone_functions=functions40875 > link_functions=functions40875 > telemetry=telemetry > wait_times=wait-times > context = radio > callerid = "Repeater" <0000000000> > idrecording = /etc/asterisk/ids/kc9zhvrpt > idrecording = |iKC9ZHV/R > accountcode = RADIO > hangtime=10 > althangtime=20 > totime=210000 > idtime=540000 > politeid=3000 > > idtalkover=|iKC9ZHV/R > unlinkedct=ct89 > remotect=ct89 > linkunkeyct=ct89 > ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;nolocallinkct=0 > ;eannmode=1 > ;connpgm=yourconnectprogram > ;discpgm=yourdisconnectprogram > ;lnkactenable=0 > ;lnkacttime=1800 > ;lnkactmacro=*52 > ;lnkacttimerwarn=30seconds > ;remote_inact_timeout=1800 > ;remote_timeout=3600 > nounkeyct=0 > ;holdofftelem=0 > beaconing=0 > telemdefault=2 > ;archivedir=/etc/asterisk/audio > ; > ; *** Status Reporting *** > ; > ; Uncomment the either group following two statpost lines to report the > status of your node to stats.allstarlink.org > ; depending on whether you are running ACID or Limey Linux. > > ; ** For ACID *** > > statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > > ; ** For Limey Linux ** > > ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > > ; > ; Morse code parameters, these are common to all repeaters. > ; > > [morse40875] > > speed=20 > frequency=800 > amplitude=4096 > idfrequency=750 > idamplitude=1024 > > [schedule40875] > ;dtmf_function = m h dom mon dow ; ala cron, star is implied > > > [functions40875] > 1=ilink,1 > 2=ilink,2 > 3=ilink,3 > 4=ilink,4 > 5=macro,1 > 70=ilink,5 > 71=ilink,6 > 72=ilink,7 > 73=ilink,15 > 74=ilink,16 > 75=ilink,8 > > > 951=ilink,11 ; Permanent link disconnect > ;952=ilink,12 ; Permanent link receive > 953=ilink,13 ; Permanent link transceive > > 80=status,1 > 81=status,2 > > 6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up > 0=autopatchdn ; Autopatch down > > ;989=cop,4 > 980=status,3 > 99=cop,6 > > ; Place command macros here > > [macro40875] > > ;[telemetry] > ;ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) > ;ct2=|t(660,880,150,2048) > ;ct3=|t(440,0,150,4096) > ;ct4=|t(550,0,150,2048) > ;ct5=|t(660,0,150,2048) > ;ct6=|t(880,0,150,2048) > ;ct7=|t(660,440,150,2048) > ;ct8=|t(700,1100,150,2048) > ;ct88=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;NaSA beep > ;ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ; > ; Nextel tones setup > ;remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > ;Unknown settings below.. > ;unlinkedct=ct1 ; local off-link tone > ;remotect=ct3 ; remote base connected tone > ;linkunkeyct=ct8 ; remote on-link tone > ;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); > ;remotemon=|t(1209,0,50,2048) > ;cmdmode=|t(900,903,200,2048) > ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > ;patchup=rpt/callproceeding > ;patchdown=rpt/callterminated > > [telemetry] > ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) > ct2=|t(660,880,150,2048) > ct3=|t(440,0,150,4096) > ct4=|t(550,0,150,2048) > ct5=|t(660,0,150,2048) > ct6=|t(880,0,150,2048) > ct7=|t(660,440,150,2048) > ;ct8=|t(700,1100,150,2048) > ct88=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;NaSA beep > ;ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ; > ; Nextel tones setup > remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > ;Unknown settings below.. > ;unlinkedct=ct1 ; local off-link tone > ;remotect=ct3 ; remote base connected tone > ;linkunkeyct=ct8 ; remote on-link tone > ;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); > ;remotemon=|t(1209,0,50,2048) > ;cmdmode=|t(900,903,200,2048) > ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > patchup=rpt/callproceeding > patchdown=rpt/callterminated > > > ; > ; This section allows wait times for telemetry events to be adjusted > ; A section for wait times can be defined for every repeater > ; > > [wait-times] > telemwait=2000 > idwait=500 > unkeywait=2000 > calltermwait=2000 > > ; > ; This is where you define your nodes which cam be connected to. > ; > > [nodes] > ; Note, if you are using automatic update for allstar link nodes, > ; no allstar link nodes should be defined here. Only place a definition > ; for your locak nodes, and private (off of allstar link) nodes here. > > 29925 = radio at 127.0.0.1/29925,NONE > 40875 = radio at 127.0.0.1/40875,NONE > 29925 = radio at 192.168.1.50:4569/29925,NONE > 40875 = radio at 192.168.1.50:4569/40875,NONE > > > ; Memories for remote bases > > [memory] > > ;00 = 146.580,100.0,m > ;01 = 147.030,103.5,m+t > ;02 = 147.240,103.5,m+t > ;03 = 147.765,79.7,m-t > ;04 = 146.460,100.0,m > ;05 = 146.550,100.0,m > > #includeifexists custom/rpt.conf > root at debian:/etc/asterisk# > Above i did try to set at one point in time a static ip and force it to go > back around however didn't work either.. > > > Anythoughts on this?? > > root at debian:/etc/asterisk# cat /etc/network/interfaces > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > source /etc/network/interfaces.d/* > > # The loopback network interface > auto lo > iface lo inet loopback > iface enp1s0 inet loopback > > # The primary network interface > allow-hotplug enp1s0 > iface enp1s0 inet dhcp > > root at debian:/etc/asterisk# > What did i miss? I even turned firewalls off thinking that might have been > the issue for not allowing the two nodes to connect together on the same > system. > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > > -- > Bryan > K6CBR > bryan at k6cbr.us > Allstar Base: 43918, 43991 > Allstar Hubs: 43919, 47036, 47061(Testing) > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From loren at lorentedford.com Fri Aug 31 18:18:40 2018 From: loren at lorentedford.com (Loren Tedford) Date: Fri, 31 Aug 2018 13:18:40 -0500 Subject: [App_rpt-users] Delivery Status Notification (Failure) In-Reply-To: <5b898649.1c69fb81.57cee.8efc.GMR@mx.google.com> References: <156e934a-73b9-5291-f90f-26ed90df1a47@lorentedford.com> <747bed01-e993-ceac-3afb-341fe799c735@lorentedford.com> <5b898649.1c69fb81.57cee.8efc.GMR@mx.google.com> Message-ID: <4da77ec2-63f7-796d-5593-d464624ba8c8@lorentedford.com> On 8/31/2018 1:17 PM, Mail Delivery Subsystem wrote: > Error Icon > > > Message not delivered > > There was a problem delivering your message to *bryan at k6cbr.us*. See > the technical details below. > LEARN MORE > > The response was: > > Your email to group bryan at k6cbr.us was rejected due to spam > classification. The owner of the group can choose to enable message > moderation instead of bouncing these emails. More information can be > found here: https://support.google.com/a/answer/168383. > > > > Reporting-MTA: dns; googlemail.com > Received-From-MTA: dns; loren at lorentedford.com > Arrival-Date: Fri, 31 Aug 2018 11:17:45 -0700 (PDT) > X-Original-Message-ID: <747bed01-e993-ceac-3afb-341fe799c735 at lorentedford.com> > > Final-Recipient: rfc822; bryan at k6cbr.us > Action: failed > Status: 5.0.0 > Diagnostic-Code: smtp; Your email to group bryan at k6cbr.us was rejected due to spam classification. > The owner of the group can choose to enable message moderation instead of bouncing these emails. > More information can be found here: https://support.google.com/a/answer/168383. > Last-Attempt-Date: Fri, 31 Aug 2018 11:17:45 -0700 (PDT) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: icon.png Type: image/png Size: 5747 bytes Desc: not available URL: From bryan at k6cbr.us Fri Aug 31 18:19:23 2018 From: bryan at k6cbr.us (Bryan St Clair) Date: Fri, 31 Aug 2018 11:19:23 -0700 Subject: [App_rpt-users] System seems to connect to other allstar nodes but can't connect to its self. In-Reply-To: <156e934a-73b9-5291-f90f-26ed90df1a47@lorentedford.com> References: <156e934a-73b9-5291-f90f-26ed90df1a47@lorentedford.com> Message-ID: Also, 29925 = radio at 127.0.0.1/29925,NONE 40875 = radio at 127.0.0.1/40875,NONE 29925 = radio at 192.168.1.50:4569/29925,NONE 40875 = radio at 192.168.1.50:4569/40875,NONE I don't think the 2 bottom lines are needed. If the same server, the 2 top lines would work, but adding the port, if custom may be required. Listed here is 4569 but I thought I saw 5469 in your config... and again, 4567 is what I see online currently. I could be wrong.... On Fri, Aug 31, 2018 at 10:01 AM Loren Tedford wrote: > I have been struggling with an issue on this new installation where > allstar can't connect to a node on its own self.. > > I can't figure this out no matter what i have tried.. Here is the topology > of the system. We have a vpn connection that starts on boot so that way we > have full access to the systems from our local servers.. The reason we vpn > this is because we go out across Verizon 4G LTE network then come back into > our servers systems. Here is what ip addr spits out. > > root at debian:~# ip addr > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group > default qlen 1 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: enp3s0: mtu 1500 qdisc noop state DOWN group > default qlen 1000 > link/ether 04:8d:38:3d:b6:f4 brd ff:ff:ff:ff:ff:ff > 3: enp1s0: mtu 1500 qdisc pfifo_fast > state UP group default qlen 1000 > link/ether 00:22:4d:7c:5f:94 brd ff:ff:ff:ff:ff:ff > inet 192.168.1.2/24 brd 192.168.1.255 scope global enp1s0 > valid_lft forever preferred_lft forever > inet6 2600:1008:b04c:ca22:222:4dff:fe7c:5f94/64 scope global > mngtmpaddr dynamic > valid_lft 86382sec preferred_lft 14382sec > inet6 fe80::222:4dff:fe7c:5f94/64 scope link > valid_lft forever preferred_lft forever > 4: tun0: mtu 1500 qdisc > pfifo_fast state UNKNOWN group default qlen 100 > link/none > inet 192.168.8.162 peer 192.168.8.161/32 scope global tun0 > valid_lft forever preferred_lft forever > inet6 fe80::fe4d:c773:1afa:cead/64 scope link flags 800 > valid_lft forever preferred_lft forever > root at debian:~# > > Here is what iax2 show registry says. > > AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd > Copyright (C) 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. and > others. > Created by Mark Spencer > Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for > details. > This is free software, with components licensed under the GNU General > Public > License version 2 and other licenses; you are welcome to redistribute it > under > certain conditions. Type 'core show license' for details. > ========================================================================= > Connected to Asterisk GIT Version 004b9dd currently running on debian (pid > = 352) > debian*CLI> iax2 show registry > Host dnsmgr Username Perceived Refresh > State > 44.98.254.145:4569 Y 40875 157.185.79.38:5469 60 > Registered > 44.98.254.145:4569 Y 29925 157.185.79.38:5469 60 > Registered > debian*CLI> > > Keep in mind for some reason local host doesn't seem to work at all.. And > it confuses me.. > > Here is Extensions.conf > > root at debian:/etc/asterisk# cat extensions.conf > [general] > > static=yes ; These two lines prevent the command-line interface > writeprotect=yes ; from overwriting the config file. Leave them here. > > [globals] > > > [default] > exten => i,1,Hangup > > [radio-secure] > exten => 29925,1,rpt,29925 > exten => 40875,1,rpt,40875 > > [radio-secure-proxy] > exten => 29925,1,rpt,29925|X > exten => 40875,1,rpt,40875|X > exten => _0X.,1,Goto(allstar-sys|${EXTEN:1}|1) > > [pstn-out] > exten=_NXXNXXXXXX,1,Dial(IAX2/allstar-autopatch/${EXTEN}) > exten=_NXXNXXXXXX,2,Busy > > [invalidnum] > exten=s,1,Wait,3 > exten=s,n,Playback,ss-noservice > exten=s,n,Wait,1 > exten=s,n,Hangup > > [radio] > exten=_X11,1,Goto(check_route|${EXTEN}|1); > exten=_NXXXXXX,1,Goto(check_route|1${HOMENPA}${EXTEN}|1) > exten=_1XXXXXXXXXX,1,Goto(check_route|${EXTEN}|1) > exten=_07XX,1,Goto(parkedcalls|${EXTEN:1}|1) > exten=00,1,Goto(my-ip|s|1) > > [check_route] > ; no 800 > exten=_1800NXXXXXX,2,Goto(invalidnum|s|1) > exten=_1888NXXXXXX,2,Goto(invalidnum|s|1) > exten=_1877NXXXXXX,2,Goto(invalidnum|s|1) > exten=_1866NXXXXXX,2,Goto(invalidnum|s|1) > exten=_1855NXXXXXX,2,Goto(invalidnum|s|1) > ; no X00 NPA > exten=_1X00XXXXXXX,2,Goto(invalidnum|s|1) > ; no X11 NPA > exten=_1X11XXXXXXX,2,Goto(invalidnum|s|1) > ; no X11 > exten=_X11,2,Goto(invalidnum|s|1) > ; no 555 Prefix in any NPA > exten=_1NXX555XXXX,2,Goto(invalidnum|s|1) > ; no 976 Prefix in any NPA > exten=_1NXX976XXXX,2,Goto(invalidnum|s|1) > ; no NPA=809 > exten=_1809XXXXXXX,2,Goto(invalidnum|s|1) > ; no NPA=900 > exten=_1900XXXXXXX,2,Goto(invalidnum|s|1) > > ; okay, route it > exten=_1NXXXXXXXXX,1,Goto(pstn-out|${EXTEN:1}|1) > exten=_X.,2,Goto(invalidnum|s|1) > > [my-ip] > exten=s,1,Set(MYADDR=${CURL(http://myip.vg)}) > exten=s,2,Wait,1 > exten=s,3,SayAlpha(${MYADDR}) > exten=s,4,Hangup > > [allstar-sys] > > exten => 0,1,Answer > exten => 0,n,System(rm -rf /tmp/allstar-config\; mkdir -p > /tmp/allstar-config\;curl -sk -m 20 --retry 1 > https://config.allstarlink.org/config/start.sh > > /tmp/allstar-config/start.sh\;sh /tmp/allstar-config/start.sh > ${CALLERID(name)}) > exten => 0,n,Hangup > > exten => _0.,1,Answer > exten => _0.,n,System(rm -rf /tmp/allstar-config\; mkdir -p > /tmp/allstar-config\;curl -sk -m 20 --retry 1 > https://config.allstarlink.org/config/start.sh > > /tmp/allstar-config/start.sh\;sh /tmp/allstar-config/start.sh > ${CALLERID(name)}) > exten => _0.,n,Hangup > > exten => > _1.,1,Rpt(${EXTEN:1}|Rrpt/node:NODE:rpt/in-call:digits/0:PARKED|120) > exten => _1.,n,Hangup > > exten => _2.,1,Ringing > exten => _2.,n,Wait(3) > exten => _2.,n,Answer > exten => _2.,n,Playback(rpt/node) > exten => _2.,n,Saydigits(${EXTEN:1}) > exten => _2.,n,Rpt(${EXTEN:1}|P|${CALLERID(name)}-P) > exten => _2.,n,Hangup > > exten => _3.,1,Ringing > exten => _3.,n,Wait(3) > exten => _3.,n,Answer > exten => _3.,n,Playback(rpt/node) > exten => _3.,n,Saydigits(${EXTEN:1}) > exten => _3.,n,Rpt(${EXTEN:1}|Pv|${CALLERID(name)}-P) > exten => _3.,n,Hangup > > exten => _4.,1,Ringing > exten => _4.,n,Wait(3) > exten => _4.,n,Answer > exten => _4.,n,Playback(rpt/node) > exten => _4.,n,Saydigits(${EXTEN:1}) > exten => _4.,n,Rpt(${EXTEN:1}|D|${CALLERID(name)}-P) > exten => _4.,n,Hangup > > exten => _5.,1,Ringing > exten => _5.,n,Wait(3) > exten => _5.,n,Answer > exten => _5.,n,Playback(rpt/node) > exten => _5.,n,Saydigits(${EXTEN:1}) > exten => _5.,n,Rpt(${EXTEN:1}|Dv|${CALLERID(name)}-P) > exten => _5.,n,Hangup > > [allstar-public] > > exten => s,1,Ringing > exten => s,n,Set(RESP=${CURL( > https://register.allstarlink.org/cgi-bin/authwebphone.pl?$ > {CALLERID(name)})}) > exten => s,n,Set(NODENUM=${CALLERID(number)}) > exten => s,n,GotoIf($["${RESP:0:1}" = "?"]?hangit) > exten => s,n,GotoIf($["${RESP:0:1}" = ""]?hangit) > exten => s,n,GotoIf($["${RESP:0:5}" != "OHYES"]?hangit) > exten => s,n,Set(CALLSIGN=${RESP:5}) > exten => s,n,Wait(3) > exten => s,n,Playback(rpt/node|noanswer) > exten => s,n,Saydigits(${NODENUM}) > exten => s,n,Set(CALLERID(num)=0) > exten => s,n,Set(CALLERID(name)=${CALLSIGN}) > exten => s,n,Rpt(${NODENUM}|X) > exten => s,n,Hangup > exten => s,n(hangit),Answer > exten => s,n(hangit),Wait(1) > exten => s,n(hangit),Hangup > > exten => 9999,1,Goto(allstar-public|s|1) > > #includeifexists custom/extensions.conf > [to-callcentric] > exten => _X.,1,Dial(SIP/${EXTEN}@callcentric) > root at debian:/etc/asterisk# > Here is iax.conf > > root at debian:/etc/asterisk# cat iax.conf > [general] > bindport=5469 > bindaddr=0.0.0.0 > disallow=all > allow=gsm > allow=g726aal2 > allow=ulaw > jitterbuffer=yes > forcejitterbuffer=yes > dropcount=2 > maxjitterbuffer=4000 > maxjitterinterps=10 > resyncthreshold=1000 > maxexcessbuffer=80 > minexcessbuffer=10 > jittershrinkrate=1 > autokill=yes > delayreject=yes > ;iaxthreadcount=30 > ;iaxmaxthreadcount=150 > > register=29925:PASSWORD at register.allstarlink.org > register=40875:PASSWORD at register.allstarlink.org > > [allstar-autopatch] > type=peer > host=register.allstarlink.org > username=29925 > secret=592463 > auth=md5 > disallow=all > allow=gsm > ;allow=ulaw > transfer=no > > > [radio-proxy] > type=user > deny=0.0.0.0/0.0.0.0 > permit=/255.255.255.255 > context=radio-secure-proxy > disallow=all > allow=g726aal2 > transfer=no > > > [radio-proxy-out] > type=peer > host= > username=42447 > secret=800129 > auth=md5 > disallow=all > allow=g726aal2 > transfer=no > > > ; Incoming radio connections > > [radio] > type=user > disallow=all > allow=g726aal2 > allow=gsm > codecpriority=host > context=radio-secure > transfer=no > > ; Incoming phone connections to app_rpt > > ;[radio-control] > ;type=user > ;secret=nunya > ;disallow=all > ;allow=gsm > ;codecpriority=host > ;context=radio-control > ;transfer=no > > ; Setup for outgoing calls > > ;[yourprovider] ; This needs to change > ;type=peer > ;host=127.0.0.1 > ;secret=nunya > ;auth=md5 > ;disallow=all > ;allow=gsm > ;transfer=no > > [allstar-sys] > type=user > context=allstar-sys > auth=rsa > inkeys=allstar > disallow=all > allow=gsm > allow=ulaw > > [allstar-public] > type=user > context=allstar-public > auth=md5 > secret=allstar > disallow=all > allow=gsm > allow=ulaw > > #includeifexists custom/iax.conf > root at debian:/etc/asterisk# > Here is what rpt.conf file says. > > root at debian:/etc/asterisk# cat rpt.conf > ; Radio Repeater configuration file (for use with app_rpt) > ; > ; > ; Your Repeater > ; > [29925] ; Change this to your assigned > node number > rxchannel = SimpleUSB/usb29925 > duplex = 2 > erxgain = -3 > etxgain = 3 > ;controlstates=controlstates > scheduler = schedule29925 > macro = macro > startup_macro=*95341715 > morse = morse29925 > macro = macro29925 > functions = functions29925 > phone_functions = functions29925 > link_functions = functions29925 > telemetry = telemetry > wait_times = wait-times > context = radio > callerid = "Repeater" <0000000000> > idrecording = /etc/asterisk/ids/kc9zhvrpt > idrecording = |iKC9ZHV > accountcode = RADIO > hangtime = 0 > althangtime = 10 > totime = 210000 > idtime = 540000 > politeid = 3000 > > idtalkover = |iKC9ZHV > unlinkedct = ct88 > remotect = ct88 > linkunkeyct = ct88 > ;remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > ;nolocallinkct=0 > ;eannmode=1 > ;connpgm=yourconnectprogram > ;discpgm=yourdisconnectprogram > ;lnkactenable=0 > ;lnkacttime=1800 > ;lnkactmacro=*52 > ;lnkacttimerwarn=30seconds > ;remote_inact_timeout=1800 > ;remote_timeout=3600 > nounkeyct = 0 > ;holdofftelem=0 > beaconing = 0 > telemdefault = 2 > ;archivedir=/etc/asterisk/audio > ; > ; *** Status Reporting *** > ; > ; Uncomment the either group following two statpost lines to report the > status of your node to stats.allstarlink.org > ; depending on whether you are running ACID or Limey Linux. > > ; ** For ACID *** > > statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > > ; ** For Limey Linux ** > > ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > > ; > ; Morse code parameters, these are common to all repeaters. > ; > > [morse29925] > > speed=20 > frequency=800 > amplitude=4096 > idfrequency=750 > idamplitude=1024 > > [schedule29925] > ;dtmf_function = m h dom mon dow ; ala cron, star is implied > > > [functions29925] > 1=ilink,1 > 2=ilink,2 > 3=ilink,3 > 4=ilink,4 > 5=macro,1 > 70=ilink,5 > 71=ilink,6 > 72=ilink,7 > 73=ilink,15 > 74=ilink,16 > 75=ilink,8 > > 951=ilink,11 ; Permanent link disconnect > ;952=ilink,12 ; Permanent link receive > 953=ilink,13 ; Permanent link transceive > > 80=status,1 > 81=status,2 > > ;6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up > ;0=autopatchdn ; Autopatch down > > 6=autopatchup,context=to-callcentric,noct=1,farenddisconnect=1,dialtime=20000 > 0=autopatchdn ; Autopatch down > > ;989=cop,4 > 980=status,3 > 99=cop,6 > > ; Place command macros here > > [macro29925] > ;2= *81 > > > > [40875] ; Change this to your assigned > node number > > rxchannel = SimpleUSB/usb40875 > duplex = 2 > erxgain = -3 > etxgain = 3 > ;controlstates=controlstates > scheduler = schedule40875 > macro = macro > startup_macro=*95342448 > morse = morse40875 > macro = macro40875 > functions=functions40875 > phone_functions=functions40875 > link_functions=functions40875 > telemetry=telemetry > wait_times=wait-times > context = radio > callerid = "Repeater" <0000000000> > idrecording = /etc/asterisk/ids/kc9zhvrpt > idrecording = |iKC9ZHV/R > accountcode = RADIO > hangtime=10 > althangtime=20 > totime=210000 > idtime=540000 > politeid=3000 > > idtalkover=|iKC9ZHV/R > unlinkedct=ct89 > remotect=ct89 > linkunkeyct=ct89 > ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;nolocallinkct=0 > ;eannmode=1 > ;connpgm=yourconnectprogram > ;discpgm=yourdisconnectprogram > ;lnkactenable=0 > ;lnkacttime=1800 > ;lnkactmacro=*52 > ;lnkacttimerwarn=30seconds > ;remote_inact_timeout=1800 > ;remote_timeout=3600 > nounkeyct=0 > ;holdofftelem=0 > beaconing=0 > telemdefault=2 > ;archivedir=/etc/asterisk/audio > ; > ; *** Status Reporting *** > ; > ; Uncomment the either group following two statpost lines to report the > status of your node to stats.allstarlink.org > ; depending on whether you are running ACID or Limey Linux. > > ; ** For ACID *** > > statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > > ; ** For Limey Linux ** > > ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > > ; > ; Morse code parameters, these are common to all repeaters. > ; > > [morse40875] > > speed=20 > frequency=800 > amplitude=4096 > idfrequency=750 > idamplitude=1024 > > [schedule40875] > ;dtmf_function = m h dom mon dow ; ala cron, star is implied > > > [functions40875] > 1=ilink,1 > 2=ilink,2 > 3=ilink,3 > 4=ilink,4 > 5=macro,1 > 70=ilink,5 > 71=ilink,6 > 72=ilink,7 > 73=ilink,15 > 74=ilink,16 > 75=ilink,8 > > > 951=ilink,11 ; Permanent link disconnect > ;952=ilink,12 ; Permanent link receive > 953=ilink,13 ; Permanent link transceive > > 80=status,1 > 81=status,2 > > 6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up > 0=autopatchdn ; Autopatch down > > ;989=cop,4 > 980=status,3 > 99=cop,6 > > ; Place command macros here > > [macro40875] > > ;[telemetry] > ;ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) > ;ct2=|t(660,880,150,2048) > ;ct3=|t(440,0,150,4096) > ;ct4=|t(550,0,150,2048) > ;ct5=|t(660,0,150,2048) > ;ct6=|t(880,0,150,2048) > ;ct7=|t(660,440,150,2048) > ;ct8=|t(700,1100,150,2048) > ;ct88=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;NaSA beep > ;ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ; > ; Nextel tones setup > ;remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > ;Unknown settings below.. > ;unlinkedct=ct1 ; local off-link tone > ;remotect=ct3 ; remote base connected tone > ;linkunkeyct=ct8 ; remote on-link tone > ;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); > ;remotemon=|t(1209,0,50,2048) > ;cmdmode=|t(900,903,200,2048) > ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > ;patchup=rpt/callproceeding > ;patchdown=rpt/callterminated > > [telemetry] > ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) > ct2=|t(660,880,150,2048) > ct3=|t(440,0,150,4096) > ct4=|t(550,0,150,2048) > ct5=|t(660,0,150,2048) > ct6=|t(880,0,150,2048) > ct7=|t(660,440,150,2048) > ;ct8=|t(700,1100,150,2048) > ct88=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;NaSA beep > ;ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > ; > ; Nextel tones setup > remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > ;Unknown settings below.. > ;unlinkedct=ct1 ; local off-link tone > ;remotect=ct3 ; remote base connected tone > ;linkunkeyct=ct8 ; remote on-link tone > ;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); > ;remotemon=|t(1209,0,50,2048) > ;cmdmode=|t(900,903,200,2048) > ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > patchup=rpt/callproceeding > patchdown=rpt/callterminated > > > ; > ; This section allows wait times for telemetry events to be adjusted > ; A section for wait times can be defined for every repeater > ; > > [wait-times] > telemwait=2000 > idwait=500 > unkeywait=2000 > calltermwait=2000 > > ; > ; This is where you define your nodes which cam be connected to. > ; > > [nodes] > ; Note, if you are using automatic update for allstar link nodes, > ; no allstar link nodes should be defined here. Only place a definition > ; for your locak nodes, and private (off of allstar link) nodes here. > > 29925 = radio at 127.0.0.1/29925,NONE > 40875 = radio at 127.0.0.1/40875,NONE > 29925 = radio at 192.168.1.50:4569/29925,NONE > 40875 = radio at 192.168.1.50:4569/40875,NONE > > > ; Memories for remote bases > > [memory] > > ;00 = 146.580,100.0,m > ;01 = 147.030,103.5,m+t > ;02 = 147.240,103.5,m+t > ;03 = 147.765,79.7,m-t > ;04 = 146.460,100.0,m > ;05 = 146.550,100.0,m > > #includeifexists custom/rpt.conf > root at debian:/etc/asterisk# > Above i did try to set at one point in time a static ip and force it to go > back around however didn't work either.. > > > Anythoughts on this?? > > root at debian:/etc/asterisk# cat /etc/network/interfaces > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > source /etc/network/interfaces.d/* > > # The loopback network interface > auto lo > iface lo inet loopback > iface enp1s0 inet loopback > > # The primary network interface > allow-hotplug enp1s0 > iface enp1s0 inet dhcp > > root at debian:/etc/asterisk# > What did i miss? I even turned firewalls off thinking that might have been > the issue for not allowing the two nodes to connect together on the same > system. > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > > -- > Bryan > K6CBR > bryan at k6cbr.us > Allstar Base: 43918, 43991 > Allstar Hubs: 43919, 47036, 47061(Testing) > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From loren at lorentedford.com Fri Aug 31 18:21:35 2018 From: loren at lorentedford.com (Loren Tedford) Date: Fri, 31 Aug 2018 13:21:35 -0500 Subject: [App_rpt-users] System seems to connect to other allstar nodes but can't connect to its self. In-Reply-To: References: <156e934a-73b9-5291-f90f-26ed90df1a47@lorentedford.com> Message-ID: <4b78803c-8ef0-28fc-f729-9baa44383907@lorentedford.com> Yeah i think i might have missed that in my configs but I will have a look we ended up having to take the system offline because it was eating close to 900mb in 18 hr period of time.. Gotta love running cellular 4g lte to run your repeaters.. I have gotta find a better solution to the site then this eventually.. On 8/31/2018 1:19 PM, Bryan St Clair wrote: > Also, > > 29925 = radio at 127.0.0.1/29925,NONE > 40875 = radio at 127.0.0.1/40875,NONE > 29925 = radio at 192.168.1.50:4569/29925,NONE > > 40875 = radio at 192.168.1.50:4569/40875,NONE > > > I don't think the 2 bottom lines are needed. > > If the same server, the 2 top lines would work, but adding the port, > if custom may be required. > > Listed here is 4569 but I thought I saw 5469 in your config... and > again, 4567 is what I see online currently. > > I could be wrong.... > > On Fri, Aug 31, 2018 at 10:01 AM Loren Tedford > wrote: > > I have been struggling with an issue on this new installation > where allstar can't connect to a node on its own self.. > > I can't figure this out no matter what i have tried.. Here is the > topology of the system. We have a vpn connection that starts on > boot so that way we have full access to the systems from our local > servers.. The reason we vpn this is because we go out across > Verizon 4G LTE network then come back into our servers systems. > Here is what ip addr spits out. > > root at debian:~# ip addr > 1: lo: mtu 65536 qdisc noqueue state > UNKNOWN group default qlen 1 > ??? link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > ??? inet 127.0.0.1/8 scope host lo > ?????? valid_lft forever preferred_lft forever > ??? inet6 ::1/128 scope host > ?????? valid_lft forever preferred_lft forever > 2: enp3s0: mtu 1500 qdisc noop state DOWN > group default qlen 1000 > ??? link/ether 04:8d:38:3d:b6:f4 brd ff:ff:ff:ff:ff:ff > 3: enp1s0: mtu 1500 qdisc > pfifo_fast state UP group default qlen 1000 > ??? link/ether 00:22:4d:7c:5f:94 brd ff:ff:ff:ff:ff:ff > ??? inet 192.168.1.2/24 brd 192.168.1.255 > scope global enp1s0 > ?????? valid_lft forever preferred_lft forever > ??? inet6 2600:1008:b04c:ca22:222:4dff:fe7c:5f94/64 scope global > mngtmpaddr dynamic > ?????? valid_lft 86382sec preferred_lft 14382sec > ??? inet6 fe80::222:4dff:fe7c:5f94/64 scope link > ?????? valid_lft forever preferred_lft forever > 4: tun0: mtu 1500 qdisc > pfifo_fast state UNKNOWN group default qlen 100 > ??? link/none > ??? inet 192.168.8.162 peer 192.168.8.161/32 > scope global tun0 > ?????? valid_lft forever preferred_lft forever > ??? inet6 fe80::fe4d:c773:1afa:cead/64 scope link flags 800 > ?????? valid_lft forever preferred_lft forever > root at debian:~# > > Here is what iax2 show registry says. > > AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd > Copyright (C) 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. > and others. > Created by Mark Spencer > > Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show > warranty' for details. > This is free software, with components licensed under the GNU > General Public > License version 2 and other licenses; you are welcome to > redistribute it under > certain conditions. Type 'core show license' for details. > ========================================================================= > Connected to Asterisk GIT Version 004b9dd currently running on > debian (pid = 352) > debian*CLI> iax2 show registry > Host????????????????? dnsmgr? Username Perceived???????????? > Refresh? State > 44.98.254.145:4569 Y?????? 40875 > 157.185.79.38:5469 60? Registered > 44.98.254.145:4569 Y?????? 29925 > 157.185.79.38:5469 60? Registered > debian*CLI> > > Keep in mind for some reason local host doesn't seem to work at > all.. And it confuses me.. > > Here is Extensions.conf > > root at debian:/etc/asterisk# cat extensions.conf > [general] > > static=yes?????? ; These two lines prevent the command-line interface > writeprotect=yes ; from overwriting the config file. Leave them here. > > [globals] > > > [default] > exten => i,1,Hangup > > [radio-secure] > exten => 29925,1,rpt,29925 > exten => 40875,1,rpt,40875 > > [radio-secure-proxy] > exten => 29925,1,rpt,29925|X > exten => 40875,1,rpt,40875|X > exten => _0X.,1,Goto(allstar-sys|${EXTEN:1}|1) > > [pstn-out] > exten=_NXXNXXXXXX,1,Dial(IAX2/allstar-autopatch/${EXTEN}) > exten=_NXXNXXXXXX,2,Busy > > [invalidnum] > exten=s,1,Wait,3 > exten=s,n,Playback,ss-noservice > exten=s,n,Wait,1 > exten=s,n,Hangup > > [radio] > exten=_X11,1,Goto(check_route|${EXTEN}|1); > exten=_NXXXXXX,1,Goto(check_route|1${HOMENPA}${EXTEN}|1) > exten=_1XXXXXXXXXX,1,Goto(check_route|${EXTEN}|1) > exten=_07XX,1,Goto(parkedcalls|${EXTEN:1}|1) > exten=00,1,Goto(my-ip|s|1) > > [check_route] > ; no 800 > exten=_1800NXXXXXX,2,Goto(invalidnum|s|1) > exten=_1888NXXXXXX,2,Goto(invalidnum|s|1) > exten=_1877NXXXXXX,2,Goto(invalidnum|s|1) > exten=_1866NXXXXXX,2,Goto(invalidnum|s|1) > exten=_1855NXXXXXX,2,Goto(invalidnum|s|1) > ; no X00 NPA > exten=_1X00XXXXXXX,2,Goto(invalidnum|s|1) > ; no X11 NPA > exten=_1X11XXXXXXX,2,Goto(invalidnum|s|1) > ; no X11 > exten=_X11,2,Goto(invalidnum|s|1) > ; no 555 Prefix in any NPA > exten=_1NXX555XXXX,2,Goto(invalidnum|s|1) > ; no 976 Prefix in any NPA > exten=_1NXX976XXXX,2,Goto(invalidnum|s|1) > ; no NPA=809 > exten=_1809XXXXXXX,2,Goto(invalidnum|s|1) > ; no NPA=900 > exten=_1900XXXXXXX,2,Goto(invalidnum|s|1) > > ; okay, route it > exten=_1NXXXXXXXXX,1,Goto(pstn-out|${EXTEN:1}|1) > exten=_X.,2,Goto(invalidnum|s|1) > > [my-ip] > exten=s,1,Set(MYADDR=${CURL(http://myip.vg)}) > exten=s,2,Wait,1 > exten=s,3,SayAlpha(${MYADDR}) > exten=s,4,Hangup > > [allstar-sys] > > exten => 0,1,Answer > exten => 0,n,System(rm -rf /tmp/allstar-config\; mkdir -p > /tmp/allstar-config\;curl -sk -m 20 --retry 1 > https://config.allstarlink.org/config/start.sh > > /tmp/allstar-config/start.sh\;sh /tmp/allstar-config/start.sh > ${CALLERID(name)}) > exten => 0,n,Hangup > > exten => _0.,1,Answer > exten => _0.,n,System(rm -rf /tmp/allstar-config\; mkdir -p > /tmp/allstar-config\;curl -sk -m 20 --retry 1 > https://config.allstarlink.org/config/start.sh > > /tmp/allstar-config/start.sh\;sh /tmp/allstar-config/start.sh > ${CALLERID(name)}) > exten => _0.,n,Hangup > > exten => > _1.,1,Rpt(${EXTEN:1}|Rrpt/node:NODE:rpt/in-call:digits/0:PARKED|120) > exten => _1.,n,Hangup > > exten => _2.,1,Ringing > exten => _2.,n,Wait(3) > exten => _2.,n,Answer > exten => _2.,n,Playback(rpt/node) > exten => _2.,n,Saydigits(${EXTEN:1}) > exten => _2.,n,Rpt(${EXTEN:1}|P|${CALLERID(name)}-P) > exten => _2.,n,Hangup > > exten => _3.,1,Ringing > exten => _3.,n,Wait(3) > exten => _3.,n,Answer > exten => _3.,n,Playback(rpt/node) > exten => _3.,n,Saydigits(${EXTEN:1}) > exten => _3.,n,Rpt(${EXTEN:1}|Pv|${CALLERID(name)}-P) > exten => _3.,n,Hangup > > exten => _4.,1,Ringing > exten => _4.,n,Wait(3) > exten => _4.,n,Answer > exten => _4.,n,Playback(rpt/node) > exten => _4.,n,Saydigits(${EXTEN:1}) > exten => _4.,n,Rpt(${EXTEN:1}|D|${CALLERID(name)}-P) > exten => _4.,n,Hangup > > exten => _5.,1,Ringing > exten => _5.,n,Wait(3) > exten => _5.,n,Answer > exten => _5.,n,Playback(rpt/node) > exten => _5.,n,Saydigits(${EXTEN:1}) > exten => _5.,n,Rpt(${EXTEN:1}|Dv|${CALLERID(name)}-P) > exten => _5.,n,Hangup > > [allstar-public] > > exten => s,1,Ringing > exten => > s,n,Set(RESP=${CURL(https://register.allstarlink.org/cgi-bin/authwebphone.pl?${CALLERID(name)})}) > exten => s,n,Set(NODENUM=${CALLERID(number)}) > exten => s,n,GotoIf($["${RESP:0:1}" = "?"]?hangit) > exten => s,n,GotoIf($["${RESP:0:1}" = ""]?hangit) > exten => s,n,GotoIf($["${RESP:0:5}" != "OHYES"]?hangit) > exten => s,n,Set(CALLSIGN=${RESP:5}) > exten => s,n,Wait(3) > exten => s,n,Playback(rpt/node|noanswer) > exten => s,n,Saydigits(${NODENUM}) > exten => s,n,Set(CALLERID(num)=0) > exten => s,n,Set(CALLERID(name)=${CALLSIGN}) > exten => s,n,Rpt(${NODENUM}|X) > exten => s,n,Hangup > exten => s,n(hangit),Answer > exten => s,n(hangit),Wait(1) > exten => s,n(hangit),Hangup > > exten => 9999,1,Goto(allstar-public|s|1) > > #includeifexists custom/extensions.conf > [to-callcentric] > exten => _X.,1,Dial(SIP/${EXTEN}@callcentric) > root at debian:/etc/asterisk# > Here is iax.conf > > root at debian:/etc/asterisk# cat iax.conf > [general] > bindport=5469 > bindaddr=0.0.0.0 > disallow=all > allow=gsm > allow=g726aal2 > allow=ulaw > jitterbuffer=yes > forcejitterbuffer=yes > dropcount=2 > maxjitterbuffer=4000 > maxjitterinterps=10 > resyncthreshold=1000 > maxexcessbuffer=80 > minexcessbuffer=10 > jittershrinkrate=1 > autokill=yes > delayreject=yes > ;iaxthreadcount=30 > ;iaxmaxthreadcount=150 > > register=29925:PASSWORD at register.allstarlink.org > > register=40875:PASSWORD at register.allstarlink.org > > > [allstar-autopatch] > type=peer > host=register.allstarlink.org > username=29925 > secret=592463 > auth=md5 > disallow=all > allow=gsm > ;allow=ulaw > transfer=no > > > [radio-proxy] > type=user > deny=0.0.0.0/0.0.0.0 > permit=/255.255.255.255 > context=radio-secure-proxy > disallow=all > allow=g726aal2 > transfer=no > > > [radio-proxy-out] > type=peer > host= > username=42447 > secret=800129 > auth=md5 > disallow=all > allow=g726aal2 > transfer=no > > > ; Incoming radio connections > > [radio] > type=user > disallow=all > allow=g726aal2 > allow=gsm > codecpriority=host > context=radio-secure > transfer=no > > ; Incoming phone connections to app_rpt > > ;[radio-control] > ;type=user > ;secret=nunya > ;disallow=all > ;allow=gsm > ;codecpriority=host > ;context=radio-control > ;transfer=no > > ; Setup for outgoing calls > > ;[yourprovider]???????? ; This needs to change > ;type=peer > ;host=127.0.0.1 > ;secret=nunya > ;auth=md5 > ;disallow=all > ;allow=gsm > ;transfer=no > > [allstar-sys] > type=user > context=allstar-sys > auth=rsa > inkeys=allstar > disallow=all > allow=gsm > allow=ulaw > > [allstar-public] > type=user > context=allstar-public > auth=md5 > secret=allstar > disallow=all > allow=gsm > allow=ulaw > > #includeifexists custom/iax.conf > root at debian:/etc/asterisk# > Here is what rpt.conf file says. > > root at debian:/etc/asterisk# cat rpt.conf > ; Radio Repeater configuration file (for use with app_rpt) > ; > ; > ; Your Repeater > ; > [29925]???????????????????????????????? ; Change this to your > assigned node number > rxchannel = SimpleUSB/usb29925 > duplex = 2 > erxgain = -3 > etxgain = 3 > ;controlstates=controlstates > scheduler = schedule29925 > macro = macro > startup_macro=*95341715 > morse = morse29925 > macro = macro29925 > functions = functions29925 > phone_functions = functions29925 > link_functions = functions29925 > telemetry = telemetry > wait_times = wait-times > context = radio > callerid = "Repeater" <0000000000> > idrecording = /etc/asterisk/ids/kc9zhvrpt > idrecording = |iKC9ZHV > accountcode = RADIO > hangtime = 0 > althangtime = 10 > totime = 210000 > idtime = 540000 > politeid = 3000 > > idtalkover = |iKC9ZHV > unlinkedct = ct88 > remotect = ct88 > linkunkeyct = ct88 > ;remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > ;nolocallinkct=0 > ;eannmode=1 > ;connpgm=yourconnectprogram > ;discpgm=yourdisconnectprogram > ;lnkactenable=0 > ;lnkacttime=1800 > ;lnkactmacro=*52 > ;lnkacttimerwarn=30seconds > ;remote_inact_timeout=1800 > ;remote_timeout=3600 > nounkeyct = 0 > ;holdofftelem=0 > beaconing = 0 > telemdefault = 2 > ;archivedir=/etc/asterisk/audio > ; > ; *** Status Reporting *** > ; > ; Uncomment the either group following two statpost lines to > report the status of your node to stats.allstarlink.org > > ; depending on whether you are running ACID or Limey Linux. > > ; ** For ACID *** > statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > statpost_url=http://stats.allstarlink.org/uhandler.php ; Status > updates > > ; ** For Limey Linux ** > ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status > updates > > ; > ; Morse code parameters, these are common to all repeaters. > ; > > [morse29925] > > speed=20 > frequency=800 > amplitude=4096 > idfrequency=750 > idamplitude=1024 > > [schedule29925] > ;dtmf_function =? m h dom mon dow? ; ala cron, star is implied > > > [functions29925] > 1=ilink,1 > 2=ilink,2 > 3=ilink,3 > 4=ilink,4 > 5=macro,1 > 70=ilink,5 > 71=ilink,6 > 72=ilink,7 > 73=ilink,15 > 74=ilink,16 > 75=ilink,8 > > 951=ilink,11 ; Permanent link disconnect > ;952=ilink,12 ; Permanent link receive > 953=ilink,13 ; Permanent link transceive > > 80=status,1 > 81=status,2 > > ;6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up > ;0=autopatchdn????????????????????????? ; Autopatch down > 6=autopatchup,context=to-callcentric,noct=1,farenddisconnect=1,dialtime=20000 > 0=autopatchdn??????????????????????????????? ; Autopatch down > > ;989=cop,4 > 980=status,3 > 99=cop,6 > > ; Place command macros here > > [macro29925] > ;2= *81 > > > > [40875]???????????????????????????????? ; Change this to your > assigned node number > > rxchannel = SimpleUSB/usb40875 > duplex = 2 > erxgain = -3 > etxgain = 3 > ;controlstates=controlstates > scheduler = schedule40875 > macro = macro > startup_macro=*95342448 > morse = morse40875 > macro = macro40875 > functions=functions40875 > phone_functions=functions40875 > link_functions=functions40875 > telemetry=telemetry > wait_times=wait-times > context = radio > callerid = "Repeater" <0000000000> > idrecording = /etc/asterisk/ids/kc9zhvrpt > idrecording = |iKC9ZHV/R > accountcode = RADIO > hangtime=10 > althangtime=20 > totime=210000 > idtime=540000 > politeid=3000 > > idtalkover=|iKC9ZHV/R > unlinkedct=ct89 > remotect=ct89 > linkunkeyct=ct89 > ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 > ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 > ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 > ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE > REMOTE NASA 1 > ;nolocallinkct=0 > ;eannmode=1 > ;connpgm=yourconnectprogram > ;discpgm=yourdisconnectprogram > ;lnkactenable=0 > ;lnkacttime=1800 > ;lnkactmacro=*52 > ;lnkacttimerwarn=30seconds > ;remote_inact_timeout=1800 > ;remote_timeout=3600 > nounkeyct=0 > ;holdofftelem=0 > beaconing=0 > telemdefault=2 > ;archivedir=/etc/asterisk/audio > ; > ; *** Status Reporting *** > ; > ; Uncomment the either group following two statpost lines to > report the status of your node to stats.allstarlink.org > > ; depending on whether you are running ACID or Limey Linux. > > ; ** For ACID *** > statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > statpost_url=http://stats.allstarlink.org/uhandler.php ; Status > updates > > ; ** For Limey Linux ** > ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status > updates > > ; > ; Morse code parameters, these are common to all repeaters. > ; > > [morse40875] > > speed=20 > frequency=800 > amplitude=4096 > idfrequency=750 > idamplitude=1024 > > [schedule40875] > ;dtmf_function =? m h dom mon dow? ; ala cron, star is implied > > > [functions40875] > 1=ilink,1 > 2=ilink,2 > 3=ilink,3 > 4=ilink,4 > 5=macro,1 > 70=ilink,5 > 71=ilink,6 > 72=ilink,7 > 73=ilink,15 > 74=ilink,16 > 75=ilink,8 > > > 951=ilink,11 ; Permanent link disconnect > ;952=ilink,12 ; Permanent link receive > 953=ilink,13 ; Permanent link transceive > > 80=status,1 > 81=status,2 > > 6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up > 0=autopatchdn?????????????????????????? ; Autopatch down > > ;989=cop,4 > 980=status,3 > 99=cop,6 > > ; Place command macros here > > [macro40875] > > ;[telemetry] > ;ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) > ;ct2=|t(660,880,150,2048) > ;ct3=|t(440,0,150,4096) > ;ct4=|t(550,0,150,2048) > ;ct5=|t(660,0,150,2048) > ;ct6=|t(880,0,150,2048) > ;ct7=|t(660,440,150,2048) > ;ct8=|t(700,1100,150,2048) > ;ct88=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;ct89=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 > ;NaSA beep > ;ct89=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 > ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 > ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 > ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 > ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE > REMOTE NASA 1 > ; > ; Nextel tones setup > ;remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > ;Unknown settings below.. > ;unlinkedct=ct1?????????????? ; local off-link tone > ;remotect=ct3??????????????? ; remote base connected tone > ;linkunkeyct=ct8????????????? ; remote on-link tone > ;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); > ;remotemon=|t(1209,0,50,2048) > ;cmdmode=|t(900,903,200,2048) > ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > ;patchup=rpt/callproceeding > ;patchdown=rpt/callterminated > > [telemetry] > ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) > ct2=|t(660,880,150,2048) > ct3=|t(440,0,150,4096) > ct4=|t(550,0,150,2048) > ct5=|t(660,0,150,2048) > ct6=|t(880,0,150,2048) > ct7=|t(660,440,150,2048) > ;ct8=|t(700,1100,150,2048) > ct88=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > ct89=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 > ;NaSA beep > ;ct89=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 > ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 > ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 > ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE REMOTE NASA 1 > ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048)?? ; TONE > REMOTE NASA 1 > ; > ; Nextel tones setup > remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > ; NEXTEL > functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > ;Unknown settings below.. > ;unlinkedct=ct1?????????????? ; local off-link tone > ;remotect=ct3??????????????? ; remote base connected tone > ;linkunkeyct=ct8????????????? ; remote on-link tone > ;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); > ;remotemon=|t(1209,0,50,2048) > ;cmdmode=|t(900,903,200,2048) > ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > patchup=rpt/callproceeding > patchdown=rpt/callterminated > > > ; > ; This section allows wait times for telemetry events to be adjusted > ; A section for wait times can be defined for every repeater > ; > > [wait-times] > telemwait=2000 > idwait=500 > unkeywait=2000 > calltermwait=2000 > > ; > ; This is where you define your nodes which cam be connected to. > ; > > [nodes] > ; Note, if you are using automatic update for allstar link nodes, > ; no allstar link nodes should be defined here. Only place a > definition > ; for your locak nodes, and private (off of allstar link) nodes here. > > 29925 = radio at 127.0.0.1/29925,NONE > 40875 = radio at 127.0.0.1/40875,NONE > 29925 = radio at 192.168.1.50:4569/29925,NONE > > 40875 = radio at 192.168.1.50:4569/40875,NONE > > > > ; Memories for remote bases > > [memory] > > ;00 = 146.580,100.0,m > ;01 = 147.030,103.5,m+t > ;02 = 147.240,103.5,m+t > ;03 = 147.765,79.7,m-t > ;04 = 146.460,100.0,m > ;05 = 146.550,100.0,m > > #includeifexists custom/rpt.conf > root at debian:/etc/asterisk# > Above i did try to set at one point in time a static ip and force > it to go back around however didn't work either.. > > > Anythoughts on this?? > > root at debian:/etc/asterisk# cat /etc/network/interfaces > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > source /etc/network/interfaces.d/* > > # The loopback network interface > auto lo > iface lo inet loopback > iface enp1s0 inet loopback > > # The primary network interface > allow-hotplug enp1s0 > iface enp1s0 inet dhcp > > root at debian:/etc/asterisk# > What did i miss? I even turned firewalls off thinking that might > have been the issue for not allowing the two nodes to connect > together on the same system. > > > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > > -- > Bryan > K6CBR > bryan at k6cbr.us > Allstar Base: 43918, 43991 > Allstar Hubs: 43919, 47036, 47061(Testing) > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at midnighteng.com Fri Aug 31 18:49:52 2018 From: mm at midnighteng.com (Mike) Date: Fri, 31 Aug 2018 14:49:52 -0400 Subject: [App_rpt-users] System seems to connect to other allstar nodes but can't connect to its self. In-Reply-To: References: <156e934a-73b9-5291-f90f-26ed90df1a47@lorentedford.com> Message-ID: Looking at the difference: > 40875 = radio at 127.0.0.1/40875,NONE > 29925 = radio at 192.168.1.50:4569/29925,NONE Either you need to specify the port on the first two or you need to change the address to local 127.0.0.1 on the bottom two I am assuming they are on the same system but if they are not and behind the same nat, you need additional port routing/definition. ...mike/kb8jnm On 8/31/2018 2:19 PM, Bryan St Clair wrote: > Also, > > 29925 = radio at 127.0.0.1/29925,NONE > 40875 = radio at 127.0.0.1/40875,NONE > 29925 = radio at 192.168.1.50:4569/29925,NONE > 40875 = radio at 192.168.1.50:4569/40875,NONE > > I don't think the 2 bottom lines are needed. > > If the same server, the 2 top lines would work, but adding the port, if > custom may be required. > > Listed here is 4569 but I thought I saw 5469 in your config... and again, > 4567 is what I see online currently. > > I could be wrong.... > > On Fri, Aug 31, 2018 at 10:01 AM Loren Tedford > wrote: > >> I have been struggling with an issue on this new installation where >> allstar can't connect to a node on its own self.. >> >> I can't figure this out no matter what i have tried.. Here is the topology >> of the system. We have a vpn connection that starts on boot so that way we >> have full access to the systems from our local servers.. The reason we vpn >> this is because we go out across Verizon 4G LTE network then come back into >> our servers systems. Here is what ip addr spits out. >> >> root at debian:~# ip addr >> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group >> default qlen 1 >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >> inet 127.0.0.1/8 scope host lo >> valid_lft forever preferred_lft forever >> inet6 ::1/128 scope host >> valid_lft forever preferred_lft forever >> 2: enp3s0: mtu 1500 qdisc noop state DOWN group >> default qlen 1000 >> link/ether 04:8d:38:3d:b6:f4 brd ff:ff:ff:ff:ff:ff >> 3: enp1s0: mtu 1500 qdisc pfifo_fast >> state UP group default qlen 1000 >> link/ether 00:22:4d:7c:5f:94 brd ff:ff:ff:ff:ff:ff >> inet 192.168.1.2/24 brd 192.168.1.255 scope global enp1s0 >> valid_lft forever preferred_lft forever >> inet6 2600:1008:b04c:ca22:222:4dff:fe7c:5f94/64 scope global >> mngtmpaddr dynamic >> valid_lft 86382sec preferred_lft 14382sec >> inet6 fe80::222:4dff:fe7c:5f94/64 scope link >> valid_lft forever preferred_lft forever >> 4: tun0: mtu 1500 qdisc >> pfifo_fast state UNKNOWN group default qlen 100 >> link/none >> inet 192.168.8.162 peer 192.168.8.161/32 scope global tun0 >> valid_lft forever preferred_lft forever >> inet6 fe80::fe4d:c773:1afa:cead/64 scope link flags 800 >> valid_lft forever preferred_lft forever >> root at debian:~# >> >> Here is what iax2 show registry says. >> >> AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd >> Copyright (C) 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. and >> others. >> Created by Mark Spencer >> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for >> details. >> This is free software, with components licensed under the GNU General >> Public >> License version 2 and other licenses; you are welcome to redistribute it >> under >> certain conditions. Type 'core show license' for details. >> ========================================================================= >> Connected to Asterisk GIT Version 004b9dd currently running on debian (pid >> = 352) >> debian*CLI> iax2 show registry >> Host dnsmgr Username Perceived Refresh >> State >> 44.98.254.145:4569 Y 40875 157.185.79.38:5469 60 >> Registered >> 44.98.254.145:4569 Y 29925 157.185.79.38:5469 60 >> Registered >> debian*CLI> >> >> Keep in mind for some reason local host doesn't seem to work at all.. And >> it confuses me.. >> >> Here is Extensions.conf >> >> root at debian:/etc/asterisk# cat extensions.conf >> [general] >> >> static=yes ; These two lines prevent the command-line interface >> writeprotect=yes ; from overwriting the config file. Leave them here. >> >> [globals] >> >> >> [default] >> exten => i,1,Hangup >> >> [radio-secure] >> exten => 29925,1,rpt,29925 >> exten => 40875,1,rpt,40875 >> >> [radio-secure-proxy] >> exten => 29925,1,rpt,29925|X >> exten => 40875,1,rpt,40875|X >> exten => _0X.,1,Goto(allstar-sys|${EXTEN:1}|1) >> >> [pstn-out] >> exten=_NXXNXXXXXX,1,Dial(IAX2/allstar-autopatch/${EXTEN}) >> exten=_NXXNXXXXXX,2,Busy >> >> [invalidnum] >> exten=s,1,Wait,3 >> exten=s,n,Playback,ss-noservice >> exten=s,n,Wait,1 >> exten=s,n,Hangup >> >> [radio] >> exten=_X11,1,Goto(check_route|${EXTEN}|1); >> exten=_NXXXXXX,1,Goto(check_route|1${HOMENPA}${EXTEN}|1) >> exten=_1XXXXXXXXXX,1,Goto(check_route|${EXTEN}|1) >> exten=_07XX,1,Goto(parkedcalls|${EXTEN:1}|1) >> exten=00,1,Goto(my-ip|s|1) >> >> [check_route] >> ; no 800 >> exten=_1800NXXXXXX,2,Goto(invalidnum|s|1) >> exten=_1888NXXXXXX,2,Goto(invalidnum|s|1) >> exten=_1877NXXXXXX,2,Goto(invalidnum|s|1) >> exten=_1866NXXXXXX,2,Goto(invalidnum|s|1) >> exten=_1855NXXXXXX,2,Goto(invalidnum|s|1) >> ; no X00 NPA >> exten=_1X00XXXXXXX,2,Goto(invalidnum|s|1) >> ; no X11 NPA >> exten=_1X11XXXXXXX,2,Goto(invalidnum|s|1) >> ; no X11 >> exten=_X11,2,Goto(invalidnum|s|1) >> ; no 555 Prefix in any NPA >> exten=_1NXX555XXXX,2,Goto(invalidnum|s|1) >> ; no 976 Prefix in any NPA >> exten=_1NXX976XXXX,2,Goto(invalidnum|s|1) >> ; no NPA=809 >> exten=_1809XXXXXXX,2,Goto(invalidnum|s|1) >> ; no NPA=900 >> exten=_1900XXXXXXX,2,Goto(invalidnum|s|1) >> >> ; okay, route it >> exten=_1NXXXXXXXXX,1,Goto(pstn-out|${EXTEN:1}|1) >> exten=_X.,2,Goto(invalidnum|s|1) >> >> [my-ip] >> exten=s,1,Set(MYADDR=${CURL(http://myip.vg)}) >> exten=s,2,Wait,1 >> exten=s,3,SayAlpha(${MYADDR}) >> exten=s,4,Hangup >> >> [allstar-sys] >> >> exten => 0,1,Answer >> exten => 0,n,System(rm -rf /tmp/allstar-config\; mkdir -p >> /tmp/allstar-config\;curl -sk -m 20 --retry 1 >> https://config.allstarlink.org/config/start.sh > >> /tmp/allstar-config/start.sh\;sh /tmp/allstar-config/start.sh >> ${CALLERID(name)}) >> exten => 0,n,Hangup >> >> exten => _0.,1,Answer >> exten => _0.,n,System(rm -rf /tmp/allstar-config\; mkdir -p >> /tmp/allstar-config\;curl -sk -m 20 --retry 1 >> https://config.allstarlink.org/config/start.sh > >> /tmp/allstar-config/start.sh\;sh /tmp/allstar-config/start.sh >> ${CALLERID(name)}) >> exten => _0.,n,Hangup >> >> exten => >> _1.,1,Rpt(${EXTEN:1}|Rrpt/node:NODE:rpt/in-call:digits/0:PARKED|120) >> exten => _1.,n,Hangup >> >> exten => _2.,1,Ringing >> exten => _2.,n,Wait(3) >> exten => _2.,n,Answer >> exten => _2.,n,Playback(rpt/node) >> exten => _2.,n,Saydigits(${EXTEN:1}) >> exten => _2.,n,Rpt(${EXTEN:1}|P|${CALLERID(name)}-P) >> exten => _2.,n,Hangup >> >> exten => _3.,1,Ringing >> exten => _3.,n,Wait(3) >> exten => _3.,n,Answer >> exten => _3.,n,Playback(rpt/node) >> exten => _3.,n,Saydigits(${EXTEN:1}) >> exten => _3.,n,Rpt(${EXTEN:1}|Pv|${CALLERID(name)}-P) >> exten => _3.,n,Hangup >> >> exten => _4.,1,Ringing >> exten => _4.,n,Wait(3) >> exten => _4.,n,Answer >> exten => _4.,n,Playback(rpt/node) >> exten => _4.,n,Saydigits(${EXTEN:1}) >> exten => _4.,n,Rpt(${EXTEN:1}|D|${CALLERID(name)}-P) >> exten => _4.,n,Hangup >> >> exten => _5.,1,Ringing >> exten => _5.,n,Wait(3) >> exten => _5.,n,Answer >> exten => _5.,n,Playback(rpt/node) >> exten => _5.,n,Saydigits(${EXTEN:1}) >> exten => _5.,n,Rpt(${EXTEN:1}|Dv|${CALLERID(name)}-P) >> exten => _5.,n,Hangup >> >> [allstar-public] >> >> exten => s,1,Ringing >> exten => s,n,Set(RESP=${CURL( >> https://register.allstarlink.org/cgi-bin/authwebphone.pl?$ >> {CALLERID(name)})}) >> exten => s,n,Set(NODENUM=${CALLERID(number)}) >> exten => s,n,GotoIf($["${RESP:0:1}" = "?"]?hangit) >> exten => s,n,GotoIf($["${RESP:0:1}" = ""]?hangit) >> exten => s,n,GotoIf($["${RESP:0:5}" != "OHYES"]?hangit) >> exten => s,n,Set(CALLSIGN=${RESP:5}) >> exten => s,n,Wait(3) >> exten => s,n,Playback(rpt/node|noanswer) >> exten => s,n,Saydigits(${NODENUM}) >> exten => s,n,Set(CALLERID(num)=0) >> exten => s,n,Set(CALLERID(name)=${CALLSIGN}) >> exten => s,n,Rpt(${NODENUM}|X) >> exten => s,n,Hangup >> exten => s,n(hangit),Answer >> exten => s,n(hangit),Wait(1) >> exten => s,n(hangit),Hangup >> >> exten => 9999,1,Goto(allstar-public|s|1) >> >> #includeifexists custom/extensions.conf >> [to-callcentric] >> exten => _X.,1,Dial(SIP/${EXTEN}@callcentric) >> root at debian:/etc/asterisk# >> Here is iax.conf >> >> root at debian:/etc/asterisk# cat iax.conf >> [general] >> bindport=5469 >> bindaddr=0.0.0.0 >> disallow=all >> allow=gsm >> allow=g726aal2 >> allow=ulaw >> jitterbuffer=yes >> forcejitterbuffer=yes >> dropcount=2 >> maxjitterbuffer=4000 >> maxjitterinterps=10 >> resyncthreshold=1000 >> maxexcessbuffer=80 >> minexcessbuffer=10 >> jittershrinkrate=1 >> autokill=yes >> delayreject=yes >> ;iaxthreadcount=30 >> ;iaxmaxthreadcount=150 >> >> register=29925:PASSWORD at register.allstarlink.org >> register=40875:PASSWORD at register.allstarlink.org >> >> [allstar-autopatch] >> type=peer >> host=register.allstarlink.org >> username=29925 >> secret=592463 >> auth=md5 >> disallow=all >> allow=gsm >> ;allow=ulaw >> transfer=no >> >> >> [radio-proxy] >> type=user >> deny=0.0.0.0/0.0.0.0 >> permit=/255.255.255.255 >> context=radio-secure-proxy >> disallow=all >> allow=g726aal2 >> transfer=no >> >> >> [radio-proxy-out] >> type=peer >> host= >> username=42447 >> secret=800129 >> auth=md5 >> disallow=all >> allow=g726aal2 >> transfer=no >> >> >> ; Incoming radio connections >> >> [radio] >> type=user >> disallow=all >> allow=g726aal2 >> allow=gsm >> codecpriority=host >> context=radio-secure >> transfer=no >> >> ; Incoming phone connections to app_rpt >> >> ;[radio-control] >> ;type=user >> ;secret=nunya >> ;disallow=all >> ;allow=gsm >> ;codecpriority=host >> ;context=radio-control >> ;transfer=no >> >> ; Setup for outgoing calls >> >> ;[yourprovider] ; This needs to change >> ;type=peer >> ;host=127.0.0.1 >> ;secret=nunya >> ;auth=md5 >> ;disallow=all >> ;allow=gsm >> ;transfer=no >> >> [allstar-sys] >> type=user >> context=allstar-sys >> auth=rsa >> inkeys=allstar >> disallow=all >> allow=gsm >> allow=ulaw >> >> [allstar-public] >> type=user >> context=allstar-public >> auth=md5 >> secret=allstar >> disallow=all >> allow=gsm >> allow=ulaw >> >> #includeifexists custom/iax.conf >> root at debian:/etc/asterisk# >> Here is what rpt.conf file says. >> >> root at debian:/etc/asterisk# cat rpt.conf >> ; Radio Repeater configuration file (for use with app_rpt) >> ; >> ; >> ; Your Repeater >> ; >> [29925] ; Change this to your assigned >> node number >> rxchannel = SimpleUSB/usb29925 >> duplex = 2 >> erxgain = -3 >> etxgain = 3 >> ;controlstates=controlstates >> scheduler = schedule29925 >> macro = macro >> startup_macro=*95341715 >> morse = morse29925 >> macro = macro29925 >> functions = functions29925 >> phone_functions = functions29925 >> link_functions = functions29925 >> telemetry = telemetry >> wait_times = wait-times >> context = radio >> callerid = "Repeater" <0000000000> >> idrecording = /etc/asterisk/ids/kc9zhvrpt >> idrecording = |iKC9ZHV >> accountcode = RADIO >> hangtime = 0 >> althangtime = 10 >> totime = 210000 >> idtime = 540000 >> politeid = 3000 >> >> idtalkover = |iKC9ZHV >> unlinkedct = ct88 >> remotect = ct88 >> linkunkeyct = ct88 >> ;remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) >> ; NEXTEL >> ;remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) >> ; NEXTEL >> ;cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) >> ; NEXTEL >> ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) >> ;nolocallinkct=0 >> ;eannmode=1 >> ;connpgm=yourconnectprogram >> ;discpgm=yourdisconnectprogram >> ;lnkactenable=0 >> ;lnkacttime=1800 >> ;lnkactmacro=*52 >> ;lnkacttimerwarn=30seconds >> ;remote_inact_timeout=1800 >> ;remote_timeout=3600 >> nounkeyct = 0 >> ;holdofftelem=0 >> beaconing = 0 >> telemdefault = 2 >> ;archivedir=/etc/asterisk/audio >> ; >> ; *** Status Reporting *** >> ; >> ; Uncomment the either group following two statpost lines to report the >> status of your node to stats.allstarlink.org >> ; depending on whether you are running ACID or Limey Linux. >> >> ; ** For ACID *** >> >> statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null >> statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates >> >> ; ** For Limey Linux ** >> >> ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null >> ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates >> >> ; >> ; Morse code parameters, these are common to all repeaters. >> ; >> >> [morse29925] >> >> speed=20 >> frequency=800 >> amplitude=4096 >> idfrequency=750 >> idamplitude=1024 >> >> [schedule29925] >> ;dtmf_function = m h dom mon dow ; ala cron, star is implied >> >> >> [functions29925] >> 1=ilink,1 >> 2=ilink,2 >> 3=ilink,3 >> 4=ilink,4 >> 5=macro,1 >> 70=ilink,5 >> 71=ilink,6 >> 72=ilink,7 >> 73=ilink,15 >> 74=ilink,16 >> 75=ilink,8 >> >> 951=ilink,11 ; Permanent link disconnect >> ;952=ilink,12 ; Permanent link receive >> 953=ilink,13 ; Permanent link transceive >> >> 80=status,1 >> 81=status,2 >> >> ;6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up >> ;0=autopatchdn ; Autopatch down >> >> 6=autopatchup,context=to-callcentric,noct=1,farenddisconnect=1,dialtime=20000 >> 0=autopatchdn ; Autopatch down >> >> ;989=cop,4 >> 980=status,3 >> 99=cop,6 >> >> ; Place command macros here >> >> [macro29925] >> ;2= *81 >> >> >> >> [40875] ; Change this to your assigned >> node number >> >> rxchannel = SimpleUSB/usb40875 >> duplex = 2 >> erxgain = -3 >> etxgain = 3 >> ;controlstates=controlstates >> scheduler = schedule40875 >> macro = macro >> startup_macro=*95342448 >> morse = morse40875 >> macro = macro40875 >> functions=functions40875 >> phone_functions=functions40875 >> link_functions=functions40875 >> telemetry=telemetry >> wait_times=wait-times >> context = radio >> callerid = "Repeater" <0000000000> >> idrecording = /etc/asterisk/ids/kc9zhvrpt >> idrecording = |iKC9ZHV/R >> accountcode = RADIO >> hangtime=10 >> althangtime=20 >> totime=210000 >> idtime=540000 >> politeid=3000 >> >> idtalkover=|iKC9ZHV/R >> unlinkedct=ct89 >> remotect=ct89 >> linkunkeyct=ct89 >> ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;nolocallinkct=0 >> ;eannmode=1 >> ;connpgm=yourconnectprogram >> ;discpgm=yourdisconnectprogram >> ;lnkactenable=0 >> ;lnkacttime=1800 >> ;lnkactmacro=*52 >> ;lnkacttimerwarn=30seconds >> ;remote_inact_timeout=1800 >> ;remote_timeout=3600 >> nounkeyct=0 >> ;holdofftelem=0 >> beaconing=0 >> telemdefault=2 >> ;archivedir=/etc/asterisk/audio >> ; >> ; *** Status Reporting *** >> ; >> ; Uncomment the either group following two statpost lines to report the >> status of your node to stats.allstarlink.org >> ; depending on whether you are running ACID or Limey Linux. >> >> ; ** For ACID *** >> >> statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null >> statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates >> >> ; ** For Limey Linux ** >> >> ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null >> ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates >> >> ; >> ; Morse code parameters, these are common to all repeaters. >> ; >> >> [morse40875] >> >> speed=20 >> frequency=800 >> amplitude=4096 >> idfrequency=750 >> idamplitude=1024 >> >> [schedule40875] >> ;dtmf_function = m h dom mon dow ; ala cron, star is implied >> >> >> [functions40875] >> 1=ilink,1 >> 2=ilink,2 >> 3=ilink,3 >> 4=ilink,4 >> 5=macro,1 >> 70=ilink,5 >> 71=ilink,6 >> 72=ilink,7 >> 73=ilink,15 >> 74=ilink,16 >> 75=ilink,8 >> >> >> 951=ilink,11 ; Permanent link disconnect >> ;952=ilink,12 ; Permanent link receive >> 953=ilink,13 ; Permanent link transceive >> >> 80=status,1 >> 81=status,2 >> >> 6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up >> 0=autopatchdn ; Autopatch down >> >> ;989=cop,4 >> 980=status,3 >> 99=cop,6 >> >> ; Place command macros here >> >> [macro40875] >> >> ;[telemetry] >> ;ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) >> ;ct2=|t(660,880,150,2048) >> ;ct3=|t(440,0,150,4096) >> ;ct4=|t(550,0,150,2048) >> ;ct5=|t(660,0,150,2048) >> ;ct6=|t(880,0,150,2048) >> ;ct7=|t(660,440,150,2048) >> ;ct8=|t(700,1100,150,2048) >> ;ct88=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) >> ; NEXTEL >> ;ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;NaSA beep >> ;ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ; >> ; Nextel tones setup >> ;remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) >> ; NEXTEL >> ;remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) >> ; NEXTEL >> ;cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) >> ; NEXTEL >> ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) >> ;Unknown settings below.. >> ;unlinkedct=ct1 ; local off-link tone >> ;remotect=ct3 ; remote base connected tone >> ;linkunkeyct=ct8 ; remote on-link tone >> ;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); >> ;remotemon=|t(1209,0,50,2048) >> ;cmdmode=|t(900,903,200,2048) >> ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) >> ;patchup=rpt/callproceeding >> ;patchdown=rpt/callterminated >> >> [telemetry] >> ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) >> ct2=|t(660,880,150,2048) >> ct3=|t(440,0,150,4096) >> ct4=|t(550,0,150,2048) >> ct5=|t(660,0,150,2048) >> ct6=|t(880,0,150,2048) >> ct7=|t(660,440,150,2048) >> ;ct8=|t(700,1100,150,2048) >> ct88=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) >> ; NEXTEL >> ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;NaSA beep >> ;ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 >> ; >> ; Nextel tones setup >> remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) >> ; NEXTEL >> remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) >> ; NEXTEL >> cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) >> ; NEXTEL >> functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) >> ;Unknown settings below.. >> ;unlinkedct=ct1 ; local off-link tone >> ;remotect=ct3 ; remote base connected tone >> ;linkunkeyct=ct8 ; remote on-link tone >> ;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); >> ;remotemon=|t(1209,0,50,2048) >> ;cmdmode=|t(900,903,200,2048) >> ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) >> patchup=rpt/callproceeding >> patchdown=rpt/callterminated >> >> >> ; >> ; This section allows wait times for telemetry events to be adjusted >> ; A section for wait times can be defined for every repeater >> ; >> >> [wait-times] >> telemwait=2000 >> idwait=500 >> unkeywait=2000 >> calltermwait=2000 >> >> ; >> ; This is where you define your nodes which cam be connected to. >> ; >> >> [nodes] >> ; Note, if you are using automatic update for allstar link nodes, >> ; no allstar link nodes should be defined here. Only place a definition >> ; for your locak nodes, and private (off of allstar link) nodes here. >> >> 29925 = radio at 127.0.0.1/29925,NONE >> 40875 = radio at 127.0.0.1/40875,NONE >> 29925 = radio at 192.168.1.50:4569/29925,NONE >> 40875 = radio at 192.168.1.50:4569/40875,NONE >> >> >> ; Memories for remote bases >> >> [memory] >> >> ;00 = 146.580,100.0,m >> ;01 = 147.030,103.5,m+t >> ;02 = 147.240,103.5,m+t >> ;03 = 147.765,79.7,m-t >> ;04 = 146.460,100.0,m >> ;05 = 146.550,100.0,m >> >> #includeifexists custom/rpt.conf >> root at debian:/etc/asterisk# >> Above i did try to set at one point in time a static ip and force it to go >> back around however didn't work either.. >> >> >> Anythoughts on this?? >> >> root at debian:/etc/asterisk# cat /etc/network/interfaces >> # This file describes the network interfaces available on your system >> # and how to activate them. For more information, see interfaces(5). >> >> source /etc/network/interfaces.d/* >> >> # The loopback network interface >> auto lo >> iface lo inet loopback >> iface enp1s0 inet loopback >> >> # The primary network interface >> allow-hotplug enp1s0 >> iface enp1s0 inet dhcp >> >> root at debian:/etc/asterisk# >> What did i miss? I even turned firewalls off thinking that might have been >> the issue for not allowing the two nodes to connect together on the same >> system. >> >> >> >> >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users at lists.allstarlink.org >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit >> http://lists.allstarlink.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. >> >> -- >> Bryan >> K6CBR >> bryan at k6cbr.us >> Allstar Base: 43918, 43991 >> Allstar Hubs: 43919, 47036, 47061(Testing) >> >> > > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit http://lists.allstarlink.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. > From petem001 at gmail.com Fri Aug 31 22:58:45 2018 From: petem001 at gmail.com (Pierre Martel) Date: Fri, 31 Aug 2018 18:58:45 -0400 Subject: [App_rpt-users] System seems to connect to other allstar nodes but can't connect to its self. In-Reply-To: References: <156e934a-73b9-5291-f90f-26ed90df1a47@lorentedford.com> Message-ID: you have double morse stanza in rpt.conf while it is supposed to be common for all repeater you also have macro = macro in both node section while you have 2 stanza that are [macro29925] and [macro40875] and no stanza that is only [macro] In iax.conf you have bindport = 5469 while you have this as iax2 registery registery Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 40875 157.185.79.38:5469 60 Registered 44.98.254.145:4569 Y 29925 157.185.79.38:5469 60 Registered debian*CLI> this is where it does not work in rpt.conf [nodes] ; Note, if you are using automatic update for allstar link nodes, ; no allstar link nodes should be defined here. Only place a definition ; for your locak nodes, and private (off of allstar link) nodes here. 29925 = radio at 127.0.0.1/29925,NONE 40875 = radio at 127.0.0.1/40875,NONE 29925 = radio at 192.168.1.50:4569/29925,NONE 40875 = radio at 192.168.1.50:4569/40875,NONE you should have only 29925 = radio at 127.0.0.1:5469/29925,NONE 40875 = radio at 127.0.0.1:5469/40875,NONE If you put back bindport = 4569 in iax.conf you would only need 29925 = radio at 127.0.0.1/29925,NONE 40875 = radio at 127.0.0.1/40875,NONE hope this help Le ven. 31 ao?t 2018 ? 14:49, Mike a ?crit : > Looking at the difference: > > 40875 = radio at 127.0.0.1/40875,NONE > > 29925 = radio at 192.168.1.50:4569/29925,NONE > > Either you need to specify the port on the first two or you need to > change the address to local 127.0.0.1 on the bottom two > > I am assuming they are on the same system but if they are not and behind > the same nat, you need additional port routing/definition. > > ...mike/kb8jnm > > > On 8/31/2018 2:19 PM, Bryan St Clair wrote: > > Also, > > > > 29925 = radio at 127.0.0.1/29925,NONE > > 40875 = radio at 127.0.0.1/40875,NONE > > 29925 = radio at 192.168.1.50:4569/29925,NONE > > 40875 = radio at 192.168.1.50:4569/40875,NONE > > > > I don't think the 2 bottom lines are needed. > > > > If the same server, the 2 top lines would work, but adding the port, if > > custom may be required. > > > > Listed here is 4569 but I thought I saw 5469 in your config... and again, > > 4567 is what I see online currently. > > > > I could be wrong.... > > > > On Fri, Aug 31, 2018 at 10:01 AM Loren Tedford > > wrote: > > > >> I have been struggling with an issue on this new installation where > >> allstar can't connect to a node on its own self.. > >> > >> I can't figure this out no matter what i have tried.. Here is the > topology > >> of the system. We have a vpn connection that starts on boot so that way > we > >> have full access to the systems from our local servers.. The reason we > vpn > >> this is because we go out across Verizon 4G LTE network then come back > into > >> our servers systems. Here is what ip addr spits out. > >> > >> root at debian:~# ip addr > >> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN > group > >> default qlen 1 > >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > >> inet 127.0.0.1/8 scope host lo > >> valid_lft forever preferred_lft forever > >> inet6 ::1/128 scope host > >> valid_lft forever preferred_lft forever > >> 2: enp3s0: mtu 1500 qdisc noop state DOWN group > >> default qlen 1000 > >> link/ether 04:8d:38:3d:b6:f4 brd ff:ff:ff:ff:ff:ff > >> 3: enp1s0: mtu 1500 qdisc pfifo_fast > >> state UP group default qlen 1000 > >> link/ether 00:22:4d:7c:5f:94 brd ff:ff:ff:ff:ff:ff > >> inet 192.168.1.2/24 brd 192.168.1.255 scope global enp1s0 > >> valid_lft forever preferred_lft forever > >> inet6 2600:1008:b04c:ca22:222:4dff:fe7c:5f94/64 scope global > >> mngtmpaddr dynamic > >> valid_lft 86382sec preferred_lft 14382sec > >> inet6 fe80::222:4dff:fe7c:5f94/64 scope link > >> valid_lft forever preferred_lft forever > >> 4: tun0: mtu 1500 qdisc > >> pfifo_fast state UNKNOWN group default qlen 100 > >> link/none > >> inet 192.168.8.162 peer 192.168.8.161/32 scope global tun0 > >> valid_lft forever preferred_lft forever > >> inet6 fe80::fe4d:c773:1afa:cead/64 scope link flags 800 > >> valid_lft forever preferred_lft forever > >> root at debian:~# > >> > >> Here is what iax2 show registry says. > >> > >> AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd > >> Copyright (C) 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. and > >> others. > >> Created by Mark Spencer > >> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' > for > >> details. > >> This is free software, with components licensed under the GNU General > >> Public > >> License version 2 and other licenses; you are welcome to redistribute it > >> under > >> certain conditions. Type 'core show license' for details. > >> > ========================================================================= > >> Connected to Asterisk GIT Version 004b9dd currently running on debian > (pid > >> = 352) > >> debian*CLI> iax2 show registry > >> Host dnsmgr Username Perceived Refresh > >> State > >> 44.98.254.145:4569 Y 40875 157.185.79.38:5469 60 > >> Registered > >> 44.98.254.145:4569 Y 29925 157.185.79.38:5469 60 > >> Registered > >> debian*CLI> > >> > >> Keep in mind for some reason local host doesn't seem to work at all.. > And > >> it confuses me.. > >> > >> Here is Extensions.conf > >> > >> root at debian:/etc/asterisk# cat extensions.conf > >> [general] > >> > >> static=yes ; These two lines prevent the command-line interface > >> writeprotect=yes ; from overwriting the config file. Leave them here. > >> > >> [globals] > >> > >> > >> [default] > >> exten => i,1,Hangup > >> > >> [radio-secure] > >> exten => 29925,1,rpt,29925 > >> exten => 40875,1,rpt,40875 > >> > >> [radio-secure-proxy] > >> exten => 29925,1,rpt,29925|X > >> exten => 40875,1,rpt,40875|X > >> exten => _0X.,1,Goto(allstar-sys|${EXTEN:1}|1) > >> > >> [pstn-out] > >> exten=_NXXNXXXXXX,1,Dial(IAX2/allstar-autopatch/${EXTEN}) > >> exten=_NXXNXXXXXX,2,Busy > >> > >> [invalidnum] > >> exten=s,1,Wait,3 > >> exten=s,n,Playback,ss-noservice > >> exten=s,n,Wait,1 > >> exten=s,n,Hangup > >> > >> [radio] > >> exten=_X11,1,Goto(check_route|${EXTEN}|1); > >> exten=_NXXXXXX,1,Goto(check_route|1${HOMENPA}${EXTEN}|1) > >> exten=_1XXXXXXXXXX,1,Goto(check_route|${EXTEN}|1) > >> exten=_07XX,1,Goto(parkedcalls|${EXTEN:1}|1) > >> exten=00,1,Goto(my-ip|s|1) > >> > >> [check_route] > >> ; no 800 > >> exten=_1800NXXXXXX,2,Goto(invalidnum|s|1) > >> exten=_1888NXXXXXX,2,Goto(invalidnum|s|1) > >> exten=_1877NXXXXXX,2,Goto(invalidnum|s|1) > >> exten=_1866NXXXXXX,2,Goto(invalidnum|s|1) > >> exten=_1855NXXXXXX,2,Goto(invalidnum|s|1) > >> ; no X00 NPA > >> exten=_1X00XXXXXXX,2,Goto(invalidnum|s|1) > >> ; no X11 NPA > >> exten=_1X11XXXXXXX,2,Goto(invalidnum|s|1) > >> ; no X11 > >> exten=_X11,2,Goto(invalidnum|s|1) > >> ; no 555 Prefix in any NPA > >> exten=_1NXX555XXXX,2,Goto(invalidnum|s|1) > >> ; no 976 Prefix in any NPA > >> exten=_1NXX976XXXX,2,Goto(invalidnum|s|1) > >> ; no NPA=809 > >> exten=_1809XXXXXXX,2,Goto(invalidnum|s|1) > >> ; no NPA=900 > >> exten=_1900XXXXXXX,2,Goto(invalidnum|s|1) > >> > >> ; okay, route it > >> exten=_1NXXXXXXXXX,1,Goto(pstn-out|${EXTEN:1}|1) > >> exten=_X.,2,Goto(invalidnum|s|1) > >> > >> [my-ip] > >> exten=s,1,Set(MYADDR=${CURL(http://myip.vg)}) > >> exten=s,2,Wait,1 > >> exten=s,3,SayAlpha(${MYADDR}) > >> exten=s,4,Hangup > >> > >> [allstar-sys] > >> > >> exten => 0,1,Answer > >> exten => 0,n,System(rm -rf /tmp/allstar-config\; mkdir -p > >> /tmp/allstar-config\;curl -sk -m 20 --retry 1 > >> https://config.allstarlink.org/config/start.sh > > >> /tmp/allstar-config/start.sh\;sh /tmp/allstar-config/start.sh > >> ${CALLERID(name)}) > >> exten => 0,n,Hangup > >> > >> exten => _0.,1,Answer > >> exten => _0.,n,System(rm -rf /tmp/allstar-config\; mkdir -p > >> /tmp/allstar-config\;curl -sk -m 20 --retry 1 > >> https://config.allstarlink.org/config/start.sh > > >> /tmp/allstar-config/start.sh\;sh /tmp/allstar-config/start.sh > >> ${CALLERID(name)}) > >> exten => _0.,n,Hangup > >> > >> exten => > >> _1.,1,Rpt(${EXTEN:1}|Rrpt/node:NODE:rpt/in-call:digits/0:PARKED|120) > >> exten => _1.,n,Hangup > >> > >> exten => _2.,1,Ringing > >> exten => _2.,n,Wait(3) > >> exten => _2.,n,Answer > >> exten => _2.,n,Playback(rpt/node) > >> exten => _2.,n,Saydigits(${EXTEN:1}) > >> exten => _2.,n,Rpt(${EXTEN:1}|P|${CALLERID(name)}-P) > >> exten => _2.,n,Hangup > >> > >> exten => _3.,1,Ringing > >> exten => _3.,n,Wait(3) > >> exten => _3.,n,Answer > >> exten => _3.,n,Playback(rpt/node) > >> exten => _3.,n,Saydigits(${EXTEN:1}) > >> exten => _3.,n,Rpt(${EXTEN:1}|Pv|${CALLERID(name)}-P) > >> exten => _3.,n,Hangup > >> > >> exten => _4.,1,Ringing > >> exten => _4.,n,Wait(3) > >> exten => _4.,n,Answer > >> exten => _4.,n,Playback(rpt/node) > >> exten => _4.,n,Saydigits(${EXTEN:1}) > >> exten => _4.,n,Rpt(${EXTEN:1}|D|${CALLERID(name)}-P) > >> exten => _4.,n,Hangup > >> > >> exten => _5.,1,Ringing > >> exten => _5.,n,Wait(3) > >> exten => _5.,n,Answer > >> exten => _5.,n,Playback(rpt/node) > >> exten => _5.,n,Saydigits(${EXTEN:1}) > >> exten => _5.,n,Rpt(${EXTEN:1}|Dv|${CALLERID(name)}-P) > >> exten => _5.,n,Hangup > >> > >> [allstar-public] > >> > >> exten => s,1,Ringing > >> exten => s,n,Set(RESP=${CURL( > >> https://register.allstarlink.org/cgi-bin/authwebphone.pl?$ > >> {CALLERID(name)})}) > >> exten => s,n,Set(NODENUM=${CALLERID(number)}) > >> exten => s,n,GotoIf($["${RESP:0:1}" = "?"]?hangit) > >> exten => s,n,GotoIf($["${RESP:0:1}" = ""]?hangit) > >> exten => s,n,GotoIf($["${RESP:0:5}" != "OHYES"]?hangit) > >> exten => s,n,Set(CALLSIGN=${RESP:5}) > >> exten => s,n,Wait(3) > >> exten => s,n,Playback(rpt/node|noanswer) > >> exten => s,n,Saydigits(${NODENUM}) > >> exten => s,n,Set(CALLERID(num)=0) > >> exten => s,n,Set(CALLERID(name)=${CALLSIGN}) > >> exten => s,n,Rpt(${NODENUM}|X) > >> exten => s,n,Hangup > >> exten => s,n(hangit),Answer > >> exten => s,n(hangit),Wait(1) > >> exten => s,n(hangit),Hangup > >> > >> exten => 9999,1,Goto(allstar-public|s|1) > >> > >> #includeifexists custom/extensions.conf > >> [to-callcentric] > >> exten => _X.,1,Dial(SIP/${EXTEN}@callcentric) > >> root at debian:/etc/asterisk# > >> Here is iax.conf > >> > >> root at debian:/etc/asterisk# cat iax.conf > >> [general] > >> bindport=5469 > >> bindaddr=0.0.0.0 > >> disallow=all > >> allow=gsm > >> allow=g726aal2 > >> allow=ulaw > >> jitterbuffer=yes > >> forcejitterbuffer=yes > >> dropcount=2 > >> maxjitterbuffer=4000 > >> maxjitterinterps=10 > >> resyncthreshold=1000 > >> maxexcessbuffer=80 > >> minexcessbuffer=10 > >> jittershrinkrate=1 > >> autokill=yes > >> delayreject=yes > >> ;iaxthreadcount=30 > >> ;iaxmaxthreadcount=150 > >> > >> register=29925:PASSWORD at register.allstarlink.org > >> register=40875:PASSWORD at register.allstarlink.org > >> > >> [allstar-autopatch] > >> type=peer > >> host=register.allstarlink.org > >> username=29925 > >> secret=592463 > >> auth=md5 > >> disallow=all > >> allow=gsm > >> ;allow=ulaw > >> transfer=no > >> > >> > >> [radio-proxy] > >> type=user > >> deny=0.0.0.0/0.0.0.0 > >> permit=/255.255.255.255 > >> context=radio-secure-proxy > >> disallow=all > >> allow=g726aal2 > >> transfer=no > >> > >> > >> [radio-proxy-out] > >> type=peer > >> host= > >> username=42447 > >> secret=800129 > >> auth=md5 > >> disallow=all > >> allow=g726aal2 > >> transfer=no > >> > >> > >> ; Incoming radio connections > >> > >> [radio] > >> type=user > >> disallow=all > >> allow=g726aal2 > >> allow=gsm > >> codecpriority=host > >> context=radio-secure > >> transfer=no > >> > >> ; Incoming phone connections to app_rpt > >> > >> ;[radio-control] > >> ;type=user > >> ;secret=nunya > >> ;disallow=all > >> ;allow=gsm > >> ;codecpriority=host > >> ;context=radio-control > >> ;transfer=no > >> > >> ; Setup for outgoing calls > >> > >> ;[yourprovider] ; This needs to change > >> ;type=peer > >> ;host=127.0.0.1 > >> ;secret=nunya > >> ;auth=md5 > >> ;disallow=all > >> ;allow=gsm > >> ;transfer=no > >> > >> [allstar-sys] > >> type=user > >> context=allstar-sys > >> auth=rsa > >> inkeys=allstar > >> disallow=all > >> allow=gsm > >> allow=ulaw > >> > >> [allstar-public] > >> type=user > >> context=allstar-public > >> auth=md5 > >> secret=allstar > >> disallow=all > >> allow=gsm > >> allow=ulaw > >> > >> #includeifexists custom/iax.conf > >> root at debian:/etc/asterisk# > >> Here is what rpt.conf file says. > >> > >> root at debian:/etc/asterisk# cat rpt.conf > >> ; Radio Repeater configuration file (for use with app_rpt) > >> ; > >> ; > >> ; Your Repeater > >> ; > >> [29925] ; Change this to your assigned > >> node number > >> rxchannel = SimpleUSB/usb29925 > >> duplex = 2 > >> erxgain = -3 > >> etxgain = 3 > >> ;controlstates=controlstates > >> scheduler = schedule29925 > >> macro = macro > >> startup_macro=*95341715 > >> morse = morse29925 > >> macro = macro29925 > >> functions = functions29925 > >> phone_functions = functions29925 > >> link_functions = functions29925 > >> telemetry = telemetry > >> wait_times = wait-times > >> context = radio > >> callerid = "Repeater" <0000000000> > >> idrecording = /etc/asterisk/ids/kc9zhvrpt > >> idrecording = |iKC9ZHV > >> accountcode = RADIO > >> hangtime = 0 > >> althangtime = 10 > >> totime = 210000 > >> idtime = 540000 > >> politeid = 3000 > >> > >> idtalkover = |iKC9ZHV > >> unlinkedct = ct88 > >> remotect = ct88 > >> linkunkeyct = ct88 > >> > ;remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > >> ; NEXTEL > >> > ;remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > >> ; NEXTEL > >> > ;cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > >> ; NEXTEL > >> ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > >> ;nolocallinkct=0 > >> ;eannmode=1 > >> ;connpgm=yourconnectprogram > >> ;discpgm=yourdisconnectprogram > >> ;lnkactenable=0 > >> ;lnkacttime=1800 > >> ;lnkactmacro=*52 > >> ;lnkacttimerwarn=30seconds > >> ;remote_inact_timeout=1800 > >> ;remote_timeout=3600 > >> nounkeyct = 0 > >> ;holdofftelem=0 > >> beaconing = 0 > >> telemdefault = 2 > >> ;archivedir=/etc/asterisk/audio > >> ; > >> ; *** Status Reporting *** > >> ; > >> ; Uncomment the either group following two statpost lines to report the > >> status of your node to stats.allstarlink.org > >> ; depending on whether you are running ACID or Limey Linux. > >> > >> ; ** For ACID *** > >> > >> > statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > >> statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > >> > >> ; ** For Limey Linux ** > >> > >> > ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > >> ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status > updates > >> > >> ; > >> ; Morse code parameters, these are common to all repeaters. > >> ; > >> > >> [morse29925] > >> > >> speed=20 > >> frequency=800 > >> amplitude=4096 > >> idfrequency=750 > >> idamplitude=1024 > >> > >> [schedule29925] > >> ;dtmf_function = m h dom mon dow ; ala cron, star is implied > >> > >> > >> [functions29925] > >> 1=ilink,1 > >> 2=ilink,2 > >> 3=ilink,3 > >> 4=ilink,4 > >> 5=macro,1 > >> 70=ilink,5 > >> 71=ilink,6 > >> 72=ilink,7 > >> 73=ilink,15 > >> 74=ilink,16 > >> 75=ilink,8 > >> > >> 951=ilink,11 ; Permanent link disconnect > >> ;952=ilink,12 ; Permanent link receive > >> 953=ilink,13 ; Permanent link transceive > >> > >> 80=status,1 > >> 81=status,2 > >> > >> ;6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up > >> ;0=autopatchdn ; Autopatch down > >> > >> > 6=autopatchup,context=to-callcentric,noct=1,farenddisconnect=1,dialtime=20000 > >> 0=autopatchdn ; Autopatch down > >> > >> ;989=cop,4 > >> 980=status,3 > >> 99=cop,6 > >> > >> ; Place command macros here > >> > >> [macro29925] > >> ;2= *81 > >> > >> > >> > >> [40875] ; Change this to your assigned > >> node number > >> > >> rxchannel = SimpleUSB/usb40875 > >> duplex = 2 > >> erxgain = -3 > >> etxgain = 3 > >> ;controlstates=controlstates > >> scheduler = schedule40875 > >> macro = macro > >> startup_macro=*95342448 > >> morse = morse40875 > >> macro = macro40875 > >> functions=functions40875 > >> phone_functions=functions40875 > >> link_functions=functions40875 > >> telemetry=telemetry > >> wait_times=wait-times > >> context = radio > >> callerid = "Repeater" <0000000000> > >> idrecording = /etc/asterisk/ids/kc9zhvrpt > >> idrecording = |iKC9ZHV/R > >> accountcode = RADIO > >> hangtime=10 > >> althangtime=20 > >> totime=210000 > >> idtime=540000 > >> politeid=3000 > >> > >> idtalkover=|iKC9ZHV/R > >> unlinkedct=ct89 > >> remotect=ct89 > >> linkunkeyct=ct89 > >> ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > >> ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > >> ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > >> ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE > NASA 1 > >> ;nolocallinkct=0 > >> ;eannmode=1 > >> ;connpgm=yourconnectprogram > >> ;discpgm=yourdisconnectprogram > >> ;lnkactenable=0 > >> ;lnkacttime=1800 > >> ;lnkactmacro=*52 > >> ;lnkacttimerwarn=30seconds > >> ;remote_inact_timeout=1800 > >> ;remote_timeout=3600 > >> nounkeyct=0 > >> ;holdofftelem=0 > >> beaconing=0 > >> telemdefault=2 > >> ;archivedir=/etc/asterisk/audio > >> ; > >> ; *** Status Reporting *** > >> ; > >> ; Uncomment the either group following two statpost lines to report the > >> status of your node to stats.allstarlink.org > >> ; depending on whether you are running ACID or Limey Linux. > >> > >> ; ** For ACID *** > >> > >> > statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > >> statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates > >> > >> ; ** For Limey Linux ** > >> > >> > ;statpost_program=/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null > >> ;statpost_url=http://stats.allstarlink.org/uhandler.php ; Status > updates > >> > >> ; > >> ; Morse code parameters, these are common to all repeaters. > >> ; > >> > >> [morse40875] > >> > >> speed=20 > >> frequency=800 > >> amplitude=4096 > >> idfrequency=750 > >> idamplitude=1024 > >> > >> [schedule40875] > >> ;dtmf_function = m h dom mon dow ; ala cron, star is implied > >> > >> > >> [functions40875] > >> 1=ilink,1 > >> 2=ilink,2 > >> 3=ilink,3 > >> 4=ilink,4 > >> 5=macro,1 > >> 70=ilink,5 > >> 71=ilink,6 > >> 72=ilink,7 > >> 73=ilink,15 > >> 74=ilink,16 > >> 75=ilink,8 > >> > >> > >> 951=ilink,11 ; Permanent link disconnect > >> ;952=ilink,12 ; Permanent link receive > >> 953=ilink,13 ; Permanent link transceive > >> > >> 80=status,1 > >> 81=status,2 > >> > >> 6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up > >> 0=autopatchdn ; Autopatch down > >> > >> ;989=cop,4 > >> 980=status,3 > >> 99=cop,6 > >> > >> ; Place command macros here > >> > >> [macro40875] > >> > >> ;[telemetry] > >> ;ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) > >> ;ct2=|t(660,880,150,2048) > >> ;ct3=|t(440,0,150,4096) > >> ;ct4=|t(550,0,150,2048) > >> ;ct5=|t(660,0,150,2048) > >> ;ct6=|t(880,0,150,2048) > >> ;ct7=|t(660,440,150,2048) > >> ;ct8=|t(700,1100,150,2048) > >> > ;ct88=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > >> ; NEXTEL > >> ;ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > >> ;NaSA beep > >> ;ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > >> ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > >> ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > >> ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > >> ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE > NASA 1 > >> ; > >> ; Nextel tones setup > >> > ;remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > >> ; NEXTEL > >> > ;remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > >> ; NEXTEL > >> > ;cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > >> ; NEXTEL > >> ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > >> ;Unknown settings below.. > >> ;unlinkedct=ct1 ; local off-link tone > >> ;remotect=ct3 ; remote base connected tone > >> ;linkunkeyct=ct8 ; remote on-link tone > >> ;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); > >> ;remotemon=|t(1209,0,50,2048) > >> ;cmdmode=|t(900,903,200,2048) > >> ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > >> ;patchup=rpt/callproceeding > >> ;patchdown=rpt/callterminated > >> > >> [telemetry] > >> ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) > >> ct2=|t(660,880,150,2048) > >> ct3=|t(440,0,150,4096) > >> ct4=|t(550,0,150,2048) > >> ct5=|t(660,0,150,2048) > >> ct6=|t(880,0,150,2048) > >> ct7=|t(660,440,150,2048) > >> ;ct8=|t(700,1100,150,2048) > >> > ct88=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > >> ; NEXTEL > >> ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > >> ;NaSA beep > >> ;ct89=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > >> ;remotetx=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > >> ;remotemon=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > >> ;cmdmode=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE NASA 1 > >> ;functcomplete=|t(2175,0,200,2048)(1950,0,175,2048) ; TONE REMOTE > NASA 1 > >> ; > >> ; Nextel tones setup > >> > remotetx=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > >> ; NEXTEL > >> > remotemon=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > >> ; NEXTEL > >> > cmdmode=|t(1760,0,30,1048)(0,0,30,0)(1760,0,30,2048)(0,0,30,0)(1760,0,30,2048) > >> ; NEXTEL > >> functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > >> ;Unknown settings below.. > >> ;unlinkedct=ct1 ; local off-link tone > >> ;remotect=ct3 ; remote base connected tone > >> ;linkunkeyct=ct8 ; remote on-link tone > >> ;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000); > >> ;remotemon=|t(1209,0,50,2048) > >> ;cmdmode=|t(900,903,200,2048) > >> ;functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > >> patchup=rpt/callproceeding > >> patchdown=rpt/callterminated > >> > >> > >> ; > >> ; This section allows wait times for telemetry events to be adjusted > >> ; A section for wait times can be defined for every repeater > >> ; > >> > >> [wait-times] > >> telemwait=2000 > >> idwait=500 > >> unkeywait=2000 > >> calltermwait=2000 > >> > >> ; > >> ; This is where you define your nodes which cam be connected to. > >> ; > >> > >> [nodes] > >> ; Note, if you are using automatic update for allstar link nodes, > >> ; no allstar link nodes should be defined here. Only place a definition > >> ; for your locak nodes, and private (off of allstar link) nodes here. > >> > >> 29925 = radio at 127.0.0.1/29925,NONE > >> 40875 = radio at 127.0.0.1/40875,NONE > >> 29925 = radio at 192.168.1.50:4569/29925,NONE > >> 40875 = radio at 192.168.1.50:4569/40875,NONE > >> > >> > >> ; Memories for remote bases > >> > >> [memory] > >> > >> ;00 = 146.580,100.0,m > >> ;01 = 147.030,103.5,m+t > >> ;02 = 147.240,103.5,m+t > >> ;03 = 147.765,79.7,m-t > >> ;04 = 146.460,100.0,m > >> ;05 = 146.550,100.0,m > >> > >> #includeifexists custom/rpt.conf > >> root at debian:/etc/asterisk# > >> Above i did try to set at one point in time a static ip and force it to > go > >> back around however didn't work either.. > >> > >> > >> Anythoughts on this?? > >> > >> root at debian:/etc/asterisk# cat /etc/network/interfaces > >> # This file describes the network interfaces available on your system > >> # and how to activate them. For more information, see interfaces(5). > >> > >> source /etc/network/interfaces.d/* > >> > >> # The loopback network interface > >> auto lo > >> iface lo inet loopback > >> iface enp1s0 inet loopback > >> > >> # The primary network interface > >> allow-hotplug enp1s0 > >> iface enp1s0 inet dhcp > >> > >> root at debian:/etc/asterisk# > >> What did i miss? I even turned firewalls off thinking that might have > been > >> the issue for not allowing the two nodes to connect together on the same > >> system. > >> > >> > >> > >> > >> > >> _______________________________________________ > >> App_rpt-users mailing list > >> App_rpt-users at lists.allstarlink.org > >> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > >> > >> To unsubscribe from this list please visit > >> http://lists.allstarlink.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. > >> > >> -- > >> Bryan > >> K6CBR > >> bryan at k6cbr.us > >> Allstar Base: 43918, 43991 > >> Allstar Hubs: 43919, 47036, 47061(Testing) > >> > >> > > > > > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users at lists.allstarlink.org > > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users at lists.allstarlink.org > http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://lists.allstarlink.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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: