sipXcom 24.01 Released

[Ivar Plahte]

We have now released sipXcom 24.01 for CentOS 7!

The release documentation including assets and release notes can be found here.

All changes we have added since 21.04 are recorded as closed GitHub issues for milestone 24.01.

Upgrade, installation and build instructions can be found on the wiki here.

The corresponding RPM repository is here.  Remember to install the Google Cloud Artifact Registry Plugin to access it.

[Roy Reynolds]

Fantastic!!

--
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 on the web visit https://groups.google.com/d/msgid/sipxcom-users/b0b775f9-3d46-40e7-98c8-b03d43c81c6bn%40googlegroups.com.

[Ivar Plahte]

We did a 24.01 patch, update 1, see https://github.com/onrelay/sipxecs/releases. Repos have been updated.

It was the root cause of some previous TLS related problems, a missing null pointer check when sending TLS to invalid IP addresses, this time provoked by more heavy use of the RLS service.

So an important fix. See https://github.com/onrelay/sipxecs/issues/33.

[Ivar Plahte]

Hi Roy,

Did you install the Google Cloud Artifact Registry Plugin?

Ivar

On Jun 11, 2024, at 1:24 AM, Roy Reynolds <duf...@gmail.com> wrote:

Hello, 

I'm trying to install following the instructions but the Google artifacts will not install.  I get 404 not found. I checked and double checked the url to make sure it's right but still no luck.  Is there a new url to use?

 Thanks.

On Sun, May 19, 2024, 9:18 AM Ivar Plahte <ivar....@onrelay.net> wrote:

[Roy Reynolds]

Hello, 

I'm trying to install following the instructions but the Google artifacts will not install.  I get 404 not found. I checked and double checked the url to make sure it's right but still no luck.  Is there a new url to use?

 Thanks.

On Sun, May 19, 2024, 9:18 AM Ivar Plahte <ivar....@onrelay.net> wrote:

--

[Roy Reynolds]

Hi Ivar,

Thanks for responding. 

I get the 404 error when trying to do this step: 

wget -O /etc/yum.repos.d/artifact-registry-plugin.repo \
  https://storage.googleapis.com/sipxecs/artifact-registry/artifact-registry-plugin.repo

yum install -y yum-plugin-artifact-registry

Thanks.

[Roy Reynolds]

I will try again later tonight but it probably is related to a typo in the url.

[Support]

It works for us and we do this frequently for fresh Docker builds. Perhaps the copy & paste of the newline there is causing the issue?

# wget -O /etc/yum.repos.d/artifact-registry-plugin.repo \

>   https://storage.googleapis.com/sipxecs/artifact-registry/artifact-registry-plugin.repo

--2024-06-11 06:37:20--  https://storage.googleapis.com/sipxecs/artifact-registry/artifact-registry-plugin.repo

Resolving storage.googleapis.com (storage.googleapis.com)... 64.233.181.207, 74.125.126.207, 142.251.183.207, ...

Connecting to storage.googleapis.com (storage.googleapis.com)|64.233.181.207|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: 293 [application/octet-stream]

Saving to: ‘/etc/yum.repos.d/artifact-registry-plugin.repo’

100%[=======================================================================================================>] 293         --.-K/s   in 0s      

2024-06-11 06:37:20 (70.6 MB/s) - ‘/etc/yum.repos.d/artifact-registry-plugin.repo’ saved [293/293]

[Roy Reynolds]

Thanks for replying. 

I was able to get pass that step successfully.  The elasticsearch was not installed so it couldn't be enabled. I went ahead and used a separate repo to install it after installing JDK.  I could then enable it.

Sipxecs was installed and configured as normal but at the end it complained of an error and said I can come back and run the script after addressing the issue reported in the sipxagent log.  It didn't tell me what issue is and I saw multiple errors in the log. 

The Web interface was inaccessible and after several minutes, reported server error.

I have successfully installed 21.x using the Google artifacts plugin but 24.01 is not working so far.

During the CentOS install, I used a time zone for Guyana.  First time doing that and so I'm not sure if that caused the issues.  I noticed it as an error in the log. 

Sometime today, I will scrub the system and redo the install to see if I get the same result. 

Thanks for all the work you guys are doing.

[OnRelay Support]

Hi Roy,

Could you please post the error details from your logs and also let us know your environment?

We build on default Google Cloud Compute and Docker CentOS7 images and install / test / deploy on the former.

