Change of FQDN Endpoint Due with Update 2 Beta

[VictorSP]

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

Sure, we'll move all of them to v18 as soon as possible. Thanks for your replies, Nick.

 

[cobaltit]

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.

Hey Victor,

Like you, I am a Platinum Partner and I get the same questions and I give them the same answer I gave you. An ETA is a still a moving target which is why one isn't provided. It just begets complaints and additional questions when it isn't met. I'm certain it will be released well before it becomes necessary, and if it doesn't, oh well? I mean it's not like your machine is going to fall down 1 minute past the deadline and if the customer is that concerned, then you simply treat it as a 0-day vulnerability and patch it outside of your normal window. If they can't do that then I guess they don't think it's that important.

The point is if 3CX had a firm ETA I'm sure they would have provided it. Unless you think 3CX is a bunch of evil henchmen hiding in their evil lair laughing at all of us squirming under the impending deadline. If that's the case then you probably should be looking for another product to sell.

 

[VictorSP]

Hey Victor,

Like you, I am a Platinum Partner and I get the same questions and I give them the same answer I gave you. An ETA is a still a moving target which is why one isn't provided. It just begets complaints and additional questions when it isn't met. I'm certain it will be released well before it becomes necessary, and if it doesn't, oh well? I mean it's not like your machine is going to fall down 1 minute past the deadline and if the customer is that concerned, then you simply treat it as a 0-day vulnerability and patch it outside of your normal window. If they can't do that then I guess they don't think it's that important.

Well, that why ETA means "estimated", it's not the same situation if you said to customers 23th December than aprox the 3rd week of December. And this is probably an information that 3CX could only share with partners, and if the customer asks about, the partner could have a better position to resolve the date doubt.

The point is if 3CX had a firm ETA I'm sure they would have provided it. Unless you think 3CX is a bunch of evil henchmen hiding in their evil lair laughing at all of us squirming under the impending deadline. If that's the case then you probably should be looking for another product to sell.

That is something you wrote, not me. We have been working with 3CX for many years and we and our customer are happy with the solution. Please, let's leave this topic here.

Have a nice day!

 

[N_G]

@cobaltit Thank you for your support, much appreciated
@VictorSP The update for v16 will come very soon, i thought the blog post had mentioned that. It will be in the coming weeks for sure.

 

[proffitt]

@cobaltit Thank you for your support, much appreciated
@VictorSP The update for v16 will come very soon, i thought the blog post had mentioned that. It will be in the coming weeks for sure.

With Version 16, Update 8A Beta now released. I presume this is the release to address the FQDN endpoint change which being discussed in this blog thread.

It's not entirely clear from the release notes, but I suspect it's this entry -

• Updated Licensing Module

https://www.3cx.com/blog/change-log/phone-system-change-log/

Thanks

 

[N_G]

@proffitt - yes indeed. Unfortunately with not the full range of tests that we would have liked to do prior to this release so there maybe another update.

 

[VictorSP]

@proffitt - yes indeed. Unfortunately with not the full range of tests that we would have liked to do prior to this release so there maybe another update.

Hi @Nick Galea ,

So does Update8A (16.0.8.16) include the final solution to FQDN endpoint change or not? Are you working on an additional update to resolve that "issue"? The ChangeLog doesn't menction this point.



Regards

 

[MidiTélécom]

Hi @Nick Galea ,

So does Update8A (16.0.8.16) include the final solution to FQDN endpoint change or not? Are you working on an additional update to resolve that "issue"? The ChangeLog doesn't menction this point.

View attachment 26741

Regards

Check/ask the topic about it and you will find your answer : https://www.3cx.com/community/threads/v18-u2-web-client-update-and-v16-8a-are-now-final.86685/

 

[VictorSP]

Check/ask the topic about it and you will find your answer : https://www.3cx.com/community/threads/v18-u2-web-client-update-and-v16-8a-are-now-final.86685/

Thanks, it was not clear.

 

[salmartinez]

Hello, yesterday I received an email that indicates the dates for this change have been pushed to February 28th 2022, previously February 1st. Can someone please confirm this is accurate? See Below email from 3cx .

*****************
To improve our cloud services, the FQDN endpoint used to activate 3CX products will change to activate.3cx.com. The current activation endpoint will be terminated, the latest by 28th February 2022.

What do I have to do?
Review your network access rules and ensure that you allow connectivity to activate.3cx.com. Outbound TCP:443 must be allowed to activate.3cx.com. Due to the nature of our service clusters, we cannot provide you with a fixed IP list.

Ensure that you update your 3CX PBX by the 28th February 2022 to v18 Update 2. Alternatively ensure that version 16 Update 8a is installed, however this will be a short-term fix - until November 2022.

Upgrade to v18 to ensure long term support, compatibility and security. If you require assistance please contact a local 3CX Partner or ask the 3CX Community Forums.

Best regards,

The 3CX Team

 

[NickD_3CX]

Hello, yesterday I received an email that indicates the dates for this change have been pushed to February 28th 2022, previously February 1st. Can someone please confirm this is accurate? See Below email from 3cx .

*****************
To improve our cloud services, the FQDN endpoint used to activate 3CX products will change to activate.3cx.com. The current activation endpoint will be terminated, the latest by 28th February 2022.

