Search results

Then try turning it on?

What kind of router? Maybe try turning off any VOIP features that the router thinks will improve VOIP (like SIP ALG).

Did you update your "NAT Settings" in the Asterisk Sip Settings menu after the IP change?

I agree with islandtech, this seems like your VOIP provider doesn't know where to send calls because your IP changed. Unless some inbound calls work, then you have a different problem.

This is not simple, but Home Assistant w/ Ratgdo is local control of your garage that can work with voice control.

when I setup the Public version, I have to add this line to /etc/iptables/rules.v4 -A INPUT -p udp -m udp --dport 10000:20000 -j ACCEPT after you do that, you can reboot or reload iptables. Also, tcp port 2267 has to be opened for Clearly Anywhere to work.

Is this fictional? Where is Mango Park?

Finally, I'm not part of a breach.

Why can't OP install a Debian VM in Proxmox, and then follow the regular instructions?

These are the instructions I followed for Proxmox, worked fine for me. https://nerdvittles.com/introducing-incredible-pbx-2027-u-for-proxmox-7/

I It would not be whitelisted or blacklisted in the GUI. From the command prompt you can type "iptables -nL" and look at the output to see if that callcentric IP address is being allowed or dropped by iptables. Or, you can paste the output here (after removing your IP address) and someone...

run those commands from the command line, one by one, don't change the password.

Whenever I do a "Go Public" setup I add that line back in.

Depends on which version of the system you installed. Generally speaking though, PIAF is out of date, and you should start over with IncrediblePBX 2027, following one of the tutorials on nerdvittles.com. The tutorials will walk you through how to get your phone up and running.

I guess technically what I do is use the prefix on the inbound route, and use the Clearly Anywhere app, so I don't have the issue Samot describes.

I like to use a prefix, that way you can see the dialed number and caller ID. For example, if I had 3 numbers, one for a St. Louis location, one for New York, and one for LA, then I would make a code that reminds me which line is being called. For example, I would put this in the prefix: "SL-"...

Thank you, I learned a new thing today. I'm a dummy, my IP address is whitelisted using /root/add-fqdn, so my attempt to register using the IP address never even gets down far enough to hit that rule. It is working as expected.

All remote, it is a VM setup with Vultr.

I know it wasn't supported, but based on this comment I tried anyway. I followed the instructions, but am able to register to the PBX using the IP address instead of the FQDN.

I just setup a new machine today with the GO-Public instructions. Is there a way to tell if it is working in sngrep? Or is the test to try registering by IP address and then by FQDN?