IP Office R11 with One X portal in Workplace PC or Mobile no found IM

[dsx3609]

Hello everyone:

I tell you the problem I have.

On Avaya Workplace both mobile and PC, instant messaging does not work.

In the SIP registration the 200OK that the IP Office 500v2 answers returns the username, the fqdn of one x portal and the non-secure port 8080 and secure port 9443.

Our structure in with SBC for remote work, but locally without going through the SBC this fails us.
We have installed the IP WebRootCA on mobile and on PC we also have the Application Server RooCA installed where the OneX Portal is located.

One X portal is configured with the host name , the xmpp domain and everything is correct.

From the local PC with an XMPP jabber client it connects correctly to the OneX portal instant messaging but with Avaya Wokrplace we don't have this result.

We have everything in TLS in wl Workplace and the presence and telephony work correctly but IM does not.

Can you think of something about this problem we are having?

NOTE: The certificates have been generated correctly from the application server with the fqdn and the internal and external IPs, it has been established that the certificate does not exceed 820 days due to the limitation with Iphone and Android.

So far we have been able to get with this.
While the IM does not work locally on a local PC, it will work less well with the SBC that we have the certs on and the relays applied.

I hope someone has some news about this or that the same thing happens to them.

Thanks

Regards

 

[derfloh]

Do you have a valid certificate in OneX portal port 9443?

Workplace uses a web service instead of connecting directly to the XMPP service.

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

 

[dsx3609]

The certificates are generated correctly in the Application Server and in the SBC we have the certificates for the connection with the realy 9443 applied, it is the SBC traces of http and tls I see that the requests arrive and the TLS is correct, we do not have any fatal error ca Nothing like that.
What always appears to me is "cannot update messages" or in some cases "invalid username and password".

Without using the SBC locally we have the same problem, the certificates of both the Application Server RootCA and the IP500V2 RootCA are imported for the TLS connection of the workplace clients.
In the workplace client, do I have to enable the instant messaging option?

I understand that not because when the registration returns the IP Office 500V2 the 200OK with the connection data to the portal is not necessary.