Avaya IX Workplace for Windows "The required certificate is not trusted" 2

[rgunther]

We have a IPO500V2 on R11.0.4.2, that we users currently using Avaya Communicator with. We would like to try the Avaya IX workplace for Windows application - but when we keep getting "The Required certificate is not trusted" after we put in the url of the IPO and hit continue. Do i need to import a certificate into the AvayaIX workplace settings or into the IP Office 500v2 ?? Thanks,

 

[sizbut]

External or internal? TCP or TLS media? What version of IX on what platform? Same platform as Communicator?

Stuck in a never ending cycle of file copying.

 

[rgunther]

This is all using internal addresses on the same LAN. So with communicator we are using TCP - connecting directly to our IPO500v2. I downloaded the latest version of Avaya IX Workplace for windows - 3.7.6.10.1


Thanks,

 

[derfloh]

You need a valid Server certificate in IP Office covering the requested IPs/host names.

And you the root certificate of the issuing CA deployed to the computer who wants to connect (or download the settings file).

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN

 

[rgunther]

Does anyone have a link on how to create these certificates? Ive never had to mess with the certificates; although I see in web manager where to install a new cert.

 

[bahmonkeys]

Leave the system autogenerate this Certficate. Follow the installation instructions for setting up Sip Devices. You will need a Sip Domain and Sip FQDN. Avaya IX Workplace uses identity cerfticates.

 

[JazzWizzard]

Take a look at this article from IP Office Assistance:

https://www.ipofficeassistance.com/equinox-on-ipo-r11-with-self-signed-certificate/

 

[rgunther]

So everything including the link above points to R11 Server edition - which we are not using. This is just a stand-alone IPO R11.0.4.2 Essential Edition. All clients using the IX workplace for windows are on the same local LAN as the IPO. So its really wierd as we use the URL for the initial setup - which then brings us to the login screen. We enter the users extension and password - and everything works fine (can make incoming and outgoing calls via the IX workplace); but the ix workplace still has a red exclamation that says "Phone Server - Invalid extension or password". Which is really strange because it seems like it is all working properly?

Any ideas?

 

[JazzWizzard]

Dumb question, but is IX Workplace supported with Essential Edition?

 

[derfloh]

Did you enable Softphone for the user and do you have a valid softphone license?

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN

 

[rgunther]

Yes the user is a power user (of which we have plenty available), and I have all options checked - Softphone, All one-X services, Desktop/Tablet VoIP client, Mobile, Voip client, etc... Again we can make and receive calls via the application; but no contacts and have the error saying Phone Service - Invalid Extension or password.

 

[rgunther]

WOW - it was the users password the whole time. You CANNOT use 1234 as a user password. Tried it with 3 different users and got the same error. As soon as we changed the password to something different our error cleared and the IX workplace is working correctly. Thanks everyone for helping with this.

 

[bahmonkeys]

@rgunther
There is an option in the security to "Block Default IP Phone Passcodes" on R11.0.4