SSO and Boosted Performance in V18 Alpha 2!

Status
Not open for further replies.
Hello Team 3CX,

Very great news !

On the change log of v18 Alpha 2, you say "Fixed audio Transcoding from G711A to OPUS results in degraded audio quality."

The reverse, OPUS to G711A, is it also fixed ?

Best Regards,
 
Hello Team 3CX,

Very great news !

On the change log of v18 Alpha 2, you say "Fixed audio Transcoding from G711A to OPUS results in degraded audio quality."

The reverse, OPUS to G711A, is it also fixed ?

Best Regards,
Going from a high bitrate codec to a smaller one is a bit more tricky and some loss of quality in this case is to be expected, but there have been improvement made in this scenario too.
 
Going from a high bitrate codec to a smaller one is a bit more tricky and some loss of quality in this case is to be expected, but there have been improvement made in this scenario too.
As we can not change codec order for the webclient (OPUS by default on Chrome), the outbound calls from webclient still results in degraded audio quality.
I hope that the improvements made will be significant because our users constantly complain about the quality of the webclient on outbound calls...
 
@Manuskysurfeur Yes, we are aware of this and its something we are working on to improve. Look for changes here in the coming beta......

Actually even in the latest alpha you should see improvements.
 
Last edited:
Hi 3Cx team,

V18 looks very good with all of the great product updates and the SSO sounds really simple, which is awesome. One question on the SSO. I'm utilizing O365 and have the integration enabled where it's sync'ing users as well as changes to them like phone number and email. Here is where I can see SSO maybe failing for me and others as I've seen it in the forums:

User UPN is different than e-mail address, the email address is an alias. For example John Doe logs into O365 with [email protected] while his primary email is [email protected]. 3CX auto populates [email protected] which won't allow him to login as the email field in 3CX isn't his UPN.

I also have cases from growing pains and Azure AD joined systems that make UPN changes a pain where some people have old company UPN's still. Like Jane Doe has a UPN of [email protected] and has the primary email of [email protected].

Will the 3CX SSO option have the capability to change the email based on actual UPN? Or will there be a more flexible on the O365 integration to sync only certain fields? Like don't sync e-mail so I can manually apply the proper UPN for SSO in that field?

Again, thank you!
 
  • Like
Reactions: Evolute IT
@aschildmeyerSTR Thank you for the headsup and detailed description. Your case makes sense for us to consider we will check and revert.
 
Hello @aschildmeyerSTR I've just send you a personal message with the scenario as I tried to replicate it.

I cannot replicate your case, as the user was created on the PBX with the primary email and the user logs in successfully on WebClient with the UPN by clicking on "Sign in with Microsoft".

Please check your personal messages as I would like to get more insights about your previous post.
 
Hello @aschildmeyerSTR I've just send you a personal message with the scenario as I tried to replicate it.

I cannot replicate your case, as the user was created on the PBX with the primary email and the user logs in successfully on WebClient with the UPN by clicking on "Sign in with Microsoft".

Please check your personal messages as I would like to get more insights about your previous post.
Thanks Constatinos. Constantinos gave me positive validation that my scenario is something to not worry about as 3CX already is storing the UPN in the background which is great to hear. This means a match can be made based on the actual Azure/O365 UPN rather than focusing on e-mail for match.
 
@aschildmeyerSTR having different UPN than primary email, is one of the core scenarios to cover when working with M365.

I think we did correctly our homework :)
 
Audit log is for enterprise only... hmmm not sure that's fair. Should be for any paid license if anything IMO.
Wait...this is for Enterprise only? WHY? This should be a standard feature for ANY system anywhere...
 
Hello everyone,

is it save to use the V18 Alpha 2 in production? or should we wait until the stable is released?
Is there any data when the stable will be released?

Thanks
 
Hello everyone,

is it save to use the V18 Alpha 2 in production? or should we wait until the stable is released?
Is there any data when the stable will be released?

Thanks
Here at 3CX we are already using it in our production system, so Alpha 2 is at a very good level right now, we are still though working on a few things.

Usually we suggest using Alpha releases for testing purposes only and not be placed in production environments, but I suppose it also depends how "mission critical" your business is. If you do decide to install it, it works great as it is now, we are just working on a few minor details that most people probably won't even realize.

We are getting closer to the release date though in case you want to wait.
 
  • Like
Reactions: ekasjanov
@Ubiratan Martins
Compromised passwords are a top security issue so clearly SSO has to be in every version of 3CX. We will also make configuration easier by integrating it in the setup wizard in time. Audit log is really for larger installs with multiple admins, though we have taken onboard your feedback @Phone systems NZ

100% agree SSO is a great move. But I will disagree with audit log only being for enterprise. You will see a lot of smaller installs requiring audit log for compliance. Most software includes audit log by default and can even be useful for standard users as they can easily see what changes have been made to the system.
 
What would be awesome with the SSO and user sync would be syncing to 3CX based on IPPhone number in the users profile, and then creating new extensions based on users with an IPPhone listed automatically in 3CX.
 
100% agree SSO is a great move. But I will disagree with audit log only being for enterprise. You will see a lot of smaller installs requiring audit log for compliance. Most software includes audit log by default and can even be useful for standard users as they can easily see what changes have been made to the system.
They sell 4 SC Enterprise licenses so the size of the install is not a factor. If you need audit log, you buy enterprise. This is no different than any other feature or benefit. At this point, there are should be zero installs running 3CX if they require an audit log for compliance. So since that is the cause, anyone who now considers 3CX and requires an audit log has the option and I guarantee the prices is way cheaper than any other compliance initiative they will have to take.
 
Just deployed v18a2 on our internal instance, but seem to have lost the ability to configure CDR's to be sent to our logging system.

Has this been moved somewhere, as I can't find it in the Settings anywhere?
 
@AlanRamsay check on the left menu of Management Console > "Reporting" > "CDR"
 
@AlanRamsay check on the left menu of Management Console > "Reporting" > "CDR"
Thanks for that - completely missed that!

It may be useful to have a feature that if passive is selected, that it updates nftables to allow the port through the Debian firewall, perhaps even asking what IP to allow it from too.
 
Hi all, I am new here, so sorry if this info is already out there- I searched but did not see anything... We just deployed the Debian 9 version of 3cx in Azure and jsut saw that this debian 10 version is about to be released. My questions is: will I be able to do an in-place upgrade to our current system, or will I have to do a fresh install?

Thanks
 
Status
Not open for further replies.

Forum statistics

Threads
111,992
Messages
590,171
Members
164,931
Latest member
admintest