[arm-allstar] HamVoIP registration

[Don Backstrom - AA7AU]

On Thu 22-Nov-18 08:08, "David McGough via ARM-allstar" wrote:
> If you are having connection problems, I'll
> get you a HamVoIP registration (if you'd like) and that should at least
> resolve issues connecting to other HamVoIP systems.

	A few questions on HamVoIP registration:
1 - does the current release of HamVoip use *both* the ASL and the 
HamVoip lookup systems for node address lookup? In what order?
2 - does the HamVoip lookup prefer (and/or override) one over the other?
3 - does HamVoip (in default mode) still download the entire ASL lookup 
list (with resulting bandwidth implications)?
4 - if #3 is yes, will that downloading end soon? if so, when? As you 
have pointed out, this is a big issue for portable/HotSpot users.
5 - Will non-HamVoip AllStar users still be able to lookup HamVoip node 
addresses in the future without changes at their end?
6 - would you be so kind as to extend your answers into a more fulsome 
explanation of how/why the node lookup processes work in broader terms?

- and -

6 - the ability to register private node addresses soon intrigues me. 
Could you explain that a bit more if possible now? We currently have a 
few HamVoip installs on rasPi3 using the Ethernet connection for the 
WAN/public (primary node#) side and an Ethernet-to-USB adapter for our 
Mesh/private (second "private" node#) side. Do you think that this 
approach will be impacted positively? BTW: we turn OFF the WiFi and BT 
rasPi3 radios by hardware in config.txt setup.

	Thanks for all your continuing efforts,
	... and Happy Thanksgiving to All!

	- Don - AA7AU

ps: if it's OK, may I please have a new HamVoip registration for one of 
my nodes to test out, etc. If not, no problems, I can wait.