Search results

On the second server, you need to go to Advanced -> Variables. Open any of the existing variables and hit save. It will help write all FreeSwitch variables into the local XML file. Then go to Status -> SIP Status and flush the cache and reload XML. Then restart the FreeSwitch service. You should...

In your screenshot, I see that you have not assigned any lines to this device. You need to have at least one. And yes, you absolutely need to point the phone to the provisioning URL: https://yourdomain.com/app/provision In the default settings, you also need to set the provisioning username...

Mark doesn't own this forum. Otherwise, he wouldn't. Totally understand the “stick with what you know” approach. For what it’s worth, FS PBX isn’t meant to be a dig at FusionPBX — it came out of real operational needs on our side. Years ago we were hitting limitations and spending too much...

check this thread. There is a very specific order in which you need to do things otherwose it doesn't seem to work. https://www.pbxforums.com/threads/need-to-remove-privacy-header.8000/page-2#post-32420

I've been there many times. Once, I was down for a month after updates. Lost two large clients. Then I decided to fork the project, fixed all bugs, and improved it. Ever since then, we have had zero issues. We open-sourced it too - FS PBX (www.fspbx.com)

To have to lines show on the phone you will need to add them to your profile. Here is an example, but adjust it to your needs. My example will put 5 buttons (Line 1) and a few BLF buttons.

Thanks for confirming. I'll add this to the documentation

In my experience setting up the DSip router, there were so many issues that many gave up. When calls are working, problems start happening with music on hold, parking, BLFs, etc. I'd like to know if anyone out there has actually gotten it working all the way and is using it in production?

Screenshots of your Device settings with two keys, please, and a screenshot of your Profile for this device showing how you assigned these keys.

After setting that variable, go to SIP Status, flush the cache, reload the XML, and then restart FreeSWITCH. You should then see port 5061 TLS running under SIP Status.

The fix you found for mixed context when proxies are involved is good. If you make any changes to the files you modified, you may need to stash them and reaply. Those files are not likely to be modified very often, if at all. Signalwire token is no longer required. We found a workaround for...

Can you double-check that internal_ssl_enabled setting is on? got to Advanced -> Variables

Try again. I submitted a fix.

Give me a few minutes to investigate. I need a fresh box. Meanwhile if you have Debian 13 box you can try there. It installs Sofia differently.

Oh maybe it is related then I didn’t see it get stuck on Sofia before.

Give me a few minutes. I’ll spin up a Debian 12 box to check what happened to Sofia module. This is unrelated to this error but you will need 4 GB of RAM to finish the install. It’s mentioned In the system specs.

Thank you for your feedback @junction1153

My experience was that phones kept registering on different servers. I don't discount the possibility of a misconfiguration on my end. But it did seems ore of a load abalancing than failover

Why not register your ipecx UCP100 as an extension on the system? Then it can easily dial any internal extensions in FS PBX. Context public is only for external calls; an ACL adjustment is required to allow traffic. By default, everything is not allowed. This, however, is a very intricate...

Hello everyone, If you’re tired of restarting Polycom phones every January 1st to restore BLF, I may have a fix. I’m looking for a few beta testers who can validate it on live systems (or test environments) to confirm: BLF continues working after the system clock rolls over into the new year...