Table Of Contents
Release Notes for Cisco Configuration Assistant 2.2(5)Revised on August 19, 2010 for CCA 2.2(5)
These release notes include important information about Cisco Configuration Assistant Release 2.2(5) and any limitations, restrictions, and caveats that apply to this release.
The following topics are covered in these release notes:
Cisco Configuration Assistant (CCA), part of the Cisco Smart Business Communications System (SBCS) portfolio of products, simplifies the tasks of configuring, deploying, and administering Cisco network solutions, improves the security and performance of your network, and reduces the time needed for network deployment and configuration. Designed for small business networks from 8 to 100 users, this PC-based application with a graphical user interface (GUI) provides everything you need to set up a small office network.
New Features in CCA 2.2(5)
Release 2.2(5) of CCA contains these user interface changes and feature enhancements.
In addition to the changes listed below, see "Limitations and Restrictions" for important information that applies to CCA release 2.2(5).
Feature Description. UC 500 Software Pack 8.0.4 support
CCA 2.2(5) supports the UC 500 8.0.4 software pack. For more information and software pack component versions, see Cisco UC 500 Software Packs.
Microsoft Windows 7 Support (64-bit and 32-bit versions)
CCA can now be used on PCs running the Microsoft Windows 7 operating system. Microsoft Windows 7 Professional and Ultimate Editions (64-bit and 32-bit versions) are supported.
NOTE Windows 7 User Account Control (UAC) must be disabled in order for CCA drag-and-drop upgrades and file operations to work.
CCA Version Compatibility Checking
When you launch CCA, the CCA Version Conflict dialog appears if the version of CCA you are using is older than the version of CCA that was previously used to configure the system. You can either choose to update CCA to the latest version (recommended) or close the dialog to continue without updating CCA.
New Devices Supported
CCA 2.2(5) adds support for these Cisco Small Business IP Phone models:
•Cisco SPA Model 525G2
•Cisco SPA 300 Series, all models
Drag-and-drop phone load upgrades are supported for these new phones.
NOTE When using the drag-and-drop upgrade feature with Cisco SPA 300 Series and 500 Series phone loads, you must extract the .bin phone load file from the .zip file that you download from Cisco.com.
You can now configure dialable intercoms using CCA. These are configured on the User Extensions tab in the Voice window (Configure > Telephony > Voice).
You can now configure Whisper Intercoms using CCA. These are configured on the User Extensions tab in the Voice window (Configure > Telephony > Voice).
Whisper Intercoms are available only for phones that support octal lines.
Conference Barge, Privacy, and Shared Octo-Line Extensions
You can now configure Conference Barge with Privacy using CCA. cBarge and Privacy require shared octal-line extensions to be configured.
cBarge and Privacy are configured in the Conference Barge window (Configure > Telephony > Voice Features > Conference Barge). Shared octal-line extensions are configured on the User Extensions tab in the Voice window (Configure > Telephony > Voice).
Enable or Disable Conference Join and Leave Tones
You can now enable or disable tones played when callers join or exit a multi-party conference. To access these settings, choose Configure > Telephony > Voice Features > Conference. Multi-party conferencing must be enabled.
Combined Paging Groups
CCA now supports combined paging groups. This feature allows paging groups to be members of other paging groups. To access paging group configuration, choose Configure > Telephony > Phone Groups > Paging Groups from the feature bar.
Overlay Extension on CO Line
You can now configure an Overlay extension on a CO (Central Office) line using CCA.
CUE Connectivity Diagnostics
From the CUE Connectivity Diagnostics window (Troubleshoot > CUE Diagnostics > CUE Connectivity Diagnostics), you can check connectivity with the CUE module on the UC 500, generate logs, and perform recovery tasks to place the module into a known state.
From the PCM Capture window (Troubleshoot > Telephony Diagnostics > PCM Capture), you can perform a PCM capture to troubleshoot audio issues such as poor voice quality, one-way audio, or no audio.
SIP Trunk Registration Diagnostics
The SIP Trunk Registration window (Troubleshoot > Telephony Diagnostics > SIP Trunk Registration) displays SIP registration information and provides diagnostic tools for troubleshooting SIP trunk registration problems.
New Default AA Script
The aa_sbcs_v03.aef script is now the default Auto Attendant script. This version of the AA script provides an option for transferring calls to a designated phone number if the caller does not choose an action after the main greeting is played three times.
HLog softkey support for Basic ACD and other hunt groups
Agents can now log in or out of any hunt group on the system (including Basic ACD hunt groups) using the HLog softkey. The HLog softkey is presented on the IDLE screen (press more twice) and when a call to the B-ACD hunt group is ringing. This replaces the use of DND (Do Not Disturb) for this functionality.
Miscellaneous Telephony Feature Enhancements
•You can now enable or disable blocking of restricted calls and set calling permissions for common area phone/Fax devices. These settings are configured on the Analog Extensions tab in the Voice window (Configure > Telephony > Voice).
•A Use as Teleworker Phone option has been added to the User Extensions tab. When this option is checked, Media Termination Point (MTP) is configured on the selected phone.
•An Allow video calls option has been added to the User Extensions tab in the Voice window for phones that support point-to-point video. When this option is checked, Cisco Unified Voice Advantage (CUVA) is enabled on the selected phone.
•You can now edit the description that appears in the upper right corner of the display on IP phones. For example, you can edit this setting to display the full DID (direct inward dial) number of the phone. In prior releases, CCA always displayed the First and Last Name of the phone user in this area. This setting is configured on the User Extensions tab in the Voice window.
•CCA now provides the ability to enable or disable configuration of STCAPP feature-access codes on SCCP-controlled analog phones. We recommend that you disable STCAPP feature access codes to avoid conflicts with feature access codes that are configured using the
telephony-service. To access this setting, choose Troubleshoot > Telephony Diagnostics > SCCP Analog Phones. Disabling STCAPP feature-access codes does not affect feature access codes configured using the
telephony-service, which are always enabled by CCA.
The system requirements are described in these sections:
The PC on which you install Cisco Configuration Assistant must meet these minimum requirements.
System Requirements Supported Operating Systems
Microsoft Windows Vista Ultimate, Microsoft Windows XP, Service Pack 1 or later
Windows XP 64-bit Edition, Windows Vista 64-bit Edition
Microsoft Windows 7 Professional and Ultimate Editions (64-bit and 32-bit versions)
You must have write permission to your home directory and to the Cisco Configuration Assistant installation directory so that CCA can create the necessary log files and preference files.
For PCs running Windows Vista or Windows 7, Administrator privileges are required in order to update, install, and use Cisco Configuration Assistant. If User Account Control is enabled in Windows Vista or Windows 7, you are prompted to elevate privileges when you start CCA.
Mac OS Support
(requires virtualization software)
Mac OS: 10.4.10 and later
Virtual OS: Parallels Desktop 3.0 and later, VMware Fusion: 1.0 and later
Guest OS: Windows XP (Service Pack 2 or later), Windows Vista Ultimate, and Windows 7 Professional and Ultimate Editions (64-bit or 32-bit versions). CCA also supports remote control via Virtual Network Computing (VNC) clients.
PC with FastEthernet or higher LAN port
1-GHz Pentium IV or higher
200 MB (300 MB recommended)
512 MB minimum; 1024 MB recommended
Screen resolution: 1024 x 768
Font size: Small
Managed Device Support
CCA manages the following switches, routers, access points, wireless LAN controllers, and IP video cameras.
Downloading Cisco Configuration Assistant
You can download Cisco Configuration Assistant from this site:
For information on installing, starting, and connecting to Cisco Configuration Assistant, see the at this site:
Available and Deferred CCA Versions
These CCA releases are available for download on Cisco.com:
•CCA 2.0 and localized versions
•CCA 1.8 and localized versions
All other versions of CCA are deferred and are no longer available on Cisco.com.
Updating Cisco Configuration Assistant
We strongly recommend that you upgrade to the latest version of CCA in order to take advantage of new features and resolved issues.
You can use the automated Application Updates feature to update Cisco Configuration Assistant to a later release in the language that you are using. Follow these steps:
1. Start Cisco Configuration Assistant.
2. Choose System > Application Updates.
3. In the Authentication window, enter your Cisco.com username and password and click OK.
4. In the Application Updates window, click Yes.
NOTE Cisco Configuration Assistant 1.x installations cannot be updated to version 2.0 and later using the Application Update process. You must download Cisco Configuration Assistant from Cisco.com (www.cisco.com/go/configassist) and install it manually.
Cisco UC 500 Software Packs
Cisco UC 500 Software Packs are large zip files that contain all necessary files for the Cisco UC 500 Series platform. Each zip file contains multiple TAR/archive files for the components of the UC 500, including:
•IOS image for the UC 500 platform
•IP Phone firmware files
•Voice mail software
•Factory default configurations for each SKU
•Support files, such as Basic ACD prompts and scripts, ringtones, and desktop images
Separate UC 500 software package files are provided for the Model UC 520, UC 540, and UC 560 platforms. You must download the correct file for your UC 500 platform.
Two types of software packs are available:
•Default software packs: Default software packs are completely tested with Cisco Configuration Assistant and the SBCS solution.
•Early Adopter (EA) software packs: Early Adopter software packs provide the latest phone firmware, IOS, voice mail, and auto attendant software releases and are tested for installation and upgrade only.
Downloading Cisco UC 500 Software Packs
To download Cisco UC 500 Software Packs, go to the following URL:
IP phone localization files and voice mail localization files are also available from this URL. A Cisco.com login is required.
Available Software Packs
These UC 500 software packs are available for download:
Upgrading UC 500 and Device Software
To upgrade software on the UC 500 and other devices using CCA, choose Maintenance > Software Upgrade.
For instructions on how to upgrade software on Cisco UC 500 Series platforms, see the CCA online help or the Cisco Configuration Assistant (CCA) Smart Business Communications System Administrator Guide, available on Cisco.com.
Minimum Cisco IOS Releases and Device Firmware Versions
Table 5 lists the minimum software releases required for the devices that Cisco Configuration Assistant manages.
Limitations and Restrictions
These limitations and restrictions apply to the current release of Cisco Configuration Assistant:
•When using CCA on PCs running Microsoft Windows 7, file selection dialogs are missing icons for buttons on the upper right corner of the dialog (for example, the Up one Level button icon). The problem occurs due to a known issue in the Java Runtime Environment (JRE) library. The JRE library cannot retrieve the related icon resource from the native Windows 7 platform to render certain file chooser widget buttons.
The issue is cosmetic and does not affect functionality. The user can still browse the entire file system and select a target directory or file.
Although the buttons are not visible, the user can position the mouse over the button to view its Tooltip text to identify the purpose of the button. The button works as expected when the user clicks on it.
•Some Cisco Model 79xx IP phones cannot be directly upgraded from 8.3.3 or earlier to 8.5.3 or higher. You may encounter this issue when upgrading phone loads or when upgrading to a new UC 500 software pack. When the issue occurs, Cisco Model 79xx phones may fail to register. For instructions on how to resolve the issue, see Resolving Cisco Model 79xx Phone Upgrade Issues.
•Cisco SA 500 software versions 1.1.42 and earlier are not supported for use with CCA. If the SA 500 is running software version 1.1.42 or earlier, it cannot be added to a CCA customer site and cannot be managed using CCA.
Use the SA 500 Security Appliance Configuration Utility on the device to configure the SA 500 if software version 1.1.42 or earlier is installed.
•Drag-and-drop file operations from the PC running CCA onto device icons in the Topology view may fail due to Windows Vista or Windows 7 User Account Control (UAC) restrictions. A "No Entry" icon is displayed.
To work around this limitation, temporarily disable User Account Control (UAC) in Windows Vista, perform the operations, then re-enable UAC.
These are some of the drag-and-drop file operations that CCA supports:
–SR 520-T1 firmware upgrade file
–IOS image files
–SPA 500 Series IP phone loads
–CP-500 language files
–Music on Hold audio (.au) files
–Cisco Unity CME language files for localization
–UC 500 factory default configuration file
–System speed dial .xml file
•CCA does not support upgrade of boot code (.rfb files) on ESW 500 Series switches, only firmware (.ros files). Use the ESW 500 Configuration Utility to upgrade boot code if needed.
Since ESW 500 Series firmware version 2.1.16 requires boot version 126.96.36.199 for 8-port ESW models and boot version 188.8.131.52 for 24-port and 48-port models, you may need to manually install or upgrade the boot code to ensure that the appropriate versions are used.
Upgrade the boot code first, then the firmware, change the active image, save the configuration, then reboot the ESW switch. In the ESW 500 Series Configuration Utility, software upgrade options for ESW switches are located under Maintenance > File Management.
To download firmware and boot code files for ESW switches, go to www.cisco.com/go/esw500help, click the Resources tab, then click the Firmware link. A Cisco.com login is required.
•These limitations apply to video monitoring on SPA 525G phones:
–While monitoring video from the SPA 525G phone, the phone can still make and receive calls. However, inbound calls do not change the display focus, and the only visual indication will be a flashing LED associated with the line being called. To answer inbound calls, simply press the line button.
–If you are viewing video on the phone, the video application stops when you make an outbound call and does not automatically resume.
–There is no audio integration between the IP phone and the cameras.
–For SPA 525G phone loads prior to version 7.4.4, you cannot simultaneously enable the VPN client and video monitoring on SPA 525G phones. This issue is resolved in the 7.4.4 phone load, which is included in UC 500 software pack 8.0.4.
–Door Access Control from the SPA 525G phone using the GPIO ports on the back of the camera is not supported.
–The MJPEG settings for the cameras cannot be changed if the camera is integrated with the SPA 525G phone. Changing these settings will prevent the video stream from being displayed on the phone. These are the video settings that must be configured using the PVC2300/WVC2300 Configuration Utility:
Max Frame Rate: 10 fps
Fixed Quality: Normal
•The UC 500 software pack 8.0.4 does not contain the latest version of the SPA 500 Series phone firmware. To upgrade SPA 500 Series phones to the latest 7.4.6 software, use the drag-and-drop phone upgrade method in CCA. You must extract the .bin phone load file from the .zip file you downloaded from Cisco.com when using the drag-and-drop feature on SPA 500 Series phones.
•In mixed networks that have both AP541N and AP 521 wireless access points, the CCA 2.2(2) Wireless Setup Wizard automatically synchronizes AP541N settings only. In this case, existing AP 521 access points must be synchronized from the Configure > Wireless > WLANs (SSIDs) window.
•CCA 2.2(2) and later can discover a Services Ready Platform SRP 500 device and display its icon in the Topology view. However, in order to be discovered, the SRP 500 device must be connected to a UC 500 or a port on an ESW 500 Series switch that is connected to a UC 500. You must use the UC 500 or ESW 500 IP address as the starting IP address for discovering the SRP 500. You cannot use the IP address of the SRP 500 to discover the device or network.
•The Cisco VPN Client does not provide 64-bit support. However, 64-bit support is available for the Cisco AnyConnect VPN Client. This client and release notes can be obtained from the Software Center (www.cisco.com/go/software). If you do not have a valid service contract associated with your Cisco.com profile you cannot log in and download the AnyConnect VPN Client. The AnyConnect client supports SSL and DTLS. It does not support IPSec at this time.
For more information, see the release notes for the Cisco VPN Client and Cisco AnyConnect client.
•Remote SSL VPN phones (for example, SPA525G phones with remote VPN configured through the CCA VPN Phone Setup wizard) are not displayed in the Topology view.
•For full-tunnel mode with SSL-VPN server on UC 500 and SR 500 platforms, only the Anyconnect-win-2.3.2016-k9.pkg for Windows 32-bit or 64-bit OS is supported.
•If the PC running Cisco Configuration Assistant is not directly connected to the UC 500 LAN (through a wired connection or VPN connection), the Multisite Manager is not available. When managing a multisite deployment, care should be taken not to invoke or configure features such as software upgrade, backup and restore, internet connection, or restart/reset on remote sites.
•For Cisco SR 500 Series Secure Routers (all models), you cannot install an IPS (Intrusion Prevention System) Signature Data File (SDF) package with a version that is greater than 384. This is due to file size constraints on SR 500 devices.
As a workaround, install the SDF package version 384, then upgrade to a later version.
–When choosing an SDF package to install, select version 384 of the SDF package, which is sigv5-SDM-S384.
–After the SDF package is installed, choose Configure > Security > IPS and select the IPS Signature Update tab to perform the update.
•The following limitations apply to the WebEx PhoneConnect application:
–In order for WebEx PhoneConnect to function properly, password changes must be disabled on the WebEx service site. The WebEx site administrator must un-check the Allow user to change password option on the service site to disable it, even if Auto-Login APIs are being used.
–Once a phone has received two consecutive, unacknowledged meeting alerts, audio (tone) alerts are suspended until the phone user presses the Snooze, Dismiss, or Call softkey. This can occur when multiple unanswered alerts are received for the same meeting or for multiple meetings scheduled for the same time.
•The following limitation applies to the WebEx Connect client and may affect Cisco WebEx PhoneConnect users who are also using the click-to-dial feature.
–The WebEx Connect client Click-to-Dial feature does not work if you do not run as Administrator in Microsoft Windows Vista.
On a PC running the Microsoft Vista operating system, if you login with a username that has administrator privileges but does not have the username of Administrator or if you login with a username that does not have any administrator privileges, when you configure Click to Dial, you will encounter the following error:
Unable to get profile due to network or certificate issue
No workaround is available for an account without administrator privileges. The user must have administrator privileges in Vista in order for Click-to-Dial to work. For an account with administrator privileges: In Windows Explorer, go to the WebEx Connect client application (for example, C:\Program Files\WebEx\Connect), right-click on it, and choose Run as administrator. This launches the Connect client with the correct privileges to modify the registry for click-to-dial to work in Windows Vista.
•The following limitations apply to deployment of Cisco IP Phone SPA 525G phones in Wireless-G mode using Cisco Configuration Assistant:
–Multicast Music on Hold (MoH) for internal calls (IP phone-to-IP phone) is not supported for this solution and must be disabled using CCA.
When you disable MoH for internal calls, Music on Hold for the external MoH port on the UC 500 is also disabled.
To disable Music on Hold for internal calls using CCA:
1. Launch CCA and navigate to the Music on Hold configuration settings.
2. Uncheck these options: Enable external music on hold port and Enable music on hold for internal calls.
–Unicast paging groups are required with Cisco SPA 525G wireless phones. A maximum of ten (10) phones can be in a unicast paging group.
–The SPA 525G phone is not designed to comply with Japanese Wi-Fi requirements. Specifically it does not support channel 14.
The AP521G-PK9 SKU also does not support channel 14.
For detailed information on supported reference designs, limitations and caveats for deployment of Cisco IP Phone SPA 525G phones, see the Cisco SPA 525G Wireless Deployment Guide for Cisco SBCS, available at www.cisco.com/go/sbcs-docs.
•In the Port Settings window, you must apply a change to speed settings before you can change a duplex setting. After you configure a speed setting, click Apply, and then configure a duplex setting.
•You must use the Smartports feature to apply an Access Point role to Catalyst Express switch ports, ESW 500 Series switch ports, and Cisco Unified Communications 500 Series ports that are connected to wireless LAN controllers, autonomous access points, or lightweight access points.
•When you create or modify a service set identifier (SSID) for a wireless LAN controller:
–Assign the native VLAN to it only if the native VLAN is VLAN 1.
–Ensure that the IP address of the management and AP manager interfaces of the wireless LAN controller belong to the native VLAN.
•When you create or modify an SSID for an autonomous access point:
–Check Native VLAN only if the assigned VLAN is the native VLAN.
–Ensure that the IP address of the autonomous access point belongs to the native VLAN.
The following notes apply to Cisco Configuration Assistant 2.0 and later:
•When you start Cisco Configuration Assistant, Java determines whether the resources it needs are available.
If they are not, Java displays the message Could not create Java Virtual machine, and the session ends. To overcome this problem, open the file C:\Program Files\Cisco Systems\CiscoSMB\Cisco Configuration Assistant\startup\startup.properties (the default installation path), and modify this entry:
Replace 1024m with a lower setting that does not exceed the available RAM. There is no way to foresee what value will work. Try 512m, and lower it further if necessary.
This problem can occur on PCs with lesser specifications.
•If the Cisco Configuration Assistant InstallShield wizard fails to start, it is likely that there is a problem with the temporary folder location defined through the environment variables TMP and TEMP. Assign a correct temporary folder location to fix this problem.
Resolving Cisco Model 79xx Phone Upgrade Issues
After installing a UC 500 software pack that contains version 8.5(3) phone firmware for Cisco Model 79xx IP phones, Model 79xx phones being upgraded from firmware versions prior to 8.5(2) may not register or may register but still be running an older version of the phone firmware. When the phone attempts to upgrade to 8.5(3), you may see the message "Auth Fail" displayed on the phone.
This is due to a known issue with Model 79xx IP phones (the issue is documented in the Cisco Unified IP Phone Release Notes for Firmware Release 8.5(3) (SCCP and SIP (www.cisco.com/en/US/docs/voice_ip_comm/cuipph/firmware/8_5_3/english/release/notes/7900_853.html#wp57602).
For all SCCP firmware upgrades from firmware release versions earlier than 8.3(3) to version 8.5(3) or later, you must first upgrade your firmware to version 8.5(2). Once you have upgraded to version 8.5(2), you can upgrade your IP Phone to version 8.5(3) or later. The problem affects these CCA-supported phone models:
•Model 7975, 7970, and 7971
•Models 7945 and 7965
•Models 7942 and 7962
•Models 7941 and 7961
•Models 7906 and 7911
Perform the procedure in this section to correct the problem by upgrading the phones to an intermediate load before upgrading them to version 8.5(3) firmware.
Before You Begin—Download the 8.5(2) Phone Firmware
Download the 8.5(2) phone firmware .zip file for each model phone that must be upgraded. This is the intermediate load that will be used.
IMPORTANT You must download the 8.5(2) version of the phone firmware. The 8.5.2SR1 load cannot be used for this purpose.
To locate the 8.5(2) version of the SCCP (Skinny Client Control Protocol) version of the firmware for the desired phone models, follow these steps.
1. Log in to Cisco.com (you must have a Cisco.com login to download phone firmware).
2. Open a Web browser and go to www.cisco.com/go/software.
3. On the Download Software page, choose Voice and Unified Communications > IP Telephony > IP Phones > Cisco Unified IP Phone 7900 Series > Cisco Unified IP Phone <79xx>.
4. Click the Skinny Client Control Protocol (SCCP) Software link.
5. In the Search Release field, enter 8.5(2) and click Go.
6. Click the link to the 8.5(2) software.
7. Download the .zip file for the selected model. For example, the filename for Model 7975 phones is cmterm-7975-sccp.8-5-2.zip.
8. Repeat these steps to download 8.5(2) firmware for each of the phone models to be upgraded.
Upgrading the Phone Firmware
Perform these steps to upgrade the affected Model 79xx phones with version 8.5(2) firmware as an intermediate step and then upgrade them to version 8.5(3) firmware.
IMPORTANT The embedded TFTP server in CCA is used for drag-and-drop file uploads. Before performing the upgrade, disable any third-party TFTP services running on your PC and check the firewall and network security settings on your PC to make sure that TFTP packets can be transmitted between your PC and the UC 500.
1. Launch CCA and open the Topology view.
2. Drag and drop the .zip file with the 8.5(2) phone firmware onto the UC 500 icon in the Topology view.
Do not change the .zip file name or unzip the file.
3. In the File Upload dialog, click Upload.
CCA extracts the files from the .zip archive and copies them to a temporary directory on the UC 500 flash. If there are any TFTP and load configurations for 8.5(3), these are replaced with the intermediate 8.5(2) load and files.
The Phone Firmware Update dialog shows the progress of the upload. Once the files are copied to the flash, CCA displays the following message:
"Disconnect all Cisco Model <Model_Number> IP phones, and then reconnect them. Wait until the phone firmware upgrade completes, then click OK to continue."
4. Disconnect and then immediately reconnect the indicated phones and wait for the upgrade to complete on all the indicated phones.
IMPORTANT Do not click OK until all of the affected phones have upgraded their firmware and re-registered. The upgrade takes at least 10 - 11 minutes and the phones will restart. To verify that the interim load has been installed, press the settings button on the phone and navigate to Settings > Status > Firmware Versions > Load File. The interim load filename is SCCP45.8-5.2S.
After the interim upgrade completes, CCA removes the interim 8.5(2) TFTP and load commands, replaces them with the 8.5(3) TFTP and load commands, and then issues a reload/reset command to the phones to load the 8.5(3) firmware.
Once the final reload and reset completes, the phones will be upgraded to the 8.5(3) firmware and re-register with the UC 500.
5. Repeat these steps for each different phone firmware .zip file.
Cisco SBCS Features Supported Within CCA
The Cisco Smart Business Communications System Feature Reference Guide provides guidance to partners on the features that can be configured using the latest releases of CCA. The information is categorized by Voice, Switching, Wireless, and Security.
This guide is available on the Resources tab on the main Cisco Smart Business Communications product page (www.cisco.com/go/sbcs). From within CCA, you can choose Partners Connection > SBCS Feature Guide to access the guide.
This section describes the open caveats that could create unexpected activity in this software release.
IMPORTANT Some workarounds may require IOS command-line interface (CLI) configuration. The CLI configuration provided is not guaranteed to be compatible with future versions of CCA or UC 500 software packages.
Table 6 Open Caveats in Cisco Configuration Assistant 2.2(5) and earlier
Ref Number Description
UC 500 reboots during multi-party conference configuration
Symptom Under certain circumstances, the UC 500 may restart unexpectedly when using CCA, due to an IOS crash. The problem is rare and occurs very intermittently. The problem has been observed when the CCA user enables and applies multi-party conferencing, then immediately modifies Join and Leave Tone Settings for multi-party conferencing using CCA.
The problem is likely due to an internal timing issue in IOS that is related to use of the
restart allcommand by CCA when applying voice configuration.
When the UC 500 restarts, all configuration changes since the last Save are lost.
Workaround When applying voice configuration using CCA, wait until all phones have restarted and are ready to make calls before applying additional voice feature configuration using CCA. We also recommend that you configure production systems during off-peak hours to avoid interruptions in service for your users.
Broadcast SSID cannot be saved for more than one SSID on wireless screen
Symptom The WLANs (SSIDs) window under Configure > Wireless does not allow broadcast to be enabled on both voice and data SSIDs. However, this can be configured using the Wireless Setup Wizard. The issue occurs only on the UC540W internal access point.
If the Wireless Setup Wizard is used to configure data and voice SSIDs on the UC540W SSIDs with broadcast enabled on both SSIDs, and you subsequently attempt to make changes in the WLANs (SSIDs) window (Configure > Wireless > WLANs (SSIDs), the error message "Broadcast SSID already exists" is displayed when you try to make configuration changes to the SSIDs. You cannot save any changes until you disable broadcast on one of the SSIDs. In expert mode, CCA allows only one SSID to have broadcast enabled.
Workaround Re-run the Wireless Setup Wizard after applying configuration changes from the WLANs (SSIDs) window to enable broadcast on both SSIDs.
User Extensions tab: Overlay with CO LINE does not configure port to be CO LINE
Symptom When FXO lines are mapped to Overlay phone buttons on the User Extensions tab in the Voice window, incoming calls from the FXO line do not ring the phone. This is because the underlying FXO port is not configured as a CO_LINE.
Workaround Two steps are required for configuring Overlay buttons with CO Lines. You can perform these steps in any order.
1. Choose Configure > Telephony > Dial Plan > Incoming to open the Incoming Dial Plan window and select the Incoming FXO Calls tab. On the Incoming FXO Calls tab, set the Destination Type to CO_LINE for each FXO port that you want to configure as a CO_LINE.
2. Assign the CO Lines that are mapped to these FXO ports to Overlay buttons on phones.
After performing these steps, incoming calls on the CO Line will ring the Overlay buttons on the phones.
Smartports shows an incorrect UC560-BRI-K9 unit (FXS ports in wrong location)
Symptom For UC560-BRI-K9 unit, the front panel view of the UC 560 shown in the Smartports window shows the FXS ports in the wrong location.
CCA does not properly configure a SIP phone
Symptom When a Cisco Model 3951 SIP phone is connected to the UC 500, CCA discovers and displays the 3951 phones in the Topology view, but the phones are not listed on the User Extensions tab in the Voice window (Configure > Telephony > Voice > User Extensions). As a result, the phones cannot be configured using CCA.
Workaround Configure Cisco Model 3911 and Model 3951 SIP phones out-of-band using CLI.
SR520 crashes after applying IPS configuration
Symptom SR520 crashes after configuring IPS with CCA when the sigv5-SDM- S414.zip signature file is used.
Workaround None. Use a different IPS signature file.
SR520-T1: Change to LAN1 IP is saved in LAN0 IP instead
Symptom In the default configuration for the SR520, LAN0 (FastEthernet 0/0) is assigned to data pool 192.168.75.0 and LAN1 (FastEthernet0/1) has no IP address.
When the user launches the IP Address window in CCA, assigns an IP address to the LAN1 (FastEthernet 0/1) interface, and applies the configuration, CCA changes the IP address of the default DHCP pool named "data," (the default DHCP pool on the SR520-T1) and assigns it to LAN0 (FastEthernet 0/0) instead of creating a new DHCP pool and assigning it to LAN1 (FastEthernet 0/1).
Workaround None. CCA supports configuration of LAN0 (FastEthernet 0/0) only.
To and From display for dialable intercoms on the phone is reversed (CME issue)
Symptom The To and From labels displayed for dialable intercoms on the phone are reversed.
Workaround This problem does not affect functionality. To avoid confusion, you may want to use the same To and From label for the dialable intercom (for example, Dialable Intercom).
Telephony Setup Wizard: Configuring analog phones in user mode results in duplicate extensions
Symptom When an SCCP analog phone is assigned an extension number that is already assigned to an unassigned ephone-dn on the device, calls to that analog phone may sometimes result in a busy tone.
Workaround Use CLI to issue the command
where <tag> is the tag for the unassigned ephone-dn that contains the duplicate number.
To determine the <tag> of the unassigned ephone-dn with the duplicate extension number, choose Monitor > Telephony > Phones and Extensions from the feature bar in CCA.
CCA does not enable the radio on AP541 initial configuration
Symptom The radio on the AP541N access point is disabled by default. When CCA sends the initial Wireless SSID configuration to the AP541N, it should enable the radio, but it does not.
Workaround Use the AP541N Access Point Configuration Utility to enable the wireless radio. For information about how to enable this setting, see the Cisco AP541N Access Point Administration Guide or online help.
VPN address pool should different from remote local LAN
Symptom When configuring VPN server on an SR520-T1, CCA recommends the 192.168.75.128 to 192.168.75.137 address range for the VPN remote IP address. If a remote teleworker router is using 192.168.75.0 as VLAN1, and you chose to use 192.168.75.128 to192.168.75.137 for the VPN remote IP address range in the VPN server, then the remote teleworker router cannot assign an address from the 192.168.75.128 - 192.168.75.137 range to the loopback interface. The VPN address pool should be different from the remote teleworker VLAN1 IP address subnet, and CCA should not recommend 192.168.75.128 - 192.168.75.137 for VPN remote IP range.
This issue occurs on SR520-T1 secure routers only. It does not occur on non-T1 SR500 SKUs.
Workaround Do not use the remote teleworker router VLAN1 IP subnet for the VPN remote IP address range.
Anyconnect 2.5 does not work with the SR520-T1 SSL VPN sever
Symptom A SR520-T1 running SSL-VPN sever with version 2.5 of the Anyconnect client (anyconnect-win-2.5.0217-k9.pkg) cannot connect to the SSL VPN server due to a certification error.
Workaround Use version 2.3 of the Anyconnect client (anyconnect-win-2.3.0254-k9.pkg).
SIP Trunk: Support individual DIDs for diversion header on SIP trunks
Symptom When the UC 500 is using SIP trunks for PSTN access and there are hairpin calls from the PSTN to the UC 500 and back out to the PSTN, the diversion header for forwarded calls on SIP INVITE from the UC 500 only has the main number DID.
Need call hold audible alert notifications on CCA via the hold-alert CLI
Symptom CCA lacks support for the "hold-alert" ephone-dn configuration command. This command is used to set an audible alert notification on a Cisco Unified IP phone to remind the phone user that a call is on hold.
Workaround The only workaround for this issue is to configure the
hold-alertcommand via the CLI interface. This defect has no negative effects on call routing and does not hinder the performance of the voice gateway in any way.
Intercom: Label modifications do not take effect
Symptom When a one-to-one intercom label is modified in CCA, it does not take effect after the change has applied. The default label "Intercom" is always displayed.
CO Line: CO Line appears in Extension list in error
Symptom CCA allows you to assign the same CO line to two different buttons on the same phone when one button is an overlay. The issue is seen when you perform these steps:
1. On one button, select the type to be CO Line. Do not select or fill the extension field. Leave it blank.
2. On another button on the same phone, select an Overlay button and select a regular extension and a CO Line.
3. Go back to the line appearance created in step 1. Note that you the CO Line that you selected in step 2 still appears in the drop-down list.
Workaround You should not configure the same extension or CO Line on more than one button on the same phone, even if CCA allows you to do so. The issue is not specific to overlays.
Unable to create maximum number of Basic ACD hunt groups or other hunt groups due to mailbox issue
Symptom After creating the maximum number of users and blast groups, with personal mailboxes created for each user, CCA displays a "mailbox capacity reached "error if you then attempt to create the maximum number of Basic ACD hunt groups and services or other hunt groups because it cannot create GDM mailboxes for the groups. The Voicemail window, however, still shows that the required mailbox space is available.
Workaround None. This issue occurs because the CME and CUE configurations are out of sync.
Licensing: Transfer license returns error: Failed to revoke License: -ERR 21
Symptom When you choose License Management > License Management Actions > Transfer License To or From This Device > Remove Licensed and Save for Transfer, CCA returns the error: Failed to revoke License:-ERROR 21.
Reset to factory defaults has issues when an ESW 500 switch and UC 500 are both present at the customer site
Symptom If both a UC 500 and ESW 500 Series switch are present in the customer site and both are selected for factory reset, CCA prompts you to reconnect after restoring factory defaults on the ESW 500 switch. However, the UC 500 reset to factory defaults has already started. A dialog then appears that asks you whether you want to perform CUE diagnostics to verify that the voicemail system is working normally or ignore the warning and continue. Exceptions are also seen in the console output.
Workaround When restoring devices to factory default in CCA, select only one device at a time to restore. Wait until the restore is complete before choosing another device to reset.
If you see this dialog, click Yes to run the CUE diagnostics tool and verify that the voicemail system is operating normally before continuing. Ignoring the warning may result in system instability.
Multi-site IPSec / EZVPN cannot both be running at the same time
Symptom When both EasyVPN server and MultiSite VPN are configured on the same router/interface, the EZVPN IKE session does not get established. As a result, the EasyVPN client (SR 500) cannot communicate with the server site via the tunnel.
Workaround There is no workaround using CCA.
To correct the problem, you must use CLI to replace the wild card address (0.0.0.0 0.0.0.0) with its valid peer address.
crypto isakmp key key-string address 0.0.0.0 0.0.0.0should be changed to
crypto isakmp key key-string address<peer address>.
Software Upgrade: Progress Details window shows no entry
Symptom Software upgrade window progress bar sometimes does not show the upgrade tasks and status. The issue occurs when you choose Software Upgrade, uncheck auto disk cleanup, select three or more phone loads, and choose Yes to skip copying the IOS image and continue with the upgrade.
CUE reset fails if Reset to Factory Defaults is started immediately after CCA is launched
Symptom When using CCA 2.2(5), CUE reset fails if a Reset to Factory Defaults is initiated on the UC 500 immediately after CCA is launched and before voice data has finished loading.
Workaround To work around the problem, wait until voicemail data finishes loading (make sure that you can open the Voicemail window), then reset the UC 500 to factory defaults.
Validation missing while configuring user extension
Symptom On the User Extension tab in the Voice window, CCA allows you to configure extensions with the wrong number of digits.
Workaround Before applying the configuration, manually verify that all extensions contain the correct number of digits as specified in the Number of digits per extension field on the System tab in the Voice window.
Error in GUI and exception in console when a static route is configured with an invalid value
Symptom When invalid values are entered and applied in the Static Routes window, exceptions are shown in the console and the error bar in the CCA GUI lists the errors without descriptions.
Workaround Click Cancel, then re-open the window.
CO Line: Invalid extensions are shown in Select Extensions in a scenario
Symptom When an extension is changed, CCA issues a
no ephone-dn commandto clean up data on that ephone-dn and recreate an ephone-dn with the same tag and extension number. CCA then creates a new ephone-dn with the new, modified extension. The Overlay dialog is not aware of this change, so it still references the original ephone- dn tag. As a result, the Overlay button still has the old extension assigned.
Workaround The new, modified extension will be listed as an available extension in the Overlay dialog. Open the Overlay dialog, remove the old, invalid extension, select the newly created extension and add it to the Overlay, then click Apply.
SR520-T1: issues in Topology when SR520-T1 is added to customer site from Topology
Symptom CCA takes more than 2 or 3 minutes to re-display the Topology view after an SR520-T1 is added to a customer site from the Topology view. Also, the connected phones are not being displayed in the Topology view after running the SR 520-T1 Configuration Utility.
This issue occurs only when a SR520-T1 is added to an existing customer site from the Topology view.
Workaround Add the SR520-T1 to a customer site from the Connect window and not by choosing Add to Site from the right-click menu in the Topology view.
Apply does not work while modifying CFNA/CFB to numbers other than Voicemail or None
Symptom In the Voice window, when you select a configured user and set Call Forward No Answer or Call Forward Busy to a value other than Voicemail or None, the Apply button is not enabled.
Workaround Select the user and set CFNA or CFB to None so that the Apply button is enabled, enter an extension or other number, then click Apply.
System: Unclear how to remove Telephony System Message
Symptom On the System tab in the Voice window, if System Message contains only whitespace, no configuration is sent. Even if the text is changed so that a "no" command is sent to the router, the message defaults to "Cisco Unified CME."
Workaround To minimize the System Message on the phone display, set the System Message to a single character (for example, a period (.).
Application Update: If User Account Control is enabled, CCA does not automatically restart after the update.
Symptom On PCs running Microsoft Windows Vista, if User Account Control (UAC) is enabled and you use the CCA application update feature to upgrade to a newer version, CCA does not automatically restart after the update. The message "Another instance of Cisco Configuration Assistant is already running" is displayed.
Workaround Manually restart CCA after the application update by running the executable file.
Smartports: Shows UC560 BRI ports in the wrong place
Smartports: Missing UC 520 T1 port label and AL, LP, and CD indicators
Symptom Missing or inaccurate labels for status indicators and ports incorrectly positioned in the Smartports window.
License Management: Expand auto-registration range when license is installed
Symptom Auto registration failure for more than 16 phones on UC 560. Only the first 10 phones are registered and are assigned an extension.
Workaround Use the command-line interface (CLI) to change
auto assign 10 to 19under
telephony-serviceto the maximum license count installed.
User Extensions tab: Exceptions while configuring SIP users after VPN is configured
Symptom A Null Pointer Exception error occurs when you configure a SIP phone user on the User Extensions tab in the Voice window after configuring the VPN Server and EZ VPN on the UC 500. The Firewall - Edit ACL dialog appears unnecessarily when adding the SIP users.
Workaround Add SIP users before you configure the VPN server.
CCA application update Restart button does not work
Symptom Nothing happens when you click the Restart button after using the automated Application Update feature in CCA (System > Application Updates) to install a newer version of CCA.
Workaround Close CCA, then restart CCA to see the new version.
UC 520 Defective Flash
UC 520 crashes with checksum error after software upgrade
Symptom UC 520 does not boot after software upgrade and crashes with a checksum error. The UC 520 goes into rommon mode and console port access is locked. This problem can occur due to a defective compact flash. This issue affects Model UC 520 platforms only.
Workaround Replace the compact flash on the UC 520.
The following compact flash part were found to be defective:
Serial number: STI J11B207243104605
Cisco part number:
16-2651-02 CCE128JCGS1MA03H CISCO-01186-575CBH 070831 - FL1-001
Serial number: STI J11e107073054220
Cisco part number:
16-2651-02 CCD128JCGS1MA03H CIS00-01186-575CBH 070313 - FL1-006
Serial number: STI J183607073055821
Cisco part number:
16-2651-02 CCD128JCGS1MA03H CIS00-01186-575CBH 070313 - FL1-006
Out-of-band configuration causes CCA to fail to display voice information
Symptom CCA cannot display incoming dial plan if BRI is configured out-of-band.
Workaround Remove the out-of-band configuration.
WLANs: SPA 525G phones fail to sync with access point (AP) in the network
Symptom SPA 525G phones with Wi-Fi enabled are not associating automatically with the corresponding access point. The SPA 525G phones fail to automatically sync with the AP 521 or AP541N in a network when the SSID on the AP 521 or AP541N is changed via CCA.
Workaround Manually associate the phones with the corresponding access point.
Video Monitor Setup Wizard: Bonjour devices do not show connectivity in Topology view on discovery
Symptom If the UC 500 and PVC2300/WVC2300 cameras are part of a CCA customer site, the connectivity line between the cameras and the UC 500 is not displayed in the Topology view. This issue is seen only with wired devices, If a wireless camera is registered with an access point, the connectivity lines between the access point and cameras are displayed correctly in the Topology view.
Workaround Manually add links between cameras and devices by performing these steps:
1. Click on the camera icon on the Topology view.
2. Press and hold the CTRL key.
3. Select the device to which the camera is connected.
4. Right-click to open the pop-up menu.
5. Choose Add Link.
Unable to add/configure SIP phones via CCA
Symptom SIP phones added using the Telephony Setup Wizard or from the User Extensions tab in the Voice window (Configure > Telephony > Voice) are not configured.
Telephony Setup Wizard: Four digit extensions work, but subsequent phones get 3 digits
Symptom The UC 540 is configured with 4-digit extensions using the Telephony Setup wizard in CCA, which works correctly. However, when you add a new phone to the network, it automatically receives a 3-digit extension number instead of a 4-digit extension number.
Workaround On the User Extensions tab in the Voice window in CCA, manually re-configure the phones to assign 4-digit extensions.
PVC2300 camera disappears from CCA Topology view when video is used on SPA 525G phone
Workaround To temporarily display the camera in the Topology view, right-click on the Topology and choose Discover Bonjour Devices. However, the camera will disappear from the Topology the next time video is used on the SPA 525G phone.
CCA stops responding with a stack overflow error caused by ephone-dn for virtual mailbox
Symptom The voice dialog under Telephony hangs upon launch. CA requires ephone- dn(s) to be mapped to an ephone. If a user configures ephone-dn(s) for virtual mailboxes, CCA may stop responding when the Telephony > Voice > User Extensions tab is launched.
Workaround To work around the problem:
1. Close CCA.
2. Identify the ephone-dn(s) that are associated with the virtual mailboxes.
3. Configure a dummy ephone that is mapped to the ephone-dns identified in step 1. In the example below, they are ephone-dn's 42, 43, 44, and 45.
button 1:42 2:43 3:44 4:45
description Dummy Phone
4. Using CCA, open the Telephony > Voice > User Extensions tab and configure a username and password for the dummy IP phone.
ephone-dn must be in B-ACD hunt-group list if OOB intercom configuration is detected
Symptom If the configuration on a UC500 is modified using the CLI to include intercom ephone-dn in the overlay assigned to the 1st button. This causes the ephone-dn to not appear as an available member on the drop-down menu for B-ACD hunt groups (nor the User Extensions tab). If CCA detects this out-of-band (OOB) configuration with the primary line having overlay with intercom, it should still display the ephone-dn and allow it to appear on the B-ACD hunt group and call blast drop-down menus as well as the User Extensions tab.
CCA has a limitation whereby an intercom on the 1st button is NOT supported, while an Overlay on the 1st button is supported. As a result of this restriction, the configuration described above is an OOB configuration that was implemented via the CLI.
Workaround To correct the problem, remove the intercom extensions and make sure the 1st button does not have an intercom with overlay. After you restart CCA, this will allow the phones to appear on the B-ACD drop-down menu.
Need to be able to use a loopback IP address as source IP for XO SIP Trunk
Symptom XO SIP trunk requires the ability to specify source IP address for SIP and RTP packets on UC 500.
Workaround XO SIP trunk provider will provision circuit with source IP address to be the same as internet IP address on XO circuit.
SPA50x phones with expansion module option shows wrong icon in the Voice window
Problem: The wrong phone icon is displayed for SPA 500 Series phones if an expansion module is selected for the phone on the User Extensions tab in the Voice window.
Workaround None needed. The issue is cosmetic and does not affect functionality.
Multiple call forwards (CFwdALL) followed by rollover to voice mail not working
Symptom Assume the following call flow:
PSTN phone -> SIP trunk -> Phone A with CFwdALL to Phone B -> Rollover to voice mail
In this scenario, the PSTN phone continues to ring, and never rolls over to voice mail. Phone B disconnects after 10 seconds (as expected for rollover to voice mail), but the PSTN phone keeps ringing.
Topology View: Cisco AP 541N wireless AP only shows up to four (4) CDP client devices
Symptom A Cisco AP 541N with version 1.8.0 firmware only accepts up to four (4) CDP clients. As a result, some wireless devices associated to AP 541N are not displayed in the CCA Topology View.
Phone VPN Setup Wizard: Error Message should be thrown if config not applied
Symptom The CCA Phone VPN Setup Wizard does not display any error message if the phone is disconnected before the configuration is applied. When this occurs, the VPN phone configuration progress page in the wizard indicates that the configuration failed.
Phone VPN Setup Wizard: Display Password as Plain Text checkbox does not work
Symptom When configuring passwords in the Phone VPN Setup Wizard, passwords are always displayed as plain text even when the Display Password as Plain Text checkbox is disabled (unchecked).
Software Upgrade: Upgrading IOS Using TFTP Mode fails
Symptom When performing an IOS-only software upgrade with Remote TFTP Server selected as the Mode in the Upgrade Settings window, the upgrade fails with the error "Invalid/incompatible IOS image."
Workaround Choose a different upgrade method in the Upgrade Settings window when performing the upgrade.
CCA does not support multi-line configuration for SIP phones
Symptom CCA can only configure button 1 on a SIP phone (for example, a Model 3951 SIP phone). CCA does not configure other lines correctly.
Workaround When using CCA to configure a SIP phone, configure button 1 only.
Enabling or disabling the mailbox for a SIP phone does not update Call Forward settings
Symptom If you enable or disable the voice mailbox for a SIP phone in the Voicemail window (Configure > Telephony > Voicemail), Call Forward settings are not updated as expected on the User Extensions tab in the Voice window (Configure > Telephony > Voice).
Workaround Manually update the Call Forward settings on the User Extensions tab after enabling or disabling a voice mailbox for a SIP phone.
CCA might not configure the UC 500 correctly when several UC 500s are in the same customer site
Symptom CCA might not configure the UC 500 correctly if there are multiple UC 500s in the same customer site (multisite deployment scenario). These issues have been seen:
•The system extension for a remote site cannot be displayed.
•If a remote site has an SR 520-T1, it is shown as not connected on the Topology view.
•If a remote site uses the same extensions as the local site, these extensions are not shown as being unique.
Other issues might be encountered in addition to the ones listed above.
Workaround When working with UC 500s that are part of a multisite deployment, connect to only one UC 500 at a time. You can create separate customer sites to administer each site that is part of a multisite deployment. Any changes that you make to settings that are configured through the Multisite Manager after the initial setup must be imported to the other customer sites.
When Maximum Calls is set to 4, the fourth call does not go through
Symptom After configuring call admission control (CAC) by setting Maximum Calls to 4, make 4 voice calls. The fourth call to the PSTN gets a fast busy tone and does not go through.
When applying voice configuration, CLI Postview window pops up for system message
Symptom If CLI Postview is enabled, the CLI Postview window appears while voice configuration is being applied and displays a system message (telephony-service system message siteX") before the Apply completes.
Workaround Close the CLI Postview window and wait for the voice configuration changes to be applied.
Upgrading the image to router, task bar shows CUE information
Symptom When performing an IOS image-only upgrade, CUE information is incorrectly displayed in the Details section of the Software Upgrade window during the upgrade.
Workaround None. This does not affect the upgrade.
Opening multiple voice windows in quick succession can cause exceptions
Symptom Exception errors are displayed if several voice windows are opened quickly, one after another.
Workaround Close and re-open any voice windows that launched with errors. Wait until voice data has finished loading in one window before opening another voice window.
Cannot configure AA (upload script or .wav file) over site-to-site VPN connection
Symptom Cannot configure Auto Attendant for a remote site, even though the Configure > Telephony > Auto Attendant link is enabled for the remote site.
Workaround Configure Auto Attendant locally.
Call Forward set to None by default for imported users
Symptom When user and phone data is imported from a .csv file from the User Extensions tab in the Voice window, the default value that is used for Call Forward Busy (CFB) and Call Forward No Answer (CFNA) is None. The correct default setting for CFB and CFNA is Voicemail.
Workaround Choose Configure > Telephony > Voice from the feature bar in CCA and click the User Extensions tab. Manually configure CFB and CFNA settings for the imported users as needed.
CFNA and CFB are set to None by default (occurs intermittently)
Symptom When adding users and phones on the User Extensions tab in the Voice window, Call Forward Busy (CFB) and Call Forward No Answer are sometimes set to None as the default value. The problem occurs intermittently. The correct default setting for CFB and CFNA is Voicemail.
Workaround Choose Configure > Telephony > Voice from the feature bar in CCA and choose the User Extensions tab. Manually configure CFB and CFNA settings for the imported users as needed.
User screen does not show PSTN number configured for user's extension
Symptom The PSTN Number field on the User Extensions tab in the Voice window is empty, even though Direct Dial to User Extension is configured for that extension on the Direct Dialing tab in the Incoming Dial Plan window.
Workaround None. The PSTN Number field on the User Extensions tab in the Voice window is read-only.
VLAN conflict error incorrectly displayed when a VLAN is created with a special character in the name
Symptom A VLAN conflict error message is incorrectly displayed if you create a VLAN with a name that includes a special character. The following special characters cause the error: pound sign (#), plus sign (+), and forward slash (/).
Workaround When creating a new VLAN, do not use special characters in the VLAN name.
Unable to Configure CUE time from CCA; WebEx PhoneConnect meeting alert delivery is delayed
Symptom Cisco Webex PhoneConnect applications alerts are sent at the wrong time, and can be several hours off. This can occur if the NTP server on the UC 500 is not correctly configured on the CUE to sync up with the CME NTP server. Currently Cisco Configuration Assistant only configures the CME NTP server. It does not configure the NTP server on the CUE side.
Workaround Perform the following steps to work around the problem:
1. From a PC directly connected to the UC 500, open Internet Explorer and go to http:10.1.10.1 to launch the CUE web GUI and log in as administrator.
2. Go to System > Network Time & Time Zone Settings.
3. Add an NTP server (the CME NTP server at 10.1.10.2 is recommended).
Application Update from Cisco Configuration Assistant 1.x release to 2.0 must be done manually
Symptom Application Update does not work across major releases (for example, 1.x to 2.x). The installation must be performed manually.
Workaround Manually download and install Cisco Configuration Assistant 2.0 or later from Cisco web site (www.cisco.com/go/configassist).
CCA shows only 48 users supported despite having a valid 64-user license
Symptom On a 64-user UC 500 that is configured with the Telephony Setup Wizard, the Cisco Configuration Assistant application shows only 48 users are supported, despite having a valid 64-user license. In the configuration, the maximum number of supported e-phones is incorrectly reverted to 56.
Workaround Re-apply the 64-user license after the Telephony Setup Wizard completes (go to Maintenance > License Management to re-upload the license).
FXS port setting from Telephony Setup Wizard are not correctly shown in Voice window
Symptom When the Telephony Setup Wizard is used to shut down FXS ports or assign them to the Common Area Phone role, they are incorrectly displayed on the User Extensions tab in the Voice window (Configure > Telephony > Voice). FXS ports that have been shut down or configured as Common Area Phones or Fax should not be displayed on the User Extensions tab.
No warning message is displayed when user mailbox creation fails because storage limit is reached
Symptom If the voice mail storage limit has been reached and user voice mailbox creation fails, no warning message is displayed. The Mailboxes tab on the Voice Mail window also incorrectly lists the mailbox for the new user as Enabled.
Workaround Refresh the Voicemail window so that it correctly indicates that the user voice mailbox is Disabled.
Incorrect configuration sent to device after changing the extension type on the User Extensions tab
Symptom On the User Extensions tab in the Voice window, when a user changes the Button Type for an extension from Shared to Normal but does not change the extension number, the huntstop channel Cisco IOS command is not removed from the associated ephone-dn.
Workaround Delete the Shared extension and re-create it as a Normal extension.
Single Number Reach: SNR configuration window should list only one user for shared line
Symptom All users sharing a DN are displayed in Single Number Reach configuration window.
Workaround Configure SNR to only one shared line (that is, only one SNR number per directory number).
Single Number Reach: Extension types are not validated on the SNR Configuration window
Symptom All extension types are listed in the SNR Configuration window. However, not all extension types can be configured for SNR.
Port Settings window shows phones are half-duplex, but ESW switch shows full-duplex
Symptom The switch port runtime status in CCA is not consistent with the actual switch port settings on the ESW 500 Series switch. CCA reports that all switch ports are set for half-duplex.
Workaround Use the ESW 500 Series Switch Configuration Utility to view runtime status for ESW 500 Series switch ports.
WebEx PhoneConnect: Locale change not picked up unless admin enters WebEx PhoneConnect application screen
Symptom The user changes the CME locale after having configured WebEx PhoneConnect and the phone does not pick up the new language. This occurs only if the WebEx PhoneConnect configuration windows in Cisco Configuration Assistant are not accessed after the CME locale is changed.
Workaround Set the CME locale before configuring the WebEx PhoneConnect application.
Alternatively, after having set up PhoneConnect users and changed the CME locale, if WebEx PhoneConnect screens on user phones do not have the new language, do the following:
1. Exit any WebEx PhoneConnect configuration windows that may be open in CCA. Close any open WebEx PhoneConnect application screens on IP phones.
2. In CCA, go to Applications > Smart Business Applications, select the WebEx PhoneConnect application, click Setup Options and log in to the WebEx PhoneConnect application. This will open the PhoneConnect Application Main window and send the CME locale to the PhoneConnect application.
3. Click OK or Apply.
If the new language does not appear on the phones after performing the above actions, then do the following.
1. Exit all WebEx PhoneConnect configuration windows and IP phone screens again.
2. Restart CUE from the Maintenance window (Maintenance > Restart/Reset).
3. Wait for the CUE restart to finish.
WebEx PhoneConnect: Join before meeting start option is only available to host, not attendee.
Symptom When scheduling a non-audio WebEx Meeting Pro with an option to let attendees join x minutes before start time, alerts with the Call button x minutes before the start time are only sent to the host. Alerts for the attendees do not display a Call button until the meeting start time.
WebEx PhoneConnect: Intermittently phones can not dial into meeting.
Symptom Intermittently, phone users are unable to have PhoneConnect auto-dial into the meeting. After the Call button is pressed, the phone remains on the dialing screen, and no audio is heard.
Workaround To recover, the phone user must end the call manually. The phone user can then press the Services button, select WebEx Meetings > Today, click Details, then either click Call to re-try the auto-dial, or dial in to the meeting manually using the information from the meeting details page.
WebEx PhoneConnect: Alternate host and host cannot both join meeting.
Symptom If a user creates a meeting with an alternate host, then the host and the alternate host cannot both join the meeting. The first host to join the meeting is granted host privileges and the other host cannot join the meeting.
WebEx PhoneConnect: XML parser error when viewing meeting attendees
Symptom When a WebEx meeting title has special characters, an XML parser error is displayed on IP phones when viewing the attendees.
Day 2 changes for custom SIP Provider incorrect if made from a different PC
Some day 2 additions or modifications under Telephony are mis-configured for a custom SIP Provider. For example, an added DID may not register correctly. The custom SIP Provider name is shown in the SIP Provider drop-down list, but no template information is displayed, and the Cisco Configuration Assistant application log contains the following error:++: ERROR: : SIPData: SIP Provider read from device is not supported by any template: <PROVIDER NAME>
The problem occurs when a custom SIP Provider has been configured on the UC520, but the Cisco Configuration Assistant installation reading the configuration does not have the SIP Provider template (.xml) added.
To configure the custom SIP Provider on the UC 500 initially, the SIP Provider template (.xml) must be added to the Cisco Configuration Assistant installation. Once applied to the UC520, that configuration may be read back by any other Cisco Configuration Assistant installation, even if the custom SIP Provider was not added by the user. The problem occurs when modifications are made, and in this case, all attributes of that provider will be the system default.
In addition to SIP Trunk configurations, the following Telephony configurations depend on the attributes defined by the SIP Provider template (.xml) for correct behavior:
•Dial Plan: Outbound Call Handling
•Dial Plan: Inbound Call Handling
•Voicemail PSTN number
•AA PSTN numbers
Workaround Use only the original Cisco Configuration Assistant installation to make Telephony related modifications OR add the custom SIP Provider template (.xml) to all Cisco Configuration Assistant installations that may be used to configure the same UC 500.
DID not registered when Service Provider SIP trunk configuration is loaded from different PCs
Symptom A DID is not registered when Service Provider SIP trunk configuration is loaded to the UC 500 from two different devices (for example, from two PCs).
Workaround Only one device should be used to perform configuration of the SIP template using Cisco Configuration Assistant.
Dial Plan: Outgoing Numbers do not properly show out-of-band permissions
Symptom For Outgoing Numbers configured on from Dial Plan tab in the Voice window, permissions may be blank or upon selection of the Permissions field, the current value is lost. This can occur if the Permissions value is not supported—that is, it does not map to one of the following categories:
Workaround If the current value is lost, it may be restored by refreshing or closing and reopening the Voice window.
For any Outgoing Number with a permission not supported or configured by Cisco Cisco Configuration Assistant, use caution when making modifications and do not click the Permissions field.
Outgoing Number Permissions map to the following CLI:
corlist outgoing<corlist name>
For any out-of-band configuration, Cisco Configuration Assistant typically displays the value as greyed out (disabled) and does not allow further modification.
Dial Plan: Incoming dial plan does not handle swapping of AA numbers
Symptom When there are two Auto-Attendants configured as destinations for Many- to-One dial plans, and the pilot numbers of the two Auto-Attendants are swapped, both Many-to-One dial plans are configured with the same Auto-Attendant as the destination.
Workaround The swapping of Auto-Attendant numbers must be done in two operations.
For example, if the AA1 number is 600 and the AA2 number is 601, instead of swapping the numbers in one Apply or OK operation, set AA1 to some other number, for example, "700," set AA2 to 600, and click Apply or OK. To complete the swap, set AA1 to 601 and click Apply or OK.
IPS: Modify label in error message area
CCA does not give further detailed error message for invalid public key.
Symptom When the public key submitted for IPS (Intrusion Prevention System) is invalid, the error message area at the top of the screen displays the message, "Click on red items to show further details," but no details are shown ("Invalid public key" should be displayed for the label).
Workaround Update the public key to a valid one and retry the operation.
CCA shows flash space available = -1 when there is a flash error on the UC 520
Symptom When there is an issue with UC 520 flash, the Cisco Configuration Assistant Software Upgrade window shows available space on flash as -1. This issue typically occurs during when a software package is downgraded to a prior version.
Workaround Replace the flash or reload the router, then use the
dir flash:command to see if the flash is OK.
CCA only displays the first DCHP pool exclusion when multiple exclusions are configured
Symptom CCA only displays the first DHCP pool exclusion for multiple exclusion configuration. DHCP pools are not able to follow multiple exclusions. For example, if the following exclusions are configured using Configure > Routing > DHCP Server, DHCP Exclusions tab:
192.168.2.1 - 192.168.2.39
192.168.2.60 - 192.168.2.65
192.168.2.245 - 192.168.2.254
Only the first DHCP pool 192.168.2.40 through 192.168.2.59 is displayed. 192.168.2.66 through 192.168.2.244 should also be listed as a valid DHCP pool, but is not.
Workaround None — There is no functional impact.
CCA Device Setup Wizard - VLAN 1 Address change problem
Symptom The following issues are seen when the Device Setup Wizard is re-run after the initial setup to change the VLAN 1 IP address:
•IP NAT configuration is not updated to the latest VLAN IP address.
•If the user runs the Device Setup Wizard a second time (after the first time, the IP address is changed from the factory default IP address), CCA still displays the factory default 192.168.10.1 instead of the modified IP address.
Workaround Reconfigure NAT after the Device Setup Wizard VLAN 1 IP address change.
Dial Plan - interdigit timeout, CCA cannot read the default timeout 10
Symptom CCA cannot read the default interdigit timeout 10. If user configure 10 seconds of interdigit timeout value from CCA Dial Plan tab, CCA will show default 5 seconds on the GUI, even though 10 seconds is configured on the router.
Workaround Change the interdigit timeout value to 11 or 9 seconds.
Dial Plan - CCA cannot read back access code for emergency # if trunk list none
Symptom Access code for Emergency number will not be read back by CCA if the there is no trunk (T1/E1, BRI, FXO or SIP) associated with the emergency number (that is, None is selected for the trunk list for the emergency number).
Workaround An emergency number must always be associated with a trunk. You must either delete the emergency number or associate it with a trunk.
CCA should warn the user or remove Firewall from VLAN 100 when it is unchecked.
Symptom The firewall settings on the VLAN 100 and loopback 0 interfaces are not removed when invoking Cisco Configuration Assistant on a Cisco UC520 with a default firewall configuration. Note: VLAN 100 is used as the voice vlan and loopback 0 is used for tftp source-interface and sccp.
Workaround This is as designed.
Cisco Configuration Assistant is using the same username-password to access multiple devices
Symptom Users can discover and add a wireless LAN controller to a community regardless of the privilege setting for the device (read-write or read-only) or the privilege setting of the community (read-write or read-only).
Workaround The privilege settings for the wireless LAN controllers in a community should be the same when the same username and password pairs are associated with them. You should enter only read-write username and password pairs when discovering wireless LAN controllers in a read-write community, and you should enter the read-only username and password pairs when discovering wireless LAN controllers in a read-only community.
Cisco Configuration Assistant error message for the access point reload failure
Symptom After you upgrade the software of an autonomous access point, the device cannot be reloaded if it receives a new IP address from DHCP.
Workaround Remove the access point from the community, and add it back with the new IP address.
Mandatory for the user to remove or change the default credential
Symptom The 800 Series routers and the UC 500 are shipped with a default configuration that contains default user credentials (cisco/cisco). Cisco Configuration Assistant does not force you to change these default credentials after the initial configuration, therefore leaving a potential security hole in a production network.
Workaround Secure all UC 500 and 800 series devices by replacing the default cisco-user with a new admin-user, as follows:
1. From the Device Properties menu on the Configuration tab, select Users and Passwords.
2. Select a device from the device list. The local usernames for the selected device appear.
3. Click Create.
4. Enter the new username and password, and set the privilege level to 15.
5. Click OK. The new user appears in the local usernames list.
6. Select the default user cisco.
7. Click Delete, and then click OK.
8. Repeat Step 2 through Step 6 for each device.
Speed dial does not work if invoked over WAN interface with a firewall
Symptom You cannot use speed dial on the WAN interface. A firewall on the WAN interface blocks the TFTP traffic used by the speed dial feature.
Workaround Manually configure the firewall to allow TFTP traffic between the PC and the device.
SIP trunk error message should request mandatory fields
Symptom If you do not enter values for the mandatory SIP trunk fields, Cisco Configuration Assistant displays the message "please correct errors marked in red." The message should be "Fields marked in red are mandatory."
Workaround There is no workaround.
SIP Trunk: Service provider drop-down menu should not include AT&T and Cbeyond
Symptom Outgoing Dial Plan is not compatible with the SIP Trunk Service Provider selected.
•The Outgoing Numbering Plan Locale selected on the Dial Plan tab in the Voice window is not North American.
•AT&T and Cbeyond Communications and several other North American SIP trunk providers can still be selected from the SIP Trunk Providers list on the SIP Trunk tab.
This is a usability issue; it does not impact functionality.
Workaround Always select the North American for the Number Plan Locale when configuring SIP Trunk Providers AT&T, Cbeyond Communications, or any other North American SIP Trunk Provider. Generally, Service Providers are associated with specific locales. Make sure that the SIP Trunk Service Provider selected is compatible with the Number Plan Locale selected.
Active conferences dropped and ad-hoc hardware configuration delete fails on configuration of AT&T SIP Trunks
Symptom Active ad-hoc conferencing might be terminated while configuring other features, such as AT&T SIP Trunk. Also, the hardware-based ad-hoc conferencing configuration might not be deleted after switching to software conferencing (3 or fewer participants).
Workaround We recommend that you verify that no active conferencing calls are present before modifying the device configuration by using Cisco Configuration Assistant. If this recommendation is not followed and the hardware-based ad-hoc conferencing configuration is not deleted after switching to software conferencing, save the configuration on the device and reload, then switch to software based conferencing in Cisco Configuration Assistant.
The time zone change message is not intuitive and it is sometimes misleading
Symptom A warning message, "CUE reload need at least 5 minutes, do you want to proceed with reload?" displays when time zone changes are made. No time zone changes are made to the CME if you skip the message.
Workaround Do not cancel the message if you intend to change the time zone.
Resolved Caveats in CCA 2.2(5)
This section describes the resolved caveats for the current release.
Caveats Resolved in Cisco Configuration Assistant 2.2(5)
Cisco Small Business Support Community
The Cisco Small Business Support Community site provides resources to assist VARs and Partners with design, implementation, and maintenance for Cisco SBCS platforms. To access the Cisco Small Business Support Community, point your web browser to the following URL:
Documentation for Cisco Configuration Assistant
The following documentation is provided for Cisco Configuration Assistant:
•Cisco Configuration Assistant Smart Business Communications System Administrator Guide, a comprehensive, end-to-end guide that covers all features and configuration tasks that can be performed using CCA.
The administration guide is also available in PDF format through the online help system in CCA.
•Online help. To access online help, click the Help button provided in CCA windows and dialogs, choose Help > Contents from the menubar, or press F1 to display Help for the active window.
•These release notes
To access documentation for Cisco Configuration Assistant on Cisco.com, visit the following URL:
Where to Go From Here
Cisco provides a wide range of resources to help you and your customer obtain the full benefits of Cisco Configuration Assistant.
Cisco Configuration Assistant
Cisco Configuration Assistant
Cisco Configuration Assistant Technical Documentation
Cisco Small Business Cisco Partner Central for Small Business (Partner Login Required) Cisco Small Business Home Cisco Small Business Support
Cisco Small Business Support Community
Cisco Small Business Support and Resources
Phone Support Contacts
Cisco Small Business Firmware Downloads
Select a link to download firmware for Cisco Small Business Products. No login is required.
Downloads for all other Cisco Small Business products, including Network Storage Systems, are available in the Download area on Cisco.com at www.cisco.com/go/software (registration/login required).
Cisco Smart Business Communications System and Components
Cisco UC 500 software packages and localization files
(Cisco.com Login Required)
Cisco Smart Business Communications System
Cisco Unified Communications 500 Series
Cisco SPA 500 Series IP Phone
Cisco SPA 300 Series IP Phones
Cisco Unified IP Phones 7900 Series
Cisco AP541N Access Point
Cisco SA 500 Security Appliance
Cisco ESW 500 Series Switches
Cisco PVC2300 (Audio/PoE) and WVC2300 (Audio/Wireless-G) Business Internet Video Cameras
Cisco Secure Router SR 500 Series
Open Source License Notices
The Open Source LIcense Notice for CCA 2.2(5) is available on the CCA Software Download page on Cisco.com.
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
© 2010 Cisco Systems, Inc. All rights reserved.
Document Number: 78-19558-01