Update 6 Alpha - The Next Generation 3CX!

[JohnS_3CX]

@Nick Galea

Will auto-provisioning support for the EOL Yealink Phones T46G, T48G, T56A be returning as mentioned in the previous post?

https://www.3cx.com/blog/news/yealink-firmware-release/

Yes, they will.

 

[JohnS_3CX]

I see to be missing the voice and chat option to setup SMS on my instance. I'm hosted.

The providers that support SMS can be configured from the trunk page's SMS tab. An example:
https://www.3cx.com/docs/manual/sms-text/

 

[JohnS_3CX]

The routing still works but its confusing when the truck says its going to extension system admin but the inbound rule says its goes to the group.
Is this a bug?

This is normal because we already had the ability to set the "catch all" main rule under the trunk settings to go to one destination, while actually controlling calls using the inbound rules which have a higher priority.

And if you see an Inbound Rule pointing to a Group, that's your clue that you should launch the Webclient Admin and manage the Group destinations from there onwards.

Also with all these changes to the groups is there now an actual group voicemail setup? What i mean by this is sending calls to a group and being able to upload your own audio file. Everyone in that group gets the voicemial on their phone and if someone listens to it the notifications disappears for everyone else?

This is a feature request, it can be posted in Ideas

Also with the new user roles. I can select a user to be a group owner and enable management console access but not allowing the access to edit the SIP trunks but even with these settings the user can still edit the trunks from withint the webclient. Am i missing something here or is this a bug?

The roles control the webclient access, the MC rights control the MC access.

To achieve what you want, you could set the Manager role instead of the Group Owner, which will hide the trunks from them in the WC too.

 

[N_G]

Thanks for the feedback

