Upgrading to 24.01 from propritary Ezuce version
104 views
Skip to first unread message
Jacob Hess - Information Technology
Jan 21, 2025, 5:16:41 PMJan 21
to sipxcom-users
What would my organization give up from moving from the Ezuce version and moving to the OnRelay version of sipXcom?
I'm hoping that there might be some people here who have made this move and could give some information on how it went for your organization.
I'm hoping that there might be some people here who have made this move and could give some information on how it went for your organization.
Nathaniel Watkins
Jan 21, 2025, 6:53:52 PMJan 21
to Jacob Hess - Information Technology, sipxcom-users
I’m looking at doing this as well.
On Tue, Jan 21, 2025 at 5:16 PM 'Jacob Hess - Information Technology' via sipxcom-users <sipxco...@googlegroups.com> wrote:
What would my organization give up from moving from the Ezuce version and moving to the OnRelay version of sipXcom?
I'm hoping that there might be some people here who have made this move and could give some information on how it went for your organization.
--
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/67d7ae45-4a90-442a-8081-f44d52b71825n%40googlegroups.com.
mkitchi...@gmail.com
Jun 20, 2025, 9:27:19 AMJun 20
to sipxcom-users
I'm looking at the same. I have a very outdated on prem Ezuce openUC cluster that I am considering moving to an Azure based sipXcom instance.
One of the main features we used to use was the Reach Call Center app. We use Twilio cloud for that now. I'm fine with losing that.
It is a 3 node cluster for now. I found some pointers to old wiki articles that seem to say clustering is supported in sipXcom.
One of the main features we used to use was the Reach Call Center app. We use Twilio cloud for that now. I'm fine with losing that.
It is a 3 node cluster for now. I found some pointers to old wiki articles that seem to say clustering is supported in sipXcom.
I don't remember what all the differences were between the free and paid versions. There was something about presence, bla, shared line
or something like that that only came with paid. That and Reach were the only things I can remember. We also have a very dated Sangoma
or something like that that only came with paid. That and Reach were the only things I can remember. We also have a very dated Sangoma
SBC that I need to work with. It has been rock solid, so I will likely go with a newer version of that if it is still a good solution.
glasses685
Jun 20, 2025, 8:32:33 PMJun 20
to sipxcom-users
Same here - I'm also running an older Ezuce OpenUC cluster (along with a Sangoma SBC) and trying to figure out the best way forward. We also used to use Reach but switched over to Zoom phones a few years ago for call center stuff so no need for that any more, although we do use shared lines and BLA so losing that would be a downer. Interested in what anyone's experience has been - I'm pretty reluctant about switching over to something completely cloud based so sipXcom might be something to think about.
Nathaniel Watkins
Jun 20, 2025, 9:20:01 PMJun 20
to glasses685, sipxcom-users
Same boat - EZuce plus a sangoma SBC. I’ve signed up with onrelay for support (I officially start with them in July).
We switched from a 3 node cluster down to a single VM several years ago. For our number of users, the cluster was more of a hassle than it was worth (roughly 700 users).
To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/29fd3a6d-f5b9-4928-955e-0e33f45755fbn%40googlegroups.com.
Ivar Plahte
Jun 21, 2025, 4:16:24 AMJun 21
to Nathaniel Watkins, glasses685, sipxcom-users
BLA is included in standard sipXcom, we have several customers using it.
We have also done quite a lot of work on the built in SBC, most notably adding support for TLS and SRTP such that it is possible to use secure signaling and media for all endpoints and trunks, which we also do in production.
Our architecture at OnRelay is we use an unmodified version of the standard open source sipXcom in production and install our proprietary mobility server and admin modules etc on top of it on the same instance.
As for moving things over from Ezuce, we are working with Nathaniel to use one of two approaches:
1) Install sipXcom on top of a CentOS7 server built from an Ezuce disk image
2) Install sipXom on a fresh CentOS7 image and do a config backup from Ezuce / restore to sipXcom
We recommend checking both of those on a staging server before choosing an option.
Subsequently you can then follow the documented and tested sipXcom CentOS7 to Rocky Linux 9 upgrade when the latter is ready. It is coming along nicely.
Ivar
To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/CAJEQSSamGTa5fV4eyt9igLVTEodUirubsxL0uEoEo61NzFVSZQ%40mail.gmail.com.
Roy Reynolds
Jun 21, 2025, 9:14:25 AMJun 21
to Ivar Plahte, Nathaniel Watkins, glasses685, sipxcom-users
Thank you so much Ivar. I have not done any of the releases being 24 but you guys rock!
Much Appreciated.
To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/F7AFFA94-A5EA-4FE9-8C5B-E51D5DA82E9F%40onrelay.net.
Matthew Kitchin (Public/Usenet)
Jun 21, 2025, 11:03:22 AMJun 21
to sipxco...@googlegroups.com, ivar....@onrelay.net
Sounds like a bunch of us are in the same boat. I'm on a 3 node Uniteme 20.04.20200422050452 cluster with an equally outdated Sangoma VM based SBC. We would possibly interested in a support agreement of some sort and migrating to maybe a single node in Azure. The Sangoma has been a rock. Not one single issue and great support when we initially needed it. I'm a longtime (back to Pingtel days) user of the various predecessors of sipXcom. We had a lot of trouble initially with some flaws/bugs in this setup, but it has been relatively stable. Do you consider the internal SBC to be on par with a Sangoma VM? Older versions of sipXcom/Uniteme had a variety of issues when put under specific types of heavy load and things could go very poorly. Our setup is pretty vanilla these days. Not using too many features. All Polycom VVX handsets plus a couple conference room phones.
Message has been deleted
Ivar Plahte
Jun 22, 2025, 10:35:47 AMJun 22
to sipxcom-users
Hi Matt (thanks Roy!)
We run single instance cloud images on GCP ourselves, and our assessment is that scaling or performance issues are better solved throwing CPU and RAM at the problem than adding deployment complexity with clustering etc that was more necessary when HW resources were more restricted. So we have designed out our hardware redundancy instead relying on native cloud mechanisms. It factors that cloud images have excellent self recovery and monitoring mechanisms, as well as super fast direct fiber connections to any location.
As for IP phones, even if our service offering is predominantly mobile extensions many of our customers use a few IP phones in their setups, for receptionists, office managers and the likes. And we recommend and test everything IP phone related on Polycom VVX here.
We have done a lot of work on the built in SBC over the years, which we used to fork, but we resubmitted all that work back to the regular open source domain in our sipXcom 24.01 release last year. We don't know the Sangoma, but the internal SBC is stable, and it is also a great benefit for us we 100% control it when needing to adapt to some new SIP trunk interface. We have probably done something like 20-30 of them, including Twilio, Flowroute, Bandwidth.com, and others. You just have to factor in your setup and dimensioning that the media relay mechanism is activated for trunk calls. You may also want to check out the closed issues list on https://github.com/onrelay/sipxecs/issues?q=is%3Aissue%20state%3Aclosed, there were a few really important fixes there since the last 21.04 sipXcom release by Ezuce on which I expect Unitme is based.
As for moving from Uniteme it is difficult for us to know exactly what it entails, since we have never seen or used it. As for standard support, we include in our SLAs anything running live on our sipXcom v24.01 for CentOS7 and the upcoming 25.01 release for Rocky Linux 9 onwards. But I am still open to discuss some sort of service package for moving things over from Uniteme to a supported platform. We have e.g. suggested to Nathaniel we spend a bit of time here testing the abovementioned two mechanisms for moving things over using their real config/disk image data, we assess any issues on a GCP test server, and if all looks OK then agree a port date where we are standby for any urgent problems.
PS. I had the pleasure of meeting some of the original members of the PingTel dev team, Dan Petrie and Thomas Howe, at a VCON event in Cap Cod a few weeks ago :) Across the whole IP comms space there is a renewed optimism from the simple fact that AI and voice molds really well, so there are lots of new opportunities, integration options and new feature use cases.
We run single instance cloud images on GCP ourselves, and our assessment is that scaling or performance issues are better solved throwing CPU and RAM at the problem than adding deployment complexity with clustering etc that was more necessary when HW resources were more restricted. So we have designed out our hardware redundancy instead relying on native cloud mechanisms. It factors that cloud images have excellent self recovery and monitoring mechanisms, as well as super fast direct fiber connections to any location.
As for IP phones, even if our service offering is predominantly mobile extensions many of our customers use a few IP phones in their setups, for receptionists, office managers and the likes. And we recommend and test everything IP phone related on Polycom VVX here.
We have done a lot of work on the built in SBC over the years, which we used to fork, but we resubmitted all that work back to the regular open source domain in our sipXcom 24.01 release last year. We don't know the Sangoma, but the internal SBC is stable, and it is also a great benefit for us we 100% control it when needing to adapt to some new SIP trunk interface. We have probably done something like 20-30 of them, including Twilio, Flowroute, Bandwidth.com, and others. You just have to factor in your setup and dimensioning that the media relay mechanism is activated for trunk calls. You may also want to check out the closed issues list on https://github.com/onrelay/sipxecs/issues?q=is%3Aissue%20state%3Aclosed, there were a few really important fixes there since the last 21.04 sipXcom release by Ezuce on which I expect Unitme is based.
As for moving from Uniteme it is difficult for us to know exactly what it entails, since we have never seen or used it. As for standard support, we include in our SLAs anything running live on our sipXcom v24.01 for CentOS7 and the upcoming 25.01 release for Rocky Linux 9 onwards. But I am still open to discuss some sort of service package for moving things over from Uniteme to a supported platform. We have e.g. suggested to Nathaniel we spend a bit of time here testing the abovementioned two mechanisms for moving things over using their real config/disk image data, we assess any issues on a GCP test server, and if all looks OK then agree a port date where we are standby for any urgent problems.
PS. I had the pleasure of meeting some of the original members of the PingTel dev team, Dan Petrie and Thomas Howe, at a VCON event in Cap Cod a few weeks ago :) Across the whole IP comms space there is a renewed optimism from the simple fact that AI and voice molds really well, so there are lots of new opportunities, integration options and new feature use cases.
Michael Picher
Jun 23, 2025, 8:36:57 AMJun 23
to Ivar Plahte, sipxcom-users
FYI, be aware that the sipXcom BLF/BLA are not stable over ~1000 users. The proprietary service that is in UniteMe is good out to about 15,000 iirc.
Thanks,
Mike
On Sun, Jun 22, 2025 at 10:29 AM Ivar Plahte <ivar....@onrelay.net> wrote:
Hi Matt (thanks Roy!)
We run single instance cloud images on GCP ourselves, and our assessment is that scaling or performance issues are better solved throwing CPU and RAM at the problem than adding deployment complexity with clustering etc that was more necessary when HW resources were more restricted. So we have designed out our hardware redundancy instead relying on native cloud mechanisms. It factors that cloud images have excellent self recovery and monitoring mechanisms, as well as super fast direct fiber connections to any location.
As for IP phones, even if our service offering is predominantly mobile extensions many of our customers use a few IP phones in their setups, for receptionists, office managers and the likes. And we recommend and test everything IP phone related on Polycom VVX here.
We have done a lot of work on the built in SBC over the years, which we used to fork, but we resubmitted all that work back to the regular open source domain in our sipXcom 24.01 release last year. We don't know the Sangoma, but the internal SBC is stable, and it is also a great benefit for us we 100% control it when needing to adapt to some new SIP trunk interface. We have probably done something like 20-30 of them, including Twilio, Flowroute, Bandwidth.com, and others. You just have to factor in your setup and dimensioning that the media relay mechanism is activated for trunk calls. You may also want to check out the closed issues list on https://github.com/onrelay/sipxecs/issues?q=is%3Aissue%20state%3Aclosed, there were a few really important fixes there since the last 21.04 sipXcom release by Ezuce on which I expect Unitme is based.
As for moving from Uniteme it is difficult for us to know exactly what it entails, since we have never seen or used it. As for standard support, we include in our SLAs anything running live on our sipXcom v24.01 for CentOS7 and the upcoming 25.01 release for Rocky Linux 9 onwards. But I am still open to discuss some sort of service package for moving things over from Uniteme to a supported platform. We have e.g. suggested to Nathaniel we spend a bit of time here testing the abovementioned two mechanisms for moving things over using their real config/disk image data, we assess any issues on a GCP test server, and if all looks OK then agree a port date where we are standby for any urgent problems.
PS. I had the pleasure of meeting some of the original members of the PingTel dev team, Dan Petrie and Thomas Wolfe, at a VCON event in Cap Cod a few weeks ago :) Across the whole IP comms space there is a renewed optimism from the simple fact that AI and voice molds really well, so there are lots of new opportunities, integration options and new feature use cases.
On Saturday, June 21, 2025 at 5:03:22 PM UTC+2 Matthew Kitchin (Public/Usenet) wrote:
To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/673b61ba-42fb-4457-acbb-0ae2f7ae4db9n%40googlegroups.com.
Ivar Plahte
Jun 24, 2025, 4:37:46 PMJun 24
to sipxcom-users
Michael, do you recall the limitation or cause? Signaling architecture and / or software issue?
Note we already upgraded e.g. java from 1.7 to 1.8 and fixed a few other C++ networking / socket related stability issues as well for 24.01.
Going a long way further with that for RL9 where we are stepping up pretty much every C++ and Java library and compiler dependency to the most recent version available.
Going a long way further with that for RL9 where we are stepping up pretty much every C++ and Java library and compiler dependency to the most recent version available.
Mike Picher
Jun 24, 2025, 4:51:58 PMJun 24
to Ivar Plahte, sipxcom-users
It was really old java code and we determined that it wasn't salvageable for the kind of loads we needed to handle.
We wrote a completely new service in C++.
Sorry, I don't have more details.
Mike
Sent from the Great White North
From: sipxco...@googlegroups.com <sipxco...@googlegroups.com> on behalf of Ivar Plahte <ivar....@onrelay.net>
Sent: Tuesday, June 24, 2025 4:37:46 PM
To: sipxcom-users <sipxco...@googlegroups.com>
Subject: Re: [sipxcom-users] Upgrading to 24.01 from propritary Ezuce version
Sent: Tuesday, June 24, 2025 4:37:46 PM
To: sipxcom-users <sipxco...@googlegroups.com>
Subject: Re: [sipxcom-users] Upgrading to 24.01 from propritary Ezuce version
|
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. |
To view this discussion visit
https://groups.google.com/d/msgid/sipxcom-users/12a4523e-7bbd-4485-aa28-ec74dfbb089bn%40googlegroups.com.
Ivar Plahte
Jun 24, 2025, 5:02:12 PMJun 24
to sipxcom-users
Did you perhaps subsequently push the C++ rewrite back to open source? The sipXsaa module that handles busy line appearance is C++ now.
Mike Picher
Jun 24, 2025, 5:11:11 PMJun 24
to Ivar Plahte, sipxcom-users
Oh, maybe that was done. That would be a good thing!
Sent from the Great White North
From: sipxco...@googlegroups.com <sipxco...@googlegroups.com> on behalf of Ivar Plahte <ivar....@onrelay.net>
Sent: Tuesday, June 24, 2025 5:02:12 PM
To view this discussion visit
https://groups.google.com/d/msgid/sipxcom-users/15030dbf-557e-455c-ae21-90ffd34cfdc4n%40googlegroups.com.
Ivar Plahte
Jun 24, 2025, 5:13:03 PMJun 24
to sipxcom-users
Yes, you guys for sure did a lot of good things! :)
glasses685
Jul 14, 2025, 9:36:45 AMJul 14
to sipxcom-users
Anybody have any updates on how this is going?
We also have approx 900 users on UniteMe (mostly VVX phones) and might be interested in OnRelay (if they'd offer support) as Coredial has said they won't support the Ezuce stuff after this year.
Support
Jul 14, 2025, 9:47:08 AMJul 14
to glasses685, sipxcom-users
Hi,
We are able to offer support for that setup.
If you could please drop us a note at sup...@onrelay.net with some thoughts about the level of support you are interested in we should be able to quote it quickly including SLAs etc.
We can as part of the package then also agree on approach to get your system moved over to 24.01 for CO7 and subsequently to 25.01 on RL9 when it is ready for production. We recommend upgrading in that order since we will test the 24.01 to 25.01 upgrade thoroughly from here before releasing sipXcom for RL9.
Thank you.
To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/690751d3-a1d4-4415-a0f9-3df82b2e7b8cn%40googlegroups.com.
Donkiss Boss
Aug 21, 2025, 6:10:05 AMAug 21
to sipxcom-users
Licensed Pharmaceuticals And Psychedelics Online Store
Buy the best Pharmaceuticals And Psychedelics products in our website with safe and guaranteed shipping and delivery Worldwide
Check out our website below if interested in our products.
https://shorturl.at/BvDVf
https://shorturl.at/ITBJW
https://shorturl.at/wCGS4
https://shorturl.at/RnP0b
https://shorturl.at/GTr8Q
Buy the best Pharmaceuticals And Psychedelics products in our website with safe and guaranteed shipping and delivery Worldwide
Check out our website below if interested in our products.
https://shorturl.at/BvDVf
https://shorturl.at/ITBJW
https://shorturl.at/wCGS4
https://shorturl.at/RnP0b
https://shorturl.at/GTr8Q
Donkiss Boss
Aug 21, 2025, 6:10:41 AMAug 21
to sipxcom-users
Reply all
Reply to author
Forward
0 new messages