Search results

It was turned on by accident in the previous update and rolled back in the latest update. So it won’t be on by default for new installs. However, I highly recommend turning it on as soon as the email feature is configured. It will protect your PBX from an unauthorized access.

if you didn’t run into any issues you are good to go. Some people that had enabled prior might need may need to git stash. Here’s the official tutorial how to enable it for all new installs. It won’t be on by default. https://www.fspbx.com/docs/configuration/enable-2fa/

Fixed in the latest commit

Are you sending calls to port 5080?

Create a new dialplan like this (order 100). In my example, it's for area code 909. Regex could be better, but this one would work just fine.

You don't need all the files to provision the phone. mac.cfg is enough. It fails to download the other files, and it's ok. It's true for all phones. They always look for a bunch of files and only download what's available and needed.

FS PBX relays inbound messages to Ringotel via API integration. If a mobile app exists, we prioritize delivering messages there. To send outbound messages, change the SMS settings in the Ringotel connection from "Integrations" to "API." Integrations enable direct message sending and receiving...

Try to switch to T44U (v1.0.x). When you have a version at the end these are new FS PBX templates. The provisioning URL will be different when you use the new templates. https://pbx.mydomain.com/prov/ccb8a81b8090.cfg once you switch to this template try to open that URL in the browser.

T58v. I see. You wrote t85v in the subject. I’ll check on my test server and let you know. To be honest you can probably use any Yealink template. They are very much similar. For example try t44+. That one works very well.

Can you send a screenshot of which exact template you used? P.s. that domain you are not sure about needs to be changed to yours. Or whatever works with your proxy. But this doesn’t affect you right now. The issue is somewhere else.

What may be causing the confusion is the use of the labels Server A and Server B. Those labels are not important by themselves. What matters is the order in which the steps are performed. To make this clearer, it is better to think in terms of the actual server locations, such as Miami and New...

Which server are you getting this error on? In what order did you run the migration commands?

Yes you always need to add all IPs if your gateways to the ACL list.

Run these git stash git pull php artisan app:update Then make sure you run the migration commands in the correct order as per our official instructions. You don’t need to stop Syncthing before updates.

You should check out FS PBX (www.fspbx.com) when you have a moment. Fewer bugs and a much better front end for management.

Then you are not running FS PBX, and you are probably running FusionPBX. This thread is for FS PBX users

you can run sngrep to grab it

It's showing active calls for the tenant you are currently signed in to. You can click on the Show Global button to see all. Check the logs for any errors https://www.fspbx.com/docs/troubleshooting/retrieving-logs/

something is always shown. Do you have a PCAP log you can share?

Have you tried pressing the circle arrow button to keep the page updating?