v16 Release Candidate: Getting Ready to Launch

[nb]

We will check and get back to you. Thanks for reporting.

Hi, we checked on T58 (running the same FW version) and DTMF generation using all DTMF types works perfectly - we even added SRTP to the mix to complicate things even more and everything works.
I would contact yealink at this stage. Just get another phone and prove to them that with another phone DTMF works. Then show what happens on the T58.

 

[nb]

Found something else out with Office 365. Some of our office 365 users were not showing up in our list of users to chose from under contacts and calendar within 3CX. Apparently, if you office365 account is older then 2014, the AD attribute "Usertype" is missing information. It should say "Member" I found an article that shows you how to fix this. This fixed my issue and now I can see all my AD users in 3CX. I thought I would share this. Not sure this is the best place though.

https://www.ronnipedersen.com/2017/10/30/missing-usertype-attribute-in-azure-ad/

Here are my before and after results using get-msoluser command.

Before Version
UserThemeIdentifierForO365Shell :
UserType :
ValidationStatus : Healthy
WhenCreated : 5/13/2011 3:41:47 AM

Fixed Version
UserThemeIdentifierForO365Shell :
UserType : Member
ValidationStatus : Healthy
WhenCreated : 5/13/2011 3:41:47 AM


Andy

Thank you very much for sharing - much appreciated!! We will check and update the guide.

 

[Tim Butcher]

I am not sure if this a v16 specific issue but the Meeting Options "Allow Participant Control" and "Everyone is an Organizer" are locked for the WebMeeting Profile.This seems like a serious security issue because as an organizer you can turn on anyone's webcam. I would expect all the options to be off by default and review if ogranizers should be able to control other participants webcams. I appreciate you have to authorise the webcam first however this is remembered across sessions.

 

[nb]

I am not sure if this a v16 specific issue but the Meeting Options "Allow Participant Control" and "Everyone is an Organizer" are locked for the WebMeeting Profile.This seems like a serious security issue because as an organizer you can turn on anyone's webcam. I would expect all the options to be off by default and review if ogranizers should be able to control other participants webcams. I appreciate you have to authorise the webcam first however this is remembered across sessions.

We did not change this.. This is a profile. Webmeeting profile is good for a quick trusted meeting.
But still - best avoid creating webmeetings from here. Soon this will be stripped out so start migrating your users to make meetings from the webclient.

Everyone is organizer means everyone can share by default, and you can control participants.[/QUOTE]

 

[nb]

I was able to install now. I think 3CX had issues with the activation server over the weekend. The good news, the public cert restored on to V16. Very cool. Seamless upgrade.

I am not sure if this a v16 specific issue but the Meeting Options "Allow Participant Control" and "Everyone is an Organizer" are locked for the WebMeeting Profile.This seems like a serious security issue because as an organizer you can turn on anyone's webcam. I would expect all the options to be off by default and review if ogranizers should be able to control other participants webcams. I appreciate you have to authorise the webcam first however this is remembered across sessions.

View attachment 9894

I will check this - maybe we can add another profile. But you are right - those checkboxes should not be hardcoded.

However we should avoid creating webmeetings from 3CX Windows Client.
Why is the webclient not used? Send me some reasons PM. Because this was never the right place or ui to create webmeetings. Webclient is the right place and technology to do this.

 

[StefanW]

Found something else out with Office 365. Some of our office 365 users were not showing up in our list of users to chose from under contacts and calendar within 3CX. Apparently, if you office365 account is older then 2014, the AD attribute "Usertype" is missing information. It should say "Member" I found an article that shows you how to fix this. This fixed my issue and now I can see all my AD users in 3CX. I thought I would share this. Not sure this is the best place though.

https://www.ronnipedersen.com/2017/10/30/missing-usertype-attribute-in-azure-ad/

Big thanks for this, you properby have saved the team quite some time digging this up!

 

[guilleclh]

Buenos días.
escribo realmente proocupado en relación a la siguiente modificación realizada.
• Double-click to edit is replaced with single-click across the whole UI to increase usability with touch-enabled devices and tablets.
Tengo discapacidad en los ojos, por lo que utilizo lector revisor de pantalla.
para ser más preciso, NVDA.
Implementar esta modificación, me he cortado las manos y mi interacción con cualquier casilla de verificación (casilla de verificación) en todas las partes del sistema ya no es posible. Me veo imposibilitado a trabajar sobre mis clientes, y eso me dice. El sistema tras este ajuste ha sido realmente inaccesible para su uso con lectores de pantalla. Estoy realmente preocupado y que no puedo trabajar. Me encuentro literalmente atado de manos. Solicite por favor y encarecidamente se trata de una función para elegir la función que hasta el momento era ideal para mi y la nueva. Por favor señores. 3CX me parece lo mejor del mundo, no quiero migrar a otra solución, quiero continuar vendiendo 3CX a mis clientes pero si no encontramos en forma conjunta una solución a esto mi negocio se acaba en menos de 2 minutos y no es lo que deseo.

 

