New node with IAX2 reg worked for a day or two

AllStarLink
1

Hello ASL folks,

I’ll try to keep this short and to the point. We have a new node that is behind an ISP (Team Mobile) that failed during a normal install (HTTP registration) so moved it to IAX2 and was up and running……for a couple days.

After a reboot, node is showing IAX2 registration, but can’t connect to outbound nodes. a connect to 55553 works fine. Strangely, online “whats my IP” websites return an internet IP address different than asterisk CLI node lookup. A remote user (me) trying to help can’t ping the IP of the asterisk CLI node lookup.

The node shows up in allstar as registered (green) but not reporting data. The asterisk CLI is reporting statposts failed with an error of 401 (unauthorized).

We’ve doublechecked all the changes to the config files required for IAX and everything seems to be all fine. Triple checked the node/password combo in iax.conf. I don’t believe this is a password problem as the node is showing registered (although I really don’t know that for sure).

Problem node 66957. IAX2 registry shows registered. Nothing glaring from check-install.

IT WAS WORKING before, so I don’t think this is a config problem but at this point I’m running out of things to check. Any suggestions?

Thanks and 73

Tom

2

To confirm, you followed the instructions on switching from HTTP-based registration to IAX2-based registration including :

  • updating the modules.conf file to disable loading of res_rpt_http_registrations.so
  • updating the iax.conf file to include the registration for our node with the correct node# and password
  • restarted asterisk
  • checked the IAX registration from the asterisk CLI with iax2 show registry

FYI: node 55553 allows connections from nodes even if they have not successfully registered.

Also, stat posting has the same issues as HTTP-based registration so the errors are expected.

3

Yes. After those changes everything initially worked. And it shows iax registration then and now as well.

After it stopped working we double checked all the entrys and nothing had changed.

4

NIJ meant T-Mobile as the provider.
Any further thoughts on how or why this could possibly stop working?
IAX2 is pretty braindead simple in terms of maintaining a registration even behind NAT.
Also we should have a number of other folks here using T-Mobile home routers & hotspots if you are able to chime in on any problems that would be very helpful.
It’s pretty expected that inbound connections are not going to work, but outbound should!
And the green registered status on the Allstarlink.org webpage nodes list being green and registered but with NO data make no sense.
I think it may be open a trouble ticket time.
Also if OP (original poster) could update the title to include “T-Mobile” I think that that would be really good in general and for future search hits.

5

NIJ meant T-Mobile as the provider.
Any further thoughts on how or why this could possibly stop working?
IAX2 is pretty braindead simple in terms of maintaining a registration even behind NAT.
Also we should have a number of other folks here using T-Mobile home routers & hotspots if you are able to chime in on any problems that would be very helpful.
It’s pretty expected that inbound connections are not going to work, but outbound should!
And the green registered status on the Allstarlink.org webpage nodes list being green and registered but with NO data make no sense.
I think it may be open a trouble ticket time.
Also if OP (original poster) could update the title to include “T-Mobile” I think that that would be really good in general and for future search hits.

nodelist
nodelist846×233 32.1 KB

6

Anything new on this??