OK, a clarification I received from Echolink is this: There are three callsigns that must not be blocked in the asterisk config: permit=k1rfd, k1rfd-l, k1rdf-r, vk2jtp, vk2jtp-l, vk2jtp-r, w1cdm, w1cdm-l, w1cdm-r 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..?? All's resolved now But this set of callsigns may be something the gang needs to keep in mind. And everybody gets to live happily ever after. GeorgeC W2DB On 03/13/2013 11:21 AM, James Smith wrote:

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.)

i the asterisk echolink i have to block everything and then allow a few that i hand type in. works very very well in asterisk. it sound wonderful since it runs inside the box.

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!

james kd5oxm PS - you figured anything on the ppp16, i read the entire "using lpt port" page. i would love to figure some that out too.

thanks

On Wed, Mar 13, 2013 at 11:00 AM, <app_rpt-users-request@ohnosec.org <mailto:app_rpt-users-request@ohnosec.org>> wrote:

Send App_rpt-users mailing list submissions to app_rpt-users@ohnosec.org <mailto:app_rpt-users@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@ohnosec.org <mailto:app_rpt-users-request@ohnosec.org>

You can reach the person managing the list at app_rpt-users-owner@ohnosec.org <mailto:app_rpt-users-owner@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. echolink connection issue (George Csahanin)

----------------------------------------------------------------------

Message: 1 Date: Tue, 12 Mar 2013 23:33:02 -0500 From: "George Csahanin" <george@dyb.com <mailto:george@dyb.com>> To: "app_rpt mailing list" <app_rpt-users@ohnosec.org <mailto:app_rpt-users@ohnosec.org>> Subject: [App_rpt-users] echolink connection issue Message-ID: <0301EEE1A2CD4004BDBB2D60B08CC1A2@lintv.com <mailto:0301EEE1A2CD4004BDBB2D60B08CC1A2@lintv.com>> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original

Something very odd took place. History:I had a TBD node running with an echolink id of W2DB-L. On October 2 I actually asked echolink folks about it and they said tbd was not permitted. I took it down. Now that callsign is blocked, and apparently (to them) an allstar/asterisk node looks like tbd. My node 2360 is also echolink W2DB-R and they just sent me an email of accusing me of running a tbd box at W2DB-R. It isn't, it's an ACID install of asterisk/app_rpt. Now W2DB-R doesn't seem to want to connect to anything except the echotest also. So not sure what this is all about, but if anybody else has any echolink issue you might want to see if you've been blocked/de-authorized because they think it is a tbd box. Too bad. Echolink is a nice service that allows hams around the world to keep up pc to pc. And nobody asks for any money, nice. But this is very, very out of the norm for them.

(It would also have been nice if somewhere on their web site they spelled out that tbd and/or asterisk isn't permitted...)

George W2DB

------------------------------

_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

End of App_rpt-users Digest, Vol 49, Issue 30 *********************************************