Sipxecs-Setup Issue with Changing Domain Name

[pmkr...@gmail.com]

We are in the process of moving a primary and secondary Sipxcom server (17.04) to a new data center in the middle of August. During this move, the IP address and FQDN of the servers will change. About 50 percent of the time when running sipxecs-setup, the new server fqdn for Mongo does not get applied successfully. A workaround was documented here and SIPX-658 Jira was opened.

http://wiki.ezuce.com/display/sipXcom/Changing+the+SIP+Domain+Name+for+Sipxcom+in+Release+17.04

Because of the number of users on this cluster, the move needs to go well - our internal testing leads us to believe that this works successfully. Can someone review this procedure and see whether it's complete or missing some steps. The concern is Sipxcom on the primary server as the secondary server points back to the primary via the serverid.

All the best

Peter

[Michael Picher]

Why wouldn't you just use the restore method to a 19.04 on CentOS7?  Just pick the restore options to keep the domain of the server.

Mike

Michael Picher, VP of Product Management
eZuce, Inc.

5 Central Street, Suite 302

Stoneham, MA. 02180

O.978-296-1005 X2015 
M.207-458-1892

linkedin
www.ezuce.com

Notice: This transmittal and/or attachments may be privileged or confidential. It is intended solely for the addressee(s) named above. Any dissemination or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you.

--
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/c9d416b8-3371-4d4f-8958-3b91172f3e05%40googlegroups.com.

[pmkr...@gmail.com]

Thanks Mike for the response. There are many moving pieces to this data center move, including changes to TDM gateways, L2/3 infrastructure, MPLS, core applications, etc. The Centos7/19.08 upgrade is scheduled in late Q3/early Q4 after the data center move is complete and there is a few weeks of observed stability in the network.

All the best

Peter

To unsubscribe from this group and stop receiving emails from it, send an email to sipxco...@googlegroups.com.

[pmkr...@gmail.com]

Well the use of sipxecs-setup to change the IP address of the primary and one secondary server failed on the weekend - only partial sipx services came back up. We reinstalled a fresh image of Sipxcom 17.04 and restored a backup configuration, and then built the secondary server whose IP address changed. There are two remaining issues:

• Sipxcdr fails to start. In the sipcdroath.log file, we see these errors whenever a CDR record attempts to write to the database - Patch list: gateway upgrade_version, gateway, Upgrading DB schema version to 7, ERROR:  duplicate key value violates unique constraint "version_history_pkey". The SIPXCDR database exists and looks sound. Any ideas on how clear up this issue is appreciated.
• The other secondary server whose IP address did not change cannot collect to the cluster. We tried deleting the server from Sipxcom and then adding again (forcing new Mongo id), resetting keys, etc - no joy. The one thing noticed was that when the hostname of this server changed, Sipxcom showed the node as configured immediately so Sipxcom must keep track of the server configuration by IP address. GUI keeps reporting 'command not allowed' when trying to add the secondary server to the cluster vibase menu. Mongo logs do not report any errors. Any suggestions here on adding this secondary server without changing the IP address is appreciated.

[pmkr...@gmail.com]

In regards to the first issue, we also see this error message in the sipxcallresolver.log file:

"2019-08-19T18:42:04.480894Z":3:CDR:ERR:host.sipdomain.com:main:00000000:cdr:"cdr_writer.rb:: values = 75892d547f2acaa2, d0890d9f9b, 7r5t8ce7B5cec, <sip:73421...@10.107.33.2:5060>, <sip:60...@10.107.192.63>, 2019-08-19 18:40:48.657, 2019-08-19 18:40:48.981, 2019-08-19 18:40:54.141, C, , , , , <sip:73421...@10.107.33.2:5060>, sip:I...@vm.voip1.flintgrp.com, true, UNK,AL,VMR,AL, ,  ---- Error = , ERROR:  duplicate key value violates unique constraint \"cdrs_call_id_unique\""

[pmkr...@gmail.com]

An update - by changing the hostname of the problem server within Sipxcom and assigning a new Mongo id, we ewre finally able to get the server connected to Mongo in 17.04 as an arbiter. The Sipxcdr issues also went away.

The other applications involved  with the data center move, including a voice server from another manufacturer, were able to update IP addresses without major issues. I hope the sipxecs-setup procedures get reviewed as part of the Centos 7upgrade initiatives for Sipxcom - it is needed.

All the best

Peter