Search results

did you run this command after making changes to the .env file? php artisan config:cache

Try enabling Keep Alive on your device and reduce registration timeout to a shorter number. You issue sounds like firewall closes the connection too early.

I got it to compile. FS PBX now supports Debian 13. It wasn't easy. Many packages behave differently. Additionally, Freeswitch required some updates. Sofia cannot be installed from source at this moment. Freeswitch support recommends installing it from packages.

@voipBull You are correct. I took care of that.

One thing you can do that will have a big impact immediately is to change your SIP ports to more obscure numbers. This makes it harder for SIP scanners to access you. You can also block unwanted traffic using tools like SBC, SIP proxy, or Fail2Ban.

We’re happy to announce that the latest version of FS PBX officially supports Debian 13 (Trixie)! This release ensures smooth installation and operation on the newest Debian release, while maintaining full backward compatibility with Debian 12 (Bookworm). Highlights Debian 13 (Trixie) Support...

Most likely a codec incompatibility. Or something else. Check your FS CLI. The error will be obvious.

It looks like it, but that timeline is not always accurate, as I found. I had to rebuild mine from scratch to make it more useful. Now I can tell a lot more of a story from looking at it. If you ever consider FS PBX, this is what yours will look like. It's very clear that Jennifer picked up the...

I don't see 32 minutes, but I do see someone being parked for 14 minutes. I bet 14 minutes felt like 32 to them.

Yes, there is a FusionPBX script for this that can work in FS PBX.

You need this in your config file. features.pickup.direct_pickup_enable = 1 features.pickup.direct_pickup_code = ** It should work

That is strange. This is added to each tenant. Maybe you deleted it for this particular tenant? I checked a couple of servers, and they all have it. In any case, you can add it based on the screenshot.

Last time I checked, PHP 8.2 was not officially supported. This may cause some of the issues you are having. PHP 8.1 was the recommended version.

Use small letters in the search. It should find it. I'll update the instructions

Here are the instructions on how to set up DISA for FS PBX: https://www.fspbx.com/docs/additional-information/disa-setup/

You may need to explain to Freeswitch that it is behind NAT. Add these variables. Flush the cache and restart FreeSwitch. Adjust your SIP profile accordingly.

I got it working on my system, but had to push a small fix to make the process user-friendly. SO make sure you have the latest commit. Stand by while I'm writing the article with instructions. I'll be back shortly

Let me take a look at this and get back to you. I want to make sure it's 100% functional.

FusionPBX and FS PBX are exactly the same when it comes to SIP profiles. As a matter of fact, SIP profiles are a Freeswitch thing and have nothing to do with either FS PBX or FusionPBX. By default, your external profile uses port 5080 unless you change it. Adrian is correct in pointing out that...

This is a public forum. Don't post your credentials here. Remote sessions are reserved for customers subscribed to a support plan. I'm happy to do best effort support on the forum for free, but you need to provide the required logs.