Search results

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...

Select different ring groups as destinations for each number?

https://www.fspbx.com/docs/configuration/messaging/overview/ https://www.fspbx.com/docs/configuration/voicemail-settings/sms-notifications/

To avoid issues, make sure the email provider you use in your .env file matches the one set in Default Settings. Right now, the email provider in Default Settings is only used for outbound fax email notifications, but that requirement will be removed soon. Mailgun is currently used mainly for...

That's correct. This way, you can adjust where the voicemails and faxes come from. Some people like to specify those.

That's why LUA is better, it does everything within one script and has more flexibility with what you can do.

I'm glad to hear you are knocking these issues out.

If you see the email being sent, even better. That means FS PBX is working as expected. Yes, it uses settings in the .env file. Same as for password resets. Next stop is your email host.