<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19328">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>Before this goes too far astray, I wrote that
posting, and I'll go over the sequence as briefly as possible.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>For about three years I had a TBD node running at
home, very low traffic, mainly as a convenience to me (the reason is
unimportant). It was W2DB-L</FONT></DIV>
<DIV><FONT size=2 face=Arial>Last October 1 I asked them to allow me an official
"Concerence" using this box and the reply I got was that TBD is not permitted on
Echolink, and therefore my continued use that was was a violation
of...something... I asked that is it were not permitted why is the software
available? Their response was really nil. I was tending to my gravely ill mom at
the time and never checked again until this past week. I might add that within
ten minutes of their October 2nd email saying I was a bad guy I killed TBD and
never started it again. </FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Since I started playing allstar with node 2360 I
have had W2DB-R on that same box, something like three years. Suddenly IT didn't
work.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>So last week I needed to place W2DB-L on one of my
"private" asterisk/acid nodes(ok...really Limey) and found it didn't work.
</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>So I sent an email when their web site shoewd
W2DB-L as unauthorized, and authorization failed. They replied with a curt note
saying that had I read their prior email (never got it) I'd know that I was
blocked. I explained that W2DB-L has been off, and W2DB-R gets regular use on
the echolink side. They then accused me of still running a TBD box on W2DB-R
(node allstar 2360... ACID...etc) which isn't and was never the case. And I told
them so. They said then why is it they could not connect to it. Well, after too
many drive by echolink connects from some pile of dirt calling itself a
sovereign nation on the other side of teh planet at 3AM I established an
acceptable connect list. SO...</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Echolink informed me that there are three callsigns
with all three flavors of suffix that MUST be allowed:</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>permit=k1rfd, k1rfd-l, k1rdf-r, vk2jtp, vk2jtp-l,
vk2jtp-r, w1cdm, w1cdm-l, w1cdm-r</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>And that's where it ended.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Sorry it took so many words, this didn't need to
turn into a we hate echolink discussion.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>But yeah, they really should be happy we are there
to at least let them know what good audio sounds like, since they get to remind
us of what BAD audio is.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>W2DB out</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>GeorgeC</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir=ltr>
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=wb6egr@gmail.com href="mailto:wb6egr@gmail.com">Kirk Just Kirk</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=telesistant@hotmail.com
href="mailto:telesistant@hotmail.com">Jim Duuuude</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=app_rpt-users@ohnosec.org
href="mailto:app_rpt-users@ohnosec.org">app_rpt mailing list</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, March 21, 2013 3:23
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [App_rpt-users] Echolink
Connectivity Issue</DIV>
<DIV><BR></DIV>Wait a minute......
<DIV>I do fully understand WHY Dave Cameron wanted us to all yank IRLP out of
our systems, it interfered with his SELLING you a piece of shit PCB for IRLP
to the tune of $170/with a FREE node number thrown in for a bonus. (thats my
opinion).Thats OK by me....about 85% of the IRLP installations sound like shit
anyways.</DIV>
<DIV>But Echolink should be HAPPY (YAYYYY) that the Allstar crowd is having
access to BOTH modes......</DIV>
<DIV>Smells like a rumor to me.Everyone else (other than IRLP) has YOU the
owner install/set up/operateYOUR hardware.</DIV>
<DIV>It's only IRLP that makes you wait till THEIR "Install team" can install
your software for you.</DIV>
<DIV>Echolink probably wouldnt care if you ran it on a Proctor-Silex toaster
if you can do it....(Jim can do it)</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>Kirk<BR><BR>
<DIV class=gmail_quote>On Thu, Mar 21, 2013 at 10:14 AM, Jim Duuuude <SPAN
dir=ltr><<A href="mailto:telesistant@hotmail.com"
target=_blank>telesistant@hotmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV>
<DIV dir=ltr>Hmmm..<BR><BR>I have never actually seen this policy before...
somewhat disturbing...<BR><BR>However, practical experience shows that
Echolink seems to be perfectly aware of our interconnections<BR>and seems to
be perfectly content with what we are doing. So, I guess its okay....
???<BR><BR>Jim WB6NIL<BR><BR>
<DIV>
<DIV></DIV>> From: <A href="mailto:petem001@hotmail.com"
target=_blank>petem001@hotmail.com</A><BR>> To: <A
href="mailto:app_rpt-users@ohnosec.org"
target=_blank>app_rpt-users@ohnosec.org</A><BR>> Date: Thu, 21 Mar 2013
15:59:34 -0400<BR>> Subject: Re: [App_rpt-users] Echolink Connectivity
Issue<BR>> <BR>> Well, thats bad.<BR>> <BR>> But if echolink
remove my node from there system It's their Loss,not mine.<BR>> <BR>>
Some would day that I am arrogant. nope, I just dont care for poeple that
<BR>> wont think more then that..<BR>> <BR>> the more system on
their or other networks that can interact together, the <BR>> best for
every one.<BR>> <BR>> <BR>> -----Message d'origine----- <BR>>
From: Pawlowski, Adam<BR>> Sent: Thursday, March 21, 2013 3:48 PM<BR>>
To: <A href="mailto:app_rpt-users@ohnosec.org"
target=_blank>app_rpt-users@ohnosec.org</A><BR>> Subject: Re:
[App_rpt-users] Echolink Connectivity Issue<BR>> <BR>> I sent this a
while back but it was bounced for the wrong mail address. I <BR>> don't
see it ever made it to the list.<BR>> <BR>> This was re: someone being
advised that their app_rpt node is not permitted <BR>> on the Echolink
network.<BR>> <BR>> > Echolink is a nice service<BR>> > that
allows hams around the world to keep up pc to pc. And nobody asks<BR>>
> for any money, nice. But this is very, very out of the norm for
them.<BR>> ><BR>> <BR>> I looked this up recently when I started
to talk about IRLP and how they <BR>> don't want other traffic on their
network. Then I looked at their Access <BR>> Policy:<BR>> <BR>> 4.
Stations operating in Sysop mode may interconnect EchoLink only with
<BR>> equipment operating on Amateur frequencies. EchoLink does not
permit use of <BR>> the system with other services such as GMRS, FRS, or
MARS. For security <BR>> reasons, it is also not permitted to
interconnect EchoLink with other VoIP <BR>> systems that support direct
access from a computer.<BR>> <BR>> 10. The "addressing servers" are
designed to be accessed by EchoLink <BR>> software only. For the sake of
system security and stability, any other <BR>> access requires the
permission of the server administrator. As a matter of <BR>> security, in
no event should the IP addresses (or Internet hostnames) of <BR>>
logged-in stations be displayed to anyone who is not a validated, logged-in
<BR>> user.<BR>> <BR>> 11. Although every effort will be made to
apply these policies universally <BR>> and fairly, the EchoLink Support
staff reserves the right to withdraw a <BR>> station's access privileges
at any time, without notice. EchoLink is a <BR>> privately owned and
operated system that has no connection with, and is not <BR>> governed
by, any radio licensing authority.<BR>> <BR>> So, I interpret that as
that you are not supposed to connect to with <BR>> asterisk at all
anyways, if you read that verbosely, via app_rpt or <BR>> otherwise. I
don't have the history to know if they've made any statement <BR>> about
what app_rpt is doing, but it seems like it's not permitted via their
<BR>> policy only they are less vocal about it than the IRLP
folks.<BR>> <BR>> <BR>> <BR>>
_______________________________________________<BR>> App_rpt-users
mailing list<BR>> <A href="mailto:App_rpt-users@ohnosec.org"
target=_blank>App_rpt-users@ohnosec.org</A><BR>> <A
href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users"
target=_blank>http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</A>
<BR>> <BR>> _______________________________________________<BR>>
App_rpt-users mailing list<BR>> <A
href="mailto:App_rpt-users@ohnosec.org"
target=_blank>App_rpt-users@ohnosec.org</A><BR>> <A
href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users"
target=_blank>http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</A><BR></DIV></DIV></DIV><BR>_______________________________________________<BR>App_rpt-users
mailing list<BR><A
href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</A><BR><A
href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users"
target=_blank>http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</A><BR><BR></BLOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE></BODY></HTML>