Failed to Send APN Push.

[TayZaLinZaw]

Our customer installed 3CX Version 18 Update 8 (Build 939). They have a issue like in Pic 1. Even when calling ext to ext on the mobile client, it doesn't come in as an internal call, it comes in with the DID number. One thing I am worried about is because of the update. I think if update 9A is installed, they use unsupported Cisco IP phones, so it will have a bad impact. That's my thoughts.

 

[Guillaume Bourgeois]

Is this the same client who installed the VPN directly on the 3CX server?

https://www.3cx.com/community/threads/vpn.129295/#post-616480

 

[TayZaLinZaw]

Is this the same client who installed the VPN directly on the 3CX server?

https://www.3cx.com/community/threads/vpn.129295/#post-616480

Another Customer sir, I am worried about the Update version.

 

[Guillaume Bourgeois]

update. I think if update 9A is installed, they use unsupported Cisco IP phones, so it will have a bad impact. That's my thoughts

Explain this to your client, simply:

Using unsupported hardware poses a risk with each update, which is why we specify "not supported." If your client wants peace of mind, they should consider paying to replace their phones. @Fanvil Technical Support, in particular, offers very interesting products for all budgets.

Otherwise, they must accept the risks associated with potential failures.

If the phones are "local" to 3CX or use a VPN (router to router) to connect to 3CX, the risks are quite low, though not zero. Similarly, if the phones utilize a "3CX SBC" to connect, the risks remain low, though not nonexistent.

Finally, if the phones are remote (aka STUN), the update to 9A should not affect them. The update is minor and only intended to replace the certificates.
https://www.3cx.com/blog/change-log/phone-system-change-log-v18/

However, once again, it will be necessary to thoroughly test the devices after the update.

 

[Vali_3CX]

@TayZaLinZaw
V18U8 certificate expired one month ago, you need to install V18U9A. I would highly recommend to start preparing to migrate to V20 anyway.

 

[TayZaLinZaw]

Explain this to your client, simply:

Using unsupported hardware poses a risk with each update, which is why we specify "not supported." If your client wants peace of mind, they should consider paying to replace their phones. @Fanvil Technical Support, in particular, offers very interesting products for all budgets.

Otherwise, they must accept the risks associated with potential failures.

If the phones are "local" to 3CX or use a VPN (router to router) to connect to 3CX, the risks are quite low, though not zero. Similarly, if the phones utilize a "3CX SBC" to connect, the risks remain low, though not nonexistent.

Finally, if the phones are remote (aka STUN), the update to 9A should not affect them. The update is minor and only intended to replace the certificates.
https://www.3cx.com/blog/change-log/phone-system-change-log-v18/

However, once again, it will be necessary to thoroughly test the devices after the update.

They use both inbound and outbound. I think we should have warned them in advance about the consequences that could happen if we update.

If we update v20, can we update it with backup and restore or can we update the official release version as an auto update? I would like to know the timeline of the office release version.

 

[Guillaume Bourgeois]

Are you referring to the 3CX PBX server version on Windows?

 

[TayZaLinZaw]

Are you referring to the 3CX PBX server version on Windows?

Yes, I mean 3CX V20 official release version as an auto update or backup and restore .

 

[Guillaume Bourgeois]

On Windows, no, it's not possible to automatically upgrade to v20 without having to do a full backup, uninstall 3CX v18, install 3CX v20, and then restore the backup.