Yes, you are connected to ASL… try connecting to 55553 echo test node and then try 538722. If you connect to both, then you need to redo your port forward… WAN ip:4569 forwarded Lan ip of your device:4569
I have to ask, forgive my ignorance as I am new, but how do I connect my node to other nodes? Keep in mind that I do not have my repeater radio receiver attached to the node yet where I can touch-tone in commands. Is there another way to make my node connect to another?
Without an RF component (ie. a simplex radio or repeater) attached to your node, it’s just a hub so you’d need to control it from the cmd line (asterisk -rvvv). No way to listen to it so you’d need to watch the cmd line responses. Telemetry is only local (usually; unless you’re anti-social…). If you wanted to connect to the other guy’s parrot node (I think it was?), you’d type:
rpt fun 64546 *355553
To disconnect, change the *3 to *1
Of course you can’t really take advantage of the parrot thing w/o a radio connected to it to talk/listen but at least you can check if you’ve got outgoing connectivity. Maybe you can listen locally to and try connecting to a known online node, if one’s available near you. I expect those big systems (like Win) have telemetry disabled, or it would drive users crazy (don’t know, I don’t use it). The asterisk cmdline will tell you, though.
As DTMF from a radio,
*3(node#) connects in full transcieve.
*2(node#) connects in monitor mode / just listen
*1(node#) disconnects from the node
Your audio levels must be set correctly to decode dtmf.
You might watch it if you are having issues by typeing
asterisk -rvvv
from a OS command line and exit to return to the OS command prompt.
To everyone and N2DYI, thank you so much for your advice and help! I am now able to access my node. The solution, yes port forwarding, but where it needed to be done was the actual solution.
One thing I neglected to take into account and mention is that instead of having a simple ISP modem feeding my router, I have Xfinity which has over my decades with Comcast service has evolved into their Xfi gateway product. I’ve also always had a Netgear router after this modem/gateway, probably because initially Comcast only offered a modem. So, during all of this adventure of port forwarding, I’ve been enabling the Netgear router only to have it blocked by the Comcast gateway ahead of it.
Now, I’ve forwarded port 4569 UDP in my Comcast gateway and plugged in my node directly and ahead of the Netgear router. Seems simple now that I look back at it, but it took a closer look at my network devices to see it clearly. I never really considered my Comcast ‘modem’ to be a gateway. Thanks again for all the enlightenment and understanding I’ve received over the past day! I appreciate all of you.
I think (if it’s like the one I returned), it’s a combination cable modem/wifi router. If you prefer the Netgear, put the Comcast thingy in bridge mode, then it’ll just be a cable modem or even buy your own compatible modem (often $15-ish online used) so CC doesn’t bleed you month to month for the rental…
Thank you for the advice!
1 Like
I had the same issue when trying to connect using RepeaterPhone, advice from the developer that trying to connect within same network wont work instead use phone data connection and turn off WiFi or use a VPN. Also check you have the same iax number in the RepeaterPhone settings default 4569. It’s worked perfectly since then. Hope this helps. Richard G4FBA
The op has a different problem... But, just FYI, if your router supports hairpin NAT properly, you can connect to a node on the same LAN with Repeaterphone without doing anything special. This works with my Ubiquiti equipment, but doesn't on other gear I've used.
I just connected from my allstar node no problem