[Tim Butcher]

We did not change this.. This is a profile. Webmeeting profile is good for a quick trusted meeting.
But still - best avoid creating webmeetings from here. Soon this will be stripped out so start migrating your users to make meetings from the webclient.

Everyone is organizer means everyone can share by default, and you can control participants.

I have tried the webclient and it still has the same problem. I would have thought a good default is everyone has the minimum permission rather than the maximum.

 

[craigreilly]

I wonder why they will not add EXTENSION CELLPHONE into the Phone Directory?
Right now - I have to put every cell phone into the "CONTACTS" so they get into the Desk Phones.
I know it has been requested...

 

[safemode]

I'm trying to enable the instance manager but when I select everything and it goes to install I get the following error

Server Error, install-instance-manager returned error code 255

any ideas on how to fix this?

 

[StefanW]

I'm trying to enable the instance manager but when I select everything and it goes to install I get the following error

Server Error, install-instance-manager returned error code 255

any ideas on how to fix this?

which version of V16 you are running? RC1?

 

[tsukraw]

Has anyone seen any issues with extension rights on the V16?
Specifically around "Can see group calls"
We have a system that we are trying to prevent users from seeing other group member calls. But the setting has no effect. They can always see group calls.

We have a support ticket open if anyone in support wants to take an additional look: 396414

Wondering if it is just our system or if anyone else is seeing a similar issue.

 

[safemode]

which version of V16 you are running? RC1?

yes we are on RC1 running on debian

 

[tsukraw]

Has anyone tried the Skills based routing on Call Queues.
It doesn't appear to be functioning the way i expected.

Example
If you have 5 agents. 3 agents are Skill 1 and 2 agents are skill 2.
Agent 1 (Skill 1) is on the phone.
Agent 2 (Skill 1) is on the phone.

When a 3rd call comes in it rings Agent 3 (Skill 1) as expected. But the call does not move past agent 3 if they do not answer. The call continues to ring Agent 3 until the Queue times not.

I expected that the "Skills" were like tiers. If no Skill 1 agent answered or were available it would move to Skill 2 agents.

However this doesn't seem to be the case. It only seems to move to Skill 2 agents if all Skill 1 agents are busy.

Is what i am experiencing the correct behavior?

 

[Nick W]

Hi guys,

We have been working with Fanvil on a pretty nasty bug in the X4 where behind a SBC you would get one way audio after lifting a call out of a Park position. They have fixed this in firmware 2.10.0.6617 which we are testing with them.

@nb will this firmware make release?

 

[Kanwar]

Can I run RC on production?

 

[StefanW]

Can I run RC on production?

yes, just give it another 5h...

 

[StefanW]

Has anyone tried the Skills based routing on Call Queues.
It doesn't appear to be functioning the way i expected.

There is a constraint we are aware off depending which hunt mode is selected. In brief it makes currently a difference if if the agent got "busy" by a queue call or a direct call. both are not "evaluated" the same. Already optimized for 16-U1

 

[JohnS_3CX]

Hi guys,

We have been working with Fanvil on a pretty nasty bug in the X4 where behind a SBC you would get one way audio after lifting a call out of a Park position. They have fixed this in firmware 2.10.0.6617 which we are testing with them.

@nb will this firmware make release?

Our next 3CX firmware update in V16 will fix this issue

 

[Nick W]

Found something else out with Office 365. Some of our office 365 users were not showing up in our list of users to chose from under contacts and calendar within 3CX. Apparently, if you office365 account is older then 2014, the AD attribute "Usertype" is missing information. It should say "Member" I found an article that shows you how to fix this. This fixed my issue and now I can see all my AD users in 3CX. I thought I would share this. Not sure this is the best place though.

https://www.ronnipedersen.com/2017/10/30/missing-usertype-attribute-in-azure-ad/

Here are my before and after results using get-msoluser command.

Before Version
UserThemeIdentifierForO365Shell :
UserType :
ValidationStatus : Healthy
WhenCreated : 5/13/2011 3:41:47 AM

Fixed Version
UserThemeIdentifierForO365Shell :
UserType : Member
ValidationStatus : Healthy
WhenCreated : 5/13/2011 3:41:47 AM


Andy

THANK YOU for this. I have been chasing this issue on support for a few months and could not find the reason. I would recommend this is put in the release notes for V16.