New Node won't connect to any other node. Asterisk logging registration rejected.

[WRZK971]

Every node I try to connect to immediately disconnects. Anybody have any ideas?  It is a fresh setup and my node is listed on the repeater map and the network map. My repeater is working locally, but I can't connect to any other node.  The port-forward is set up properly. The repeaterfinder.sh script has the correct username and password. The registration line was put in the iax.conf file, and asterisk was restarted before running the repeaterfinder.sh script.  I've allowed several days for the new node update to go out to the other nodes.  Any suggestions are appreciated.

I turned one of my nodes off (23301) for the time being to stop them from bombarding the registration server, which is returning the errors below.  

Can somebody try to connect to node 23302 and let me know what happens? Both my nodes are experiencing the same problem.

Running <sudo asterisk -r> and seeing the following errors non-stop:

Connected to Asterisk GIT Version adaec47 currently running on node-23301 (pid = 520)

[May 18 21:08:15] NOTICE[585]: chan_iax2.c:9712 socket_process: Registration of '23301' rejected: '<unknown>' from: '34.194.144.228'

[May 18 21:09:05] NOTICE[589]: chan_iax2.c:9712 socket_process: Registration of '23301' rejected: '<unknown>' from: '34.194.144.228'

[May 18 21:09:55] NOTICE[593]: chan_iax2.c:9712 socket_process: Registration of '23301' rejected: '<unknown>' from: '34.194.144.228'

[May 18 21:10:45] NOTICE[587]: chan_iax2.c:9712 socket_process: Registration of '23301' rejected: '<unknown>' from: '34.194.144.228'

[May 18 21:11:35] NOTICE[591]: chan_iax2.c:9712 socket_process: Registration of '23301' rejected: '<unknown>' from: '34.194.144.228'

[May 18 21:12:25] NOTICE[585]: chan_iax2.c:9712 socket_process: Registration of '23301' rejected: '<unknown>' from: '34.194.144.228'

[WRZK971]

Here is the debug info when I try to connect to node 100:

    -- Remote UNIX connection

  == Parsing '/var/lib/asterisk/rpt_extnodes_gmrs': Found

  == Parsing '/var/lib/asterisk/rpt_extnodes_gmrs': Found

    -- Remote UNIX connection disconnected

  == Parsing '/var/lib/asterisk/rpt_extnodes_gmrs': Found

Node Variable dump for node 23302:

   RPT_TXKEYED=1

   RPT_LINKS=0

   RPT_NUMLINKS=0

   RPT_AUTOPATCHUP=0

   RPT_ETXKEYED=0

   RPT_RXKEYED=0

    -- 6 variables

Node Variable dump for node 23302:

   RPT_ETXKEYED=1

   RPT_TXKEYED=1

   RPT_LINKS=0

   RPT_NUMLINKS=0

   RPT_AUTOPATCHUP=0

   RPT_RXKEYED=0

    -- 6 variables

    -- Call accepted by 3.128.112.133 (format ulaw)

    -- Format for call is ulaw

    -- Hungup 'IAX2/3.128.112.133:4569-2798'

    -- Hungup 'DAHDI/pseudo-1692635728'

    -- Hungup 'DAHDI/pseudo-928021047'

    -- <DAHDI/pseudo-376770469> Playing 'rpt/node' (language 'en')

    -- <DAHDI/pseudo-376770469> Playing 'digits/1' (language 'en')

    -- <DAHDI/pseudo-376770469> Playing 'digits/0' (language 'en')

    -- <DAHDI/pseudo-376770469> Playing 'digits/0' (language 'en')

    -- <DAHDI/pseudo-376770469> Playing 'rpt/connection_failed' (language 'en')

    -- Hungup 'DAHDI/pseudo-376770469'

Node Variable dump for node 23302:

   RPT_ETXKEYED=0

   RPT_TXKEYED=1

   RPT_LINKS=0

   RPT_NUMLINKS=0

   RPT_AUTOPATCHUP=0

   RPT_RXKEYED=0

    -- 6 variables

    -- Hungup 'DAHDI/pseudo-285719090'

