weirdness with Allstarlink

[Patrick Perdue]

Hi:

This isn't necessarily an issue with Repeaterphone, at least I don't
think it is... at least not in full.

Earlier today, I noticed a bunch of weird stuff going on with one of the
two servers linked to register.allstarlink.org, which I don't think have
been entirely resolved.

Anyway, I have a node (506317) which is registered and reporting stats.
However, according to RepeaterPhone, the node is offline. Calling it
directly from a saved favorite never manages to contact the Asterisk
server associated with that node.

So, my question is: what, exactly, is RepeaterPhone doing to get the
directory of active nodes? Is it just pulling from the same source as
astdb.php on a local node, or something else?

Also, what makes RepeaterPhone think a node is offline when it is
reporting to stats.allstarlink.org, and is clearly registered?

I'm just trying to figure out where the disconnect is, though I'm at
least reasonably sure it's something upstream that I can't do much
about, since no configuration changes have happened to this node in
probably half a year or so.

73

N2DYI

[Patrick Perdue]

Screwed something up here.

On a normal node, either HamVoIP or ASL, though they handle look-ups
differently, astdb.php gets a list of all nodes on allstarlink.org.
There's another file that only contains online nodes, generally referred
to as rpt_extnodes, which HamVoIP doesn't use unless you explicitly tell
it to, whereas ASL does.

So, does RepeaterPhone just cache both of these when the directory
refreshes, or is it a different mechanism entirely?

[Weston Bustraan]

Unfortunately, the actual implementation is more complicated than I would like. But, in order to get all the information that you see in the directory, I have to do 3 separate requests and then correlate them together because none of them contain all the details:

http://allmondb.allstarlink.org/
- Contains node number, callsign, freq, and location

Does not contain any IP addresses, so I have to call:

https://nodes1.allstarlink.org/cgi-bin/nodes.pl
- Contains node number and ip address/port

But, I also want to display the node on the map, so I need latitude and longitude, so I finally call:

https://stats.allstarlink.org/api/stats/mapData
- Contains node number, callsign, latitude, longitude, and a few extra description fields

It caches this fairly statically. You can force a refresh by using the conventional "pull down to refresh" gesture. There currently isn't any mechanism to know when the allstarlink.org data changes, other than just polling periodically. Because the current web services are agonizingly slow, I've got it set so that it doesn't refresh very often. I imagine you've all experienced the wonderful spinner while it loads the AllStarLink directory.

I now have a better communication channel with the AllStarLink dev team, so potentially we can jointly develop a single service that returns all the necessary data in a single (speedy) request.

Checking on 506317 specifically, I see that it shows in the directory now, so it may have been a timing issue.

- Wes W8WJB

--
You received this message because you are subscribed to the Google Groups "repeaterphone-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repeaterphone-u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repeaterphone-users/c52d91da-d86b-fb1e-c392-ca4a5932a510%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[James Nessen]

Sorry for the delay in responding, I don't monitor this email much.

We had a temporary issue with one of the registration servers back on the 30th of May, any nodes attempting to register were failing which caused a bunch of nodes to fall out of the registry.  

Jim, K6JWN

To view this discussion on the web visit https://groups.google.com/d/msgid/repeaterphone-users/CAEeLBeUsPQQp8CGsE2277N63OZ4677mk0893UDURQv3-sW4%2BVg%40mail.gmail.com.