Recent content by DudeInMyrtleBeach

Focus Broadband in Brunswick County, NC. I'm not using 5060 or 5061 anymore on this PBX.

Got this squared away with Mark's help. I created a new SIP profile and changed the port. Apparently, the local ISP is messing with 5060. Once I did that, NAT worked.

I tried rfc1918.auto and nat.auto. It didn't matter. What I ended up doing was moving the PBX instance to Vultr. That fixed the initial issue. Now, unfortunately - I have another. The ISP is doing what they call 'Enterprise NAT' or 'Carrier NAT' - which means that they're too cheap to shovel...

I did. No matter what I do, Fusion sees endpoints behind these 2 IP's as local and does not apply a NAT policy.

I wish it was. I could fix that. localnet.auto is being dynamically built by Fusion, and there doesn't appear to be any way to (easily) change that. Fusion examines it's own IP address, then sees that the 2 other IP's are on the same subnet (/29) and 'assumes' that they are local networks and...

It's been a while since I installed a new version of Fusion, and I don't recall having to do anything when Fusion itself had a public internet IP and the endpoints were behind a NAT. NAT isn't working. I can have 2 extensions registered sitting side by side, and one can't call the other. It...

Oh yeah. I had tried them all. I just got off the phone with Mark. Sometime in the last couple of weeks, the voicemail_destinations permission was deleted by accident. If this happens to anyone, do an update, set app defaults, set default permissions will fix it. These changes were made today...

Did that on Monday. Did it again and got a 'Already up to date' but I ran it anyway. Still no permission.

Yes.I ran it on Monday and again tonight. It didn't work. My installation steps were: 1. Install and update Debian 11. 2. Run: wget -O - https://raw.githubusercontent.com/fusionpbx/fusionpbx-install.sh/master/debian/pre-install.sh | sh; cd /usr/src/fusionpbx-install.sh/debian && ./install.sh...

That's fantastic! Please - tell me where to find it. I don't know where else to look. I just checked the v_permissions table and the v_group_permissions tables - there are no voicemail_destinations permission there. There are a bunch of xxxx_destinations permissions but none for voicemail.

Others are having this issue? Is there a thread for this somewhere? If so, my search-fu must be starting to fade with age. I submitted a ticket on Monday. The response was: ___________________________________________________________________ This is not a bug. It is likely you have not assigned...

This is what I see in the menu. The extension listed has an active voicemail box and it works fine. Notice that there is no option to set the timeout destination to a voicemail box.

On one of my smaller installs, I'm running double the extensions you are on a hosted system with 2vCPU's, 4GB RAM and a 120GB RAID SSD. It's been running *flawlessly* for several years. Unless you're running a call center in the mix, you probably won't hit your suspected number of simultaneous...

Well, I'm at wits end. I just did a complete reinstall from scratch with Debian 11, a fresh install of the master branch, and when I add an extension with a voicemail box then go to Ring Group and attempt to set the Timeout Destination to the voicemail box of the user I just created -- it's not...

Hi! I have a fresh fusion install and when adding extensions the voicemail boxes get created and appear to be working, but there are no voicemail box extensions listed in any of the context menus - for example: 'Timeout Destinations' in Ring Groups 'Actions' in setting up a new Destination Not...