Search results

Thank you for the follow up. The reason I always included the domain was the blf key would not turn red on parked calls. It was susggested in these forums to add the domain to show the red status. I tried BLF for call park and that caused other issues such as parking it but not allowing...

The two examples attached illustrate what I am referring to. I used mydomain.com for example only The previous versions of Fusion required the domain for call park to function properly In the newest version 5.4.7 call park would not function at all with the domain. I had to drop the domain then...

So I spun up a new Fusiopbx server In the past to set call forward parameters you would (Yealink phones) CallPark park+*5901@domain.com When I started using 5.4.7 it would not park correctly The only way I could get call park to work was to remove the domain and only use park+*5901 Anyone...

I tried to install Fusionpbx on Debian 13 but Nginx is broken when I do that. Debian 12 works fine though

Is it ok to install Fusionpbx on Debian 13?

When I dial out, the caller ID shows admin or unknown on the other end. I have each extension set to show the real name but regardless it shows admin. Any ideas where to look? I have stopped and started the gateways and now it shows the number but no name at all.

The issue was RPORT needed to be enabled on each handset in order to register via UDP. Rport was not necessary for TCP

I have a Yealink W80DM. I have connected 10 handsets and all register just fine with TCP. But, when I change the DM to UDP, registration fails every time. I also have many Yealink T54W desk phones on site that work fine with TCP or UDP. It is just the W80DM giving me the issue. I have...

Has anyone else had this same issue? I have checked firewalls, and nat, but all looks good. I can connect via TCP but not UDP but only with the dect manager. All the yealink T54 desk phones connect via UDP with no issue. One might ask why I want to move the dect manager handsets off of TCP...

I thought the same thing you did Mark However, when I installed it on a Hetzner server, I had to add libtools whereas when I installed on any other server, I did not. Still don’t know why that is because I know your installation script includes it. However, the workaround to use Hetzner servers...

I am using the latest master from fusion PBX. I have a client that has 17 YeaLink T 54W and they connect via UDP no issue. The YeaLink W 60 B will only connect with the hands sets on TCP but not UDP. Registration fails on UDP but not TCP. I would like to keep everything on UDP. I have disabled...

I found the issue: libtools was not installed. So what I did was spun up a new Debian 12 server from Hetzner, then did updates, then installed libtools, then rebooted, then installed Fusionpbx. Now all works as expected.

I have a failed socket connection error. When I spin up a Hetzner server, I have event socket errors, but when I use my vultr server I do not get these errors. This is on a brand new install of 5.3 fusionpbx on a dedicated VPS with Hetzner. I get socket connection failed errors. Debian 12 On...

Hello, I was looking for a way to integrate BulkVS with FusionPBX SMS but it seems this option isn't available yet so I'm looking to understand how the SMS app works and how I would be able to integrate a new carrier to the SMS app. It seems that the hook is easy enough to create since it's...

Solved - Not sure how but the permissions were off in the user settings

I went to add a new device today and the MAC address field has dissappeared Any ideas how to get it back?

I have made a few adjustments and it is automatically erasing all call recordings older than 48 hours. Any insight on this would be greatly appreciated.

My call recordings auto delete after 2 days. In the cron job I have it set for 90 days. This started when I moved to a different server I am now using servers at slicie.com Any ideas on why the call recordings delete after 2 days despite the fact that I have it set at 90 days in the...

Yes, simply record a greeting, direct calls to that greeting instead of a voice mail

Seems like whenever I post an issue I find the cause almost instantly. In the USERS set up the language had inadvertenly been changed to ARABIC. My mistake - issue resolved