Phones in "no service" after SBC loses connection to the PBX

[guidoq]

Hello,

2 times in the past couple of days, we had a problem with a SBC losing connection then coming up again after a minute (I suspect connection problems). The yealink phoens provisioned through sbc don't show up in the console and display "no service" until the SBC vm is restarted.
the 3cx pbx is hosted on AWS lightsail, the sbc is installed in a esxi vm, it has been working fine the past 3-4 months.

here's the logs from the SBC:

ERR | 20221108-170300.678 | 3CX | SBC | 139887002621888 | TunnelTcp.cpp:305 | Bridge failure on while processing TCP: Too long inactivity
ERR | 20221108-170303.058 | 3CX | SBC | 139887002621888 | TunnelTcp.cpp:620 | Secure tunnel is failed. Error 1: Secure tunnel is not supported by peer (negotiation timeout)
ERR | 20221108-170303.058 | 3CX | SBC | 139887002621888 | TunnelTcp.cpp:305 | Bridge failure on secure negotiation: Secure tunnel is not supported by peer (negotiation timeout)
ERR | 20221108-170309.096 | 3CX | SBC | 139887002621888 | TunnelTcp.cpp:620 | Secure tunnel is failed. Error 1: Secure tunnel is not supported by peer (negotiation timeout)
ERR | 20221108-170309.096 | 3CX | SBC | 139887002621888 | TunnelTcp.cpp:305 | Bridge failure on secure negotiation: Secure tunnel is not supported by peer (negotiation timeout)
ERR | 20221108-170315.050 | 3CX | SBC | 139887002621888 | TunnelTcp.cpp:620 | Secure tunnel is failed. Error 1: Secure tunnel is not supported by peer (negotiation timeout)
ERR | 20221108-170315.050 | 3CX | SBC | 139887002621888 | TunnelTcp.cpp:305 | Bridge failure on secure negotiation: Secure tunnel is not supported by peer (negotiation timeout)
CRIT | 20221108-170318.853 | 3CX | SBC | 139887002621888 | RPiTunnel.cpp:390 | Stopping: Maximum number of connection attempts reached
CRIT | 20221108-170321.992 | 3CX | SBC | 139887002621888 | RPiTunnel.cpp:385 | ** Main console thread exits.

CRIT | 20221108-170330.607 | 3CX | SBC | 140610450888640 | Log.cpp:158 | ====================== 3CX SmartSBC 18.1.36 @ 3CX-SBC ======================
CRIT | 20221108-170330.607 | 3CX | SBC | 140610450888640 | Log.cpp:159 | Log started: type = file, level = ERR, size = 104857600, resip = ERR, remote = -1
CRIT | 20221108-170330.686 | 3CX | SBC | 140610450888640 | Bridge.cpp:28 | System Clock: resolution 0 microseconds, not monotonic
ERR | 20221108-170330.687 | 3CX | RESIP | 140610450888640 | ssl/Security.cxx:268 | Error calling stat() for /var/lib/3cxsbc/.sipCerts: No such file or directory
CRIT | 20221108-170330.747 | 3CX | SBC | 140610450888640 | RPiTunnel.cpp:373 | Running in console mode
ERR | 20221108-170333.089 | 3CX | SBC | 140610450888640 | TunnelTcp.cpp:620 | Secure tunnel is failed. Error 1: Secure tunnel is not supported by peer (negotiation timeout)
ERR | 20221108-170333.089 | 3CX | SBC | 140610450888640 | TunnelTcp.cpp:305 | Bridge failure on secure negotiation: Secure tunnel is not supported by peer (negotiation timeout)

3cxsbc.conf

# Automatically generated SBC config file.
# This file is rewritten on every restart so don't try to edit it.

[General]
ReconnectInterval=5 # seconds
PrintStatsInterval=60 # seconds
FailoverInterval=120 # seconds
GiveupTimeout=300 # seconds
Hash=1

[Log]
#Type=file # optional: cout, cerr, file (default), syslog (only for Linux)
Level=ERR # optional: NONE, CRIT, ERR, WARNING, NOTICE, INFO, DEBUG, STACK, VERBOSE
#Resip=ERR # optional: same as Level
#File=
Size=100M # limit file size (up to 4G): 0 - no limit, nU - n units (G for gigabytes, M for megabytes, K for kilobytes)

[Bridge/123456]
ID=123456
Password="*********" # must match SBC's password set in the MC
SecurityMode=1 # 0 - TCP, 1 - TLS
TunnelAddr=company.my3cx.it # remote 3CX Tunnel TCP address
TunnelPort=5090 # remote TCP port (default: 5090)
PbxSipIP=company.my3cx.it
PbxSipPort=5060
LocalSipAddr=0.0.0.0 # 0.0.0.0 to auto detect on start
LocalSipPort=5060
FirstRtpPort=20000
NumRtpPorts=64
ProvLink=*******

any ideas?

 

[bitn2]

This messages is because of your connection problems. You cant do anything against that. Just have a look on your connection problems.

 

[guidoq]

thanks,
the main problem is that when the connection between the sbc and the 3cx server is restored, and the sbc shows as up, the ip phones show "no service" until the sbc is restarted manually.

 

[SteveITS]

I seem to recall another thread about this topic relatively recently but don't recall when, sorry. We've not seen this issue at any client. One option might be to just reinstall it using the same IP.