SBC restart after number of connection attempts reached

[bit101]

Hi togehter,

we´ve faced sproadically with the issue that the SBC Windows service is restarting by itself. We can see it in the logfile that this happens after this:

"ERR | 20210428-113456.038 | 3CX | SBC | 6192 | TunnelTcp.cpp:610 | Secure tunnel is failed. Error 1: Secure tunnel is not supported by peer (negotiation timeout)"

Does this happen when the internet connection is getting lost? If so it is possible to prevent the restart of the sbc service? Or if not possible can we set the tries up to 50 till
the service will restart? The SBC is locally on Windows 10 Pro to connect the phones to 3CX in the datacenter. What means "Secure tunnel is not supported by peer" ?


CRIT | 20210428-113453.727 | 3CX | SBC | 6192 | Log.cpp:158 | ====================== 3CX SmartSBC 16.2.24 @ ***PBX1.****.local ======================
CRIT | 20210428-113453.727 | 3CX | SBC | 6192 | Log.cpp:159 | Log started: type = file, level = ERR, size = 104857600, resip = ERR, remote = -1
CRIT | 20210428-113453.768 | 3CX | SBC | 6192 | Bridge.cpp:28 | System Clock: resolution 0 microseconds, not monotonic
CRIT | 20210428-113453.782 | 3CX | SBC | 6192 | RPiTunnel.cpp:373 | Running in console mode
ERR | 20210428-113456.038 | 3CX | SBC | 6192 | TunnelTcp.cpp:610 | Secure tunnel is failed. Error 1: Secure tunnel is not supported by peer (negotiation timeout)
ERR | 20210428-113456.038 | 3CX | SBC | 6192 | TunnelTcp.cpp:295 | Bridge failure 'Secure tunnel is not supported by peer (negotiation timeout)' on TCP connection: secure negotiation
CRIT | 20210428-113456.038 | 3CX | SBC | 6192 | Log.h:103 | Remote: fetch logs at level -1
ERR | 20210428-113605.158 | 3CX | SBC | 6192 | TunnelTcp.cpp:295 | Bridge failure 'Too long inactivity' on TCP connection: while processing TCP
CRIT | 20210428-113605.158 | 3CX | SBC | 6192 | Log.h:103 | Remote: fetch logs at level -1
ERR | 20210428-113608.008 | 3CX | SBC | 6192 | TunnelTcp.cpp:610 | Secure tunnel is failed. Error 1: Secure tunnel is not supported by peer (negotiation timeout)
ERR | 20210428-113608.008 | 3CX | SBC | 6192 | TunnelTcp.cpp:295 | Bridge failure 'Secure tunnel is not supported by peer (negotiation timeout)' on TCP connection: secure negotiation
CRIT | 20210428-113608.008 | 3CX | SBC | 6192 | Log.h:103 | Remote: fetch logs at level -1
ERR | 20210428-113614.028 | 3CX | SBC | 6192 | TunnelTcp.cpp:610 | Secure tunnel is failed. Error 1: Secure tunnel is not supported by peer (negotiation timeout)
ERR | 20210428-113614.028 | 3CX | SBC | 6192 | TunnelTcp.cpp:295 | Bridge failure 'Secure tunnel is not supported by peer (negotiation timeout)' on TCP connection: secure negotiation
CRIT | 20210428-113614.028 | 3CX | SBC | 6192 | Log.h:103 | Remote: fetch logs at level -1
ERR | 20210428-113620.020 | 3CX | SBC | 6192 | TunnelTcp.cpp:610 | Secure tunnel is failed. Error 1: Secure tunnel is not supported by peer (negotiation timeout)
ERR | 20210428-113620.020 | 3CX | SBC | 6192 | TunnelTcp.cpp:295 | Bridge failure 'Secure tunnel is not supported by peer (negotiation timeout)' on TCP connection: secure negotiation
CRIT | 20210428-113620.020 | 3CX | SBC | 6192 | Log.h:103 | Remote: fetch logs at level -1
CRIT | 20210428-113623.217 | 3CX | SBC | 6192 | RPiTunnel.cpp:390 | Stopping: Maximum number of connection attempts reached
CRIT | 20210428-113626.272 | 3CX | SBC | 6192 | RPiTunnel.cpp:385 | ** Main console thread exits.

CRIT | 20210428-113630.995 | 3CX | SBC | 8052 | Log.cpp:158 | ====================== 3CX SmartSBC 16.2.24 @ **PBX1.*****.local ======================
CRIT | 20210428-113630.995 | 3CX | SBC | 8052 | Log.cpp:159 | Log started: type = file, level = ERR, size = 104857600, resip = ERR, remote = -1
CRIT | 20210428-113631.025 | 3CX | SBC | 8052 | Bridge.cpp:28 | System Clock: resolution 0 microseconds, not monotonic
CRIT | 20210428-113631.038 | 3CX | SBC | 8052 | RPiTunnel.cpp:373 | Running in console mode
ERR | 20210428-113634.080 | 3CX | SBC | 8052 | TunnelTcp.cpp:610 | Secure tunnel is failed. Error 1: Secure tunnel is not supported by peer (negotiation timeout)
ERR | 20210428-113634.080 | 3CX | SBC | 8052 | TunnelTcp.cpp:295 | Bridge failure 'Secure tunnel is not supported by peer (negotiation timeout)' on TCP connection: secure negotiation
CRIT | 20210428-113634.080 | 3CX | SBC | 8052 | Log.h:103 | Remote: fetch logs at level -1

 

[bit101]

We get also this message in sbc log:

Bridge failure *TLS handshake failed: error:00000001:lib(0):func(0):reason(1)
and
Socket error (10038):

 

[ChrisC_3CX]

As you have noticed as well, based on the logs provided, the 3CX SBC service is restarting due to the continuous failed connection attempts. That said, the problem here is not that the 3CX SBC is restarting, rather that it is losing the connection with the 3CX PBX. Have you noticed any connection issues in general on the remote site where the 3CX SBC resides?

For starters, please provide the following relevant information so that we can get a better picture of your current setup:: https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Also, do you happen to have more than one 3CX SBC connected to this 3CX PBX on different remote sites? If yes, are they facing the same issue as this one or not?

 

[bit101]

Hi Chris,

yes they have from time to time internet connection issue.
So with other words that means that the sbc service is restarting because the innternet connection is getting lost?
Can we increase the value still the service will restart?

No, there are only one SBC on a Windows 10 pro virtual Machine at Hyper-V

 

[ChrisC_3CX]

That is correct, it is because it is losing the connection and reaching the maximum reconnection attempts. There is no way of increasing this value, I'd recommend simply looking into the connectivity issue on that site.