Refer to the Cisco Unified Communications Manager Business Edition Documentation Guide and other publications that are specific to your Cisco Unified Communications Manager release. Navigate from the following URL:

New and Changed Information

Hardware Diagnostics

Cisco Unified Wireless IP Phones are frequently returned and a replacement is requested when the phone is operational. In firmware 1.3(4), a self-diagnostic tool is available to determine if a valid hardware issue exists.

You can access the Diagnostics menu from the Phone Settings menu, where the Keypad, Speaker, Microphone and WLAN Radio and Antenna can be validated.

The WLAN diagnostics menu is the standard site survey utility, which will use the current network profile information to scan for the configured network.

Bulk Deployment Utility

Firmware release 1.3(4) introduces the bulk deployment utility for Cisco Unified Wireless IP Phone 7925G and 7921G. This utility may be used to provision the phones if they have the same security settings (i.e. WPA2-PSK) or if they have unique 802.1x accounts.

Two deployment methods are supported—Default and Bulk. The bulk deployment method requires that a CSV file is imported containing the MAC address, username, and password. A configuration file is created using the CSV file and the common credentials (SSID, Security mode, 802.11 mode, etc.). When using the bulk deployment method, the username and password apply to Network profile 1 only.

The Bulk Deployment Utility does not support EAP-TLS or PEAP with server validation because it does not support certificates.

PEAP, without server validation, is supported using the Bulk Deployment utility. If a server validation is required, you must import the server certificate using the phone and enable server validation in the network profile via the phone web page.

Note The bulk deployment utility can support a CSV file with a maximum of 1000 entries.

Interband Roaming

Interband Roaming allows a Cisco Unified Wireless IP Phone to seamlessly roam between 2.4 GHz and 5.0 GHz bands. This feature allows you to configure the phone for an Auto 802.11 mode (i.e. Auto-RSSI, Auto-a, or Auto-b/g) that will scan both bands during an active call and will use a less preferred band if the preferred band is no longer available.

Interband roaming is leveraged for various scenarios:

•5 GHz indoor and 2.4 GHz outdoor

•Migrating from 2.4 GHz to 5 GHz

•2.4 GHz footprint but 5 GHz band for critical areas only (5 GHz cannot provide adequate coverage for all areas.)

When a phone is idle, it may scan, depending on the scan mode configured in the Unified CM. If the phone is configured for automatic scan mode, the Cisco Unified Wireless IP Phone will not scan until the current signal reaches the scan threshold. At this point, it will scan both bands.

If the phone if configured for continuous scan mode, an idle phone may scan both bands depending on the number of 2.4 GHz neighbors that are available. If enough neighbors are available and there is a 2.4 GHz candidate with an adequate signal, the phone can possibly stop scanning 5 GHz (active channel parking) and roam to 2.4 GHz to preserve battery life.

The Auto-RSSI logic is also used when the phone is idle and is configured for an Auto 802.11 mode and continuous scan mode. If the 2.4 GHz signal reaches the scan threshold, the 5 GHz channel scanning will resume. If there is an inbound or outbound call, the phone can temporarily roam to 5GHz, if available. However, the phone can roam to 2.4 GHz after the call is terminated if the channel parking criteria is met.

Before firmware release 1.3(4), both bands would be scanned only at power up or if the current band was lost if configured for an Auto 802.11 mode. Because of this, there was no seamless roaming since the current band would have been disconnected before the target band could be discovered. Also, there was a possibility that the phone could stay connected to the less preferred band (i.e. connected to 2.4 GHz when it is configured for Auto-A mode and a good 5 GHz signal is available).

Full CCKM Support

Cisco Centralized Key Management (CCKM) reduces the amount of delay time by centralizing the key management, which reduces the number of key exchanges. To optimize secure roaming, CCKM can be enabled while in WPA or WPA2 mode.

Prior to this firmware release, CCKM was not supported when WPA2/AES was selected; this required a full re-authentication when roaming between access points, and could result in loss of audio during the roam. Now that CCKM is supported when WPA2/AES is selected, the full re-authentication is no longer required and roaming to a new access point should not result in any perceptible loss of audio.

Firmware Installation Procedure

Before using the Cisco Unified Wireless IP Phone 7925G or 7921G with Cisco Unified Communications Manager, you must install the latest firmware on all Cisco Unified Communications Manager servers in the cluster.

Before You Begin

To make the Cisco Unified Wireless IP Phone available in the Cisco Unified Communications Manager system, you might need to upgrade your system with the latest DevPack patch for your release of Cisco Unified Communications Manager. Check the Readme file (cmterm-7925-sccp.1-3-4-Readme.html or cmterm-7921-sccp.1-3-4-Readme.html) that is posted with the firmware version 1.3(4) for more information.

Step 8 Click one of these hyperlinks, and follow the prompts to download the firmware:

•For Cisco Unified CallManager release 4.3 and earlier:

Cisco Unified Wireless IP Phone 7925G:

cmterm-7925-sccp.1-3-4.exe

Cisco Unified Wireless IP Phone 7921G:

