Here are some issues or I can’t seem to find the answer, so far and am hoping someone here might know for ASL3
1 - I want to be able to connect to my other node on startup. In HamVoip there is a place in the Rpt.conf, but something is different, so I don’t know where that is.
When I try to connect my node 62030 to 61172 or the other way around, it just sits there saying connecting and will not connect. But when I connect to another node of someone it connects. Both nodes are currently at my home on the same network.
I did change the one port from 4569 to 4580 and opened the port up. Am I missing another port that I need to change and open up?
2 - how to I change from Morse code ID to Voice ID instead?
3 - Logging for connections and web connections, how and where to turn that on?
So far, I have been doing searching, but so far, no luck in getting this resolved.
1 - Two nodes on a local network will be always be squirrely regardless of ASL3 or HamVOIP because the system is using your public IP address as NAT’d through your router. Depending on a whole host of randomness in a given setup, it’s hard to predict how that may work. If these nodes don’t move, then I’d suggest putting custom entries into rpt.conf and hard-code your local LAN IPs. Another possibility is that your router setup is doing enough traffic handling to send your traffic to a node but it’s responding locally. In this case, you could try toggling off the firewall in cockpit to see if that resolves your issue. However that is NOT recommend as a permanent solution.
2 - Simply change your idrecording in your local node’s [62030](node-main) staza from an |i to a path to an appropriate encoded .gsm file. See Rpt.conf - AllStarLink Wiki.
3 - I’m not sure what you mean by "logging for connections and web connections? Can you clarify?
4 - By “DVSwitch” are you asking about the DVSwitch Mobile app? If so, yes it does.
Yes, hairpin NAT can be a problem on some routers. That’s where the [nodes] stanza the OP mentioned comes into play. ASL3 is no different in that regard than any other AllStar system.
I cannot advise you on anything about Supermon. I know that /var/log/asterisk/connectlog requires installing and configuring some process specific to Supermon - the “smlogger” stuff. Have you tried managing the connections and data in Allmon3? That works out-of-the-box and does not require any special configuration or local installation files.
Regarding /var/log/* items, I assume you’re using the Pi appliance. The Pi appliance is not running syslog by default to cut down on write-wear of SD cards. I would not suggest it, but you can install the rsyslog package if you want traditional syslog logs.
Finally, what are you trying to accomplish with the startup_macro line?
Oh, I see what you were trying to do… *813 is the default “persistent link” command. So you could use *81361172 but that’s likely overkill for the startup_macro.
I’m sure we could make it work. Our sounds are in /usr/share/asterisk/sounds/ but we don’t have a notices directory. If that is something HamVoIP is willing to share, we’d be happy to consider it.