v16 update 2 - New SBC

[manfer]

I'm trying to test new SBC functionality on current beta.

I have already updated a 3CX PBX to v16 update2.

Now I'm trying to configure the SBC on that PBX so I can see it on Trunks list. Current one is an SBC on a raspberry PI.

Reading the document https://www.3cx.com/docs/3cx-tunnel-session-border-controller/ looks like the easiest way is to just upgrade the SBC following the instructions at the end of that document. But when I run the command

sudo apt -t testing upgrade 3cxsbc

I get the following error message

E: The value 'testing' is invalid for APT::Default-Release

What's wrong? I can remove and install the SBC Beta but I prefer to learn how to do an upgrade.

 

[AWS2P]

Hi,
I have same behavior, get stuck same as you to testing value is invalid

 

[AWS2P]

Finally, i got SBC to be updated , it was my stupid fault , even with steps under my eyes i started looping from step 2 each time.
So doing all like it should have be done, Works !

 

[manfer]

I read the error message again and if I understand correctly it is just complaining about a missing repository source.

So decided to download the new version of the installer 3cxsbcV16.zip to try to unzip it and see if it contained the sources. But that file can't be unzipped.

So payed a little more attention to the command used to install sbc on linux and I can see is just a wget command that downloads a file 3cxsbcV16.zip which is just piped to bash. So that indicates me 3cxsbcV16.zip is just a bash script. Not sure why has been decided to use .zip on that filename.

We can read on the script:

        aptlist=/etc/apt/sources.list.d/3cxpbx.list
        apttestinglist=/etc/apt/sources.list.d/3cxpbx-testing.list
        machine_arc=$(dpkg --print-architecture)
        tcxurl=http://downloads-global.3cx.com
        echo "deb $tcxurl/downloads/debian stretch main" > $aptlist
        echo "deb [arch=$machine_arc] $tcxurl/downloads/debian stretch-testing main" > $apttestinglist
        wget -t 1 -T 10 -qO - "$tcxurl/downloads/3cxpbx/public.key" | apt-key add -

Where we can see on new version there are two repositories. One in 3cxpbx.list file and other in 3cxpbx-testing.list.

So first I run

dpkg --print-architecture

To find out which is the architecture string on a rasperry-pi. I thought that was going to spit arm64 but the result was armhf instead.


Then I just copy the 3cxpbx.list which already is on my system to 3cxpbx-testing.list to reduce the typing later.

sudo cp /etc/apt/sources.list.d/3cxpbx.list /etc/apt/sources.list.d/3cxpbx-testing.list

Then I open the file to edit it with nano

sudo nano /etc/apt/sources.list.d/3cxpbx-testing.list

And I change the line there that reads

deb http://downloads.3cx.com/downloads/debian stretch main

to:

deb [arch=armhf] http://downloads.3cx.com/downloads/debian stretch-testing main

I save the changes on the file and I'm done. I have the testing repository configured.


Now I can run:

sudo apt-get update
sudo apt-get -t testing upgrade 3cxsbc

Once it is upgraded read the messages. It asks to restart 3cxsbc and rsyslog

sudo systemctl restart 3cxsbc
sudo /etc/init.d/rsyslog restart

 

[AWS2P]

Here it is !!

 

[manfer]

With the upgrade process I mention the SBC has appeared automatically on the PBX with the naming convention explained on the docs.

sbc.xxxx.xxxxx

Then I had to do the last step "Push Config". As explained on the last sentence of the upgrade process.

Manually upgrading a legacy SBC to the latest version on Linux, automatically creates the respective SBC connection in 3CX “Management Console” > “SIP Trunks”. Once the SBC connection in created, in order to complete the SBC upgrade, you need to select it and “Push Config” to re-configure remotely. After re-configuration, IP phones connected via the SBC connection are available for use.

Knowing if a SBC is alive or not and its public and private IP is just great.

 

[AWS2P]

Now new question
what are the new credentials to SSH SBC ?
my old are no more working
Tryed with this with no more luck

 

[manfer]

I don't think the linux PAM credentials are changed at all. If you are using a pi, are you sure you are not trying to ssh with root user by mistake? I make that mistake a lot.

I'm still in a ssh session to the pi. But I have just opened other one to confirm the credentials have not changed.

The password you see on 3CX SBC under trunks list is just that SBC tunnel password. You can check that by reading the file /etc/3cxsbc.conf

 

[AWS2P]

You are right on target Manfer, finally i tried once more with my old Pi credentials and it logs me in.

Humm... So what is the use of Name & Pwd fields in my screenshot?

In 3CX console SBC name changed but in real on SBC it's always the previous one, credentials are also always the old one.

Is this normal way ?

 

[manfer]

If you didn't do it already you have to force the reconfiguration of the SBC. On the trunks list you select the SBC and you use the "Push Config" button.

Then if you read on the pi the file /etc/3cxsbc.conf you can understand each field meaning.

The password is just the tunnel password. That password was previously only one tunnel password shared by all SBCs used on one PBX and was configured under Security->Tunnel Password.

And the KEY Authentication ID looks just for the provisioning url. Not sure if it means something else too.

 

[AWS2P]

Yes, already pushed the config, but I didn't searched in linux config files because i'm not a guruX at all. My linux knowledge is too poor to investigate alone without expert assistance.
Thanks for all details you give us.