After maintenance, allstar-public not functional

[N2DYI]

Greetings:

as of 1:17 PM EDT, WT/allstar-public doesn’t appear to be functional.

Here is the setup from a call placed to one of my nodes from a SharkRF M1KE using this method:

Connected to Asterisk 22.4.1+asl3-3.5.5-1.deb12 currently running on asl (pid = 4003039)-- Accepting AUTHENTICATED call from 72.89.237.157:4569:--        > requested auth methods = (MD5),--        > actual auth method = MD5,--        > encrypted = no,--        > requested format = Unknown,--        > requested prefs = (),--        > actual format = ulaw,--        > host prefs = (ulaw|adpcm|gsm),--        > priority = mine
-- Executing [s@allstar-public:1] Ringing("IAX2/allstar-public-11995", "") in new stack
-- Executing [s@allstar-public:2] Set("IAX2/allstar-public-11995", "RESP=???") in new stack
-- Executing [s@allstar-public:3] Set("IAX2/allstar-public-11995", "NODENUM=506318") in new stack
-- Executing [s@allstar-public:4] GotoIf("IAX2/allstar-public-11995", "1?hangit") in new stack
-- Goto (allstar-public,s,15)
-- Executing [s@allstar-public:15] Answer("IAX2/allstar-public-11995", "") in new stack
-- Executing s@allstar-public:16] Wait("IAX2/allstar-public-11995", "1") in new stack
-- Executing [s@allstar-public:17] Hangup("IAX2/allstar-public-11995", "") in new stack
== Spawn extension (allstar-public, s, 17) exited non-zero on 'IAX2/allstar-public-11995'
-- Hungup 'IAX2/allstar-public-11995'asl*CLI>
Disconnected from Asterisk serverAsterisk cleanly ending (0).
Executing last minute cleanups
root@asl:/home/patrick#

If I use Repeaterphone, it doesn’t appear to ever hit the server in the first place. Just rings until it times out client-side.

[N8EI]

RepeaterPhone is working okay for me. Can you give me an example node that's failing?

[wd6awp]

It not working for me. I use account authentication for all my nodes...

The call drops instantly

Nothing happens on the Asterisk console on connect attempt.

[N8EI]

Are you using file lookup and is your /var/lib/asterisk/rpt_extnodes file correct? We had a problem for a bit with that and it should have downloaded a new, correct version but that might be it?

[WA3WCO]

Something to check on your node(s) :

$ wc -l /var/lib/asterisk/rpt_extnodes 
11576 /var/lib/asterisk/rpt_extnodes

If you get a large count (over 10K) then you should be good. If not, try :

$ sudo systemctl start asl3-update-nodelist.service 

[wd6awp]

I never needed asl3-update-nodelist.service, but I did install it and set node_lookup_method = both (it was dns) and restarted asterisk. Repeater phone is still not connecting.

It's just a swag but I suspect the web transceiver flag api is not working.

EDIT: wc -l /var/lib/asterisk/rpt_extnodes returns 11560 /var/lib/asterisk/rpt_extnodes
EDIT2: or maybe Repeaterphone has a bad rpt_extnodes (or equivalent) list.

[kg5ie]

Both of mine fail 655100 and 655101

[kg5ie]

Both nodes fail to connect on AllStar. Fine on Echolink.

655100 and 655101

[WA3WCO]

Just now, I was able to connect to both 655100 and 655101 using RepeaterPhone.

Are you still having issues?

Have you checked the actual nodes to ensure that they have a good (complete) node list?

In case you didn't know, with RepeaterPhone you can select the "Directory" tab. Then, with the node list displayed, you can drag the list down from the top towards the bottom and when letting go it looks as if the app is refreshing its node list. That may (or may not) help.

[kg5ie]

Still no connect from RepeaterPhone. Just rings.

[WA3WCO]

To confirm :

• you are trying to use RepeaterPhone to connect with these nodes?
• you have refreshed RepeaterPhone's node directory?
• you have checked the rpt_extnodes files on the nodes to ensure that they have reasonable content (see my earlier post)?

... and, lastly, are you trying to use RepeaterPhone on the same local network as the nodes you are trying to connect with? If so, try using the cell network to connect from RepeaterPhone to the nodes (i.e. turn off WiFi on your phone).

[N8EI]

I can connect successfully to 2503, 655100, and 655101. On 655100 and 655101 I made a transmission which appeared to work. On 2503 I'm listening to a QSO in process. The only thing I can offer is that I opened RepeaterPhone "cold" - i.e. wasn't already running in the background.

[VA2WE]

This happened to us as well, a few of us actually. All our usual nodes were grayed out (via RepeaterPhone). Echolink was also a challenge to acess.

6 hours later, we can access our club repeater node number again (public access).

Would be curious what was the root cause.

Please, let us know.

Thank you.

[N8EI]

No idea. We had a few problems with the Stats API and the node database at various times. Must have been one of those. Not sure. Glad it's working now.

[VA2WE]

I thought the cause was in those waters…

Thank you Jason.

[kg5ie]

All seems back to normal this morning. Seems refreshing of RepeaterPhone listing may have solved the issue…or things finally got refreshed down line. I blasted out a bulk suggestion to our 208 members to refresh their RepeaterPhone directory listings and the complaints stopped

Thanks as usual for the prompt assist.