Debian Linux 9 SBC not showing phones

[voice11]

Hello there, a little help please.
My Debian SBC linux version 9 on ESXI 6.7 has been working just flawlessly with 3CX 16.0.4.504 on Vultr cloud for past couple year without a single hiccup.
Something happened last night and I had to restart my ESXI, and now my SBC shows-up but doesn't show/populate any phones that I can connect to 3CX cloud.

Very odd behavior. I have restarted VM as well as whole server countless times without an issue what so ever. Can someone shed some light to what might have gone wrong.
I don't eve know where to start.

 

[eddv123]

So the phones are already provisioned by the sounds of things, so either one of two things I believe are occurring:

* The registration requests are not reaching the SBC (run a Wireshark off the SBC to see).
* The tunnel from SBC to PBX is not connected - see the SIP Trunking section of the PBX - is it green

 

[princer800]

Have seen something si,iar where a firewall had sessions open on the firewall.IN the case of an SBC - which proxies - it would just be one.
Reboot the firewall if possible or a command/GUI to clear open sessions on the firewall>
We had something similair when we moved a VIrtual between hosts. Same Mac and IP - but open sessions had to be cleared. Weird.

 

[eddv123]

Whilst on the subject of networks also a DNS resolution failure from the local LAN would cause this behaviour. DNS failure causes the tunnel to drop and thus the connection to the PBX and registration.

 

[JohnS_3CX]

Hello there, a little help please.
My Debian SBC linux version 9 on ESXI 6.7 has been working just flawlessly with 3CX 16.0.4.504 on Vultr cloud for past couple year without a single hiccup.
Something happened last night and I had to restart my ESXI, and now my SBC shows-up but doesn't show/populate any phones that I can connect to 3CX cloud.

Very odd behavior. I have restarted VM as well as whole server countless times without an issue what so ever. Can someone shed some light to what might have gone wrong.
I don't eve know where to start.

So you have V16 on an ESXi machine hosted by Vultr?
And where is the SBC and what does it run on?
In the trunks section, is the SBC registered?
Have you rebooted the SBC machine?

 

[voice11]

So you have V16 on an ESXi machine hosted by Vultr?
And where is the SBC and what does it run on?
In the trunks section, is the SBC registered?
Have you rebooted the SBC machine?

Hello John, SBC is Debian 9 running local on ESXI 6.7.
Yes SBC shows registered. And yes I have rebooted SBC and the 3CX server several times. I also restarted services many times to no avail.

 

[voice11]

Thank you for all the replies. I am more comfortable with windows environment and not so much with Linux, especially when it comes to troubleshooting. For instance I know how to get logs & read them in windows but don''t really know how to get log report from Debain SBC...or even that is an option.
For that reason I installed another windows SBC as failover on the same host in a separate VM.
I was able to get the log report, it does show some error but I can't make sense of it.
Can someone see please and advise if it tells you to why connection is failing.

Thank you in advance.

CRIT | 20200401-152602.534 | 3CX | SBC | 2008 | log.cpp:158 | ====================== 3CX SmartSBC 16.0.390 @ ======================
CRIT | 20200401-152602.534 | 3CX | SBC | 2008 | log.cpp:159 | Log started: type = file, level = ERR, size = 104857600, resip = ERR, remote = -1
CRIT | 20200401-152602.542 | 3CX | SBC | 2008 | bridge.cpp:28 | System Clock: resolution 0 microseconds, not monotonic
CRIT | 20200401-152603.333 | 3CX | SBC | 2008 | rpitunnel.cpp:373 | Running in console mode
CRIT | 20200401-152603.495 | 3CX | SBC | 2008 | log.h:103 | Remote: fetch logs at level -1
ERR | 20200402-095729.599 | 3CX | SBC | 2008 | tunneltcp.cpp:587 | Socket error (6):
ERR | 20200402-095729.599 | 3CX | SBC | 2008 | tunneltcp.cpp:288 | Bridge failure 'error:00000006:lib(0):func(0):EVP lib' on TCP connection: secure read
CRIT | 20200402-095729.600 | 3CX | SBC | 2008 | log.h:103 | Remote: fetch logs at level -1
CRIT | 20200402-095730.671 | 3CX | SBC | 2008 | log.h:103 | Remote: fetch logs at level -1

 

[JohnS_3CX]

The above error would suggest that the SBC is not green on the management console (disconnected).
This can be due to a bad connection, something breaking TLS, or the PBX tunnel and/or tunnel port is down.

Regardless, if the SBC is green and you don't see phones that have just been reset, the issue may lie in the the multicast transmission between the phones and the SBC. The SBC listens for multicast from phones, and if one should arrive, it forwards it to the PBX which will make the phone appear in the Phones section in bold.

So either look into ensuring the tunnel between the SBC and PBX remains active ( no disconnection or low uptime) and if that is ok, then start investigating for any possible multicast filtering. The SBC and phones should be on the same subnet so they can see each other.

 

[voice11]

I have a good news and an update, phones are up with new failover windows based SBC. But it doesn't explain to what changed. I have exact same logs as i shared in my last post but after rebooting phones manually, they register with the new SBC, however still no luck with the first Debian SBC.

Old Debian based SBC worked perfectly from past couple years without a single issue. Windows was only installed today as a failover. Is there a way I can troubleshoot and generate logs for old SBC as well that I can share with you later. I am curious to know as windows server might not be always available in customer environment.
I feel lucky it happened internally, I can't imagine if it happened in one of our customer's environment.

 

[JohnS_3CX]

Since we changed the way the SBC works with V16 Update 2 (to make it manageable and upgradeable via the management console), if you have a much older version Debian SBC, just remove it and reinstall the latest version using our Debian ISO. It should come up online again and work as before, with the added benefit of monitoring and remote management plus some bugfixes.

https://www.3cx.com/phone-system/download-links/

 

[voice11]

Thank you John.
Just to confirm, there was a separate ISO download for Debain SBC before and separate ISO for server itself. Now its SBC is bundled with 3CX server. Is it the same ISO file for the purpose of SBC also.

 

[JohnS_3CX]

Yes exactly, our Debian ISO includes both the PBX and SBC, and you can pick what you want to install when you boot off of the ISO.

Since this is an SBC only machine, you can wipe the VM completely and install from scratch.