What do I have to do?
Review your network access rules and ensure that you allow connectivity to activate.3cx.com. Outbound TCP:443 must be allowed to activate.3cx.com. Due to the nature of our service clusters, we cannot provide you with a fixed IP list.

Ensure that you update your 3CX PBX by the 28th February 2022 to v18 Update 2. Alternatively ensure that version 16 Update 8a is installed, however this will be a short-term fix - until November 2022.

Upgrade to v18 to ensure long term support, compatibility and security. If you require assistance please contact a local 3CX Partner or ask the 3CX Community Forums.

Best regards,

The 3CX Team

Hi!

What you received in the email is accurate, however, please don't leave it until last minute. You don't want to be scrambling last minute because a client is unavailable, the server doesn't upgrade, you can't find the network guy, etc...

There will be no extensions to this date.

 

[Mike Big]

Is This Applicable to On-premises ???

Yesterday i receive email Below

To improve our cloud services, the FQDN endpoint used to activate 3CX products will change to activate.3cx.com. The current activation endpoint will be terminated, the latest by 28th February 2022.

What do I have to do?
Review your network access rules and ensure that you allow connectivity to activate.3cx.com. Outbound TCP:443 must be allowed to activate.3cx.com. Due to the nature of our service clusters, we cannot provide you with a fixed IP list.

Ensure that you update your 3CX PBX by the 28th February 2022 to v18 Update 2. Alternatively ensure that version 16 Update 8a is installed, however this will be a short-term fix - until November 2022.

Upgrade to v18 to ensure long term support, compatibility and security. If you require assistance please contact a local 3CX Partner or ask the 3CX Community Forums.

Best regards,

The 3CX Team

 

[NickD_3CX]

Is This Applicable to On-premises ???

Yesterday i receive email Below

To improve our cloud services, the FQDN endpoint used to activate 3CX products will change to activate.3cx.com. The current activation endpoint will be terminated, the latest by 28th February 2022.

What do I have to do?
Review your network access rules and ensure that you allow connectivity to activate.3cx.com. Outbound TCP:443 must be allowed to activate.3cx.com. Due to the nature of our service clusters, we cannot provide you with a fixed IP list.

Ensure that you update your 3CX PBX by the 28th February 2022 to v18 Update 2. Alternatively ensure that version 16 Update 8a is installed, however this will be a short-term fix - until November 2022.

Upgrade to v18 to ensure long term support, compatibility and security. If you require assistance please contact a local 3CX Partner or ask the 3CX Community Forums.

Best regards,

The 3CX Team

This is applicable to all 3CX installations.

 

[Bolz IT]

Because v18 U2 is missing some translations, we have not updated yet. Is the fix with v18 U3 coming before the 28th February or are we forced to update to U2 regardless?

 

[NickD_3CX]

Because v18 U2 is missing some translations, we have not updated yet. Is the fix with v18 U3 coming before the 28th February or are we forced to update to U2 regardless?

We don't have a firm date that we can share yet about the release of V18 U3, so I would suggest being prepared to update to U2 until U3 is out.

 

[Sanderr]

Hello,

If you still run V15.5 on-premise and cant update because of hardware limitations. Does 3CX keeps working with that version? Or do they will loose functions, phones are not provisioned trough 3CX right now.

We have a customer who is currently changing management and the new management will update the hardware. But i think they wont make it before 28th of february.

 

[Saqqara]

Hello,

If you still run V15.5 on-premise and cant update because of hardware limitations. Does 3CX keeps working with that version? Or do they will loose functions, phones are not provisioned trough 3CX right now.

We have a customer who is currently changing management and the new management will update the hardware. But i think they wont make it before 28th of february.

Check https://www.3cx.com/blog/releases/fqdn-endpoint-change/

To Note: Customers still on v15.5 will no longer be able to activate post-March 2022

This means that the call home function to validate your license with not work, and the license will be changed to the free version - 4sc

 

[NickD_3CX]

Hello,

If you still run V15.5 on-premise and cant update because of hardware limitations. Does 3CX keeps working with that version? Or do they will loose functions, phones are not provisioned trough 3CX right now.

We have a customer who is currently changing management and the new management will update the hardware. But i think they wont make it before 28th of february.

Just to slightly expand on what @Saqqara said, he is mostly right, post-March 2022 V15.5 systems will not be able to activate/re-activate.

About the call home mechanism, he is also right, however this *may* not happen on the first day, the intervals at which this happens are completely random, so the "downgrade" to the Standard feature set may not happen on the first day.

I must say though that if March comes and you haven't done something, be prepared to have to do the upgrade to V18 at the same time that you do the hardware/OS upgrade, because if the server is powered off, the chances of the software re-checking the license increase a lot, and there will be nothing we can do about it of that happens.

 

[ismailasaad]

We were using 15.5
Renew your subscription for a year
But he did not accept to activate the key because the version is old
We have updated this version v18
But it is still not activated
I accepted the subscription renewal and received the money
But you do not accept the activation of the product
How can we work with you please help

 

[NickD_3CX]

We were using 15.5
Renew your subscription for a year
But he did not accept to activate the key because the version is old
We have updated this version v18
But it is still not activated
I accepted the subscription renewal and received the money
But you do not accept the activation of the product
How can we work with you please help

I will send you a PM shortly to try and help you get the product activated.