Random Register failed - Error 10053

[Uptime]

Hi all,

Running the latest version of 3CX on a 3CX partner hosted instance.

I have a pc running windows 10, running the latest "3CX App for Windows" (the file 3CXPhoneforWindows16.msi).

Two PCs with two different extensions, one pc may provision ok for a while, but then randomly after a few mins it reports "register failed / service unavailable".

It may remain in that error state for a random period of time, maybe 15mins? And then register again, work again for 5-10mins, then once again fail to register.

The other pc, on the same LAN, has no issues at all.

In the 3CX logs, it reports this:

[05.09.2022 16:52:51.963][18] 3CXTunnel: Bridge 3 MultiplexerImpl: couldn't send packet header to TCP destination, error 10053
[05.09.2022 16:52:51.963][18] 3CXTunnel: Bridge 3 Tunnel sent SIP packet, result: 0, queue size: 1
[05.09.2022 16:52:53.966][18] 3CXTunnel: Bridge 3 MultiplexerImpl: couldn't send packet header to TCP destination, error 10053
[05.09.2022 16:52:53.966][18] 3CXTunnel: Bridge 3 Tunnel sent SIP packet, result: 0, queue size: 1
[05.09.2022 16:52:55.977][18] 3CXTunnel: Bridge 3 MultiplexerImpl: couldn't send packet header to TCP destination, error 10053
[05.09.2022 16:52:55.977][18] 3CXTunnel: Bridge 3 Tunnel sent SIP packet, result: 0, queue size: 1
[05.09.2022 16:52:57.979][18] 3CXTunnel: Bridge 3 MultiplexerImpl: couldn't send packet header to TCP destination, error 10053
[05.09.2022 16:52:57.979][18] 3CXTunnel: Bridge 3 Tunnel sent SIP packet, result: 0, queue size: 1

EDIT: For the past few hours it was randomly saying the above error messages, but has not done it for about 30mins now.

Anyone have any ideas what this might be?

Thank you.

 

[JohnS_3CX]

Hello,

Can you also try the latest Desktop App (not the legacy client you are using now) and see if the problem persists for that PC?

 

[Uptime]

Hi John,

thanks for your response.

I didn't know there was a different / newer app. I've installed that Desktop App now (3CXDesktopApp-18.9.933.msi) and will see how it goes.

I assume that moving forward, that one is the one to use, and the other application is deprecated?


Thank you,

Vlad

 

[JohnS_3CX]

Hi Vlad,

Exactly, this has been out for a while now and is the one we are actively developing, while the other one has become legacy.

Also note that this one works directly via HTTPS so it may actually end up bypassing whatever the issue was anyway.

Let me know whether this has solved the problem for you.