sipXcom 21.04 GA

[Michael Picher]

sipXcom 21.04 General Availability

November 16, 2021

Summary

CoreDial is pleased to announce the GA release of sipXcom 21.04.

We've made a number of enhancements to the API service for system management to a number of features including Auto Attendants, Web UI Localization/Language, Call Queues, and Time Zone.

We’ve also added a server column within the Web UI for registration entries.  This will allow for more in depth troubleshooting and verification by indicating the server that the endpoint is currently registered to.

Last, but certainly not least, our most exciting enhancement for this release is High Availability Configuration Service.  We’ve made the configuration service and the underlying database redundant and highly available.  This provides a safeguard for the configuration data by replicating it among the cluster server members.  In addition we’ve made it possible to migrate the configuration service to a secondary server essentially making it become the primary and assuming control of the cluster.

We’re continuing to look for ways to improve sipXcom and we’re excited about the opportunities that 2022 will bring.

HighlightssipXcom Enhancements:

• Manage Auto Attendants via API

• Manage Call Queues via API

• Manage Language settings via API

• Manage Time Zone  via API

• Configuration service and database is now highly available and redundant

• Ability to recover primary node on secondary server

• Add server column to registration entries

Notes

1. 19.08 and later are now released on CentOS 7 only. This will require that administrators install CentOS 7 minimal, then install Uniteme with our single line installer and then restore from a previous version backup.

2. AudioCodes and other gateways may need to have their configuration changed if faxing is used. See SIPX-811.

3. For Let's Encrypt certificates to work properly, the server must have a valid outside DNS name and have port 80 and 443 open to LE's servers.

Who Should Install?

New software releases are made at a rate of two to four releases a year. Releases are numbered in the <yy>.<mm>.<uu> format where <yy> and <mm> designate the year and the month, respectively, in which a release is made generally available. Where applicable, <uu> corresponds to an update release relative to a general release on which fixes are made available. 

Questions

Please post to the sipXcom-users google group if you have questions. 

https://groups.google.com/forum/#!forum/sipxcom-users

Specific Issues Addressed

Specific issues can be located in the detailed release notes in the wiki at: https://wiki.sipxcom.org/display/sipXcom/sipXcom+21.04

[Todd Hodgen]

Thanks Mike!!!

sent using my two left twiddling thumbs

---

From: sipxco...@googlegroups.com <sipxco...@googlegroups.com> on behalf of Michael Picher <mpi...@coredial.com>
Sent: Wednesday, November 17, 2021 4:49:23 AM
To: sipxcom-users <sipxco...@googlegroups.com>
Subject: [sipxcom-users] sipXcom 21.04 GA

 

--
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/b77dc54e-6bed-4f4d-a238-43b980767a93n%40googlegroups.com.

[Peter Krautle]

Ability to recover primary node on secondary server

Wow - need to look at this capability!!

[Amit Kansal]

Great Mike!!

Hope with this release we can open the configuration web page in secondary server also incase of primary fails. 

m I correct? 

[Mircea Carasel]

Hi,

You need to enable the new Admin Ui service on the node where you want admin ui to run, and where you want postgress database to replicate to.

Mircea

--
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/488bde82-71cd-402b-ae36-974d5d9ee9c9n%40googlegroups.com.

[Amit Kansal]

Thanks a lot Mircea!! 

Sent from my iPhone

On 21-Nov-2021, at 11:55 AM, Mircea Carasel <mir...@ezuce.com> wrote:



[rakes...@gmail.com]

Hi , 

It does not work with us, any other settings are required to enable this.

Thanks,

Rakesh

[Mircea Carasel]

Please provide sipxconfig.log from secondary

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/655f61a1-234f-405c-aa57-9c6dfc095be0n%40googlegroups.com.

[Rakesh]

[Mircea Carasel]

Please clean the log, try restarting the secondary with admin ui enabled and post again sipxconfig.log

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/5fa9b366-5395-4518-b52a-f6ff68dbb05dn%40googlegroups.com.

[Rakesh]

[Mircea Carasel]

