04-23-2018 02:43 AM - edited 03-20-2019 10:05 PM
This is such a problem, especially if you cannot sign into the thick CMA client via Expressway....
User guides and adoption plans have to be put on hold.
05-07-2018 10:31 AM
I have the same issue with a customer using CMA WebRTC through Expressway (no option for thick CMA client).
I have asked TAC if they can provide some sort of ETA for resolution but have not heard back as of yet.
07-05-2018 12:38 PM
Hi There,
For the benefit of others, this bug has now been resolved in 2.3.6, I just tested changing end user PINs from the WebRTC application and it seems to function correctly now.
- Jon
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: