FQDN issue

[Nick Redfern]

Hi, I was attempting to migrate to a new serer with v18 over the weekend, current version v16. We use a custom domain name of our own on this. During the install, the new server registered with the FQDN - unfortunately the re-pointing of the trunks has not happened and I need to use the existing v16 until that is resolved. Some services are not available now as a result of this. Is there any way to get the existing server to re-register with 3cx and the FQDN?

 

[ChrisC_3CX]

What exact version of v16 is the machine running? You can check in Dashboard >> Information >> Version. Also, what do you mean by "some services are not available" are they shown as stopped in the 3CX MC >> Dashboard >> Services section?

 

[Saqqara]

What do you mean the re-pointing of the trunks has not happened.

What services are not available ?

As you are using a custom fqdn, did you update the dns record to point to the new wan IP address

Is this a windows installation of 3cx ?

if so are you running it on a supported OS and excluded the 3cx folders from av scanning - https://www.3cx.com/docs/manual/phone-system-installation-windows/

 

[Nick Redfern]

Version 16.0.8.9 on the existing box. It is a windows version, on server 2012 hence the need to move to a new install. We have IP-based registration on the trunks and the provider failed to switch over on the schedule. We currently have issues with users taking calls on the web client, hard phones and app users seem fine. The Webmeeting sync status shows network error at the present time.

 

[Nick Redfern]

ok, looks like restarting (again) has taken the main issues away, I'll limp on with it until I can get the switchover complete. thanks for the responses

 

[ChrisC_3CX]

Just remember to shutdown to v18 system in case you already have it running.