Audio Conferences Back to the Clients

Discussion in 'Ideas' started by Rodrigo Fusco Lobo, Dec 8, 2017.

Audio Conferences Back to the Clients 5 5 1votes
5/5, 1 vote

  1. Rodrigo Fusco Lobo

    Joined:
    Dec 8, 2017
    Messages:
    3
    Likes Received:
    2
    We had a major step back with the 15.5 SP2 update on the Audio Conference scenario.
    Previously, all Conferences where made inside the clients, Either Windows, Mac, Android or IOS.
    The user created all conferences, invited guests, received invites, edited, etc... INSIDE the clients.
    Now, when you click on conference, it sends the users to a website!
    Problems here:
    1- The Website has Certificate problems, which scares the users
    2- The user must login again, using a Password he never had.
    3- This password can´t be changed by the user himself! We need to provide it administratively! If we provide an easily remembered password, we will be risking that our Conference rooms may end up being used by hackers or so... If we provide a strong password (Like we used to, as only the client softwares, not the end users, were using this password before), the user will not be able to remember it when we wants.
    4- We need to expose the https port of our 3CX servers, which we didn´t had before
    5- The website is messy, doesn´t allow to invite users and doesn´t send the invites by email!

    So, as we can see, this was a major step back. So, just please go back for the old and good inside the clients solution. It was working just fine, and was one of the strenghts of the 3CX solution!
     
    3CXDude likes this.
  2. LeonidasG

    LeonidasG Support Team
    Staff Member 3CX Support

    Joined:
    Nov 19, 2008
    Messages:
    1,406
    Likes Received:
    81
    SP3 will be addressing most of the above especially for the WebClient.

    Ad-hoc is already added back in the latest release of the 3CX Clients that was done last Friday. We are also making another client (iOS, Android, Mac, Windows) extremely soon with further improvements to ad-hoc. The Android client has already been released moments ago, the others will follow soon and there will be an official announcement.

    The certificate part is something that the user himself has to properly manage with correct system configuration (Exts > Provisioning > FQDN select).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #2 LeonidasG, Dec 8, 2017
    Last edited: Dec 8, 2017
  3. Rodrigo Fusco Lobo

    Joined:
    Dec 8, 2017
    Messages:
    3
    Likes Received:
    2
    The worst part is to oblige the users to create the scheduled conferences on a website, using a password that they never had, and that is not integrated with any other password, cannot be changed by the user, cannot have a two factor authentication.... If your development was not completed, you should have not messed up with something that was working really fine. Just put it back, exactly as it was, until you have a solution that makes improvements over the one in production.

    The changes you are doing remembers us to the old Microsoft updates, for the Windows 95/98 era, where everybody was really afraid to run a service pack, as it normally brought more troubles than solutions...
     
    3CXDude likes this.
  4. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,889
    Likes Received:
    191
    Just for the record our client does not have certificate problems. Its probably because you have your certificate incorrectly configured. With a 3CX FQDN or properly configured certificate all works fine. Secondly users can most definitely change the password.

    That said we will be adding an improved scheduled conference option back into the clients.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...