Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Conference in new client causes SSL error

Discussion in 'Windows' started by MichaelG, Nov 20, 2017.

Thread Status:
Not open for further replies.
  1. MichaelG

    Joined:
    Nov 19, 2017
    Messages:
    2
    Likes Received:
    0
    Hi,

    In 3CX 15.5 sp2 update the create and view conference buttons in the softphone client go to the webclient.
    The issue we are having is that it uses the <PBXLocalAddr> setting from the provisioning file, which in our case is a local IP address. This throws a SSL cert error because the CN doesn't match the certificate we have loaded. The FQDN under <PBXPublicAddr> points to the same IP in <PBXLocalAddr> internally anyway.

    Is there a way to update the <PBXLocalAddr> in the provisioning files?

    Thanks
     
  2. Marios Neophytou

    Marios Neophytou Support Team

    Joined:
    Mar 1, 2016
    Messages:
    258
    Likes Received:
    13
    Hello @MichaelG,


    Go to the extension that you want to modify and under Phone provisioning > Network click on the drop down list and change the Network interface for registration and provisioning to be the FQDN instead of the local IP. After that re-provision is require.

    This is happening because you do not have a Local FQDN. For more information follow this link.

    Thank you
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. ryanfonash

    Joined:
    Aug 19, 2016
    Messages:
    5
    Likes Received:
    0
    You can't create a local FQDN if you are using the .3cx.us hosted service though... So this still doesn't work.

    I'm using a 3cx subdomain so as to not have to worry about SSL certs - and this completely kills that.
     
  4. ryanfonash

    Joined:
    Aug 19, 2016
    Messages:
    5
    Likes Received:
    0
    Furthermore, the user has to authenticate every time. There should be a token that gets passed from the desktop client to the web login so the user is logged in automatically.
     
Thread Status:
Not open for further replies.