• Is there any plan to associate DIDs with a group for timings and holidays, but still allow it to have its own call routing (ie to its own DR/RG etc? For example a car yard with a sales number and a service number, each going to a different IVR, they'd be associated with the same group, but the only way I could see to handle this at the moment would be to create a group for each to handle routing.

No, you would have to make separate groups

• Is there a plan to set up holiday specific routing and messages for groups? I might be wrong but it appears at the moment that they're sent to the out of office rule.

Yes that is how it is now, we are looking into making a holiday route as well.

• I understand that an SBC is the preferred method of remote connectivity, and really appreciate the work that 3CX and the vendors have put into simplifying getting these on site with them being built into phones. I would strongly ask that Direct SIP capability not be removed however (even if 3CX stops supporting it), as we have a few deployments where installing an SBC isn't as simple, like retail chains where the only device on each site is a DECT base and handset for example, or WFH situations where a staff member has been given a low cost handset for their home office or "router phones". (or another solution of course if they really insist )

Existing will work. You can use the management console, but it will not appear in the web admin. It will remain unsupported and those WFH situations must use apps going forward at some point.

 

[CentrexJ]

No, you would have to make separate groups



Yes that is how it is now, we are looking into making a holiday route as well.

Existing will work. You can use the management console, but it will not appear in the web admin. It will remain unsupported and those WFH situations must use apps going forward at some point.

Are there plans from Yealink (or others) for a DECT base station to support the 3CX SBC? We do have some sites with Yealink DECT gear only, for now with a Raspberry Pi 3CX SBC. A DECT base with 3CX SBC would be very attractive and less cabling/devices for those customers.

 

[N_G]

@CentrexJ good point, we will ask yealink. If you can push from your side too.... two sides this always helps. I dont know about the architecture of a base station, this might be the issue. In general yealink is quite happy to do stuff as long as the architecture can handle it and the volume is there of course. I would think DECT base station is nice to have as a router phone.

 

[Thomas Six]

@KjetilSorby Well as soon as Snom completes its development & testing, yes they will be added on the first update, not sure if that will be U6.

I see that in release https://service.snom.com/display/wiki/10.1.137.15+Release this is available (XQI-1610: Support for the 3CX SBC tunnel feature, incl. new settings). So let's hope it will be available in U6. Because we realy need a solution for raspberry pi's which are not available anymore. We only want to work with snom, because all our other phones are snom.

 

[N_G]

@Thomas Six Maybe they made the entry, but the firmware did not pass our QA unfortunately. So we are awaiting for them to do it and then we can queue them for a retest. But we want to add snom support soonest. To be clear it will only be for the new 8XX models.

 

[velrusev]

Is there chance to see phonebook per group in MCM environment, beside company and personal ones ?

 

[velrusev]

Is there chance to see TLS / SRTP provisioning method for phones over public internet ?

 

[velrusev]

Will it be possible to restrict group admin of being able to add / remove extensions (users) into the group ?
Also in MCM environment, will it be possible to limit the number of simultaneous calls per group ?

 

[velrusev]

Also probably good idea: SIP ID to be unique per group, or a kind of speed dialing to be implemented in order users in different groups to be able to dial short number for extensions in their group -- useful both for MCM groups and for STARTUP ?
This can be simulated with loop trunk, outbound rule and DID entries, for example users of group 1 dial numbers like 101, 102, 103 -- these are expanded let say to 10101, 10102, 10103 (real extension numbers). When call is routed back via DIDs, caller-IDs like 1010x are shrinked to 10x. Same for users in group 2 -- their short numbers 101, 102, 103, .... are expanded to 20101, 20102, 20103, .... When call routed back: the number shown is again 101, 102, 103, ... -- valid for this specific group, and so on.
If this idea is implemented natively into 3CX design real multi-company functionality will be achieved

 

[N_G]

@velrusev Thanks for your feedback, to answer your questions

a. Yes there will definitely be a group phonebook coming soon
b. TLS/SRTP - The phone must be behind the SBC which handles encryption for all the phones.... Nonetheless this option will be considered in time.
c. Startup is licensed by users, not sim calls. Group admin should be able to add and remove users, thats the number one task of an admin... There might be more roles in future yes, you can post in the ideas forum.
d. I think a 5 digit extension is not a problem, so in our view we already have multi company functionality.....

 

[David Masters]

After a bit of troubleshooting, I have aT53W working as an SBC perfectly.

My issue was that the selected extension had 'Block remote phones using stun (Insecure!)' set. It took a while to discover as this new configuration isn't using STUN - but this switch prevents the handset as acting as an SBC.

U6 is brilliant, well done 3CX! - Just two questions

1. Is the 10 extensions per handset-based SBC a hard limit, and what is driving this number?
2. Are we now limited to 1 handset (IP Phone) per extension. It took me a little while to discover that I had to remove the existing IP Phone before I had the ability to add the new Router based IP Phone?

 

[N_G]

@David Masters Thank you for the heads up, much appreciated! We will look into this configuration matter, thanks for reporting.

In regards to the 10 extension behind SBC. Its not a hard limit, its just a recommendation. We are still collecting data. It depends a little on the phone processor, number of BLFs etc. But its safe to say that a network with more then 10 users might need a VM, Raspberry Pi or a small intel NUC type device for better performance. As the phones grow more powerful this might not be required but we will know more in say 3 months.

 

[ThePhone]

Fanvil X5U-U2 as a router phone doesn't configure as an SBC. I have been prompted for a username and password twice, entered the details, but then nothing.

I have looked at the phone menu as well, and I see only the provision URL, Authentication is missing.

Any ideas on what I am doing wrong?

 

[ThePhone]

I think that my issue is related that this phone has been previously auto-provisioned with a different instance and now I have to wait 14 days.
https://www.3cx.com/community/threa...rovisioning-static-provisioning-server.86458/

 

[JohnS_3CX]

Fanvil X5U-U2 as a router phone doesn't configure as an SBC. I have been prompted for a username and password twice, entered the details, but then nothing.

I have looked at the phone menu as well, and I see only the provision URL, Authentication is missing.

Any ideas on what I am doing wrong?
View attachment 33134

I will PM you so we can check something on your PBX.

 

[JohnS_3CX]

My issue was that the selected extension had 'Block remote phones using stun (Insecure!)' set. It took a while to discover as this new configuration isn't using STUN - but this switch prevents the handset as acting as an SBC.

That was probably just a coincidence I reckon. By default all extensions have the option set to enabled and it doesn't prevent the phone from connecting. That setting is specifically for remote phones connecting without an SBC via the 3CX public IP (ie. STUN phones)

General things to look out for if anyone is facing difficulties:

• You must choose Router Phone via the Web Client Admin (not the management console) when adding a phone to your user
• MAC and Model must be correctly entered
• You will get a pop up with your user and pass (and an email)
• The phone must be factory reset first (if it was previously configured to an extension)
• The phone must be running the latest firmware from our website
• It should ask for credentials during startup, but be careful when typing them in - switch keypad to "123"

 

[StanM]

A change, we found, in U6.
The rules for generating a strong authentication User ID, are now enforced.

Auth ID should be at least 10 characters long with no spaces and contain a lowercase letter, an uppercase letter and a digit

This is nice and secure, although not mentioned in the release notes and not always without impact.

Will there be a possibility to switch off the enforcement? (custom parameter?)
There are some real life situations of installations not supporting "strong" authentication user ID's

For example systems with users connected through a custom SBC?
This is something we see with large cordless phone installations.
Where these dect multi-cel systems have problems integrating with a 3CX system.
A custom SBC can overcome problems with call transfers etc.

If this change is permanent, it sure would be nice to know before the rollout of U6.