Search results

There is something going on with parsing your data coming from Freeswitch. production.DEBUG: array_combine(): Argument #1 ($keys) and argument #2 ($values) must have the same number of elements This will require a remote session to figure it out.

@jeroentjed Check the logs to see if there are any errors when you open the registration page. Go to Status->Logs->Laravel.

The scheduled announcements service must be enabled before you can use it. Refer to the wiki page for instructions. https://www.fspbx.com/docs/configuration/scheduled-announcements/ Something is not healthy on your system. Registrations should work. I just checked the server with the latest...

Please update to the latest commit as of today and run the command below to move SQLite back to RAM storage. Disclaimer: If you have customized your setup to use PostgreSQL instead of SQLite, you can disregard this notice. After the upgrade, SQLite was moved to file storage, which is not ideal...

What’s your FS PBX version and Freeswitch version? When did the issue start? Do you see registrations when you go to Status -> Registrations?

What’s your FS Pbx version and freeswitch version? Do you have redundant servers? Are the phones registered to your backup server by any chance?

That means the update didn't apply. This comes up a lot. Here is a solution: https://github.com/nemerald-voip/fspbx/issues/489

Hi @kenn10, you can use Dialplan Manager or a Lua script.

This is planned for future releases. For now, you can select and copy text.

What you described is exactly how it's designed to work. If you're running into issues, there is a chance your system is blocking something. It's hard to tell what it is without live troubleshooting.

Each node must be individually accessible for verification. If you added these 3 nodes to your Let's Encrypt list of domains: pbx.domain.com pbxa.domain.com pbxb.domain.com Let's Encrypt will try to verify all 3. If one of them fails, the whole verification fails. This is how Let's...

Since this is no longer an FS PBX concern and was more of your proxmox setup and geoip blocking I will not be making any changes to the codebase. The way you have it right now is better long term. You should document your steps so you don’t have this issue again when you roll out a new box.

@Voipy how was your m4a generated? This meant to work with files generated on iPhone recordings app. It was added because users often made recordings that way and shared with us.

The real startup error is here: status=214/SETSCHEDULER That means systemd is trying to start FreeSWITCH with a CPU scheduling policy that the environment does not allow. This is happening on Debian 13 LXC containers, and the journal shows FreeSWITCH failing before it actually starts: an...

run the as is says to retrieve the real error journalctl -xeu freeswitch.service

Are you able to install the Freeswitch certificate? The directory is the same. I understand your problem, but it’s unusual. If you can read one file from that directory, you should be able to read others as well. At this point, it’s challenging to determine the issue without examining your...

We are not only updating the pages now but also actively removing the old ones completely. They still exist in the background but no longer used. I just wanted to make sure you don’t get left hanging with the non existing page when time comes. There might be other users out there that use...

Now just make sure you can hit the reload XML button on the Variables page. If you rebooted the server it should work. Php should hopefully have the right permissions after the reboot. Otherwise you may experience issues in the future. This is a large Freeswitch upgrade. All these small things...

We made that page for you. But it’s not in fspbx menu by default. Feel free to change the menu link yourself to /pin-numbers

Yes, those steps are important. You might need to reboot the server. it could be due to PHP not having access to those directories. Recent php versions have stricter access limitations.