cmterm-7921-sccp.1-3-4.exe

•For Cisco Unified CallManager release 5.1 and later:

Cisco Unified Wireless IP Phone 7925G:

cmterm-7925-sccp.1-3-4.cop.sgn

Cisco Unified Wireless IP Phone 7921G:

cmterm-7921-sccp.1-3-4.cop.sgn

•For image upgrade via USB:

Cisco Unified Wireless IP Phone 7925G:

CP7925G-1.3.4.TAR

Cisco Unified Wireless IP Phone 7921G:

CP7921G-1.3.4.TAR

Step 9 Double-click one of the downloadable files in Step 1, and click the Readme hyperlink, under the Additional Information section, which contains installation instructions for the corresponding firmware:

•Cisco Unified Wireless IP Phone 7925G:

cmterm-7925-sccp.1-3-4-Readme.html

•Cisco Unified Wireless IP Phone 7921G:

cmterm-7921-sccp.1-3-4-Readme.html

Step 10 Follow the instructions in the Readme file to install the firmware.

Step 7 For the 7925G device type, set the load type to CP7925G-1.3.4.LOADS

For the 7921G device type, set the load type to CP7921G-1.3.4.LOADS

For more information about this procedure, refer to the "Installing and Upgrading Cisco Unified CME Software" chapter in the Cisco Unified Communications Manager Express System Administrator Guide at this URL:

For firmware release 1.3(4), Cisco Unified Wireless IP Phone 7925G Configuration Utility version 1.3(1) or the Cisco Unified Wireless IP Phone 7921G Configuration Utility version 1.2(1), depending on which model is used, is required for using the Wavelink Avalanche server to configure the phone.

Note If you use the Wavelink Avalanche Management Console to configure your phone, be aware that the Cisco Unified Wireless IP Phone 7925G Configuration Utility (CU) version 1.3(1) is labeled as 7921G, but that CU works for the both the Cisco Unified Wireless IP Phone 7925G and Cisco Unified Wireless IP Phone 7921G.

Important Notes

This section provides general information about using and supporting the Cisco Unified Wireless IP Phone 7925G in your system:

Battery Life After Returning From Out of Range State

The Cisco Unified Wireless IP Phone may have a short battery life after returning from the out-of-range state. The battery life can be two to four hours long if the IP phone travels out of range for up to three to five seconds, and then returns in range of the configured network without rebooting the IP phone.

This may occur with IP phones using firmware release 1.3(4), but not with any earlier release. If your IP phone experiences a short battery life after it has operated out-of-range for a few seconds, you can reboot the IP phone. The out-of-range alert may be enabled in Unified CM to provide a notification anytime the IP phone leaves the service area. For more information of the status of this operation, refer to CSCtf82507, using the Software Bug Toolkit.

USB Connection Disabled After Powering Off/On the Phone

If you power off the Cisco Unified Wireless IP Phone 7925G with the USB cable connected and then power it on again, the USB connection might fail.

To enable the USB connection, unplug the USB cable from the phone and then plug it back in.

Use in Healthcare Environments

This product is not a medical device and uses an unlicensed frequency band that is susceptible to interference from other devices or equipment.

Increasing the Debug Level in Trace Settings Can Impact Voice Quality

Voice quality can be impaired when you set system log trace files for higher debug levels. Set only the modules that are required when capturing trace files for a phone.

Supported Access Points

When deploying voice over the wireless LAN, ensure the autonomous access points have Cisco IOS Version 12.3(8)JEA or later, and controllers have version 4.0 or later.

Third-party access points are not supported since there is no interoperability testing with these access points. However, as long as the access point supports the key features and follows the standards, the Cisco Unified Wireless IP Phone should be compliant.

Wi-Fi compliant APs that are manufactured by third-party vendors should support the Cisco Unified Wireless IP Phone 7925G, but might not support key features such as Wi-Fi MultiMedia (WMM), Unscheduled Auto Power Save Delivery (U-APSD), Traffic Specification (TSPEC), QoS Basic Service Set (QBSS), Dynamic Transmit Power Control (DTPC), or proxy ARP.

To look for information about a specific problem, enter the bug ID number in the "Search for bug ID" field, then click Go.

Open Caveats

Table 3 lists Severity 1, 2 and 3 defects that are open for the Cisco Unified Wireless IP Phone 7925G and 7921G using firmware release 1.3(4).

For more information about an individual defect, you can access the online record for the defect by clicking the Identifier or going to the URL shown. You must be a registered Cisco.com user to access this online information.

Because defect status continually changes, be aware that Table 3 reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit as described in the "Using Bug Toolkit" section.

Resolved Caveats

For more information about an individual defect, you can access the online record for the defect by clicking the Identifier or going to the URL shown. You must be a registered Cisco.com user to access this online information.

Because defect status continually changes, be aware that Table 4 reflects a snapshot of the defects that were resolved at the time this report was compiled. For an updated view of resolved defects, access Bug Toolkit as described in the "Using Bug Toolkit" section.

A blank IP address is exported to the Wireless IP Phone when configured via the webpage

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

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)

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.