Don't have a root cert from GoDaddy but the intermediate cert gave an
error also. OpenSSL error was 16447:error:02001002:system
library:fopen:No such file or directory:bss_file.c:259:fopen
 
Todd

________________________________

From: Brian Desmond [mailto:[email protected]] 
Sent: Friday, June 19, 2009 12:04 PM
To: NT System Admin Issues
Subject: RE: Shoretel SSL cert question.



You may need to ty importing the root and intermediate certs first?

 

Thanks,

Brian Desmond

[email protected]

 

c - 312.731.3132

 

From: Todd Lemmiksoo [mailto:[email protected]] 
Sent: Friday, June 19, 2009 10:50 AM
To: NT System Admin Issues
Subject: RE: Shoretel SSL cert question.

 

When I try to import/add the SSL cert, using the Shoretel menu, it
errors with a OpenSSL error. Sorry I don't have the error right here.

 

________________________________

From: Brian Desmond [mailto:[email protected]] 
Sent: Friday, June 19, 2009 11:35 AM
To: NT System Admin Issues
Subject: RE: Shoretel SSL cert question.

What is the problem you're having?

 

I've never heard of this device but we can start with the problem if
there is one...

 

Thanks,

Brian Desmond

[email protected]

 

c - 312.731.3132

 

Active Directory, 4th Ed - http://www.briandesmond.com/ad4/
<http://www.briandesmond.com/ad4/> 

Microsoft MVP - https://mvp.support.microsoft.com/profile/Brian
<https://mvp.support.microsoft.com/profile/Brian> 

 

From: Todd Lemmiksoo [mailto:[email protected]] 
Sent: Friday, June 19, 2009 9:48 AM
To: NT System Admin Issues
Subject: Shoretel SSL cert question.

 

Has anyone had success installing a GoDaddy SSL cert into the Shoretel
Conference Bridge server? 

Todd Lemmiksoo 
Network Administrator 

All-Mode Communications, Inc. 
1725 Dryden Road 
Freeville, New York  13068 
(607) 347-4164 x440 
1-877-ALLMODE  (toll free) 
http://www.all-mode.com <http://www.all-mode.com>  

 

 

 

 

 

 

 

 


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to