Elasticsearch is preinstalled on both environments. elasticsearch-1.7.3.noarch.rpm is also in our repo, but, yes, that becomes a chicken and egg issue since it requires the plugin to install from there. We will find a solution.

After install your likely culprit is some sort of runtime dependency similar to elasticsearch that we assume is present, which is missing on your platform.

As soon as we figure what your issue is we can go ahead and update both repos and build script.

[Ivar Plahte]

Here is a workaround for preinstalling elasticsearch.

Note if you used a different repo, such as Epel, without disabling it afterwards, you may have installed some incorrect dependencies during sipXcom installation.

As a workaround, change directory to a temp folder or similar and run:

    wget https://storage.googleapis.com/sipxecs/sipxcom/24.01/centos-7-x86_64/elasticsearch-1.7.3.noarch.rpm

    yum localinstall -y elasticsearch*

    rm -f elasticsearch*

We will update docs accordingly

[Roy Reynolds]

Where do you want me to post the logs? It's pretty long so don't want to flood the email. 

I also used this guide to install elasticsearch: https://azdigi.com/blog/en/linux-server-en/install-elasticsearch-on-centos-7/

I'm running CentOS 7 minimal on a standalone server with 8g Ram, 120g Hd and Intel i3 cpu.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/02ff5e9a-d9c7-4575-abc7-825ee23f0fd2n%40googlegroups.com.

[OnRelay Support]

Hi Roy,

If you could grep just the :ERR 's you see that would give us a starting point.

Also note the elasticsearch version you installed is quite a bit later than the one used by sipXcom. We will endeavor to upgrade everything, but have taken a conservative approach now.

So that dependency may potentially be problematic, and would recommend using the abovementioned workaround instead.

[Roy Reynolds]

I will try to capture add many of the errors but the wording is not consistent. Some lines just lists unknown and nothing else. 

The work around you mentioned: is that too install elasticsearch-1.7.3.noarch.rpm

If yes, how do I get to it?  Github is telling I don't have access. 

Thanks.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/4671e842-de20-4905-8d38-8e17c51e9b3cn%40googlegroups.com.

[OnRelay Support]

Hi Roy,

The workaround was posted above, reposting:

> Change directory to a temp folder or similar and run:

>
>    wget https://storage.googleapis.com/sipxecs/sipxcom/24.01/centos-7-x86_64/elasticsearch-1.7.3.noarch.rpm
>
 >   yum localinstall -y elasticsearch*
>
>    rm -f elasticsearch*

Those unknown errors may perphaps point to elasticsearch, if you could just post a couple of examples that would be helpful.

[OnRelay Support]

A simpler solution seems just to reorder the installation instructions, such that the sipXcom repo file is added before elasticsearch is needed / installed.

We also added a line to install elasticsearch before enabling in case it is not preinstalled.

See https://onrelay.github.io/sipxecs/installing.html which has been updated accordingly.

[Roy Reynolds]

Hi Ivar,

I am attaching some files with snippets of errors from the logs.  I tried to name the files so you would recognize which logs it's related to (sipxagent.log and sipxconfig.log)  I hope this helps is some way.  If not, I can try to get you more details from the error logs.

Thanks.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/952c3726-2208-4a45-b97e-b0f7881d0759n%40googlegroups.com.

[Ivar Plahte]

Before digging into this too deeply I would definitely start fresh with the sipXcom repo version of elasticsearch.

[OnRelay Support]

Hello Roy,

Also make sure you disable the epel repo before installing sipXecs:

yum remove -y epel-release

There are some references to org.postgresql.core.v3 in your logs -- looks like a later version of postgresql has been pulled in.

[Roy Reynolds]

Okay. I will attempt a reinstall on the weekend following the recommendations.

Thanks.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/82a18168-841a-44b3-9681-c795a94bfacfn%40googlegroups.com.

[OnRelay Support]

Hello Roy,

The error was ours, see other post about 24.01 update 3, which is now available.

Appreciate if you confirm it installs OK now.

[Roy Reynolds]

Thanks for letting me know. I will attempt the install today and report back. 

Appreciate you guys!

--
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 on the web visit https://groups.google.com/d/msgid/sipxcom-users/39e67a6d-a406-4a57-82ff-a0e7545f201bn%40googlegroups.com.

[Roy Reynolds]

I am now able to install successfully and log into the portal.

Thanks!