Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MiCollab Certificate for server on local domain

Status
Not open for further replies.

Joe King

Technical User
Feb 22, 2017
105
GB
Hi
My MiCollab server version 8 needs not to be in a registered domain just a local domain. Softphones not being deployed in teleworker, i know i still need a certificate for the softphones to work so as long as the MiCollab still has access on port 443 to the Mitel deployment server this should work. Does this sound workable or am I missing something?

Thanks in advanced
 
havent actually tried to run any of the new clients in a non named environment

here are my 2 cents worth .....

I think you will need a public certificate listing the name of the server
- this can be free using lets encrypt

the name of the server MUST be publically resolvable and tied to the public IP address associated with the server

pretty sure that that means you must have some sort of domain name for it to be able to be publically named

I think you could use a NON micollab client Softphone ( bria or xlite etc) internally without the public name but the new deployment blade method needs to have that external communication to the Mitel server that allows the clients to be authenticated

I think the new next gen clients also rely on that to be working ( not just the smart device ones)


If I never did anything I'd never done before , I'd never do anything.....

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top