Problem: A friend who was using Repeater Phone to access my node without issue is now getting a "node not available" when he finds my node in his search. He can connect to other nodes without problems so the issue is on my end. I just don't know what.
My node reports up on the Lists and Stats page. I can connect to it via my android phone and DV Switch in WT mode or as a client from local Wi-Fi or with the Wi-Fi off, using cell data. Another friend can do the same from his android phone.
So what did I change.... Right before he lost the ability to connect, I did a firmware update on my router but none of the WAN settings or port forwarding changed. I had also setup DDNS.
I've disabled the DDNS with no change, I've had the Repeater Phone user hard reboot his phone a few times. I've shutdown and rebooted a few times myself to no avail.
The node has been up for the last 24 hours having DV switch connections without issues.
Does anyone have a suggestion as to what to check?
I'm like Santa Claus, I've checked it twice and toggled it No then Yes just in case there's a hitch in the giddyup. The twist is that DVSwitch on Androids in WT mode work without a problem on cell data or Wi-Fi...
I thought the same thing. The RP user has had to do a few full reboots over the last week or so to get his phone to play. We waited more than 24hrs between reboots and attempts only to get the same result of nada. I've looked at the Asterisk CLI when he was attempting to connect but saw absolutely nothing pop. Being a complete Noob, I may have done that wrong. I'm still stumbling around Linux. DVSwitch at least shows you a RED token when its not happy in WT mode. The odd part is that he can connect to another node (not that far from me, like it matters...) doing the same process that fails when attempting to connect to me. I will track him down tomorrow and attempt the verbose text.
You aren't alone in experiencing this issue. This occurs with both RepeaterPhone on iOS and Transceive on Mac OS on my hub node. Rebooting and time have no impact towards resolving the issue.
I had the exact same issue with RepeaterPhone when I had to move my node to a new location. This resulted in the node’s public IP to change and was properly updated in the ASL public db.
The issue was actually with RepeaterPhone, that was using (remembering?) the previous public IP.
Once I edited RepeaterPhone’s Node Details with the new public IP, problem solved.
So not an ASL issue, but rather an incorrect configuration within RepeaterPhone.
BTW - now that I have noip-duc running on my asl server, I can put the fully qualified domain name into RepeaterPhone Node Details HOST field.
One thing not mentioned is uninstalling RepeaterPhone from the cellphone, and then power cycling the cellphone, then reinstalling RepeaterPhone, then power cycling the cellphone again.
Excellent info. The WAN address of my node matches the host address listed for the node in the RepeaterPhone directory. So this doesn't appear to be the issue in my particular case. But thanks for this in any case.
I received a text from my RP user that he solved the issue. Going into "Edit Node Details" and looking for "Authentication" he toggled the selection of "Account" to "Node" then back again.
My node became available as soon as he toggled back to "Account".