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
Alan -
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.
Cheers,
Rob
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 would see the helpdesk and let’m have a look.
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.
Cheers,
Rob
I have set a port 4570 for the node I am currently building and NOT currently running. I will be running this in future on the same IP thus the different port. That is Node 512820.
The Node 512811 (not registering) is on port 4569
On Node 512811, I have the bindport set 4569, with server registered on AllStarLink also as 4569
I have matched the passwords on the register => line and the secret line and copy and pasted it from the node password register. I have rebooted the node and no difference… just keeps trying to register with timeout
Can you run iax2 reload for me again? I’ll look at the raw packets and see what’s happening.
What does Identifier state QUEUED FOR CLEANUP mean?
I just did a reload - same result - gets to Pseudo signalling… hangs a few seconds and the does the connection/disconnected lines
The node that works has this:
Identifier state CLEAN
The node that fails has this:
Identifier state QUEUED FOR CLEANUP
in the blue panel (status)
I exited reload CLI and it has returned to Clean after announcing “Last minute cleanups”
I’ll message you privately.
sorry but where do I see messaging?
Click your profile at the top right (Just an A with a circle around it) and click the Mail icon.
JUst out of curiosity.
Can you confirm that the new node can resolv dns?
in the cli do something like
ping register.allstarlin.org
after a few line of output do a control-c to stop the ping
it should give you something like:
ping register.allstarlink.org
PING allstarlink.org (34.105.111.212) 56(84) bytes of data.
64 bytes from register-west1-b.allstarlink.org (34.105.111.212): icmp_seq=1 ttl=55 time=62.7 ms
64 bytes from register-west1-b.allstarlink.org (34.105.111.212): icmp_seq=2 ttl=55 time=63.0 ms
64 bytes from register-west1-b.allstarlink.org (34.105.111.212): icmp_seq=3 ttl=55 time=62.9 ms
64 bytes from register-west1-b.allstarlink.org (34.105.111.212): icmp_seq=4 ttl=55 time=62.9 ms
^C
— allstarlink.org ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 8ms
rtt min/avg/max/mdev = 62.742/62.893/63.027/0.323 ms
the numbers will be different, but it soul look about the same.
If you have some error, you have a problem with DNS.
If you did not do any updating of the raspbian software you could have miss it.
Pierre
VE2PF
···
Le jeu. 14 janv. 2021 à 19:40, Alan McDonald via AllStarLink Discussion Groups <noreply@community.allstarlink.org> a écrit :
| Alan
January 15 |
- | - |
The node that works has this:
Identifier state CLEAN
The node that fails has this:
Identifier state QUEUED FOR CLEANUP
in the blue panel (status)
Visit Topic or reply to this email to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, click here.
We were able to work it out over private message. He shut off his node for >10 min and it seemed to register after that. Might have been something on the router, or the node, but we have no idea!
Rob
Could it be 1 of the pttlink hijacked node #'s?
···
On Thu, Jan 14, 2021 at 7:24 PM Rob V via AllStarLink Discussion Groups <noreply@community.allstarlink.org> wrote:
| KK9ROB ASL Admin
January 15 |
- | - |
Click your profile at the top right (Just an A with a circle around it) and click the Mail icon.
Visit Topic or reply to this email to respond.
In Reply To
January 15 |
- | - |
sorry but where do I see messaging?
Visit Topic or reply to this email to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, click here.
where do I find more info on that?
speaking of them, they are not really fast to answer request.
After 3 email to have my account removed, I can still log in the site.
They must be to busy restarting the asterisk process every 20 minute to process the removing of the stolen data.