This document answers some of the most frequently asked questions about Cisco Unified Communications Manager Express (Cisco Unified CME) 7.x and later versions.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
In order to get support information for Cisco Unified CME, including design, configure, and troubleshooting information, refer to Cisco Unified Communications Manager Express.
A. No, it is not possible to change the order of directories. The first three Call History directories are "hard-coded" in the IP phone.
A. Currently, iDivert is only supported for Cisco Unified Communications Manager, not for Cisco Unified CME. However, as a workaround, try using direct transfer to voicemail. This configuration can be done using the E.164 option. Refer to Transfer a Caller Directly into a Unity Express Mailbox for configuration information.
Another workaround to achieve the iDivert functionality in Cisco Unified CME is by using the DND soft key. This will forward any incoming call to the call forward destination for each line configured on the phone. For example, in order to forward to voicemail, press the DND soft key.
Note: If the call-forward destination is not set, pressing the DND soft key disables the ringer. Pressing the DND soft key during an incoming call in order to forward the call to the call-forward no answer destination if Call Forward No Answer is enabled. If Call Forward is not enabled, pressing the DND soft key disables audible ringing and visual alerting, but the call information is visible on the phone display. Refer to Configuring Do Not Disturb for more information.
A third workaround is available for Cisco Unified CME 4.3 or later. The Transfer to Voice Mail feature allows a phone user to transfer a caller directly to a voicemail extension.
Perform these steps:
Press the TrnsfVM soft key to place the call on hold.
Enter the extension number.
Press the TrnsfVM soft key again to commit the transfer.
Note: The TrnsfVM soft key is not supported on the Cisco Unified IP Phone 7905, 7912, or 7921, or analog phones connected to the Cisco VG224 or Cisco ATA. These phones support the trnsfvm FAC.
A. Yes, Cisco Unified CME supports the + number dialing pattern beginning with version 7.
A. Yes, Cisco Unified CME does support Directed Call Park beginning with version 7.1.
A. Yes, Cisco Unified CME does support the call monitoring feature beginning with version 7.1.
A. Yes, Cisco Unified CME provides a personal address book beginning with version 8.x.
A. Cisco Unified CME supports mobility or the Single Number Reach (SNR) feature beginning with version 7.1. Perform these steps in order to configure the mobility on Cisco Unified CME:
Enable the mobility feature and configure SNR under the directory number.
Create an ephone-template and assign the mobility softkey option under this ephone-template.
Apply the newly created ephone-template to ephone.
A. Release 12.4(24)T provides a number of advanced Cisco Unified CME and Cisco Unified SRST features, including SNR, Whisper Intercom, SIP line side enhancements, CME/CUE user name/password synchronization, MLPP over PRI, enhanced BLF monitoring, SIP line side DND update, and video across SIP trunks between CMEs.
A. CME 8.5 provides support for new Cisco 8900 and 9900 Series IP Phones and CME 8.6 will offer enhanced collaboration capabilities, including video telephony support for Cisco IP phones as well as native video conference for several Cisco IP phones. Also, CME 8.6 will provide improved mobility by allowing users to access their business phone extension via their iPhone or iPod Touch devices.
A. For Cisco Unified CME 8.5, the limit is 33 local speed-dial entries (numbers 1 through 33). The local speed-dials use the speeddial.xml file.
Note: In a Cisco Unified CME system, each phone can have up to 33 local speed-dial numbers (codes 1 to 33), up to 99 system-level speed-dial numbers (codes 1 to 99), or a combination of the two. If you program both a local and a system-level speed-dial number with the same speed-dial code (tag), the local number takes precedence. Typically, you will want to reserve codes 1 to 33 for local, per-phone speed-dial numbers and use codes 34 to 99 for system-level speed-dial numbers so that there is no conflict.
Refer the document Speed Dial Buttons and Abbreviated Dialing for more information.
Q. A blank search in the CME Local Directory returns an XML Parse Error on IP phones with Russian Locale. How do I troubleshoot this issue?
The Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers.
Refer to Cisco Technical Tips Conventions for information on conventions used in this document.