Update 6 Alpha - The Next Generation 3CX!

[kenn10]

@kenn10

If running a fully 3CX supported setup everything should've been fine.

As a quick check:

• Check your specs and installed OS.
• Check resource usage and availability.
• Remove any 3rd party software.
• Check for any stopped 3CX services.

If you still need help, don't hesitate to start a new thread.

Note: Although thoroughly tested, Alpha/Beta releases are not meant for production environments but if this happens to be the case and you need to be up and running fast, just redeploy 3CX 18 U5 using your latest backup. You'll be up and running in no time.

Thank you. I ultimately did an apt update and that responded that I needed to

dpkg --configure -a

. After that, the update completed and I'm able to log in.

 

[ChrisC_3CX]

Can you set up more than 1 phone as an SBC to have redundant SBCs?

You can have more than 1 SBC phones on the same LAN just not as a failover per se, but as an additional SBC you can use for a second group of IP Phones. That's not to say that you can't use it for the rest of the IP Phones should your 1st SBC fail. All you would need to do is re-provision your phones to it, which is now dead simple to do.

 

[noord]

I agree with the others here, this all looks really nice!
Also the SBC on a phone is great news, I guess version 19 can be run completely on a phone

Looking forward to experimenting with the new groups though, that seems really useful, own office hours and things like that are really much appreciated. Until now we had to ‘hack around’ a bit with DID rules and ‘specific office hours’ for trunks or extensions, this seems much easier and simpler!
And also the Admin tab is very useful, it’ll save us quite some time because often we have to change routing or office hours for customers and now they can more easily do that themselves!

 

[illcsales]

I tried on another test server for the System Owner requirement seems you have no choice to but create a new extension and assign it to the System Owner to make the pink warning go away it would be good to know the logic here. Prior to creating the new user, I tried many times to assign the System Owner role to an existing user so as to not have to create a new user just for System Owner to no avail, it seemed to me there was an effort to get rid of the Root Credential, but it seems that you need a separate user which is basically the same as the root user in previous versions?

 

[Evolute IT]

if you set a phone as "router phone", does it show in the trunks/SBC section?

if not, this helps no bloat the interface will possible WFH scenario.

 

[pcwizarduk]

hi i set up the router phone but requires removing from the yealink RPS
this courses an issue where i have to ask them to restart phone type in ext number and code
would have been handy if i could keep on yealink rps and just auto provision once changed to a router phone

 

[CentrexJ]

if you set a phone as "router phone", does it show in the trunks/SBC section?

if not, this helps no bloat the interface will possible WFH scenario.

Yes it shows up under sip trunks as an SBC named like “Yealink T54W (225)” where router type configured T54W on x225. Then you can select it for normal phones going forward.

 

[Evolute IT]

Yes it shows up under sip trunks as an SBC named like “Yealink T54W (225)” where router type configured T54W on x225. Then you can select it for normal phones going forward.

Interesting!

 

[Sparky Bear]

I have installed update 6 alpha on a demo tenancy and noticed that the Yealink t53W phones updated to firmware 96.86.100.5 and couldn't roll back as it was "latest"
I had to cleanup the 100 firmware and manually install the .48 onto the phone

Setup was simple for the SBC phone via the webclient however as an MSP we work mostly in the admin portal not the webclient portal.

Is the SBC Phone coming to the Admin portal?

Additionally the highlighted settings in the phone we always change to Att Xfr, 5 min backlight and 30 min screensaver,
These options are not available in the webclient so if this is the direction 3CX is heading can we please get a default setting option to customise these as default or add them to the webclient (preferably both)


Lastly,
There is no way to add a second phone to the user using the web client,
this will cause limitations with a few customers that have desks at multiple sites as we can't use that phone as the router phone

Okay I lied, This is the last I swear,



Will we be getting REST API???

 

[Soli]

where is the messaging tab now? with the Facebook integration

 

[Soli]

