Where are all the CME menu options in CUE 8?

Unanswered Question
May 13th, 2010

First time installing CUE 8.0.1 and it appears that the CME menu options are missing.  This means I'm unable to modify the extensions, phones, call transfer patterns, etc, from the CUE GUI.  I've searched through docs to see if something has changed with the new CUE 8 GUI changes but never found anything.  Am I missing some config or is this the new way of doing things for CME/CUE?


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.5 (2 ratings)
dlcharville Thu, 05/13/2010 - 08:54


Yes, I'm using compatable version of CME 7.1.  When I navigate to the CME GUI, the page comes up but all the links are broke with JavaScriptVoid errors.



dlcharville Thu, 05/13/2010 - 11:28


Yeah my CME GUI files were a little jacked up with all caps for some of the file names.  Fixed those file name and so this fixed the CME GUI.  Still not seeing the CME options in CUE GUI though.



dlcharville Fri, 05/14/2010 - 10:11


Opened a TAC case on this, apparently CUE version 8 removes the CME menu options.

From TAC...." /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} I am sorry to informyou that on CUE GUI 8.0x you don't have the phone and extensionoption any more by default.  This was design to work this way. If you need this option you can log in to the CME GUI or downgrade to CUE 7.1that still has this options on the GUI."

Thanks Cisco...for making our jobs more difficult.



Brandon Buffin Fri, 05/14/2010 - 10:13

Wow, that's hard to believe. Did TAC give any reason for making this decision? Thanks for updating the post, Dan.


Cristian Zaharia Sat, 09/04/2010 - 07:50

I totally agree with Dan.

For experts CLI is the way to go, but for the customer/admin people CLI might be a little too much. For admin/training matters native integrated GUI serves well the purposes. Cisco tried for years to push native integrated CUE/CME GUI vs CLI – and now a step back.

I see no reasons/drivers for such decision, but is it a bad one. Cisco/product manager has to reassess it.


ahalstea Fri, 01/07/2011 - 19:56

I have been so thrilled with 15.x from the moment I have heard about it!!! (sarcastic)

Why in the world would you take the best customer friendly feature out of the system?  Is this how we compete with the very GUI BCM  ??

Yes as stated above ... most of the People using this CCME were talked into it from integrators like me who set it all up for them via CLI, and then show them how easy it is to do MAC work in the GUI, I cant even get the CME GUI to launch on 8.5


This Discussion