since last night. one of my nodes keeps requesting and does a timeout. It keeps returning a sate Timeout/Request. My other node just fires up and is Registered.
I have rebooted the node several times and also restarted asterisk several times but my node 512811 does not register. So I cannot link to many nodes.
Strangely I can connect to BlindHamsCQ but no one else.
This node does not appear in green in the nodes list but the other node does.
How do I force the registration or correct this issue?
thanks
Yep they match and I have not changed them in the last 24 hours either so I expected them to remian correct.
The register entry is correct and the secret also match as expected.
If I go here: AllStar Link | Node List
I see the node 512811 with green
But if I go here: AllStarLink Active Nodes List
My node is not listed and I cannot connect to many other nodes.
I have rebooted my router and node more than once… no change.
Alan
I can connect to BlindHams Node 50631 but no other node in my favourites…
I can also connect to Echolink but that is not the same registration issue.
I keep seeing (on the Node Status page) State cycling between Request Sent and Timeout… never Registered as per other nodes…
I have put another node 512812 on the same router and it registers straight away. So it’s not the router. and not the port forwarding… it seems to be something at the registration side for node 512811
Alan, can you capture the screen when it attempts to register with the error message or grab it from the logs. There must be a error message while registering.
Knowing what that is would help locate the issue.
With a putty window, run asterisk in the foreground : asterisk -rvvv
Once you see the asterisk cli
Type : reload
I might also ask if this node ever reg’d since you extended the node number ?
51281 is not showing as a valid node
Out of my pay grade.
I know nothing about extending nodes… yet -outside of what I see in the asl menu.
Not seeing instructions for it, can you post the link to the instructions you followed.
I suspect that is the area the problem resides.
it was indeed registered - for the past year has worked no problems.
On the node which has the same image (but different node number 512812 - also extended, the log above is the same up to the point of
– Reconfigured channel -2, Pseudo signalling
The node that does work has:
[Jan 15 10:03:26] NOTICE[355]: chan_iax2.c:7446 iax2_ack_registry: Registered IAX2 to ‘34.105.111.212’, who sees us as 121.209.136.176:4570 with no messages waiting
instead of "Re-Loading config … etc
When you extend a node via NNX, you’re unable to use the 5 digit node number 51281. There’s an explanation of this when you do extend it so I apologize if that wasn’t clear. Due to the DTMF dialing behavior of Asterisk & ASL, as soon as a node # is matched in the dialing, it initiates the call. So 51281 and 512810 can’t coexist in the same system, unfortunately.
But I am NOT using the 5 digit. I have the 6 digit everywhere… 512811 and 512812 where did you see 5 digits? I have had this node running this way for nearly a year
I must have misunderstood the conversation. Sorry.
IAX runs on UDP so telnet won’t work
I believe the port you’ve set in your Server Settings in the ASL portal doesn’t reflect the port you’re using. It replied with “sees us as …:4570” which means you’re using port 4570. You have it set to 4569 on 512812. I changed it to 4570 on the portal for you so you should be able to connect IN to 512812.
We were having some minor registration issues when you posted this, so I encourage you try again. Double check the node passwords with the password you have set in iax.conf.
For 512811, just verify that the port # you have set in IAX matches with the port # you’ve set in the Server in your portal.