[App_rpt-users] Allstar connecting to Echolink Problem

Tue Mar 4 18:56:32 UTC 2014

>>Is that your correct public IP? This is the echolink downloaded data so
you should be there. What are you using to confirm that?

Yes.

http://www.echolink.org/links.jsp?lat_deg=41&lat_min=53.75000000000057&lat_NS=North&lon_deg=88&lon_min=7.5&lon_EW=West&sel=gridsq&gs=en51wv&city=&state=&country=US&d=1

I only appear if you open the filter up to see offline nodes.

On Tue, Mar 4, 2014 at 9:56 AM, Doug Crompton <doug at crompton.com> wrote:

> I see you here -
>
> WA3DSP_Allstar*CLI> echolink dbget c N9JPG-L
> 960818|N9JPG-L|71.194.253.53
>
> Is that your correct public IP? This is the echolink downloaded data so
> you should be there. What are you using to confirm that? You are in all the
> lists I have looked at here -
>
>
> http://www.repeaterbook.com/repeaters/echolink/node_status.php?node&type=search
>
> N9JPG-L960818Wheaton, IL USA [0/20]ON
> The 0/20 indicates you have 0 connections active out od a possible 20.
>
> and this is the official echolink site -
>
> http://echolink.org/logins.jsp
> N9JPG-LWheaton, IL USA [0/20]ON09:04960818
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
> Date: Tue, 4 Mar 2014 07:53:17 -0600
> From: n9jpg.ham at gmail.com
> To: kentochs at sbcglobal.net
> CC: app_rpt-users at ohnosec.org
>
> Subject: Re: [App_rpt-users] Allstar connecting to Echolink Problem
>
> I tried rebooting and still no luck. It's weird in that asterisk is able
> to connect and download the node database, but doesn't list me as active on
> the web page.
>
> What tests can be done to diagnose this from within asterisk?
>
>
>
> *N9JPG-L*
> *thanks*
>
>
> On Mon, Mar 3, 2014 at 1:30 PM, Kent Ochs <kentochs at sbcglobal.net> wrote:
>
> I too have been experiencing some inbound connection problems with
> Echolink.  This only effects certain Echolink users but not others user,
> who at the same time are able to connect without problem. After restarting
> our system, the problem does go away
>
> I had a chance the other night to do some troubleshooting with a user who
> was having trouble connecting to our system.
>
> Running the Asterisk remote console, I saw his connection attempt and
> failure.  The attempted Echolink connection lookup was by his IP address.
>
> 1.  I confirmed that his IP address was valid.
> 2.  I confirmed that his Callsign/IP was not in the local Allstar Echolink
> database.
>
> What was interesting was I could not lookup his Callsign on the Echolink
> Database Server either, but he was able to connect directly to my personal
> computer, so he was authenticated somehow to the Echolink system.
>
> 3.  After 5 minutes he did show up in the Echolink database I was looking
> at (Shown at the top of the Echolink database lookup screen as
> nawest.echolink.org)
> 4.  After a server restart he was able to connect my Allstar Node.
>
> What I did notice was that there is a naeast.echolink.org database server
> that is not in my server list.
>
> Here is what I think is happening.
>
> 1.  I'm not sure which database the sync runs against.  (First one in the
> server list?)
> 2.  If a call/ip can not be authenticated local, then a separate lookup
> occurs against each server in the Server List.
> 3.  If the user has authenticated to an Echolink server not in the Server
> List (like naeast.echolink.org), this individual Echolink database lookup
> process will also fail.
>
> It appears the sync process between Echolink database server is a little
> longer than the stated 20 seconds stated by the Echolink folks.
>
> So, if  a user connects to an Echolink server, other than one in your
> server list.  There may be a significant delay from the time the user shows
> up in the Echolink database and is finally downloaded to the local copy on
> the Allstar server.
>
> I have added naeast.echolink.org to the list of recommended database
> servers in the Servers list and I am waiting to see if this solves the
> problem.  (Is Echolink load balancing first to nawest and naeast?  Are they
> having sync delays and/or problems?)
>
> Then again perhaps there is something wrong with the local Echolink
> database sync process that restarting the server fixes.  I sure would like
> to know what Echolink database server the sync process connects to by
> default.
>
> Kent
> W9KAO
>
>
>
>
>
> 1. Re: Allstar connecting to Echolink? (Kevin Oleniczak)
>   2. Re: Re :__Problems_with_Echolink (torben at klimt-online.com)
> Thanks to those that responded... i had waited several hours/days without
> the node appearing active and do not have a second client running
> simultaneously within my network. The later responses indicated the search
> for my node failed to find a match, but that was because the wrong callsign
> was used. See below.
>
> cruiser*CLI> echolink dbget c N9JPG-L
> 960818|N9JPG-L|71.194.253.53
>
> >> Below that is my echolink.conf file for reference. Note the servers
> listed - 1,5,3.
> I used these in my conf file as it noticed that was what my echolink
> client was using.
>
> server1=nawest.echolink.org
> server2=nasouth.echolink.org
> server3=servers.echolink.org
>
> >>Make sure you point the echolink ports in your router to your allstar
> server and as was mentioned you can only run one echolink node per public
> IP address.
>
> As noted earlier, that is all set as suggested on the howto page for
> allstar to do echolink.
>
> Any other ideas?
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at 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.
>
>
>
> _______________________________________________ App_rpt-users mailing list
> App_rpt-users at 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20140304/b9431fa2/attachment.html>