Can you acces web ui on chosen secondary now?

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/803af0eb-55b9-4ca2-abd1-8049dcd2de45n%40googlegroups.com.

[Rakesh Panwar]

Not opening.

[Mircea Carasel]

Is the page loading, or the page loads with error messages?

please run and post the output of:

systemctl status sipxconfig

ps -ef | sipxconfig

netstat -tupan | 12000 

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CANsuRoGL-RFShs2Ukd3ttmg92%2BW33AjALXC%2BAbRdrF0DYMRicA%40mail.gmail.com.

[Rakesh Panwar]

z

Page not loading .

[Mircea Carasel]

what about the specified commands ?

Also, maybe your secondary is not accesible due to firewall restrictions.

Also, check postgres:

psql -U postgres sipxconfig

select * from users;

[Rakesh]

Not a firewall issue, already allowed IP of the machine where we opening the page.

[Mircea Carasel]

postgres appears in sync, log is generating and looks good (after restart).

I did not get from you output of:

systemctl status sipxconfig

netstat -tupan | 12000

also for httpd port 80

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/4c76a010-5010-4229-b5d6-679d3493e34fn%40googlegroups.com.

[Rakesh Panwar]

netstat -tupan | grep 12000 > not showing output

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CAJWhAbhjoNxTZxfsjmxnKcS4WcmH8pJWtTDvFi6ZiaV1PKgjJg%40mail.gmail.com.

[Mircea Carasel]

you wrote tupn instead tupan. missed.

this is not the same thing

a is important - means all active connections

[Rakesh Panwar]

[Mircea Carasel]

checking your connections file, sipxconfig is up and running on your machine (port 12000 is listening)

the issue seems to be the httpd web proxy:

please  run:

systemctl status httpd

also, send me /var/log/httpd/error_log

Mircea

[Rakesh Panwar]

yes, httpd is not running.

[Mircea Carasel]

[lbmethod_heartbeat:notice] [pid 1291] AH02282: No slotmem from mod_heartmonitor

not sure where this is coming from. try sending profiles to all nodes in the cluster, then restart

Mircea

[Rakesh]

It is same after send profile and restart secondary node.

Hint : before adding database page was loading.

[Mircea Carasel]

What do you mean by adding database? what database?

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/da5ec58b-4182-4e47-ab44-df94a0d5b434n%40googlegroups.com.

[Rakesh Panwar]

Global database > Secondary nodes

sent you a snapshot

[Mircea Carasel]

Secondary mongo node? Prior enabling Web admin UI on secondary, did you have mongo database added on this secondary?

Usually HA setups are made of three nodes all with mongo added, one master, one secondary and one arbiter. Do you have a different setup config?

Mircea 

[Rakesh Panwar]

yes enabled all the services and then added database, currently have 2 secondary nodes without Arbiter, I think so no need arbiter for Web-Ui test but I have made it earlier with Arbiter (third node ) got the same issue with secondary node not seen Web-UI.

[Mircea Carasel]

your httpd is the culprit, not web ui. But I don't know how to fix httpd on your machine.

check all log files from /var/log/httpd , maybe you find some hint 

--
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/5ec4940c-3b74-4cb3-b8a3-e3d30d749780n%40googlegroups.com.

[Rakesh Panwar]

[Rakesh Panwar]

Worked GUI on Seondary nodes after reinstall secondary nodes.

Notice two things 

1. Secondary nodes GUI isn't showing Global Database Status.

2. Secondary nodes GUI is showing nodes Uninitialized.

Primary All are showing ok.

You received this message because you are subscribed to a topic in the Google Groups "sipxcom-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sipxcom-users/0beuyAZIXiI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sipxcom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/381c1bd7-32b1-4904-a1fa-9c09db545fe8n%40googlegroups.com.

[Mircea Carasel]

Great!

These are known.

The secondary did not turn in primary node, those pages, also the Backup page won't be available. 

Mind that also the web ui is read only.

For backup, you can execute via command line.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CANsuRoEobEtm44cPNc9_Gp2mrg4Zdj%3DajfOL2NUgZYGi%3D-Ot4g%40mail.gmail.com.