The SBC phone will work on port 5001 and 5090?

 

[N_G]

Many great improvements Thank You.
Please clarify Root Credentials vs System Owner it appears that there is no symmetry in the alpha to assign an existing extension to the Root Credential user in the Root Credential page in Console Admin.
Is the plan to remove Root Credential page at some point and just use a User with System Owner because we got the pink flag requiring us to setup the extension after we upgraded, which we did but the Root Credential page is still there in security in Console Admin afterwords?

And @davide.bonavita

You have to assign at least one extension user on the system the "System Owner" role. This person has all the rights. The root user on the management console will continue to work and this will allow you to access the management console, but not admin pages on the webclient.

The System owner is the way to go. We will keep reminding you to to assign at least one extension system owner role until you do it, as at some point the management console root user will be replaced or set to the system owner role (to be the same person). But you have plenty of time to evaluate your options. As for when you can do it, you can do it from U6 (you cant do it in U5) nd it has to be done from the management console. From then onwards you can use system owner in web client. Please note the roles do not apply to the management console.

Just a note - only the current root user in the management console (i.e. the one configured as admin with password and without extension) can assign the system owner role to another extension user.

@noord - look forward to your feedback on our groups feature!

 

[N_G]

The SBC phone will work on port 5001 and 5090?

The recommended way to deploy 3CX is using the SBC on port 5090 and leave the secure HTTPS port to 443 for the web client

 

[N_G]

I tried on another test server for the System Owner requirement seems you have no choice to but create a new extension and assign it to the System Owner to make the pink warning go away it would be good to know the logic here. Prior to creating the new user, I tried many times to assign the System Owner role to an existing user so as to not have to create a new user just for System Owner to no avail, it seemed to me there was an effort to get rid of the Root Credential, but it seems that you need a separate user which is basically the same as the root user in previous versions?

You should be able to use an existing user, no need to create a separate one. If this persists then let us know and we will PM you for access to the system to check it out

 

[N_G]

@Sparky Bear Definitely more settings will be coming to the web client. You will have to move to the webclient over time for sure.

 

[AWS2P]

Hello,
Nice job on SP6, I just applied it like a breeze on a demo PBX and I wanted to follow root user creation using a specific extension number, but once in creation, console forced me to use extension 100 instead of what I wanted to use.
I tried with 5xx number to be able to use the same on all pbxs and have easy same number to remember to gain admin access.

Is there any reason why 100 is forced ?

 

[AWS2P]

Is there any reason why 100 is forced ?

My bad , after console validation it create the new extension with number I wanted, so no problem for me.

 

[illcsales]

You should be able to use an existing user, no need to create a separate one. If this persists, then let us know and we will PM you for access to the system to check it out

Nick Thank you for the clarification...
I had another system we use for testing; I tested the update this morning and it worked as expected. I am not sure why the flag did not clear last night immediately and despite logging in and out, clearly its coded to go away once assigned. Thank you also @JohnS_3CX for reaching out.
We all good here, looking forward to all goodness U6 provides!

 

[illcsales]

Any hope V1 will be able to become SBC in the future went the manual and found X7C and X4U supported V2 only?

• Fanvil V64, V65, V62, X4U-V2, X5U-V2, X6U-V2, X7-V2, X7C-V2, X210-V2 and X210i-V2

 

[JohnS_3CX]

Any hope V1 will be able to become SBC in the future went the manual and found X7C and X4U supported V2 only?

• Fanvil V64, V65, V62, X4U-V2, X5U-V2, X6U-V2, X7-V2, X7C-V2, X210-V2 and X210i-V2

At launch, the following phones are “SBC capable”:

• Yealink T53, T53C, T53W, T54W, T57W
• Fanvil V64, V65, V62, X4U-V2, X5U-V2, X6U-V2, X7-V2, X7C-V2, X210-V2 and X210i-V2

We will try to bring more in the future, but the models that aren't powerful enough will not make it into the list