Avaya Workplace, SBCE and IPOffice SE

[lulsperger]

Hello Comunity

I have a problem with Certificats on an actuall installation on Avaya Workplace, SBCE and IPOffice SE. We use the latest Rls.
When i create all teh cirtificats in the IPOffice than works all.
Now the customer will use an public certificate for the connection from Workplace to SBCE. We created the CSR in the SBCE with the FQDN from the IPOffice.But it dont works. Need i the Sip Domain too as alternative? Is there any more DNS/IP to set in the alternative?

thank you

Lutz

 

[G van Hamburg]

What does your certificate look like? In my ipo my sip registrar is ipo.domain.com and the sip domain is ipo.domain.com too! The onex portal fqdn is onex.domain.com. My external cert has 2 entries, ipo.domain.com and onex.domain.com. if you have a different sip domain, you need to define thta too!

Freelance Certified Avaya Aura Engineer

 

[lulsperger]

Hello

We have one Server for IPOffice and OneX Service. The FQDN is for both ipo.company.de. This FQDN is written in the Certificate and the Sip Domain too.

Regards

Lutz

 

[derfloh]

Hey Lutz,

It depends... If you use reverse Proxy you should be fine with this. If you use application relay the IPO must provide the same certificate.

You also have to make sure that 46xxsettings.txt only provides FQDNs and not the public IP.

Last... The WebRootCA.pem must be the CA certificate(S) of your certificate because the app itself uses this as the only root certificate.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN