If you can’t call out nobody can call in.
I have had problems connecting to ONE node.> Got it fixed but now I have this Can’t call out problem… Never been able to call in (Which frustrates a local hacker no end so I’m happy with that. _)
Router TP Link Archer 10
ISP T-mobile.
Suggestions???
Perhaps start by stating the node number of your node
And perhaps a few of the node numbers you have tested trying to connect in/out
And the software version of the server in question.
And I take it you mean node connections and not a manager connections like the thread title states.
Tried to reply to the e-mail
My node is 55218 This is a headless node I use for outgoing only. and you should not be able to connect to it… (Router blocks incoming calls) has worked fine however for outgoing.
Node 28848 (Sunflower reflector) gave me some fits but chanign http time out in manager from 60 to 90 worked (Well the error log did say “Timout error”)
Other nodes 5086 (W8ACW Remote base) Do not recall if I have ever tried to allstar to it (I use IAX clients they work fine)
574420 and 574421 W8ACW Repeaters… Those I connect to or have connected to with Allstar.
The ISP is T-mobile… Due poor connection speed I restarted the modem (Remote power cycle…or basically (literally) logged in and hit “restart device” ) That is the only change since it last worked.
Guess: Port blocked but … I’m not good enough to figure out which port or how to un-block
In addition Supermon shows the following ports should be in use (I suspect)
[ AstP: 4569 ] [ MgrP: 5038 ]
Neither of which shows up if I run NETSTAT -a
I’m kind of assuming one of those is Asterisk Manager. I can not connect to. (or both)
As I said ONLY change I made since last work was to re-boot T-mobile modem.
FYI, nodes designated as ‘remote base’ in software, will only allow one connection.
If it is only a node that is a remote base but is not designated as such in software, that is not true.
I am a bit confused as to which nodes you have a failue to connect using the allstar network.
Could you re-phrase some of your statements so it is clear where your failures are coming from.
You have not said what software version you are using.
If asl3, Make sure it is up to date.
What nodes I can not connect to is easy ALL NODES. Name a node I can not connect to it… If I can not connect to the Error msg is " Could not connect to Asterisk Manager." and all connections go throught i
As for Version… x
x —HamVoIP Firmware Version— x
x RPi2-3-4 Version 1.7-06 Allstar - November 29, 2023 - K4FXC x
x x
x —HamVoIP AllStar Version— x
x Asterisk 1.4.23-pre.hamvoip-V1.7.1-04 app_rpt-0.327-01/22/2022 x
x x
x —Linux Kernel Version— x
x Linux version 5.4.75-1-ARCH (builduser@leming) x
x gcc version 10.2.0 (GCC)) #1 SMP PREEMPT Mon Nov 9 16:58:39 UTC 2020 x
That is a bit far from the initial “can’t call out” problem.
Asterisk manager is a outside/external method for stats display and control
using the asterisk manager interface.
It is not the core of what makes connections. Just control them perhaps.
The software you are using ie allmon/supermon etc ?
If you can’t log-in with your management software, the 1st thing that are first to check are
user/password and other things in manager.conf interface that have to match-up with the management software config.
Kinda universal with all of them.
What software are you using for management,
allmon/supermon/allscan or something else ?
While I may not be able to lead you to an answer. You have to say enough for someone else to be able to who is more familiar with software you are using and did not state.
They are not all the same.
Ok…;. I am able to connect to the Pi just fine with PUTTY (I copied the software versions from that screen) also with Supermon or Allmon (Both work) from within my LAN (Which i9s how I want it )
What I can not do… and (I used to do it all the time) Is link to another node. ANY other node and the only error I can find i that
Could not connect to Asterisk Manager.
That appears on the Supermon default (Before (And after)( you log in in the node info section at the bottom
Normally it wouild say something like No Connections.
Or there Could be several lines like
|574421|W8ACW 444.200 + Flint, Michigan|014:58:15|ESTABLISHED|OUT|483:53:07|Transceive|
Copied those from the remote base (no connections since I’m not connected to it and far as I know I’m the only user) and the VHF repeater I am Admin on (The connection is the UHF repeater same site/admin) just in case.
I used to connect to all 3 of those. and to Sunflower reflector via my Allstar.
I still can using IAX clients (IAX.rpt on this comptuer or DV-Switch on my phone)
But after a modem restart. No joy.
Of course a putty connection is a SSH connection.
A asterisk manager /supermon is a http connection.
And they use different ports.
The only thing I would see that might change on a simple router restart is your IP address.
So, I would review your server network setting in your hamvoip server and make sure you are set to a static ip address.
If you putty into the server, you should be able to
ifconfig
to see the local address of the server.
Then i would look at your router to be sure your port forwarding the correct ports to the correct ip addresses if your connection issue is while connecting from outside of your network. (only if)
Ones you have verified that, the only thing left that comes to mind is a problem with DNS
and restarting the ISP router may be the 1st and your local router second.
I don’t know how hamvoip handles it’s network/dns if at all but perhaps someone else will chime in on that.
You should be also able to see your node in the node list locally via putty connection
grep "55218" /var/lib/asterisk/rpt_extnodes
And you might also check the nodes you are trying to connect to the same way and be sure they are registered and in your list of connectable’s.
The file you are looking through is listed in that command.
If you go to a asterisk command line in putty,
asterisk -rvvv
You should be able to issue manually a connection command from CLI>
rpt fun *3node# yournode#
for a test of your server over your management software.
So, see if the ip address matches what your supermon thinks it is 1st
Ok none of that worked.
How to I find out what my WAN IP is I know Supermon says 172.58.xxx.yyy
It shows numbers of courese but how do I figure out if that’s the correct address.
As I said I do not accept connections incoming.
Oh and all the commands suggested replied failure No such file save for the Rpt Run which simply tried to connect same as if I’d sent *328848
A couple of things here:
A while back in this thread, you mentioned a four digit node starting with a 5. Those don’t exist on the Allstarlink network. Is that some sort of odd private peering arrangement? If so, that will break your ability to connect to some public nodes. This is why private nodes should always be under 2000.
I’m starting to think that somehow, your Supermon/Allmon is listening on an address other than 127.0.0.1, which it shouldn’t be doing, and that matched your IP address previously assigned by your router, which just happened to work for a while.
as long as you do not specify port forward of 4569 then you will not have inbound connections. you can make as many outbound as you want.
Supermon uses port 80 and the manager port only. if you want to see supermon outside of your local network then you have to forward port 80 only. you will also have to change the bindaddr=127.0.0.1 to bindaddr=0.0.0.0
Well Fixed it
Re-burned the card and re-did the configuration files from backups.
Save for 28848 (Which has been a problem on and off all along) Working
Funny (not) how often that cures things.
Just never know when there is a corruption.
Hope you have some hair left.
Got that straight… Plus the new Raspberry PI (The old one the micro-sd slot broke) has Wi-Fi.
Don’t toss it, you can boot from a usb sd card adapter.
Thanks… Was thinking about trying that.
The 4 digit node is a remote base… Now that I fixed the problem I connect to it easily.