Iax2 show registry

App_rpt-users
1

Not sure if I should submit a bug or maybe ask for workaround in the community for this. I have loaded up asl-2.0.0-beta.5-kc1kcc-20210226-amd64.hybrid and setup the software on a computer.everything went well there. Set bindport in IAX.conf file to 4571. The problem looks like the registry is not being updated to this bindport. Below is output from the CLI. looks like it tries, but doesn’t see anything returned. I’ve been beating my head against the wall with this for 2 days now,

450631*CLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
34.105.111.212:4569 Y 450631 108.36.209.145:4569 179 Registered
[Feb 27 16:03:01] WARNING[4198]: chan_iax2.c:10277 iax2_do_register: REGISTER-LOG: Sending registration request for ‘450631’

I must mention that this is and extended node number that is not on the same server as original. I created a new server at ASL and then set node number to the new server. This node connects outbound, but not inbound.

Has any one else run into this problem and solved?

2

The registry port is not updated by the node. That comes from the portal. Did you remember to set the port for that node’s server on your www.allstarlink.org account?

3

Tim - it looks like he set it correctly.

@k3srm.steve your port is showing up correctly on the network, so ignore that its saying 4569. I’ll see why it reports that. If the port itself isn’t opening up correctly on your end, restart Asterisk / reboot entirely and see if that fixes it.

Thanks for using the beta!

4

No dice. Even double checked the port in router. I’ve setup a few of these things now and this one is killing me.

I sent a diagnostic file using the ASL-menu.

5

Can you put the output of:

sudo netstat -tulpn

here?

6

root@450631:~# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:5038 0.0.0.0:* LISTEN 357/asterisk
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/init
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 387/sshd
tcp6 0 0 :::111 :::* LISTEN 1/init
tcp6 0 0 :::80 :::* LISTEN 411/apache2
tcp6 0 0 :::22 :::* LISTEN 387/sshd
udp 0 0 0.0.0.0:68 0.0.0.0:* 341/dhclient
udp 0 0 0.0.0.0:111 0.0.0.0:* 1/init
udp 0 0 0.0.0.0:4571 0.0.0.0:* 357/asterisk
udp 0 0 0.0.0.0:44220 0.0.0.0:* 350/avahi-daemon: r
udp 0 0 0.0.0.0:5353 0.0.0.0:* 350/avahi-daemon: r
udp6 0 0 :::38663 :::* 350/avahi-daemon: r
udp6 0 0 :::111 :::* 1/init
udp6 0 0 :::5353 :::* 350/avahi-daemon: r
root@450631:~#

7

That show the port is open on your server.

grep 450631 /var/lib/asterisk/rpt_extnodes
450631=radio@108.36.209.145:4571/450631,108.36.209.145
root@pi4-beta4:~#

That shows the port is propagating to my and likely all nodes.

I was able to connect to 450631 from my 2530 hub. In bound connects are working now. Did you change anything?

8

have not changed anything other than reboot. Funny, stil shows 4569 in iax2 reg status. Also, I can’t connect from other nodes here in same domain. I’ll try from external rf node.

I’ll let you know if I connect.

9

Yeap, Looks like I can now connect from external nodes. Wow, not sure how that happened though. The other thing is that I still can not connect from nodes in my local network, and I’m not seeing any node information showing up in supermon.

10

Other nodes behind the same NAT router may need an entry in the [nodes] stanza if the router does not support hairpin NAT. There is mention of this here Two Servers Behind NAT Router - AllStarLink Wiki

11

New nodes take a little time for other nodes to accept them. It’s a deficiency in the older ASL distros that we’re working on a fix for. The fix is in the beta, so you don’t need to add anything.

Thanks for helping us beta test!

Cheers,
Rob

1 Like
12

I’ve already set the stanzas up in all the nodes. I’ll let this roll the way it is now. I’m able to accept connections now from outside my local network. Maybe by tomorrow things will be better.

Thanks for the help and hopefully I won’t be a problem for you guys.