SBC wont connect

[Alphabetic]

Hi Guys

I prebuild an SBC on a pi in house and it worked.

Took it to site and it doesnt connect.

Can ping google and 3CX.

from my laptop I can telnet to port 5090 on the 3CX.

Im suspicious the router is possibly doing something with the traffic (will need to do further diagnostics) but for now, has anyone got any suggestions?

No logs in 3CX to indicate the SBC has attempted connection..

ive reinstalled the SBC.

 

[AWS2P]

as you are experienced , not sure my questions may help you , but in case

What was prebuild state, as you said it was working? what do you mean by working?

on remote site did the Pi received a static IP ?
is the pbx FQDN resolved from this site ?
did you previously create in trunk section an item for new SBC ?

 

[Alphabetic]

I’ve been on site all day cabling in networking infrastructure and installing the sbc was the last thing needed. My whole body aches and I thought I’d throw the question out here so I can follow up on once I’ve been home and rested.
SBC has static, DNS is fine, yes I created a new SBC in trunk section. I’m going to do some more troubleshooting tomorrow on the SBC and get some logging going.
If I provision the SBC in-house then take to site it should just work should it not? I set up IP details on SBC before I switched it off.
Weird thing is, the SBC doesn’t complain about contacting FQDN when it’s going through SBC setup and when I look in the config file on the SBC it has got the password in there set by the pbx

 

[AWS2P]

did the Pi kept the same IP from the initial setting and when installed on final location?

 

[Alphabetic]

No I had it on DHCP when I set it up then static when I removed it.
But I’ve uninstalled SBC and reinstalled it twice with a static on site

 

[AWS2P]

in general sbc settings on console is there the right ip adress used by SBC now ?

 

[Alphabetic]

No none of that, it’s red.
im suspicious it’s not getting out the network but curious to know how it’s picking up it’s password from the PBX

 

[AWS2P]

from initial in house site was the Pi connected to pbx ?

 

[AWS2P]

If I provision the SBC in-house then take to site it should just work should it not? I set up IP details on SBC before I switched it off.

not sure what to take care in that case , almost same ip that seems obvious but don't know if it's enough.
Never done this way, my Pis are set directly with their definitive settings

 

[AWS2P]

Most of the time I replicate same ip range behind a 4G router where I set my pi, when done, I go on remote location connect it to the LAN , done.
Never encountered a problem doing like this

 

[Alphabetic]

Yes and it worked as expected. I assumed I could then just up and take it as long as the Pi was on the internet the SBC would connect. I believe it’s the router but not sure what really as far as I’m aware all outbound is allowed, any ALG is off - it’s from the ISP

 

[AWS2P]

first you said it was in DHCP, then static but is the static ip kept in console in sbc settings or the one while it was using DHCP ?

 

[AWS2P]

if i'm not wrong remote router just need let access to tunnel port 5090, 5001, 443

 

[Alphabetic]

Do you know if SBC log location has changed? I have it down as var/log/3cxsbc.log but i've got one in var/log/3cxsbc/3cxsbc.log and it's empty.

 

[Alphabetic]

Answered my own Q

 

[Alphabetic]

Changed it to VERBOSE and the log is completely empty :/

 

[Alphabetic]

Okay so.. I ran through the DHCPC.conf file again and removed the router IP as the primary DNS and just had it as Google's DNS and gave it a reboot.

SBC now showing as online in 3CX but I can no longer SSH to it externally.

- Does the provision disable SSH?
- Does provision change logging leval to what's specified in 3CX as that would explain why it kept going back to ERR when I was setting it to VERBOSE.

I dont understand why there was nothing in the event logs once I changed it to verbose (unless once i started the service it pulled config and set back to ERR)

 

[cobaltit]

Networking strikes again!

What does can no longer SSH to it externally mean? From outside the network to the Pi? That would require port forwarding on the router. No provisioning does nothing with SSH.

 

[Alphabetic]

I had set up SSH and had port forwarding, that's how i was accessing it before I changed the DNS. Not sure why changing the DNS would stop me accessing the Pi and I still dont know why there was no logging recorded

 

[Alphabetic]

Ok the plot thickens.

After I couldnt get on to it remotely I tried to access it locally and couldnt.

It now has an IP via DHCP - Dont know why.. here is my dhcpcp.conf file..

I dont know whats going on but the phones connected via SBC (set to 192.168.1.250) are working?!