How to handle laggy calls, getting warning emails on "Trunk SBC...has changed status to up"

[lcchai]

I am using 3cx hosted on AWS, and in restaurant using SBC running on Windows 10, we encountered laggy calls a while back and after tweaking with windows, to disable MS Defender real time protection, the issue was resolved, but recently the issue resurface again. I can't figure out what is the issue, anyone can help? We are using DELL pc with 8GB ram running Windows 10 Pro, and the PC is purely for SBC. There are only 5 phones connected, although I found from the backend that the phones are no longer supported, from Snom.
From the SBC log file, I am seeing a lot of SSL error(5)

CRIT | 20240125-091640.010 | 3CX | SBC | 3192 | Log.cpp:158 | ====================== 3CX SmartSBC 18.1.36 @ DESKTOP-P4A6656 ======================
CRIT | 20240125-091640.040 | 3CX | SBC | 3192 | Log.cpp:159 | Log started: type = file, level = ERR, size = 104857600, resip = ERR, remote = -1
CRIT | 20240125-091640.048 | 3CX | SBC | 3192 | Bridge.cpp:28 | System Clock: resolution 0 microseconds, not monotonic
ERR | 20240125-091640.077 | 3CX | SBC | 3192 | UdpMulticast.h:55 | Failed to join interface 169.254.205.232 to multicast SIP group, error(10049):
ERR | 20240125-091640.077 | 3CX | SBC | 3192 | UdpMulticast.h:55 | Failed to join interface 169.254.11.143 to multicast SIP group, error(10049):
ERR | 20240125-091640.077 | 3CX | SBC | 3192 | UdpMulticast.h:55 | Failed to join interface 169.254.160.2 to multicast SIP group, error(10049):
CRIT | 20240125-091640.108 | 3CX | SBC | 3192 | RPiTunnel.cpp:373 | Running in console mode
ERR | 20240125-091850.207 | 3CX | SBC | 3192 | TunnelTcp.cpp:607 | SSL error (5):
ERR | 20240125-091850.208 | 3CX | SBC | 3192 | TunnelTcp.cpp:305 | Bridge failure on secure read: System error 10054: An existing connection was forcibly closed by the remote host.
ERR | 20240125-091923.982 | 3CX | SBC | 3192 | TunnelTcp.cpp:607 | SSL error (5):
ERR | 20240125-091923.982 | 3CX | SBC | 3192 | TunnelTcp.cpp:305 | Bridge failure on secure read: System error 10054: An existing connection was forcibly closed by the remote host.
ERR | 20240125-091930.097 | 3CX | SBC | 3192 | TunnelTcp.cpp:620 | Secure tunnel is failed. Error 3: TLS handshake failed: Unknown system error
ERR | 20240125-091930.097 | 3CX | SBC | 3192 | TunnelTcp.cpp:305 | Bridge failure on secure negotiation: TLS handshake failed: Unknown system error
ERR | 20240125-091930.097 | 3CX | SBC | 3192 | TunnelTcp.cpp:607 | Socket error (10038):
ERR | 20240125-091930.098 | 3CX | SBC | 3192 | TunnelTcp.cpp:305 | Bridge failure on while begin to read a packet from tunnel: An operation was attempted on something that is not a socket.
ERR | 20240125-092217.831 | 3CX | SBC | 3192 | TunnelUdp.cpp:221 | UDP channel has been silent for more than 30 seconds, temporarily disabling UDP
ERR | 20240125-092520.706 | 3CX | SBC | 3192 | TunnelTcp.cpp:607 | SSL error (5):
ERR | 20240125-092520.706 | 3CX | SBC | 3192 | TunnelTcp.cpp:305 | Bridge failure on secure read: System error 10054: An existing connection was forcibly closed by the remote host.
ERR | 20240125-093249.189 | 3CX | SBC | 3192 | TunnelUdp.cpp:221 | UDP channel has been silent for more than 30 seconds, temporarily disabling UDP
ERR | 20240125-093258.635 | 3CX | SBC | 3192 | TunnelTcp.cpp:607 | SSL error (5):
ERR | 20240125-093258.635 | 3CX | SBC | 3192 | TunnelTcp.cpp:305 | Bridge failure on secure read: System error 10054: An existing connection was forcibly closed by the remote host.
ERR | 20240125-093308.727 | 3CX | SBC | 3192 | Dns.cpp:16 | [DNS] Got no answer during 10 sec., SRV resolution failed
ERR | 20240125-093308.727 | 3CX | SBC | 3192 | TunnelTcp.cpp:190 | Failed to resolve DNS SRV record for tunnel connection to imperial-sg.3cx.asia
ERR | 20240125-093539.272 | 3CX | SBC | 3192 | TunnelUdp.cpp:221 | UDP channel has been silent for more than 30 seconds, temporarily disabling UDP
ERR | 20240125-093812.243 | 3CX | SBC | 3192 | TunnelTcp.cpp:607 | SSL error (5):
ERR | 20240125-093812.243 | 3CX | SBC | 3192 | TunnelTcp.cpp:305 | Bridge failure on secure read: System error 10054: An existing connection was forcibly closed by the remote host.
...

So I am receiving a lot of waning emails from 3CX telling me the interface status is up, all emails are the same, even when nobody is using the phones, like the whole 24 hours the system kept sending emails with the same content, "Trunk SBC ... has changed status to up".
Wondering if anyone can help?

 

[TheodorosG_3CX]

From the log errors i can see multiple issues. All of them are related with firewall/network as the SBC has connectivity issue with the PBX.

 

[N_G]

Get one snom router phone to replace the windows machine and get a much better Internet connection....

 

[lcchai]

Noone change settings on network/firewall for a long time, it was working fine, until recently. In fact we turned off firewall on the SBC computer.

 

[TheodorosG_3CX]

The fact that nothing has changed on the network does not mean that there is no issue.
Since the SBC cannot contact the PBX correctly this can also be an ISP issue for example. In any case this has to be checked from the SBC location network. Also consider using a router phone instead on an on-premise SBC. Check the complete list of the 3CX Supported Devices.

 

[SteveITS]

So I am receiving a lot of waning emails from 3CX telling me the interface status is up, all emails are the same, even when nobody is using the phones

Just to be clear the up alert triggers at every reconnect. The down alert triggers after five minutes. So you are reporting short connection drops. Packet loss? Switch port? Router? Cable? Not prioritized traffic? ISP routing issues? Etc.

 

[TheodorosG_3CX]

Correct, all the above can cause those disconnections however traffic analysis will give you more information here.