Solved v20 SBC doesn't connect to 3CX FREE hosted, but to on prem 3CX v18

[bad_joker]

Hi there,

I'm trying to set up a small 3CX FREE Hosted by 3CX, but to connect my desk phone (Snom D375) I need a SBC.

3CX works fine with android app, I can do what I want to.

But my fresh installed SBC linux VM won't connect to my 3CX free hosted.

SBC is latest version, 3CX SmartSBC 20.0.100

I can connect the SBC to an on prem v18 3CX from a customer without any problems, gets green in the SIP-Trunks immediately.

Tried already "SecurityMode=1" and "SecurityMode=0" via the 3cxsbc.conf.local, but no difference at all. Also set "LocalSipAddr=" to my local IP (192.168.1.90), also no change. I set "Level=DEBUG" to see everything important, but no clue what's the problem at all.

Main problem seems to happen here:

ERR | 20240702-190202.215 | 3CX | SBC | 0x7f69b3a21800 | TunnelTcp.cpp:621 | SSL error (104):
ERR | 20240702-190202.215 | 3CX | SBC | 0x7f69b3a21800 | TunnelTcp.cpp:305 | Bridge failure on while begin to read a packet from tunnel: Connection reset by peer
WARNING | 20240702-190202.215 | 3CX | SBC | 0x7f69b3a21800 | security.cpp:1178 | === TCP Statistics: uptime 0 sec, KA rx/tx 1/1, bytes rx/tx 8/79, elapsed ms rx/tx 0/14
WARNING | 20240702-190202.215 | 3CX | SBC | 0x7f69b3a21800 | TunnelUdp.cpp:372 | === UDP Statistics: Passive, downtime 6 sec, UDPA rx/tx 5185/5185 sec ago, bytes rx/tx 0/0, queue tx 0, skip tx 0
NOTICE | 20240702-190202.215 | 3CX | SBC | 0x7f69b3a21800 | TunnelTcp.cpp:330 | Closing TCP socket
NOTICE | 20240702-190202.215 | 3CX | SBC | 0x7f69b3a21800 | security.cpp:1171 | TCP Accepted -> Invalid
NOTICE | 20240702-190202.215 | 3CX | SBC | 0x7f69b3a21800 | security.cpp:613 | TLS Prepared -> NonSecure
NOTICE | 20240702-190202.215 | 3CX | SBC | 0x7f69b3a21800 | TunnelUdp.cpp:45 | close: Passive -> Closed
WARNING | 20240702-190202.215 | 3CX | SBC | 0x7f69b3a21800 | Bridge.cpp:228 | Tunnel disconnected.

Full logfile is attached. I removed important information.

Any help is appreciated.

 

[bad_joker]

Problem is solved, I guess my IP from my ISP where the SBC runs was on a blacklist