Freeswitch 1.11.3
- Thread starter Voipy
- Start date
We have started our testing environment. It's not ready yet for release
On FusionPBX upgrading FreeSWITCH was a royal pain. The upgrade would abort on the configure first because spandsp was not the correct version and then because sofia was not the correct version. I would have expected the upgrade script for FreeSwitch to handle bringing the dependencies up to correct version. I was at spandsp 3.0.0 and sofia 1.13.17. The upgrade requires spandsp 3.1.1 and sofia 1.13.18. Hopefully @pbxgeek is watching for this sort of thing as he tests.
@kenn10, we discovered that almost immediately. Even before we merged the updates into our fork. This is one of the things we are testing to make sure the update goes smoothly. We always read the docs carefully, along with the code itself, to understand what is new and what's required.
Kudos Awesome to hear that @kenn10. Thank you for giving it a try.
Don't forget we use our own fork of FreeSWITCH, and it includes bug fixes we've discovered over the years. We've had many conversations with FreeSWITCH support about adding those to their main repo and have submitted PRs, but they've been left completely unattended. They acknowledge receipt and promise to look into it, but it never happens.
Just recently, we fixed a memory bug with Music on hold that doesn't free up properly. And this fix is part of this update you just installed. It may not affect a server with 100 concurrent calls. But it starts making a huge difference for someone with 500 concurrent calls. Our tests showed 50% less RAM usage during automated simulation.
Don't forget we use our own fork of FreeSWITCH, and it includes bug fixes we've discovered over the years. We've had many conversations with FreeSWITCH support about adding those to their main repo and have submitted PRs, but they've been left completely unattended. They acknowledge receipt and promise to look into it, but it never happens.
Just recently, we fixed a memory bug with Music on hold that doesn't free up properly. And this fix is part of this update you just installed. It may not affect a server with 100 concurrent calls. But it starts making a huge difference for someone with 500 concurrent calls. Our tests showed 50% less RAM usage during automated simulation.
Upgraded FS PBX to 2.0.1 then FREESWITCH to 1.11.3. Both upgrades went ok.
Could not make or receive calls. Gateway not enabled and extensions down.
Sofia Status Profiles all were stopped, Started all profiles.
Call processing resumed on my small test system.
Thanks to all that made a smooth upgrade!
Could not make or receive calls. Gateway not enabled and extensions down.
Sofia Status Profiles all were stopped, Started all profiles.
Call processing resumed on my small test system.
Thanks to all that made a smooth upgrade!
Last edited:
Interesting. When I did the FreeSwitch upgrade on my FusionPBX test system, I had to restart Sofia. I did not have to do that on the FS PBX upgrade and my SIP profiles came up on their own.
You did restart FreeSWITCH after the update, right? Does this happen every time you restart FreeSWITCH? Or was it a one-off issue after the upgrade?
Rebooted again, FS PBX and FREESWITCH up and running. Gateway up. My two extensions took a while to be registered.