<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">OK, a clarification I received from
Echolink is this:<br>
<br>
There are three callsigns that must not be blocked in the asterisk
config:<br>
<br>
permit=k1rfd, k1rfd-l, k1rdf-r, vk2jtp, vk2jtp-l, vk2jtp-r, w1cdm,
w1cdm-l, w1cdm-r<br>
<br>
<br>
If you're restricting access, as I am as well, the above needs to
be there, according to the echolink folks as of this AM. I guess
my permitting only a few thru made them think I was still running
TBD..??<br>
<br>
All's resolved now<br>
<br>
But this set of callsigns may be something the gang needs to keep
in mind. And everybody gets to live happily ever after.<br>
<br>
GeorgeC<br>
W2DB<br>
<br>
<br>
<br>
On 03/13/2013 11:21 AM, James Smith wrote:<br>
</div>
<blockquote
cite="mid:CAK_+afbkdMbhqV4BDMo1NHxxu-sPsu4TS6ayOHgRb1u9MW9_PQ@mail.gmail.com"
type="cite">man, i have had echolink running on 3 of our nodes for
about 6 months and no problems. they run the -R instance. i also
run a kd5oxm-L instance on the traditional windows box because its
easy to control for public access (i wanted to block foriegners.)
<div>
<br>
</div>
<div>i the asterisk echolink i have to block everything and then
allow a few that i hand type in.</div>
<div>works very very well in asterisk. it sound wonderful since it
runs inside the box.</div>
<div><br>
</div>
<div>but like i said we have had it going for about 6months. maybe
you stired the pot when you asked ofr permission to go TBD
maybe? you should know that. dont ask for permission, ask for
forgiveness when they catch you!</div>
<div><br>
</div>
<div>james</div>
<div>kd5oxm</div>
<div>PS - you figured anything on the ppp16, i read the entire
"using lpt port" page. i would love to figure some that out too.</div>
<div><br>
</div>
<div>thanks </div>
<div><br>
</div>
<div><br>
<br>
<div class="gmail_quote">On Wed, Mar 13, 2013 at 11:00 AM, <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:app_rpt-users-request@ohnosec.org"
target="_blank">app_rpt-users-request@ohnosec.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Send
App_rpt-users mailing list submissions to<br>
<a moz-do-not-send="true"
href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a moz-do-not-send="true"
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>
or, via email, send a message with subject or body 'help' to<br>
<a moz-do-not-send="true"
href="mailto:app_rpt-users-request@ohnosec.org">app_rpt-users-request@ohnosec.org</a><br>
<br>
You can reach the person managing the list at<br>
<a moz-do-not-send="true"
href="mailto:app_rpt-users-owner@ohnosec.org">app_rpt-users-owner@ohnosec.org</a><br>
<br>
When replying, please edit your Subject line so it is more
specific<br>
than "Re: Contents of App_rpt-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. echolink connection issue (George Csahanin)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 12 Mar 2013 23:33:02 -0500<br>
From: "George Csahanin" <<a moz-do-not-send="true"
href="mailto:george@dyb.com">george@dyb.com</a>><br>
To: "app_rpt mailing list" <<a moz-do-not-send="true"
href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a>><br>
Subject: [App_rpt-users] echolink connection issue<br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:0301EEE1A2CD4004BDBB2D60B08CC1A2@lintv.com">0301EEE1A2CD4004BDBB2D60B08CC1A2@lintv.com</a>><br>
Content-Type: text/plain; format=flowed;
charset="iso-8859-1";<br>
reply-type=original<br>
<br>
Something very odd took place. History:I had a TBD node
running with an<br>
echolink id of W2DB-L. On October 2 I actually asked
echolink folks about it<br>
and they said tbd was not permitted. I took it down. Now
that callsign is<br>
blocked, and apparently (to them) an allstar/asterisk node
looks like tbd.<br>
My node 2360 is also echolink W2DB-R and they just sent me
an email of<br>
accusing me of running a tbd box at W2DB-R. It isn't, it's
an ACID install<br>
of asterisk/app_rpt. Now W2DB-R doesn't seem to want to
connect to anything<br>
except the echotest also. So not sure what this is all
about, but if anybody<br>
else has any echolink issue you might want to see if you've
been<br>
blocked/de-authorized because they think it is a tbd box.
Too bad. Echolink<br>
is a nice service that allows hams around the world to keep
up pc to pc. And<br>
nobody asks for any money, nice. But this is very, very out
of the norm for<br>
them.<br>
<br>
(It would also have been nice if somewhere on their web site
they spelled<br>
out that tbd and/or asterisk isn't permitted...)<br>
<br>
George<br>
W2DB<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
App_rpt-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a><br>
<a moz-do-not-send="true"
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>
End of App_rpt-users Digest, Vol 49, Issue 30<br>
*********************************************<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>