Change of FQDN Endpoint Due with Update 2 Beta

Status
Not open for further replies.
Hi,

Does this update will affected which the FQDN endpoint that hosted cloud hosting? If yes, what should need to do for the next steps? Kindly advise on this. Thanks.
 
@CentrexJ - Thank you for the heads up Jonathan - much appreciated!
@Joo Hai - Its dependent on the version, not whether its hosted or not. But if you mean 3CX Hosted, then indeed there is nothing you have to do, as we keep the instances updated at all times.
 
  • Like
Reactions: GregG_3CX
Already tried updating Google Cloud installation on 2 instances and both crashed the systems and I had to recover from backup? These are automatic instances spun up from 3CX. So how is it exactly we are supposed to upgrade when the upgrade crashes the systems.
 
When does the v18u2 patch release? We are still waiting on this to fix the broken scheduler that is wreaking havoc on scheduled reports and backups.
 
When does the v18u2 patch release? We are still waiting on this to fix the broken scheduler that is wreaking havoc on scheduled reports and backups.
The beta should be coming soon. Release probably around Christmas, as they usually do. Otherwise, we'll get U2 before and U3 beta for Christmas (which would be a great gift lol)
 
I would like clarification, please. Is the activation simply an outbound request from the on-premise PBX? If yes, and as long as our firewalls do not restrict normal outbound traffic, then nothing needs to be done other than the patch?
Exactly.
 
Second clarification for me, please ?
We have nothing to do, even if we have a personal fqdn like myipbx.mycompany.com ?
 
@Yoann , it has nothing to do with your own FQDN or what form your FQDN is.

If you have a strict cooperate firewall policy on outbound traffic, then allow the new endpoint where your system will connect to. Nothing else will change.
 
I suggest updating the ports document pagefor 3cx to indicate this new requirement.

Can we confirm which port(s) are required from the PBX to communicate with activate.3cx.com?
 
Last edited:
  • Like
Reactions: Yoann
443/tcp
 
  • Like
Reactions: FridayIT
@CentrexJ - Thank you for the heads up Jonathan - much appreciated!
@Joo Hai - Its dependent on the version, not whether its hosted or not. But if you mean 3CX Hosted, then indeed there is nothing you have to do, as we keep the instances updated at all times.

Is this mean that even we use the hosted cloud PBX of latest updated version 18 and that FQDN provided by 3cx E.G like "mycompany.my3cx.sg". There is nothing need to do for our end right?
 
Is this mean that even we use the hosted cloud PBX of latest updated version 18 and that FQDN provided by 3cx E.G like "mycompany.my3cx.sg". There is nothing need to do for our end right?
The FQDN you use has nothing to do with the activation server.

@Nick Galea this news seems to confuse more people than it helps them lol
 
I think the below summarizes the situation.

Are you using 3cx hosting? If yes, no action needed, 3cx maintains the server :).

If not, follow the below

Your PBX makes a connection to 3cx to validate your license, the address 3cx uses to check this is changing to activate.3cx.com. You will need to make sure your PBX can reach activate.3cx.com with an outbound connection on tcp port 443.

If you want to test this ahead of time on a on prem/ 3rd party hosted server. Follow the below steps.

SSH Linux PBX: use the command telnet activate.3cx.com 443. if you get a message "connected to activate.3cx.com" no action needed. if it times out or fails, then you will need to adjust your firewall.

Windows PBX.

If telnet is enabled
Open CMD and use the command telnet activate.3cx.com 443. if you get a message "connected to activate.3cx.com no action needed. if it times out or fails, then you will need to abjust your firewall. you can use control + c to kill the connection if it connects.

Modern windows servers have telnet client disabled by default, so you can use the following powershell command to test as an alternative option

Test-NetConnection activate.3cx.com -port 443. check to see if the line "TcpTestSucceeded " is True, if true. no action needed, if false, check your firewall rules.
 
Hi team,

When will be the v16 update8"A" fix available?

Regards,
 
Hi team,

When will be the v16 update8"A" fix available?

Regards,
As with ever other software development timeline, it will be available when it's available. If there was a date I'm sure it would be in the blog post.
 
  • Like
Reactions: N_G and Evolute IT
As with ever other software development timeline, it will be available when it's available. If there was a date I'm sure it would be in the blog post.
Yes, any software development has timeline... but also an ETA. If 3CX said you must apply a critical fix before 1st February, what the customer want (because they asked us after receive the email) it's a notice about when this fix will be available or an ETA, because its installation probably will require a services restart and most customer need to schedule a maintenance window. In my opinion to keep them calm, 3CX might said "you must apply the critical fix before 1st February but don't worry because it will be available (f.e) during the third week of December.".

Do you realise the difference between one message and another for the end customer? Don't take this wrong way, it's just a constructive comment.

;)
 
Its coming soon after update 2. But really you should move your customers to v18
 
  • Like
Reactions: Evolute IT
Its coming soon after update 2. But really you should move your customers to v18

Thanks Nick. Yes, that's our intention but you know what the customers are like with major upgrades.
 
Well you have to push them.....The apps will not work with v16 at one point and no security updates for debian 9 etc..... So its madness not to go to v18
 
Status
Not open for further replies.

Forum statistics

Threads
111,995
Messages
590,194
Members
164,934
Latest member
bunthoeun.may