SBC not working on v18 Deb10 ISO

[Evolute IT]

Hi guys,

We did everything: changed PC, changed network switch, cable, SSD, etc. NOTHING WORKS.

We installed a brand new SBC in our office, running on an Acer laptop (i5, 8GB, 120GB SSD, so good machine still.) Debian 10 installed and the SBC installed as well.

However, the SBC cannot stay up more than 1sec. It crashes. Spitting out errors in the log for no reasons.



We tried different machines, recreating the USB installer, reformating the machine, all that at least twice each.

Now I am going nuts because none of our local deskphones are working because of that.

Any idea? The ".sipCerts not found" kinda freaks me out.

Next step: reinstalling the SBC using the Debian 9 ISO.

 

[ivank]

Check your DNS server. The logs say SBC cannot resolve your FQDN.

 

[Evolute IT]

Check your DNS server. The logs say SBC cannot resolve your FQDN.

DNS are Google's. I even tried Cloudflare's. They work on my PC and my server and all the other local devices. Except the SBC, and I tried multiple machines with different network cards plugged in different ports/switches.

My DNS is definitely not the issue.

 

[ivank]

Can you resolve your FQDN from the SBC host?

 

[Evolute IT]

Yes, it does resolve. For some reason, the SBC is now connected but keep this opened as it could reoccur anytime now. The DNS it's currently using are 1.1.1.1 and 8.8.8.8.

That being said, everything else was working beside the SBC up until the DNS decided to work again. No idea why and CF doesn't seem to have any outages on their DNS (it would failover to 8.8.8.8 anyway.)

 

[Saqqara]

I would remove 1.1.1.1 dns and only use 8.8.8.8 and 8.8.4.4

 

[Evolute IT]

I would remove 1.1.1.1 dns and only use 8.8.8.8 and 8.8.4.4

I'm curious: why?

 

[RCT-CP]

The error message about DNS specifically states it cannot locate SRV records. For grins I checked my 3CX domain for SRV records and there are none. Mine is a 3cx.us FQDN. I wasn't aware of 3CX using SRV records in DNS lookups, but I could be mistaken. I've seen those used in my legacy systems that when an endpoint asks "how do I reach my SIP server and what port" - scratching my head on this one.

I do however see the same error in my logs when I had a WAN outage, and the SBC couldn't reach the hosted PBX.

Edit:
The ".sipCerts not found" is also in my logs and as far as I can tell no issue here.

 

[ChrisC_3CX]

The error message about DNS specifically states it cannot locate SRV records. For grins I checked my 3CX domain for SRV records and there are none. Mine is a 3cx.us FQDN. I wasn't aware of 3CX using SRV records in DNS lookups, but I could be mistaken

We actually do have SRV records for the 3CX tunnel. To perform an SRV query you can use _3cxtunnel._tcp.FQDN

@ConceptsWeb
Could you maybe try on the SBC Host and let us know what you get:

dig srv _3cxtunnel._tcp.FQDN