Jump to content
  • 0

Node Fails To Connect


WRFP399

Question

9 answers to this question

Recommended Posts

  • 0

Now mind you I am ASKING because there were new 'rules' put into effect.  But was there any issues with interference or excessive key-ups with no one talking on your repeater?  I only ask because the MidWest group has stated that they will be banning nodes for 24 hours for infractions of the rules.  Not saying this is the case,,, only asking a question here.. So please don't think I am implying anything.

 

Try connecting to my node directly.... 23903 and see if it works.  I will try to monitor and attempt to see if the connection is coming through.

 

 

Link to comment
Share on other sites

  • 0
13 minutes ago, WRKC935 said:

Now mind you I am ASKING because there were new 'rules' put into effect.  But was there any issues with interference or excessive key-ups with no one talking on your repeater?  I only ask because the MidWest group has stated that they will be banning nodes for 24 hours for infractions of the rules.  Not saying this is the case,,, only asking a question here.. So please don't think I am implying anything.

 

Try connecting to my node directly.... 23903 and see if it works.  I will try to monitor and attempt to see if the connection is coming through.

 

 

No sir. In fact my Node sees very little action and I generally only connect it when there is a net going on. It is still failing to connect and telling me as such. 

Link to comment
Share on other sites

  • 0

Have you run any updates on your node lately?  I am thinking that there might be a version limitation on the software we can run and have it work with the rest of the system.

 

EDIT:

I just did a lookup on the IP I am seeing giving me the reject.  It seems to be in an AWS datacenter in Maryland or Virginia.  Thinking that's NOT you.

Log into your node.

run the command sudo asterisk -r and wait a few minutes.  See what it shows in the logging output.

 

 

 

Link to comment
Share on other sites

  • 0
3 hours ago, WRKC935 said:

Have you run any updates on your node lately?  I am thinking that there might be a version limitation on the software we can run and have it work with the rest of the system.

 

EDIT:

I just did a lookup on the IP I am seeing giving me the reject.  It seems to be in an AWS datacenter in Maryland or Virginia.  Thinking that's NOT you.

Log into your node.

run the command sudo asterisk -r and wait a few minutes.  See what it shows in the logging output.

 

 

 

Connected to Asterisk GIT Version adaec47 currently running on node-20201 (pid = 539)
[Jun 12 04:04:25] NOTICE[646]: chan_iax2.c:9712 socket_process: Registration of '20201' rejected: '<unknown>' from: '34.194.144.228'
node-20201*CLI>
 

Link to comment
Share on other sites

  • 0

This setup worked just fine for the past several weeks. Prior to that the interface board that plugged into the Motorola 16 pin had a failed solder joint. This interface replaced that one. The node connected in just fine this morning and I thought all was well. Now I can't even get it to try and connect to any hubs or node. It won't even give me the connection failed audio. Acts just like when you first boot it up and are waiting for the system to recognize the node.  I have once again tried to reboot everything with no change.

sudo asterisk -r gets me:

Connected to Asterisk GIT Version adaec47 currently running on node-20201 (pid = 16877)
node-20201*CLI>
 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Guidelines.