Author Topic: Next gen  (Read 2879 times)

Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Re: Next gen
« Reply #15 on: November 06, 2020, 01:49:27 PM »
If MiCollab PC Client 9.1 is an example of "next gen", then yes it works fine with Letsencrypt certs.

Yes , all softphone after 7.3 are considered as a next gen.

with lets encrypt cert + fqdn  micollab.mycompagny.com it's sure that it will work, this is what i'm trying to exeNEPhoneGuy
« Last Edit: November 06, 2020, 01:51:52 PM by sunspark »


Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Re: Next gen
« Reply #16 on: November 06, 2020, 01:50:42 PM »
FWIW, you will never get a certificate from Let's encrypt for the name host.domain.local, might be added as a SAN yo a true FQDN, never tried it. Think it is bad practise to use anything less that a true FQDN when installing MiCollab or MBG with web proxy

i agree , but let encrypt cert + fqdn micollab.mycompagny.com and without MBG it will work in lan mode only.

Offline johnp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2209
  • Country: us
  • Karma: +67/-0
    • View Profile
Re: Next gen
« Reply #17 on: November 06, 2020, 02:59:01 PM »
Yes it should work, might need to make port 80 open for the certificate fro Let's Encrypt

Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Re: Next gen
« Reply #18 on: November 06, 2020, 06:38:24 PM »
Yes it should work, might need to make port 80 open for the certificate fro Let's Encrypt

Thank you for your advice

Offline billbry66

  • Full Member
  • ***
  • Posts: 94
  • Karma: +3/-0
    • View Profile
Re: Next gen
« Reply #19 on: November 14, 2020, 03:29:18 AM »
get the customer to create an internal ssl cert for it using the domain CA
generate a csr and put the server name in the alternate name filed ( will create a cert with the name listed twice)

then install the domain ca cert into the certificate authority trust
once thats done the internally created cert should install


 

Sitemap 1 2 3 4 5 6 7 8 9 10