As many have seen, 3CX is updating some aspects that will require many of us to go back and revisit clients that are on older versions, that may or may not have elected to not renew the maintenance, and bring them up to date in order to avoid licence activation failures.
I updated one client who did have maintenance and while successful. it reverted their SMTP to the 3CX SMTP. I was of the impression that if a client had their own SMTP previously, such would remain the case. Is this incorrect? The client runs their own mail servers and has rules built to customize delivery of same, but has subsequently lost this capability. How will the update impact those whose maintenance has expired' yet still have to upgrade in order to avoid the license failure issue? Does this mean I update them, they get the 3CX SMTP server like it or not and then when then the maintenance goes away once the upgrade period has ended (10/30?) they are left with no email capability?
Additionally, for those not with maintenance and on the older versions, what is the recommended path with regard to FQDNs and Certs that were not a factor then, but come into play with the upgrade? What happens when these expire?
They will not renew or upgrade at this time, so suggestions to do so are not helpful. I am merely trying to get the clients up to date with as little pain (to me as well) as possible and still retain the functionality they were sold when they originally bought the system(s).
I have a couple who used streaming MOH and when v14 removed that function, they elected to stay with 12.5 as it meant that much to them. Others are smaller independent hotels without the PMS option (at the time) and the room status was visible via the hotel module, but not in v15.5 where a PMS is required. It became a cost issue where adding a PMS to see the room status was not worth it.
Thanks
I updated one client who did have maintenance and while successful. it reverted their SMTP to the 3CX SMTP. I was of the impression that if a client had their own SMTP previously, such would remain the case. Is this incorrect? The client runs their own mail servers and has rules built to customize delivery of same, but has subsequently lost this capability. How will the update impact those whose maintenance has expired' yet still have to upgrade in order to avoid the license failure issue? Does this mean I update them, they get the 3CX SMTP server like it or not and then when then the maintenance goes away once the upgrade period has ended (10/30?) they are left with no email capability?
Additionally, for those not with maintenance and on the older versions, what is the recommended path with regard to FQDNs and Certs that were not a factor then, but come into play with the upgrade? What happens when these expire?
They will not renew or upgrade at this time, so suggestions to do so are not helpful. I am merely trying to get the clients up to date with as little pain (to me as well) as possible and still retain the functionality they were sold when they originally bought the system(s).
I have a couple who used streaming MOH and when v14 removed that function, they elected to stay with 12.5 as it meant that much to them. Others are smaller independent hotels without the PMS option (at the time) and the room status was visible via the hotel module, but not in v15.5 where a PMS is required. It became a cost issue where adding a PMS to see the room status was not worth it.
Thanks
