Hi fellow HAMs !! I have been using my
Allstar node from my raspberry pi 3 and a Shari device for months , and it has worked flawlessly. For the past few days , I am not able to connect to any nodes. It keeps saying the registration is timing out. I contacted the help desk and they said they’re has been registration server issues as of late, but they don’t take care of that and I should post here and “someone will look into it” .. nothing in the config or network has changed, and I feel like this a backend issue and requires someone with admin access to fix. I have tried alternate registration servers and can ping them just fine, but they keep saying “timed out” and it won’t register. I really miss having this connection, can somebody help ? I’ve done all I can to fix it from here. I see there is an IAX registry workaround, and I’m wondering if I should try that. It says not unless you have to , but I have no other way to connect at the moment . Any advice or someone else I can email on this issue ? Thanks …
There was a ~24 hr issue with one of the two registration servers 6 days ago, but I've seen nothing since. The devs will see your post; they'll have more info.
There was a problem with registration servers on the evening of Friday May 23rd into mid-morning Saturday May 24th ET. That has been resolved and there are no issues reported since. Can you please provide any logging output or details of what is saying it's "timed out"?
Did you try rebooting your raspberry pi since the registration server problem was fixed?
Thanks so much for the reply, I really appreciate the help, I am able to ping both registration servers (the main one and I tried west) and the return from the ping is fine, but it gives me this :
And the web portal , node settings … it says Registered “No” , so I don’t imagine anything will connect just from that. But this account has been working just fine for months, I don’t know why that suddenly changed to not registered. I had tried changing to password to see if that fixed it but no luck there , and I have reverted it to the original one. All passwords Match in the iax.conf . I’m not the most computer savvy operator out there, so if there is somerhing specific or output from something that would help please let me know . The pi has been rebooted several times and that’s not the fix apparently. When I re-run the show registry command , state changes to “request sent” for a few and then change back to “timeout” (it will only let new users post 1 pic) .. Thanks again !!
Looking at the database and the logs, it's not failing registration so much as your node doesn't seem to be trying to register at all. There's no attempt for node 60824 to register since it's last successful registration on 2025-05-24 18:40 UTC which is well after the problem with register-central. From your screenshot, it looks like you're using HamVOIP which has a grafted-in parallel system so that could be the problem? I can't help with HamVOIP.
Thanks very much for looking into that, it’s appreciated! ‘73
I have recently run into the same problem. I have a HamVOIP node (532526) that has worked for YEARS. When I login to the AllStarLink website, the 532526 node shows as NOT REGISTERED. Nothing has changed on my node. I have rebooted it and restarted Asterisk multiple times. When I issue the “iax2 show registry”, I see the following:
pi400-532526*CLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
52.20.63.146:4569 Y 532526#4566 60 Request Sent
After a few minutes, I see the following:
52.20.63.146:4569 Y 532526#4566 60 Timeout
I can connect to the node and use it to connect to SOME nodes like Parrot Nodes and 552990 for example. However, there a some nodes like 505422 and 27339 that I cannot connect to. I assume these failed connections are due to my node not showing as registered.
Since nothing that I am aware of has changed on my node, I can only assume it has something to do with the Allstar registration servers.
Any guidance on how to get my node to register will be much appreciated.
Tim
KX4ZU
Look in /etc/asterisk/iax.conf.
Does your registration line for the node include “#4566”? If so, delete #4566 from that line, save it, then reload or restart Asterisk.
The more modern registration server doesn’t like that anymore, and there were some old instructions from years ago that had people include the port in the registration line. This no longer applies, and you’ll not have that even be a possibility if you use ASL3 with HTTP registration.
WOOHOO!!! That did the trick. Thank you so much for letting me know about this change.
Thanks again!
Have a Happy Holiday!
Do you have a URL for such directions? I've never seen that and it never came up since I deployed the new IAX auth servers back in September. The IAX registration system was completely rewritten for performance reasons and does strict string sanitization to fix other problems. If there was something in the code that worked with a #PORT designator it was completely unintentional in the old code.
Unfortunately, I can’t find it now, but I know that HamVoIP had people do this for a while, because I also had a couple of old nodes with that problem show up around maybe September 20 or so. Don’t remember the exact date, and that was the cause. I definitely remember seeing reference to it in either one of the HamVoIP howtos, or on the now defunct HamVoIP email reflector.