Yes I can confirm the issue is still present in 4.2.4.
Have avaya currently looking into this, sysmon traces is showing the same error as it was in the earlier 4.0 software release.
Quicker fix may be just to downgrade to 4.1.15 or 4.1.12.
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.