Node Variable dump for node 23302:

   RPT_TXKEYED=0

   RPT_ETXKEYED=0

   RPT_LINKS=0

   RPT_NUMLINKS=0

   RPT_AUTOPATCHUP=0

   RPT_RXKEYED=0

    -- 6 variables

[May 21 15:08:39] WARNING[18348]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '23302'

[May 21 15:08:39] NOTICE[18350]: chan_iax2.c:9712 socket_process: Registration of '23302' rejected: '<unknown>' from: '34.194.144.228'

  == Refreshing DNS lookups.

[WRZK971]

I'll try to contact Rich. I'm pretty sure he's the only one who can fix this particular case anyway.

[MSnow]

On 5/18/2024 at 4:22 PM, WRZK971 said:

The registration line was put in the iax.conf file

You uncommented both lines as well? Seems like its not pointed to the right spot based on what you posted. Maybe DMZ the node in the router just to check if its a firewall setting.

Commented out
;register => nodenumberhere:nodepasswordhere@ast1.addcorrectwebaddress.com
;register => nodenumberhere:nodepasswordhere@ast2.addcorrectwebaddress.com

Removed to parse
register => nodenumberhere:nodepasswordhere@ast1.addcorrectwebaddress.com
register => nodenumberhere:nodepasswordhere@ast2.addcorrectwebaddress.com

 

[WRZK971]

23 minutes ago, MSnow said:

You uncommented both lines as well? Seems like its not pointed to the right spot based on what you posted. Maybe DMZ the node in the router just to check if its a firewall setting.

Commented out
;register => nodenumberhere:nodepasswordhere@ast1.addcorrectwebaddress.com
;register => nodenumberhere:nodepasswordhere@ast2.addcorrectwebaddress.com

Removed to parse
register => nodenumberhere:nodepasswordhere@ast1.addcorrectwebaddress.com
register => nodenumberhere:nodepasswordhere@ast2.addcorrectwebaddress.com

 

Thank you for responding.

 

This is what my register line looks like: 

register = 23302:<myPass>@register.mygmrs.com   [with the real password in there, not <myPass>]

and left the allstarlink registration line commented out.

 

I tried DMZ'ing to the host, didn't change anything.  My normal port forward is working because I verified traffic was able to hit that port from the outside.

[MSnow]

ah ok I have another node on a different network set up that same way yours is and it works.

 

I am assuming you omitted the > after the = on your forum reply but it is there in the iax.conf file? if not add it and see if that fixes it.

 

It may just not be approved in the system yet by the admins and that is why its not connecting. On another network I have a node on a few weeks ago they updated some firewall setting that blocks about 10 different nodes from connecting until the admin could fix it.

 

[WRZK971]

35 minutes ago, MSnow said:

I am assuming you omitted the > after the = on your forum reply but it is there in the iax.conf file? if not add it and see if that fixes it.

 

It may just not be approved in the system yet by the admins and that is why its not connecting. On another network I have a node on a few weeks ago they updated some firewall setting that blocks about 10 different nodes from connecting until the admin could fix it.

 

I tried the > char, but got the same errors.  The > was not it the line given to me when I register the node, but I just gave it a shot anyway.  Kind of strange I got the same errors after changing something like that.  I did restart asterisk.

Maybe you're right that an admin has just not gotten around to approve it. 

[WRZK971]

8 hours ago, MSnow said:

It may just not be approved in the system yet by the admins and that is why its not connecting. On another network I have a node on a few weeks ago they updated some firewall setting that blocks about 10 different nodes from connecting until the admin could fix it.

 

Something changed today.  I can connect to nodes, and can see tones being sent from the asterisk console when hitting "connect' on the management console.  Instead of getting the original rejection notices, I'm getting the following warnings, but don't know if it's anything to worry about:

[May 23 10:42:21] WARNING[6714]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for '23302'
[May 23 10:42:21] WARNING[6709]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest

I'll re-connect my repeater tonight and see if sound is getting through.

 

[WRZK971]

All works.

I got an email from 'support' saying everything should be ok now.  I don't know what they did, but it works for me.  My repeater is up and running.