- App_rpt-users - lists.keekles.org

Re: [App_rpt-users] App_rpt-users Digest, Vol 69, Issue 27
by Corey 16 Nov '14

16 Nov '14

Chuck, I fixed all my issues. I didn't realize the difference between a NMEA & Garmin sentence. I deselected all sentences that started with "P" in the SNSRCFG program, reloaded the GPS file, and my warning went away. I was able to update the firmware with your advice. Thanks again for your help, Corey On 11/14/2014 11:51 PM, app_rpt-users-request(a)ohnosec.org wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users(a)ohnosec.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request(a)ohnosec.org > > You can reach the person managing the list at > app_rpt-users-owner(a)ohnosec.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > > Today's Topics: > > 1. Re: EchoLink Policy Reminder (Johnny Keeker) > 2. Voter board (Corey) > 3. Re: Voter board (Chuck Henderson) > 4. Re: Voter board (Chuck Henderson) > 5. Re: Voter board (Chuck Henderson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 14 Nov 2014 14:44:54 -0800 > From: Johnny Keeker <cypresstower(a)yahoo.com> > To: kk6ecm <kk6ecm(a)gmail.com>, Kirk Just Kirk <wb6egr(a)gmail.com> > Cc: app_rpt mailing list <app_rpt-users(a)ohnosec.org> > Subject: Re: [App_rpt-users] EchoLink Policy Reminder > Message-ID: > <1416005094.33956.YahooMailBasic(a)web163604.mail.gq1.yahoo.com> > Content-Type: text/plain; charset=iso-8859-1 > > When they kill our accounts we'll say EchoStink Stunk > -------------------------------------------- > On Tue, 11/11/14, Kirk Just Kirk <wb6egr(a)gmail.com> wrote: > > Subject: Re: [App_rpt-users] EchoLink Policy Reminder > To: "kk6ecm" <kk6ecm(a)gmail.com> > Cc: "app_rpt mailing list" <app_rpt-users(a)ohnosec.org> > Date: Tuesday, November 11, 2014, 7:08 PM > > They can > close/kill my account anytime. EchoStink sounds horrible > most of the time...constant drivebys from dingalings that > connect and disconnect over and over and say nothing...or > connect at 3 in the morning and call CQ CQ. For 5 > minutes.....I am so tired of that shit I could delete it > tonight. > > > On Nov 11, 2014 2:00 > PM, "kk6ecm" <kk6ecm(a)gmail.com> > wrote: > Can anyone shed light > on this Echolink requirement and Allstar? I'm not sure > what makes us compliant. We have Echolink enabled on our > repeater... I know of no way a non-ham could link in during > an Echolink connection. Is there a way of setting app_rpt so > an Echolink connection precludes all others? Also, Echolink > has Apps for the PC, Android, and the iPhone/iPad... Their > PC app (phones are RF, but not ham) seems to invalidate > their rf only policy, although they do verify a license > before granting a node number. What am I missing? > > Thanks,Bobkk6ecm > Sent from iPad > > ---------- Forwarded > message ---------- > From: EchoLink Support > <support(a)echolink.org> > Date: Wed, Sep 3, 2014 at 9:14 AM > Subject: EchoLink Policy Reminder > To: > > > We wanted to remind you of an important item in > EchoLink's access policies (which can be found online at > http://www.echolink.org/access_policies.htm) > > > > In general, EchoLink does not permit cross-linking. > > > > More specifically, EchoLink does not permit cross-linking > with other VoIP systems that can be accessed off-the-air > (for example, directly from a PC or Web browser).? This is > because other systems may have a validation procedure that > is far less comprehensive than EchoLink's, and we want > to continue to ensure that EchoLink is solely for use by > licensed Amateur Radio operators around the world. > > > > Therefore, while excellent systems such as Zello, AllStar, > eQSO, WIRES-II, etc. all serve an important purpose within > the Amateur Radio community, our policy is that they cannot > be directly connected to a registered EchoLink node. > > > > In other words, your node must function only as a direct RF > gateway, and not as a cross-link to another system. If your > node is reachable through another path, that path must be > disabled when an EchoLink connection is in progress. For > example, an EchoIRLP node is permitted, since it functions > only as an RF gateway when an EchoLink connection is > made. > > > > If you are running Asterisk with app_rpt and an EchoLink > channel, be sure it is configured not to allow other VoIP > connections when an EchoLink station is connected. If this > isn't practical, please disable the EchoLink channel. > > > > Thanks for ensuring that your node adheres to this policy. > In some cases we do restrict logins to be sure the policy is > being followed. > > > > 73 > > EchoLink Support > > > > (Note: This mailbox is not able to handle replies. For help > and information, please see www.echolink.org/support.htm) > > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users(a)ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > and scroll down to the bottom of the page. Enter your email > address and press the "Unsubscribe or edit options > button" > > You do not need a password to unsubscribe, you can do it via > email confirmation. If you have trouble unsubscribing, > please send a message to the list detailing the problem. > > -----Inline Attachment Follows----- > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list > please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > and scroll down to the bottom of the page. Enter your > email address and press the "Unsubscribe or edit > options button" > You do not need a > password to unsubscribe, you can do it via email > confirmation. If you have trouble unsubscribing, please send > a message to the list detailing the problem. > > > > ------------------------------ > > Message: 2 > Date: Fri, 14 Nov 2014 23:10:57 -0700 > From: Corey <kc7mrq(a)bresnan.net> > To: app_rpt-users(a)ohnosec.org > Subject: [App_rpt-users] Voter board > Message-ID: <5466EE71.1090107(a)bresnan.net> > Content-Type: text/plain; charset=utf-8; format=flowed > > > I built a through hole voter board and interfaced it to a GPS 18 LVC and > my server. I set the board up as a master, transmit. The LED shows the > GPS locked and 98 command shows the GPS, > but I am getting the following error when telnetting into the board: > > Warning: GPS Data time period elapsed. > > The error is timestamped and occurs every second. I made sure the data > format was NMEA per archived messages on here by connecting the GPS to > SNSRCFG. The config appears to be set up correctly. > What other areas do I need to look at to fix this warning? > > I did notice you can choose quite a few NMEA messages in the SNSRCFG > profile. Does it matter if all are checked? > > I have a second issue with updating the firmware. The board is at Rev > 1.41. I tried updating it, but haven't had any luck so far. Nothing > happens when I click on the "capture target" button after resetting the > voter board. The target ip is the voter board and the bootloader ip in > the voter is my laptop with ENC_Loader. > > The IC(s) were originally programmed by a friend in another state so I > never experienced what it take to do the initial programming. > > > Thanks for your help, > Corey > > > ------------------------------ > > Message: 3 > Date: Sat, 15 Nov 2014 00:27:46 -0600 > From: Chuck Henderson <rpt2(a)chuck.midlandsnetworking.com> > To: Corey <kc7mrq(a)bresnan.net> > Cc: app_rpt mailing list <app_rpt-users(a)ohnosec.org> > Subject: Re: [App_rpt-users] Voter board > Message-ID: > <CADEYVwj=UeTqkKzfERG8Oz+Rj+XZKYH649TCjaYYqtoUFoQ7og(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > set the bootloader IP to be the same as the voter board IP, or make it > different than anything else on the network. It is the IP that the voter > board uses when it is running the bootloader code. It can not have the > same IP as your laptop. That will not work. > > On Sat, Nov 15, 2014 at 12:10 AM, Corey <kc7mrq(a)bresnan.net> wrote: > >> I built a through hole voter board and interfaced it to a GPS 18 LVC and >> my server. I set the board up as a master, transmit. The LED shows the GPS >> locked and 98 command shows the GPS, >> but I am getting the following error when telnetting into the board: >> >> Warning: GPS Data time period elapsed. >> >> The error is timestamped and occurs every second. I made sure the data >> format was NMEA per archived messages on here by connecting the GPS to >> SNSRCFG. The config appears to be set up correctly. >> What other areas do I need to look at to fix this warning? >> >> I did notice you can choose quite a few NMEA messages in the SNSRCFG >> profile. Does it matter if all are checked? >> >> I have a second issue with updating the firmware. The board is at Rev >> 1.41. I tried updating it, but haven't had any luck so far. Nothing happens >> when I click on the "capture target" button after resetting the voter >> board. The target ip is the voter board and the bootloader ip in the voter >> is my laptop with ENC_Loader. >> >> The IC(s) were originally programmed by a friend in another state so I >> never experienced what it take to do the initial programming. >> >> >> Thanks for your help, >> Corey >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/ >> mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. >> Enter your email address and press the "Unsubscribe or edit options button" >> You do not need a password to unsubscribe, you can do it via email >> confirmation. If you have trouble unsubscribing, please send a message to >> the list detailing the problem. >

1 0

non SSL access to allstarlink.org
by Bryan Fields 16 Nov '14

16 Nov '14

Is there a url I can use to access this that does not redirect to the SSL server? Thank you, -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

2 1

Show link topology from cli?
by Bryan Fields 16 Nov '14

16 Nov '14

Is there an easy to see interconnected link topology database via the CLI? 73's -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

2 1

Re: [App_rpt-users] App_rpt-users Digest, Vol 69, Issue 28
by Mark Tinney 15 Nov '14

15 Nov '14

I have purchased a new URI from DMK and have the same problem, I plan to move it to channel B and see if it fails. I know enough about Linux to move around and execute files but wasn't sure if Asterisk was killing the channel and don't really know how to check. Sent from my Verizon Wireless 4G LTE smartphone -------- Original message -------- From: app_rpt-users-request(a)ohnosec.org Date: 11/15/2014 10:46 (GMT-05:00) To: app_rpt-users(a)ohnosec.org Subject: App_rpt-users Digest, Vol 69, Issue 28 Send App_rpt-users mailing list submissions to app_rpt-users(a)ohnosec.org To subscribe or unsubscribe via the World Wide Web, visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users or, via email, send a message with subject or body 'help' to app_rpt-users-request(a)ohnosec.org You can reach the person managing the list at app_rpt-users-owner(a)ohnosec.org When replying, please edit your Subject line so it is more specific than "Re: Contents of App_rpt-users digest..." Today's Topics: 1. Re: App_rpt-users Channel A audio lost (mark(a)tinney.us) 2. Re: App_rpt-users Channel A audio lost (Doug Crompton) ---------------------------------------------------------------------- Message: 1 Date: Sat, 15 Nov 2014 09:30:12 -0500 From: <mark(a)tinney.us> To: <app_rpt-users(a)ohnosec.org> Subject: Re: [App_rpt-users] App_rpt-users Channel A audio lost Message-ID: <A158DC121ED446D0BF82334CCD795451@MkTinneyPC> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original I am not sure if this is how I get help but here is my question: I have a BBB running and everything works fine until I eventually start getting a carrier only on channel A audio output, I have audio on channel B when A is not working as I have channel B setup as a monitor in the repeater building. Do you have any suggestions for me to try to figure out this problem? Thanks, Mark W4GVX -----Original Message----- From: app_rpt-users-request(a)ohnosec.org Sent: Friday, November 14, 2014 12:00 PM To: app_rpt-users(a)ohnosec.org Subject: App_rpt-users Digest, Vol 69, Issue 26 Send App_rpt-users mailing list submissions to app_rpt-users(a)ohnosec.org To subscribe or unsubscribe via the World Wide Web, visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users or, via email, send a message with subject or body 'help' to app_rpt-users-request(a)ohnosec.org You can reach the person managing the list at app_rpt-users-owner(a)ohnosec.org When replying, please edit your Subject line so it is more specific than "Re: Contents of App_rpt-users digest..." Today's Topics: 1. Re: Echolink_and_app_rpt:_Looking_for_m ore_information_on_permit=*-* (ea8ee) 2. Re: Echolink_and_app_rpt:_Looking_for_m ore_information_on_permit=*-* (Stephen Curtis) ---------------------------------------------------------------------- Message: 1 Date: Fri, 14 Nov 2014 09:41:18 +0000 From: ea8ee <ea8ee1(a)gmail.com> To: Robert Newberry <N1XBM(a)amsat.org> Cc: app_rpt mailing list <app_rpt-users(a)ohnosec.org> Subject: Re: [App_rpt-users] Echolink_and_app_rpt:_Looking_for_m ore_information_on_permit=*-* Message-ID: <CADJ3RdTVXYNbJpZi3SzJe6s3PkQ3oVct=j9uUu3Ba+Si9cOHww(a)mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" how active the vox mode in zoiper? maybe with a dmtf numbers? 2014-11-12 19:14 GMT+00:00 Robert Newberry <N1XBM(a)amsat.org>: > I think this has come up before, but if you have a spare PC you can > create a account on your box for zoiper set it for vox. Then get zello for > PC and create a account for you node. Then create a channel for your node. > Place the account into the repeater channel. Use virtual audio cables and > point zello to zoiper and cross the cables. Works slicker than sh*t! > Obviously your zoiper connection is left up full time. Also I password > protect my channel. > > Feel free to connect to my node and I'll give you a demo. > > We have a regular user who is over the road trucker and zello plays nice > with his blue parrot headset also much more "PTT radio like" friendly. > Also I can record repeater activity too! > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down > to the bottom of the page. Enter your email address and press the > "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email > confirmation. If you have trouble unsubscribing, please send a message to > the list detailing the problem. >

2 1

Voter board
by Corey 15 Nov '14

15 Nov '14

I built a through hole voter board and interfaced it to a GPS 18 LVC and my server. I set the board up as a master, transmit. The LED shows the GPS locked and 98 command shows the GPS, but I am getting the following error when telnetting into the board: Warning: GPS Data time period elapsed. The error is timestamped and occurs every second. I made sure the data format was NMEA per archived messages on here by connecting the GPS to SNSRCFG. The config appears to be set up correctly. What other areas do I need to look at to fix this warning? I did notice you can choose quite a few NMEA messages in the SNSRCFG profile. Does it matter if all are checked? I have a second issue with updating the firmware. The board is at Rev 1.41. I tried updating it, but haven't had any luck so far. Nothing happens when I click on the "capture target" button after resetting the voter board. The target ip is the voter board and the bootloader ip in the voter is my laptop with ENC_Loader. The IC(s) were originally programmed by a friend in another state so I never experienced what it take to do the initial programming. Thanks for your help, Corey

2 5

Re: [App_rpt-users] App_rpt-users Channel A audio lost
by mark＠tinney.us 15 Nov '14

15 Nov '14

I am not sure if this is how I get help but here is my question: I have a BBB running and everything works fine until I eventually start getting a carrier only on channel A audio output, I have audio on channel B when A is not working as I have channel B setup as a monitor in the repeater building. Do you have any suggestions for me to try to figure out this problem? Thanks, Mark W4GVX -----Original Message----- From: app_rpt-users-request(a)ohnosec.org Sent: Friday, November 14, 2014 12:00 PM To: app_rpt-users(a)ohnosec.org Subject: App_rpt-users Digest, Vol 69, Issue 26 Send App_rpt-users mailing list submissions to app_rpt-users(a)ohnosec.org To subscribe or unsubscribe via the World Wide Web, visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users or, via email, send a message with subject or body 'help' to app_rpt-users-request(a)ohnosec.org You can reach the person managing the list at app_rpt-users-owner(a)ohnosec.org When replying, please edit your Subject line so it is more specific than "Re: Contents of App_rpt-users digest..." Today's Topics: 1. Re: Echolink_and_app_rpt:_Looking_for_m ore_information_on_permit=*-* (ea8ee) 2. Re: Echolink_and_app_rpt:_Looking_for_m ore_information_on_permit=*-* (Stephen Curtis) ---------------------------------------------------------------------- Message: 1 Date: Fri, 14 Nov 2014 09:41:18 +0000 From: ea8ee <ea8ee1(a)gmail.com> To: Robert Newberry <N1XBM(a)amsat.org> Cc: app_rpt mailing list <app_rpt-users(a)ohnosec.org> Subject: Re: [App_rpt-users] Echolink_and_app_rpt:_Looking_for_m ore_information_on_permit=*-* Message-ID: <CADJ3RdTVXYNbJpZi3SzJe6s3PkQ3oVct=j9uUu3Ba+Si9cOHww(a)mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" how active the vox mode in zoiper? maybe with a dmtf numbers? 2014-11-12 19:14 GMT+00:00 Robert Newberry <N1XBM(a)amsat.org>: > I think this has come up before, but if you have a spare PC you can > create a account on your box for zoiper set it for vox. Then get zello for > PC and create a account for you node. Then create a channel for your node. > Place the account into the repeater channel. Use virtual audio cables and > point zello to zoiper and cross the cables. Works slicker than sh*t! > Obviously your zoiper connection is left up full time. Also I password > protect my channel. > > Feel free to connect to my node and I'll give you a demo. > > We have a regular user who is over the road trucker and zello plays nice > with his blue parrot headset also much more "PTT radio like" friendly. > Also I can record repeater activity too! > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > To unsubscribe from this list please visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down > to the bottom of the page. Enter your email address and press the > "Unsubscribe or edit options button" > You do not need a password to unsubscribe, you can do it via email > confirmation. If you have trouble unsubscribing, please send a message to > the list detailing the problem. >

2 1

EchoLink Policy Reminder
by kk6ecm 14 Nov '14

14 Nov '14

Can anyone shed light on this Echolink requirement and Allstar? I'm not sure what makes us compliant. We have Echolink enabled on our repeater... I know of no way a non-ham could link in during an Echolink connection. Is there a way of setting app_rpt so an Echolink connection precludes all others? Also, Echolink has Apps for the PC, Android, and the iPhone/iPad... Their PC app (phones are RF, but not ham) seems to invalidate their rf only policy, although they do verify a license before granting a node number. What am I missing? Thanks, Bob kk6ecm Sent from iPad > > ---------- Forwarded message ---------- > From: EchoLink Support <support(a)echolink.org> > Date: Wed, Sep 3, 2014 at 9:14 AM > Subject: EchoLink Policy Reminder > To: > > > We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm) > > In general, EchoLink does not permit cross-linking. > > More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world. > > Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node. > > In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made. > > If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel. > > Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed. > > 73 > EchoLink Support > > (Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm) >

4 3

Re: [App_rpt-users] Echolink_and_app_rpt:_Looking_for_m ore_information_on_permit=*-*
by Tim Sawyer 14 Nov '14

14 Nov '14

Another app_rpt poster just suggested the same thing. I’m trying that out now and it seems to work well. Just have to remember to hit the mute button right away after connecting if you don’t want to transmit immediately. -- Tim :wq > On Nov 12, 2014, at 8:04 AM, Stephen Curtis <steve(a)m0hoy.com> wrote: > > Hi Tim, > > I too am using Zoiper, I found it easier and more stable to change it to Vox and essentially use the mute button in Zoiper as a PTT. > > Steve M0HOY > > Sent from my iPhone > > On 12 Nov 2014, at 14:51, Tim Sawyer <tim.sawyer(a)mac.com <mailto:tim.sawyer@mac.com>> wrote: > >> I removed EchoLink. In it’s place we need some smart mobile developer to write a iPhone/Android IAX client with PTT. Anyone???? >> >> For now we’re using Zoiper. It’s a bit clunky as you have to do *99 to make PTT and # to unkey. The lack of PTT indication is disconcerting and problematic but it works. The audio is 3,000 times better than EchoLink. And you have control of who connects. Here’s how you set up the node. >> >> In iax.conf add this stanza. Change UserID and UserPassword. >> >> [UserID] >> username=UserID >> type=friend >> context=hams >> host=dynamic >> auth=md5 >> secret=UserPassword >> disallow=all >> allow=ulaw >> allow=g726aal2 >> allow=gsm >> codecpriority=host >> transfer=no >> >> In extensions.conf add this stanza. This requires a caller ID or it will not connect. I have my users put their call sign in the caller ID. That way the status pages (including Allmon) shows who is connected with a -P appended. >> >> [hams] >> exten => _X!,1,Ringing >> exten => _X!,n,NoOp(${CALLERID(name)}) >> exten => _X!,n,NoOp(${CALLERID(number)}) >> exten => _X!,n,Set(CALLSIGN=${CALLERID(name)}) >> exten => _X!,n,GotoIf($[${LEN(${CALLSIGN})} = 0]?hangit) >> exten => _X!,n,Wait(3) >> exten => _X!,n,Answer >> exten => _X!,n,Playback(connecting) >> exten => _X!,n,rpt(${EXTEN}|P|${CALLSIGN}-P) >> exten => _X!,n(hangit),Answer >> exten => _X!,n(hangit),Playback(connection-failed) >> exten => _X!,n(hangit),Wait(1) >> exten => _X!,n(hangit),Hangup >> >> -- >> Tim WD6AWP >> >>> On Nov 12, 2014, at 5:46 AM, Bryan D. Boyle <bdboyle(a)bdboyle.com <mailto:bdboyle@bdboyle.com>> wrote: >>> >>> simple solution, considering the clueless majority of users in the Echolink world, the lousy audio codecs, and the ancient technology that has not kept pace with either praxis or software advances: turn the damn thing off. >>> >>> You won't miss the drive-bys, distorted computer audio, fumble-fingered operators, and bandwidth usage. >>> >>> It's just so not worth the effort to maintain, worry about the software and technology use conditions, or anything else surrounding it. It's just amateur radio, not the launch codes. >>> >>> </grump> >>> >>> -- >>> Bryan >>> Sent from my iPhone 5...No electrons were harmed in the sending of this message. >>> >>> >>> >>> On Nov 12, 2014, at 06:36, <mike(a)midnighteng.com <mailto:mike@midnighteng.com>> <mike(a)midnighteng.com <mailto:mike@midnighteng.com>> wrote: >>> >>>> >>>> Additional info (as if the first was not enough)... >>>> >>>> I went to their (echolink) website looking for a rule... >>>> >>>> Here it is... >>>> >>>> Item #4 >>>> Stations operating in Sysop mode may interconnect EchoLink only with equipment operating on Amateur frequencies. EchoLink does not permit use of the system with other services such as GMRS, FRS, or MARS. For security reasons, it is also not permitted to interconnect EchoLink with other VoIP systems that support direct access from a computer. >>>> >>>> >>>> found on their access policy page at... >>>> >>>> echolink.org/access_policies.htm <http://echolink.org/access_policies.htm> >>>> >>>> There is no mention of other systems interconnect, just the VoIP via computer direct. >>>> I take the meaning of direct to mean "unverified" or unrestricted. >>>> This is consistent with the way I have been reading the poorly written emails some of you get from echolink. >>>> >>>> >>>> ...mike/kb8jnm >>>> >>>> >>>> >>>> >>>> -------- Original Message -------- >>>> Subject: Re: [App_rpt-users] Echolink_and_app_rpt:_Looking_for_m >>>> ore_information_on_permit=*-* >>>> From: <mike(a)midnighteng.com <mailto:mike@midnighteng.com>> >>>> Date: Wed, November 12, 2014 5:28 am >>>> To: app_rpt-users(a)ohnosec.org <mailto:app_rpt-users@ohnosec.org>, "Bob" <kk6ecm(a)gmail.com <mailto:kk6ecm@gmail.com>> >>>> >>>> >>>> Bob, Doug and all, >>>> >>>> I fully understand why you would think that. It is so poorly written. >>>> And as I have watched this conversation get out of hand at least 2 times as you have Doug. >>>> >>>> This is the first time I thought I would clarify how I was reading their email statement before anyone gets elevated on it again. >>>> >>>> other VoIP connections not Radio Sourced RoIP connections and only if you can't verify the VoIP. >>>> >>>> They are saying VOIP connections from non-radio sources...ie phone and web portal without a security check. I have many non-experimental phone and web ports but nobody knows what it is so it is not a open port. I don't provide links to it from a web page or post a phone number and it "does" have multilevel security checks. Even if folks stumbled on it by accident or not, they would not have open access. >>>> >>>> There are a lot of folks experimenting with asterisk side of the set-up. Many of us that have been using asterisk for many years know that we can port just about any kind of streaming audio or other services to asterisk and thereby app_rpt. Hard to tell what interfaces/ports are open on them and to where they go. >>>> Because some folks don't think about the implications of their actions, things happen. We all know that even from the radio side of the equation. >>>> >>>> Problems can also occur if a unauthorized station/system is connected to others who are connected to you and there is no way to track that on the echolink side. >>>> >>>> They are asking that when "you" have a open port like that (unverified VoIP), to disable the echolink port while it is active so a unverified user does not get access to echolink through VoIP, not RoIP or Radio. And I'm sure we feel the same way about that through allstar. >>>> >>>> By the way some of you guys are interpreting this, the iPhone and Android apps and/or repeater to repeater echolink connects and PC to PC echolink connects would not be legal to them. >>>> >>>> Has anyone ever asked them to clarify the statement? Please tell us/me "exactly" what they said ! >>>> >>>> If nobody answers that, perhaps one of us needs to ask them so we can set the record straight as most of us use it on our systems and left unanswered definitively, this will come up many more times. >>>> >>>> And perhaps a text of a definitive rule could be included as a default comment in the echolink.conf so there is no ignorance of what they expect if you use it. >>>> >>>> Bob (kk6ecm), you win the prize since you asked the question from the email you received. >>>> >>>> Would you Send them a message/reply to clarify the type of connections "by example" they do not want and ask they not use the text from the email that you do not understand ? or what type of VoIP connections they are speaking of exactly. >>>> >>>> Sure would put a end to the silliness of it time and time again. >>>> >>>> I think what leads folks to get one of those emails is basically a list report of connected systems when a breach has been noticed. Problem is, they have a security problem with some of the proxies on their system. I have seen many a connect through a echo-proxy without an ID (callsign) and more. I don't think anyone could ever know it's true source. Hence the poorly worded generic email notice to all connected systems and obviously, they are not familiar with the other systems to word it correctly. >>>> >>>> Sorry to be long winded, but I don't want to this get elevated again without good reason. >>>> >>>> ...mike/kb8jnm >>>> >>>> -------- Original Message -------- >>>> Subject: Re: [App_rpt-users] Echolink and app_rpt: Looking for more >>>> information on permit=*-* >>>> From: Doug Crompton <doug(a)crompton.com <mailto:doug@crompton.com>> >>>> Date: Wed, November 12, 2014 1:13 am >>>> To: "app_rpt-users(a)ohnosec.org <mailto:app_rpt-users@ohnosec.org>" <app_rpt-users(a)ohnosec.org <mailto:app_rpt-users@ohnosec.org>> >>>> >>>> Mike, >>>> >>>> I am going to break my own rule and respond here! I don't think you are interpreting there statement correctly... >>>> >>>> They say.... >>>> >>>> "If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected." >>>> >>>> They go on to specifically prohibit connections to Allstar, Wires, and many others is not to be connected to Echolink. Bottom line is they think their validation process is better than ours or others. I say we police it just fine. A non ham popping up would stick out like a sore thumb. >>>> >>>> Bottom line they don't want us connected. In other words they want it like IRLP with echolink. You can either connect to a echolink station or an IRLP node, NOT both at the same time. >>>> >>>> My assertion still stands, ignore it but on the other hand like any good ham make sure you police the activity on your nodes. There is no way to practically isolate echolink from Allstar unless you somehow disconnect all allstar nodes when an echolink call comes in and this would be crazy to do. >>>> >>>> 73 Doug >>>> WA3DSP >>>> http://www.crompton.com/hamradio <http://www.crompton.com/hamradio> >>>> >>>> >>>> From: mike(a)midnighteng.com <mailto:mike@midnighteng.com> >>>> To: App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> >>>> Date: Tue, 11 Nov 2014 21:15:26 -0700 >>>> Subject: Re: [App_rpt-users] Echolink and app_rpt: Looking for more information on permit=*-* >>>> >>>> >>>> Like many times before you, you don't seem to understand their statement. >>>> So nobody needs to go off on a tangent again. >>>> >>>> You only need to be concerned if you do something like >>>> "have a web portal to your system that has no limitation to who uses it" (as in non-hams). >>>> >>>> If you do then they have the possibility to use the echolink system through your system and that is what they do not want. >>>> >>>> Neither do we with allstar or via radio. >>>> I'm sure there are a few bad actors out there somewhere allowing access. >>>> just make sure it is not you. >>>> >>>> They could use better wording to keep the confusion/fuss down. >>>> >>>> As far as permit or deny... >>>> permit= a list that only allows calls you place in the list to connect. >>>> deny= a list of calls that can not connect. >>>> See the drupal site for info. >>>> >>>> ...mike/kb8jnm >>>> -------- Original Message -------- >>>> Subject: [App_rpt-users] Echolink and app_rpt: Looking for more >>>> information on permit=*-* >>>> From: "Bob" <kk6ecm(a)gmail.com <mailto:kk6ecm@gmail.com>> >>>> Date: Tue, November 11, 2014 10:13 pm >>>> To: <App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org>> >>>> >>>> OK... Echolink quality aside, I’m looking for some clarification how app_rpt works with Echolink. >>>> >>>> Attempting to understand the statement from Echolink, “If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel.” It seems that “other VoIP” means non-Echolink nodes; not sure how Allstar can do this. >>>> >>>> How does permit=*-* (“prohibit computer-based connections”) work with an incoming Echolink computer based node, or with an app_rpt hosted Echolink node in an Echolink to Echolink configuration. When the user enters *33 to connect, is it actually Echolink nodes connecting, or is there a difference? >>>> >>>> I think I get their point they don’t want an Allstar node with Echolink node, to simultaneously connect to another Allstar node that does not support Echolink, but not sure why... still licensed amateurs involved. >>>> >>>> I am dismayed with Echolink’s assertion that the use of a copy of a paper license is more official than the FCC recognized ULS site, which it appears Allstarlink.org <http://allstarlink.org/> uses to validate the users license. >>>> >>>> Thanks, >>>> Bob >>>> kk6ecm >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> >>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> >>>> >>>> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" >>>> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. >>>> >>>> _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> >>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> >>>> >>>> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" >>>> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> >>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> >>>> >>>> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" >>>> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. >>>> _______________________________________________ >>>> App_rpt-users mailing list >>>> App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> >>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> >>>> >>>> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" >>>> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> >>> >>> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" >>> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org <mailto:App_rpt-users@ohnosec.org> >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> >> >> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" >> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

5 4

Re: [App_rpt-users] Echolink_and_app_rpt:_Looking_for_m ore_information_on_permit=*-*
by mike＠midnighteng.com 14 Nov '14

14 Nov '14

6 6

Re: [App_rpt-users] How to setup Allstar Monitor
by Tim Sawyer 12 Nov '14

12 Nov '14

Allmon 2 is hosted here https://github.com/tsawyer/allmon/tree/allmon2 -- Tim :wq > On Nov 12, 2014, at 11:58 AM, Scott Weis <kb2ear(a)kb2ear.net> wrote: > > So where is allmon v2 being hosted? > > Thanks & 73, > Scott KB2EAR > > On 2014-11-12 09:25, Tim Sawyer wrote:

1 0