Search results

after updating the .env file you always need to run this cd /var/www/fspbx php artisan config:cache If this doesn't help.. Run this command tail -f /var/www/fspbx/storage/logs/laravel.log Then try to reproduce the error again. Post the last error. The log could be long. Make sure to post...

Did you set up email settings in the .env file?

No, those are definitely missing some critical variables. Most likely the install didn't finish correctly.

Do you have a device_address field in your upload spreadsheet? It says it's missing. You can download the template and see all the fields that are supported and their names.

I'm all about TLS. It's the way to go. But some devices don't like it, and it causes issues. I have probably 99% of all devices on TLS, though.

The issue with that is if you have a device that doesn't support TLS or SRTP, it will fail. I had an issue with an older paging system that only connected with UDP, and also some test softphones I used.

I would love to hear some opinions on this too. I've done a lot of work with TLS but SRTP has been hit or miss between different manufacturers to the point that i just had to disable it sometimes

@pbxer I pushed a fix for this. Please try again. Thank you for reporting this.

I'm pretty sure the name of the file should be greeting_1.wav. msgxxxx.wav is reserved for voicemail messages

FusionPBX provisioning server uses variables set up in the system to replace them with values. Such as SIP credentials and server info. If you run it on a separate server, it won't know the values. You may need to explore phone manufacturer provisioning portals. Each manufacturer has their own...

@markjcrane, I appreciate the work you’ve done to introduce caching in FusionPBX, which significantly optimizes the system by avoiding expensive XML regeneration directly from the database. This approach has undoubtedly made the system more efficient. However, I noticed that the current...

I was a bit surprised by the suggestion to modify the database directly, as this approach doesn’t take into account the additional steps required for the system to function as expected. Updating the database alone won’t reflect changes in the XML files used by FreeSWITCH, nor will it update the...

The screenshot demonstrates that you are still on the old version. Go to the dashboard and look at the bottom popup; it shows your current version. How did you update? The correct procedure is cd /var/www/fspbx git pull php artisan app:update Then check your version again. It should say...

Show me a new screenshot, please

I dial with the star to toggle

@Raven Download the latest updates. This issue has been resolved.

Hey everyone, We’re excited to share a new feature for FS PBX: SMS notifications for new voicemails! What’s New: FS PBX can now automatically send SMS notifications to users when they receive a new voicemail. You can set domain-specific message templates and choose your sender ID. Currently...

I checked one of mine, and it shows without a star, but it works. I checked the XML file, and it's written in there. You should be good.

@ou812 update to the latest version (0.9.59 or later). It should work. The issue was with Canadian numbers.

What is your use case for this? This means that every single call going to this extension or agent will have the prefix. Normally, you set up prefixes on a queue level, and then an agent gets to know which queue the call came from. For example, Sales queue or Support queue.