SipX RL9 Update!

[Ivar Plahte]

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

[Mike Picher]

Exciting stuff!

 

Michael Picher Product Manager E: mpi...@skyswitch.com SkySwitch Platform Support: 747-777-8100 CoreDial Platform Support:    215-297-4400 NOTE: This e-mail and any attachments are from BCM One, Inc. and are intended solely for the use and review of the individual(s) to whom it is addressed. If you believe you received this e-mail in error, please notify the sender immediately, delete the e-mail (and any attachments) from your computer and do not copy or disclose it to anyone else.

 

From: sipxco...@googlegroups.com <sipxco...@googlegroups.com> on behalf of Ivar Plahte <ivar....@onrelay.net>
Date: Thursday, March 27, 2025 at 10:59 AM
To: sipxcom-users <sipxco...@googlegroups.com>
Subject: [sipxcom-users] SipX RL9 Update!

CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/f1e7a3ae-f977-49bd-9e91-fcb10e330510n%40googlegroups.com.

[Ivar Plahte]

Just a quick update as we decided to upgrade from java 8 to java 17 for RL9, which moved us from one jar dependency hell to another. But at least the java 17 one takes us in the right direction and makes sure we get rid of outdated library dependencies that can be more vulnerable to attacks, resource leaks, performance issues etc. 

The work has involved porting most of the servlets and networking handlers to the new jakarta.servlet namespace, ensuring latest TLS / SSL is enforced, upgrading all apache and jetty dependencies. We have also upgraded the database driver modules for both PostgresSQL / JDBC and MongoDB, same as we have done for C++.

Will keep this group posted when ready for testing. It is our top priority to get this release out of the way now, and we are on full steam ahead.

[Roy Reynolds]

Awesome

To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/9750bf3f-83f7-448a-8bd8-5aac3afa601en%40googlegroups.com.

[Matt Keys]

Cool stuff! The building documentation still specifies centos7 in several areas - https://onrelay.github.io/sipxecs/building.html

Any plans to build an official sipx rl9 iso image?

Regards,

Matt

[Support]

We are working on it and will update the build documentation alongside a corresponding update ready for RL9 testing.

At the moment we are still working through the final Java 17 dependencies including spring, mongo, jdbc, servlet, jakarta etc upgrades.

Note, for anybody using the old SOAP API please beware it will be decommissioned for RL9, and start thinking about moving things over to the Rest API if it is in use. The axis libraries are just too old to maintain now.

So hopefully won’t be too long now, and we will keep this group posted.

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/dac798ed-916e-46bf-80ea-ea1ec8e8431bn%40googlegroups.com.

[Matt Keys]

I guess I'm too early to test with rpms then? I was tinkering around this morning and assumed I just grab https://storage.googleapis.com/sipxecs/sipxcom/25.01/rocky-9-x86_64/sipxcom.repo and roll from there?  I'm getting 404s when I test the baseurl path.

Regards,

Matt

[Support]

The RL9 repos are setup and in use with our build work in progress, but are not ready for any meaningful use for others as of now. Will let you know when ready.

To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/ff0a1c95-6943-45e1-9bd1-f9aeef940b63n%40googlegroups.com.

[Carlos E Olivencia Vazquez]

Hi! Any update?

On Thursday, March 27, 2025 at 10:59:35 AM UTC-4 Ivar Plahte wrote:

[Ivar Plahte]

We are still pushing hard for the RL9 release, you can track commits at https://github.com/onrelay/sipxecs.

As mentioned in other threads, following the below post we unfortunately found that we had to untangle a long sequence of java dependencies per hard requirements to upgrade to e.g. the jakarta namespace, jdk 17+, jetty 12, spring 6, hibernate 7 etc etc etc with associated refactoring. 

I frankly have no idea why many who govern these platforms seem oblivious to maintaining a resemblance of developer contract stability. The amount of forced refactoring of working code just to stay on top of these java platforms is staggering and seem way too engineering driven. 

Anyhow, all that java work completed a few weeks back, and we fortunately live in a time now where AI is a fantastic tool for all that. There have also been quite a few necessary build / configure / deploy script adjustments as well, and we are now expecting sipxecs-setup to get us to a running web config UI any time now, which we will share here.

Following that, we will test and stage everything, and when deemed ready take a RL9 server to production with some friendly customers here.

There have been no changes to any DB tables, so we hope and expect restores from 24.01 on CentOS7 to be reliable when we finally release.

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/8cda70ab-56ab-473e-8742-73e876e640fan%40googlegroups.com.

[Carlos E Olivencia Vazquez]

Looking forward to whats going to happen in the future. We are currently running v 21.04 with more than 2300 phones and more than 2600 users. Its been stable but we are looking whats out in the market locally to move, if this doesn't materialize. Keep the good work!

[Jean-Francois Aubin]

Hi,

Where is the code for the docker build with RL9?  

On Thursday, March 27, 2025 at 10:59:35 AM UTC-4 Ivar Plahte wrote:

[Ivar Plahte]

The RL9 repository is at https://github.com/onrelay/sipxecs at the main branch release-25.01-rocky9, see Environment and Building instructions, Installation is still not available as we have not yet issued a build for external testing. Please feel free to build it, but until we publish a pre-release there is no need to report any issues our way, as we will be past them already.

As for Docker, we had a mishap on CentOS7 where a Docker build corrupted some parameters. So would recommend RPM building on a real server or cloud image until we have checked that for RL9.

Present RL9 state is sipxecs-setup completes, databases are initialized OK, superadmin is added, which means a lot of the core pieces are in place. We are just now working through some spring security infrastructure changes to actually complete the superadmin login.

We don't expect too much grief once the config module is fully functional, since nearly all java dependency and web framework related changes have been in that module. If you take a look at the history of sipXcommons/.classpath you will see why this has taken longer than expected.