Hi,
we are currently running Release 12.5(1)SU4 Unified Communications Manager 12.5.1.14900-63
I am wondering if the bug is fixed in the above mentioned release.
Hope I am not wrong, but one of the Known Affected Release is 12.5(1.10000.22), which seems to be a very old (first) release
and one the Known Fixed Releases is CCM.012.005(001.11170.001), which is a Engineering Special but looks for me older than
Release 12.5(1)SU1 Unified Communications Manager 12.5.1.11900-146
Unfortunately it is currently not possible for us to upgrade to 12.5(1)SU7 on short term.
Does anybody know how to find out, if the bug is fixed in our current running version?
Thank´s in advance for a quick answer.
