I find that, when I by pass the ASBCE, it is work on IX workplace.
However, when I change the connection to ASBCE, I cannot sign in the IX workplace, even using same ext and password.
My SBC is work before when using TCP connection.
However, is fail when I change it to use TLS.
I already import the same public cert to SBC, and change server connection to TLS, but it is fail to register to IX workplace through SBC
Good news, the IX workplace push notification function is work on IPO 500v2 now.
However, when I want to use IX workplace include ASBCE, it fail to login.
I already can use public cert to login IX workplace.
However, I find this error in monitor when I enable apn in IPO.
11:45:01 1155927mS HTTP: PushNotificationAuthorizationHandler::APNP is not allowed, reset Zang Sync
11:45:01 1155927mS HTTP: PushNotificationAuthorizationHandler::APNP is...
My IPO SIP domain is: onex.mycompany.com.hk
My IPO Cert Issued To: onex.mycompany.com.hk
My Avaya Cloud Domain: mycompany.com.hk
Added Avaya Spaces API Key and Secret
I also add the following cert to my IPO: Entrust Certification Authority - L1M
Is it correct? Any miss?
I am trying to by pass all server.
Just using IPO 500V2 and IXworkplace.
It is ok to login IXworkplace when I using IPO default cert.
However, it told me cannot get a WebRoot.pem when I using public cert.
I also try to edit 46xx SET TRUSTCERTS myCA.crt
It still not work.
Hi Travis Harper,
Have you import a public cert to your IPO?
Have you also using ASBCE in you IPO environment?
If yes, Have you import a public cert between IPO and ASBCE?
It is many helpful if you can share some IPO setting screencap. This problem is stuck me on OCT last year...... but...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.