SBC not registering - no obvious error

[A.Takacs]

Just moved a setup for self hosted / on premises to hosted.

Everything went fine up to setting up the SBC.

We want to use a Debian based SBC. Followed the instructions and deployment was uneventful - went exactly as documented.

But the SBC apparently does not register (red in the admin console, no “local IP”).

I can connected to SBC via SSH. I can ping various internet hosts (such as 8.8.8.8) but not the the instance fqdn (which resolves correctly but probably is not responding to ping ?).

What more diagnostic could I run ? Is there any local log I could check ? Can I run a script to re-run the registration ?

Any info most welcome

Best regards

 

[A.Takacs]

Further update - I re-deployed the SBC from scratch. When connecting it to the instance I deliberately entered a bogus key and I got - as expected - an error message to the extent that the instance is not accepting this key. So the SBC is indeed communicating with the hosted instance.
I then entered the correct key which was accepted. Still not registered as per above.

 

[SteveITS]

Check /var/log/3cxsbc.log on the SBC?

Did you check the SBC public IP is not blacklisted? Try adding it as Allow.

 

[A.Takacs]

Thanks

Ok seeing this

CRIT | 20240219-164745.820 | 3CX | SBC | 139671464273856 | Log.cpp:158 | ====================== 3CX SmartSBC 18.1.36 @ sbc-dn-01.domain.local ======================
CRIT | 20240219-164745.820 | 3CX | SBC | 139671464273856 | Log.cpp:159 | Log started: type = file, level = ERR, size = 104857600, resip = ERR, remote = -1
ERR | 20240219-165000.193 | 3CX | SBC | 139671464273856 | Tools.cpp:95 | Failed to connect to 64.225.65.151:5090, error 110
CRIT | 20240219-165000.196 | 3CX | SBC | 139671464273856 | Bridge.cpp:28 | System Clock: resolution 0 microseconds, not monotonic
ERR | 20240219-165000.197 | 3CX | RESIP | 139671464273856 | ssl/Security.cxx:268 | Error calling stat() for /var/lib/3cxsbc/.sipCerts: No such file or directory
ERR | 20240219-165010.228 | 3CX | SBC | 139671464273856 | Dns.cpp:16 | [DNS] Got no answer during 10 sec., SRV resolution failed
ERR | 20240219-165010.228 | 3CX | SBC | 139671464273856 | TunnelTcp.cpp:190 | Failed to resolve DNS SRV record for tunnel connection to myinstance.3cx.ch
ERR | 20240219-165020.297 | 3CX | SBC | 139671464273856 | Dns.cpp:100 | [DNS] Got no answer during 10 sec., host resolution failed
ERR | 20240219-165020.297 | 3CX | SBC | 139671464273856 | TunnelTcp.cpp:207 | Failed to resolve host name myinstance.3cx.ch
ERR | 20240219-165020.297 | 3CX | SBC | 139671464273856 | TunnelTcp.cpp:265 | Failed to resolve connection FQDN myinstance.3cx.ch
CRIT | 20240219-165020.297 | 3CX | SBC | 139671464273856 | RPiTunnel.cpp:373 | Running in console mode
ERR | 20240219-165035.344 | 3CX | SBC | 139671464273856 | TunnelTcp.cpp:305 | Bridge failure on while processing TCP: Connection timeout
ERR | 20240219-165050.390 | 3CX | SBC | 139671464273856 | TunnelTcp.cpp:305 | Bridge failure on while processing TCP: Connection timeout
ERR | 20240219-165105.433 | 3CX | SBC | 139671464273856 | TunnelTcp.cpp:305 | Bridge failure on while processing TCP: Connection timeout
ERR | 20240219-165120.479 | 3CX | SBC | 139671464273856 | TunnelTcp.cpp:305 | Bridge failure on while processing TCP: Connection timeout
ERR | 20240219-165135.526 | 3CX | SBC | 139671464273856 | TunnelTcp.cpp:305 | Bridge failure on while processing TCP: Connection timeout
ERR | 20240219-165150.568 | 3CX | SBC | 139671464273856 | TunnelTcp.cpp:305 | Bridge failure on while processing TCP: Connection timeout
ERR | 20240219-165205.610 | 3CX | SBC | 139671464273856 | TunnelTcp.cpp:305 | Bridge failure on while processing TCP: Connection timeout
ERR | 20240219-165220.654 | 3CX | SBC | 139671464273856 | TunnelTcp.cpp:305 | Bridge failure on while processing TCP: Connection timeout
ERR | 20240219-165235.701 | 3CX | SBC | 139671464273856 | TunnelTcp.cpp:305 | Bridge failure on while processing TCP: Connection timeout
CRIT | 20240219-165245.029 | 3CX | SBC | 139671464273856 | RPiTunnel.cpp:390 | Stopping: global connection timeout
CRIT | 20240219-165245.369 | 3CX | SBC | 139671464273856 | RPiTunnel.cpp:385 | ** Main console thread exits.

So a DNS resolution issue.

Is the SBC using other DNS than the one from underlying system - because I can actually ping myinstance.3cx.ch

 

[A.Takacs]

Ok I increased the logging level to VERBOSE and found out that I have some filtering on port 5091 outbound - solved !
So the registration was ok (443 I guess) but not the actual connection.