IMPORTANT: Apple APNS certificate renewal reminder

[Vali_3CX]

Just an important reminder:

Be sure your PBX has the latest, up-to-date Apple APNS certificate installed.

Otherwise, on October 9th, when the old certificate expires, suddenly you will get complaints "my iPhone is no longer ringing, my iPhone no longer get notifications".
Please be advised.

Thank you!

 

[Vali_3CX]

Check also if this does not help, I searched for the same error code as yours, 50020 and I found this:
https://www.3cx.com/community/threa...-to-device-iphone-push-sender-id-50020.80846/

 

[Leroux.Steeve]

We'll check tomorrow our firewall part too. We are flooded too by the following message :



I have not the hand on the firewall now. My colleague will check that tomorrow morning.

Thanks for your help

 

[Vali_3CX]

@Leroux.Steeve
If tomorrow morning still not work, then I would ask you to set the PBX in verbose mode, then make a call an send a chat message to this iPhone, then from Management Console top bar/Support menu generate a support info and share it with me via PM (put it on a shared drive, dropbox etc) so we could have look here.
Thanks!

 

[Vali_3CX]

@Leroux.Steeve
Also your colleague may have a look at this, IPv6 related:
https://www.3cx.com/community/threa...ot-be-established-see-inner-exception.116727/

 

[Leroux.Steeve]

Hello @Vali_3CX ,

We found a "smart" workaround for the issue. We took the pfx file aps_production.pfx (version 130424) and version.txt from our backup. We put them in place of the "upgrade" version (version 132643). That fix the issue.
We think that there is something wrong between our 3CX version V18U4 and the certificate in version 132643.

Hope that will help.

 

[Vali_3CX]

Hello @Vali_3CX ,

We found a "smart" workaround for the issue. We took the pfx file aps_production.pfx (version 130424) and version.txt from our backup. We put them in place of the "upgrade" version (version 132643). That fix the issue.
We think that there is something wrong between our 3CX version V18U4 and the certificate in version 132643.

Hope that will help.

@Leroux.Steeve
Thanks for feedback!
However, the fix you made seems to be reverting to the old certificate which will expire in two days. So, as I advised above, from Management Console top bar/Support menu generate a support info and share it with me via PM (put it on a shared drive, dropbox etc) so we could have look here to figure out what's wrong.
Thanks!

 

[cristianbarbieri]

I would like to provide an update to the community of the problem encountered and reported by my workmate Steeve.
The 18U4 + version 132643 of aps_production.pfx has the problem reported (no call notification on iOS) but working with 130424.
We upgraded to 18U5 + aps_production.pfx 132643 and it is working.
We upgraded to 18U5 Patch1 + aps_production.pfx 132643 and it is working too.
Many thanks for your prompt action and to keep the forum very active.

 

[Vali_3CX]

@sgng
Thanks for spotting the date, I've corrected it.
What's your PBX version, including the build number, as in Management Console's Dashboard?

 

[Vali_3CX]

@sgng
I repeat, what's your PBX version as in Management Console's Dashboard? Including build number.
P.S We already provided certificate update since last week for V18U4 and about a month ago for V18U5.

 

[adconsulting]

Hi, we have

18.0 (Build 461) and the error is the same. I cannot put down production at this moment but if you have an hotfix, we can apply it and then upgrade this night. Thanks in advance. Davide

 

[Vali_3CX]

You should update your PBX to at least V18 U4, recommended latest V18 U5.

 

[bitn2]

can't communicate an important update on 3.10.2022 with wrong date.. (if it was the right date on 9.11.2022 time for updates were ok..)
but in whitin 6 days for the update..?
or myabe now, instantly.. sorry no chance..
the cert-hotfix should be done adhoc, so no reboot required...

we ^'ve different versions running... the one with "a not so happy customer" is on 18.0.2.314...

This version is nearly one year old. Why you didnt update? Thats not a 3cx problem...

 

[bitn2]

writing a wrong date for an important info is an 3cx problem for sure...

Thas right, but if you had your 3cx up2date it wont be a problem.

 

[Glen.c]

So what about clients on Pi versions that are stuck on update 2?

 

[Vali_3CX]

@mooseman
Unfortunately, it's deprecated: "We have already stopped updating 3CX v18 for Raspberry Pi users since Update 2"
https://www.3cx.com/blog/news/raspberrypi-migrate-startup/

 

[Marcel Odermatt]

Unfortunatly, the start up option is not a solution for our customers, because the provider is not supported and need a physical device for the siptrunk. So the only option is to have a 3CX onsite or change provider. But its not an option for everyone. So we have to sell a new pbx for customers wo ivested in a raspberry pbx just a year ago. I hoped we can let them on v18u2 at least for some time...

 

[bitn2]

Unfortunatly, the start up option is not a solution for our customers, because the provider is not supported and need a physical device for the siptrunk. So the only option is to have a 3CX onsite or change provider. But its not an option for everyone. So we have to sell a new pbx for customers wo ivested in a raspberry pbx just a year ago. I hoped we can let them on v18u2 at least for some time...

Any tiny pc will be good for 3cx. Sometimes they are cheaper than a Raspberry.

 

[Marcel Odermatt]

I doubt that you got a Intel Nuc or Shuttle PC under the price of a Raspy. I'm just a little disappointent. First they drop the support of the raspberry, after they promoted it like it is the future. And now it would just be an update for the apple certificate, wich they could release with ease

 

[bitn2]

I doubt that you got a Intel Nuc or Shuttle PC under the price of a Raspy. I'm just a little disappointent. First they drop the support of the raspberry, after they promoted it like it is the future. And now it would just be an update for the apple certificate, wich they could release with ease

I understand your problem, but its really no problem to get an tiny pc for this price. You dont need an Intel Nuc or something expensive stuff like this.

 

[AWS2P]

I use lots of second hand micro pc DELL, HP with new SSD and 8Gb of Ram and never got any problem. Cost is really near Rpi and when they are found somewhere in stock