Happy to share we have now pushed a code complete docker RPM build for sipX on Rocky Linux 9 to GitHub.
We are now continuing our 25.01 release work on to a real target where we will be installing/debugging/testing on GCP's standard Rocky Linux 9 version. We will also use RL9 on GCP in production.
As before, we have taken a conservative approach where our aim is to remove technical debt and refactor dated dependencies with minimal risk and changes. We are only using supported RL9 libraries available from standard repos. We are also abandoning the previous approach to store a versioned copy of 3rd party RPMs in our own repos, unless we have had to manually download them and / or build them from source ourselves.
Some of the most heavy lifting has been to:
- Recompile & update all C++ code for g++ v11 / C++17
- Update and refactor all Mongo DB C++ dependent modules for the latest mongo-cxx-driver v4.0, which we have built from source.
- Ugrade mongodb to v8.
- Update and refactor all dart code to use the most recent dart-sdk v3.7 as included in the latest Flutter SDK, which we have also built from source.
- Import oss_core into sipX, which has been forked from the now stale latest master branch of the joegen oss_core repository. We have scaled back and refactored oss_core compile dependencies to only include features used by sipX.
- Update freeswitch to the recent v1.10.12
- Update openfire to the recent v4.9.2
- Update cfengine to 3.24
- Update openssl to v3.
- As of now we are sticking with Java 8 as we have some legacy dependencies towards our proprietary mobility servers. We have updated jar library dependencies as required by Rocky Linux 9.
Also, I am also happy to share that Cisco Systems is now officially a reseller of OnRelay's Mobile PBX service, where sipX is an integral component. See their recent announcements at
https://blogs.cisco.com/news/transforming-mobile-networks-delivering-on-programmable-platform-promise and their corresponding mobile service provider app store at
https://apps.mobility.cisco.com.
We are prominently featured there since we have been spearheading their cell carrier voice integration the last two years.
We have in partnership with Cisco achieved a level of mobile integration previously
unavailable to us. In simple terms a sipX DID and a business cell number becomes
one and the same. This means you can e.g. roll out a sipX user extension
as an eSIM, replace IP phones with smartphones and / or port public DID
ranges to business cell contracts.
Our success is your insurance for the longevity of sipX, so please don't hesitate to get in touch if you think you can help our business along, are interested in discussing a sipX support contract, and / or if you see opportunities with our cell network integration as achieved via Cisco APIs.
We will of course keep this group posted about our testing progress, and as soon as we get this 25.01 release out of the way I will also revert with our roadmap of any new sipX features for subsequent RL9 releases. We are not planning to do any more work on CentOS7.
Ivar