Avaya IX Workspace Auto Configure

[KJBB]

After reading many documents, and posts, I have Avaya IX working with an IPO 500V2
User installs the App, Clicks on the Gear in the upper right corner, and selects Use Web Address
Enters

http://ipoffice.mydomain.com,

Clicks next then enters their extension and password

App finishes setting up, the tutorial comes up, then the App is open with a red triangle at the top

I can get rid of this error, by changing the phone settings to use port 5060, and no TLS

We are using a third-party certificate so no certificates have to be installed, on the client-side, it is added to the IP office, and everything is enabled for TLS (That I know of)
Does anyone know why we are getting this error?
Next question does anyone know how to auto-configure for all of the services, like Enterprise directory and Exchange Calendar?

It's painful doing it manually, because you have to reboot the App every time you make a change
I do not want to do this for 20 users

Thank you in advance for any help,
Ken

 

[telecomtekperson]

Check your cert here:

https://www.sslshopper.com/ssl-checker.html

Here is the process:

https://www.ipofficeassistance.com/create-3rd-party-certificate/

And this:

https://www.ipofficeassistance.com/automate-spaces-install-on-avaya-r11-equinox/

 

[janni78]

Is the IPO FQDN and SIP domain the same?

If not, does the certificate include both?

"Trying is the first step to failure..." - Homer

 

[KJBB]

UPDATE
Our current certificate only has one domain
Ipoffice.domain.net
It passes the SSL test you mentioned

From what we have found you need to have a UCC cert and have a record for
URI sip domain

When we try to purchase one they will not let us add Subject Alternative Name
SIP:domain.net

They say the colon is not accepted in an SSL cert
So if we purchase a new SSL cert with just two records
Ipoffice.domain.com
And domain.com
Will that work and allow us to connect with Avaya IX workplace with TLS?

 

[derfloh]

Probably it will work... You can test it if you temporarily create a cert with IPO server that only have those two DNS names.

If it works with the IPO generated certificate you can be sure it will work with a third party certificate, too.

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

 

[janni78]

It doesn't need to be a SIP uri, it just needs both domains.

You could also change the SIP domain to be the same as your IP Office hostname so you only need one domain in the certificate.
It's not really supposed to be like that but if you're a smaller business you'll get away with it since you won't need to separate them.
If you do this the Zang domain should still just be the domain part.

"Trying is the first step to failure..." - Homer