SBC upgrade to V18 not available

[AMistich]

So I upgraded from Windows OS V16 to V18 last week and I have one SBC that is remote. Since the upgrade to the PBX, the SBC has not reconnected. The SBC is on a Raspberry Pi 4. When looking over the instructions, it says I am able to upgrade the SBC from the management console, but that option is not available. I know the SBC is on the network as I can ping it and see it connected to the remote firewall. Unfortunately, I did not enable SSH to remote in and manually update. Does the SBC have to be connected to the PBX to upgrade it? If so, is there any other way to get it upgraded or do I need to manually connect to it?

 

[cobaltit]

There is no magic 3CX method to connect to the SBC. If it's not connecting to 3CX, 3CX can't tell it to upgrade. That being said, unless you changed a port or IP address the SBC should have reconnected. I would see if you can get someone to reboot that SBC and see if it reconnects. Otherwise it's SSH time!

 

[AMistich]

"There is no magic 3CX method to connect to the SBC." I am not looking for a magic method to connect to the SBC. I am looking for information on upgrading the SBC after the V18 upgrade as all the information I have ran across says it should have connected with V18. I wanted to verify if this is correct or not. I am not well versed in Linux/Debian so I do not know all the various methods to remote into a Raspberry Pi4.

Secondly if it is suppose to connect to the V18 PBX with the V16 SBC software, I am trying to find ideas on how to troubleshoot the issue.

No ports or IP addresses have been changed. The SBC has been rebooted multiple times and still no connection. As said in my initial post SSH was not turned on when it was setup or at least I am not able to create a SSH connection to it.

 

[adsl]

If you go into SIP trunks does the SBC show up, does it show a Green dot, and next to it does it say [UPDATE]

 

[NickD_3CX]

If what @adsl says does not show up, you would need to set it up from scratch, according to the guide:
https://www.3cx.com/docs/installing-pbx-raspberry-pi/
(you might as well just reformat the SD while you're at it...)

For your convenience, it would probably be a good idea to also enable SSH after you get it up and running.

 

[AMistich]

So it came back up for a few minutes and connected, I did the upgrade and it is not reconnecting again. I am guessing there is something else going on that is keeping it from connecting. It was just a coincidence that it happened when I did the upgrade. The other thing I am curious about is I should be able to get to the SBC web portal even if it is not connected to the PBX correct?

 

[NickD_3CX]

The other thing I am curious about is I should be able to get to the SBC web portal even if it is not connected to the PBX correct?

There is not SBC Web Portal....
The setup is done via command line for Debian and RPis.

 

[AMistich]

Ok that is a misunderstanding I had when I was at Step 5 - #4 of installing 3cx from this page: https://www.3cx.com/docs/installing-pbx-raspberry-pi/

1. When the 3CX installation is complete, run the configuration wizard:

• Using a Web Browser - Open the URL
  http://<device_ip>:5015
  .
• Using the command line

I thought both the PBX and the SBC could be configured using the web browser.

Thanks for the help and clarification.

 

[chili]

Ok that is a misunderstanding I had when I was at Step 5 - #4 of installing 3cx from this page: https://www.3cx.com/docs/installing-pbx-raspberry-pi/

1. When the 3CX installation is complete, run the configuration wizard:

• Using a Web Browser - Open the URL
  http://<device_ip>:5015
  .
• Using the command line

I thought both the PBX and the SBC could be configured using the web browser.

Thanks for the help and clarification.

The browser configuration part refers to when you actually install the 3CX PBX itself on the Pi as opposed to the SBC.

In Step 5#3 you choose 3CX SBC and then enter the provisioning URL and authentication key.
These can be found if you click on the SBC in the SIP Trunks portion of the management console.
(If there's no SBC there you have to add one.)

Check if the (remote) firewall is blocking it from connecting to 3CX.
I also recommend to enable ssh on the pi, this can even be done by inserting the micro sd in a pc and creating an empty file called "ssh" in the boot folder. (no file extension)

But basically if the web url and authentication key are correct, there's nothing else to configure on the pi related to 3CX. If it still doesn't work, it's likely a network issue.