Update 12 is out with just another fix attempt for this issue. As mentioned above we hope a missing

We just checked SIPX_PROXY_CALL_STATE_DB_HOST is not added or modified anywhere from CF engine

We have just published update 10 with the below updates: -- Database view 500 error (https://github.

Thanks for raising the issue and adding all the work around info. We believe using the --clean flag

See comments below: 1. Is 25.01 as stable as (or more stable than!) 21.04 was? OR: 24.01 is

We have bottomed out and fixed this issue. It was a combination of a python bug in the mongodb-admin

Albeit we normally use TLS we don't see any problems registering over TCP here either. Could it

We have published update 8 on 25.01 with the following fixes: - Empty SBC registration status list:

The TFTP service not starting error is due to xinetd being replaced by tftp.socket in Rocky Linux 9.

Thanks, we are able to reproduce this issue for a custom dial plan with '4' + 4 digits,

We have published an update 7 on 25.01 with several important stability fixes. Please note update 6

Looks we have gained control over the spam situation in this group after gaining admin privileges, so

That was quick - Thanks! SipXcom Newbie ----- Original Message ----- Date: Wed, 24 Jun 2026 16:20:45

Note we are tracking this issue at: https://github.com/onrelay/sipxecs/issues/60 On Jun 22, 2026, at

Thanks! You can track progress on https://github.com/onrelay/sipxecs/issues/59. On Jun 23, 2026, at 2

We have been live on 25.01 for a bit at OnRelay, and therefore now decided to remove the RC tag from

Hello, The problem you are encountering is fairly typical for some of the strengthened security

We have issued another update 4 on 25.01rc. Only minor changes there, a refactor of the ssh config

I think a good rule of thumb is, if something fundamentally breaks or goes awry during an install, eg

Hello bro I can help you setup any country sip trunk did number ivr setup for both inbound outbound

We have just published update 3 on the 25.01 release candidate. Key fixes include the backup &

Run: service sipxecs status Also doublecheck all services are actually enabled in your UI. > On

Thank you for your input and welcome to the community! On Friday, May 22, 2026 at 8:33:02 AM UTC+2

Thanks for the swift response. ```bash [root@hostname ~]# ll /etc/sipxpbx/.cfagent/ppkeys total 4 -rw

Thanks for the heads up. You all do a fantastic job. On Tue, May 19, 2026, 5:00 AM OnRelay Support

We have issued update 1 for 25.01rc on GitHub and our sipXcom repo. Most of the fixes are Rest API

## sipXcom 25.01 Configuration Issue - Server Remains Configured with Internal Address #### 1.

Hello, Yes, you may attempt to run the sipxecs-setup command with the --reset-all option to clear all

I have noted it as an open issue. Just beware one of the time consuming hurdles wit this update has

Oh on older versions we had sipxrelay run out of resource / memory all the time, but not something we