Hello!
I'm Edson Pineiro, I understand your problem is in regards to inter-operating CUE 8.5 with either CME GUI version 8.6.0.0 or 8.5.0.0. Where the CUE GUI does not work when CME GUI version 8.6.0.0 installed - However after downgrading the CME GUI files to 8.5.0.0 the CUE GUI works but the CME GUI fails.
Interestingly the CUE compatibility matrix confirmed CME 8.6 is backwards compatible with CUE version 8.5.
http://www.cisco.com/en/US/docs/voice_ip_comm/unity_exp/compatibility/cuecomp.htm
Another point to make is that CME version 8.6 is only compatible with CME GUI version 8.6.0.0.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/requirements/guide/33matrix.htm
According to the compatibility matrix the correct software configuration would be as so:
CUE version 8.5 or 8.6
CME version 8.6
CME GUI version 8.6.0.0
However software incompatibility symptoms are usually found by specific features not working correctly with other features. I wouldn't expect the complete CME web page to be un-available, un-less you have a corrupt CME gui file or bad configuration.
I would like to confirm, when accessing the CME Web interface are you using the following url syntax?
http://router_ipaddress/ccme.html
http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmegui.html#wp1056332
Also can you confirm, that when using CME GUI version 8.5.0.0, are you able to access and change ephone DN or CME related configuration changes from the CUE GUI?
In regards to the command "ip http path" the directed folder should contain the CME GUI files. The CUE GUI files are embedded in the CUE module, as so there is no need for another http path. If your CME GUI files are in the flash: root directory I would expect to see the command 'ip http path flash:' in the running configuration.
Another point to make is the CUE GUI integrates with the CME GUI and function together without one or the other the CUE GUI will not work as expected.
If all else fails I suggest you ensure "ALL" the CME GUI files have been checked/replaced and overwritten when downgrading or upgrading the CME GUI version. Sometimes customers forget to overwrite one GUI file causing strange issues after changing CME GUI versions or a gui file is corrupt. Please make sure each separate/individual GUI file has been overwritten with the corresponding version, otherwise you will see some weird problems.
I hope this helps.
If you have any further questions please do not hesitate to reply back.
Thank you
&
Regards
Edson Pineiro