[Rakesh Panwar]

Ok, thanks. 

[Amit Kansal]

Good!!

Finally achieved. 

Thanks a lot Mircea for your support!!

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CANsuRoE_waoW4iBk692EKe80eeYfryj9WkE24guh5vOLqxU3ww%40mail.gmail.com.

[Peter Krautle]

Hi Mircea - I'm getting similar findings to Rakesh. From secondary server UI, you cannot display the Mongo database settings and when powering down the primary server, the secondary admin GUI shows primary server as 'configured' and secondary/arbiter servers as 'unitialized'. My question - what is the method to convert a secondary server into a primary server using the secondary admin GUI? btw the phones registration enhancement is very useful!

All the best

Peter

[Mircea Carasel]

Hi,

This secondary node (with UI enabled) cannot be converted to primary, but it can be used to create a new primary node with all data synchronized, if the current primary goes down.

Please find below the procedure:

Prerequisite:
- One of the secondary nodes to have the WEB Admin UI service enabled (postgres gets synced)
Use case:
- Primary node goes down

Procedure to recover primary:
1. Create a new primary node with the same IP as previous
2. run sipxecs-setup --recover-primary
    - when asked for the node to recover, put the secondary node IP that has web UI enabled
    - put the same hostname as the previous

3. Reboot primary to activate all services after it is confirmed that sipxconfig has completed its startup (webui OK) (this can be done after step 6 also)
4. run sipxecs-setup --reset-all on the secondaries to attach them on the new primary
5. on the primary node WEB UI, database section, remove the mongo/arbiter from the secondaries nodes and then add them again.

6. Add query meta to the primary database

7. Send profiles to all servers

8. Reboot secondaries

Mircea

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/2dd05429-e6b9-4e1c-a1f7-7d74edaee49en%40googlegroups.com.

[Peter Krautle]

Hi Mircea - thank you. What this suggests is that the primary server can be recovered quickly from (and not on) a secondary server without having to rebuild from backups. Follow-on question regarding step 6 - is the query meta at the Postgres or Mongo DB? All the best Peter

[Mircea Carasel]

Yes, you are correct.

The Add Query Meta refers to Mongo , and should be a visible button on Mongo db ui page.

Mircea

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/a72ec36b-2006-453e-ad41-2337e6fcec1dn%40googlegroups.com.

[Iuliu Blaga]

Hi you will see this option in the MongoDB page in GUI

To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/a72ec36b-2006-453e-ad41-2337e6fcec1dn%40googlegroups.com.

--

 

Iuliu Blaga Sr. Support Engineer 215.297.4400 x 751 Arbor Way, Arbor Crest I, Suite 150, Blue Bell, PA 19422 coredial.com

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

[Peter Krautle]

I'm having trouble finding the Query Meta option - it is not in the System->Databases->Settings menu, and I could not find it on the System->Databases->Database->Global Database menu. I also looked at the other System menus and could not locate it. Can you point me in the right direction? Many thanks Peter

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/a72ec36b-2006-453e-ad41-2337e6fcec1dn%40googlegroups.com.

[Iuliu Blaga]

Hi, you only see it when it's missing from the database.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/02ef6c7c-e92c-48ff-abc2-36385377fe76n%40googlegroups.com.

[Peter Krautle]

I've tried 4 times to recover the primary server from a secondary server without success - Sipxcom services will not start after running sipxecs-setup ---recover- primary script is executed twice. The first time fails on an error but appears to successfully complete when executed the second time. The sipxagent log file is here  https://www.dropbox.com/s/t86t7aqpmdjgolh/sipxagent.log?dl=0 and putty console log is here https://www.dropbox.com/s/4bowgjdgyd1ew3i/puttylog?dl=0. Any guidance on next  steps is appreciated. Peter

On Monday, November 29, 2021 at 4:15:00 PM UTC-5 Mircea Carasel wrote:

[Peter Krautle]

I forgot to mention that the four attempts were using a new Sipxcom/Centos 7 system. Peter