Cisco Desktop Collaboration Experience DX650 Administration Guide, Release 10.0(1)
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Updated:
- June 18, 2015
Chapter: Cisco Desktop Collaboration Experience and Your Network
Cisco Desktop Collaboration Experience and Your Network
- Cisco Unified IP Communications Product Interactions
- Cisco Desktop Collaboration Experience Power
- Phone Configuration Files
- Phone Startup Process
- Cisco Unified Communications Manager Phone Addition Methods
- Cisco Desktop Collaboration Experience DX600 Series Phone MAC Address Determination
Cisco Unified IP Communications Product Interactions
Cisco Desktop Collaboration Experience DX600 series devices enable you to communicate by using voice over a data network. To provide this capability, Cisco Desktop Collaboration Experience phones depend on and interact with several other key Cisco Unified IP Telephony components, including Cisco Unified Communications Manager.
To function in the IP telephony network, the Cisco Desktop Collaboration Experience phone must connect to a network device, such as a Cisco Catalyst switch. You must also register the Cisco Desktop Collaboration Experience phone with a Cisco Unified Communications Manager system before you can send and receive calls.
This chapter focuses on the interactions between the Cisco Desktop Collaboration Experience DX600 series and Cisco Unified Communications Manager, DNS and DHCP servers, TFTP servers, and switches. The chapter also describes phone power options.
For related information about voice and IP communications, see this URL:
http://www.cisco.com/en/US/partner/products/sw/voicesw/index.html http://www.cisco.com/en/US/products/sw/voicesw/index.html
- Cisco Desktop Collaboration Experience and Cisco Unified Communications Manager Interaction
- Cisco Desktop Collaboration Experience and VLAN Interaction
Cisco Desktop Collaboration Experience and Cisco Unified Communications Manager Interaction
Cisco Unified Communications Manager is an open, industry-standard call processing system. Cisco Unified Communications Manager software sets up and tears down calls between phones, integrating traditional PBX functionality with the corporate IP network. Cisco Unified Communications Manager manages the components of the IP telephony system, such as the phones, the access gateways, and the resources necessary for features such as call conferencing and route planning. Cisco Unified Communications Manager also provides:
-
Firmware for phones
-
Configuration, CTL, and Identity Trust List (ITL) files using the TFTP service
-
Phone registration
-
Call preservation, so that a media session continues if signaling is lost between the primary Unified Communications Manager and a phone
For information about configuring Cisco Unified Communications Manager to work with the IP devices that are described in this chapter, see the "Cisco Unified IP Phone Setup" chapter in the Cisco Communications Manager Administration Guide.
 Note | If Cisco Desktop Collaboration Experience does not appear in the Phone Type drop-down list in Cisco Unified Communications Manager Administration, go to the following URL and install the latest support patch (software update or device pack) for your version of Cisco Unified Communications Manager: http://www.cisco.com/cisco/software/navigator.html To start, enter Cisco Unified Communications Manager in the search field and click Find. For more information, see the Telephony Features Available. |
Cisco Desktop Collaboration Experience and VLAN Interaction
The Cisco Desktop Collaboration Experience DX600 series phone contains an internal Ethernet switch, enabling forwarding of packets to the phone, and to the computer (access) port and the network port on the back of the phone.
If a computer is connected to the computer (access) port, the computer and the phone share the same physical link to the switch and share the same port on the switch. This shared physical link has the following implications for the VLAN configuration on the network:
-
The current VLANs might be configured on an IP subnet basis. However, additional IP addresses might not be available to assign the phone to the same subnet as other devices that connect to the same port.
-
Data traffic present on the VLAN supporting phones might reduce the quality of VoIP traffic.
-
Network security may indicate a need to isolate the VLAN voice traffic from the VLAN data traffic.
You can resolve these issues by isolating the voice traffic onto a separate VLAN. You can reconfigure the switch port to which the phone connects for separate VLANs for carrying:
-
Voice traffic to and from the IP phone (auxiliary VLAN on the Cisco Catalyst 6000 series, for example)
-
Data traffic to and from the PC that connects to the switch through the computer (access) port of the IP phone (native VLAN)
Isolating the phones on a separate, auxiliary VLAN increases the quality of the voice traffic and allows a large number of phones to be added to an existing network that does not have enough IP addresses for each phone.
For more information, see the documentation that is included with a Cisco switch. You can also access switch information at this URL:
http://cisco.com/en/US/products/hw/switches/index.html
Cisco Desktop Collaboration Experience Power
The Cisco Desktop Collaboration Experience can be powered with external power or with Power over Ethernet (PoE). A separate power supply provides external power. The switch can provide PoE through the phone Ethernet cable.
Note | When you install a phone that is powered with external power, connect the power supply to the phone and to a power outlet before you connect the Ethernet cable to the phone. When you remove a phone that is powered with external power, disconnect the Ethernet cable from the phone before you disconnect the power supply. |
- Power Guidelines
- Power Outage
- Phone Power Reduction
- Power Negotiation Over LLDP
- Wi-Fi Power Management
- Additional Information About Power
Power Guidelines
The following table provides guidelines for Cisco Desktop Collaboration Experience DX600 series device power.
|
Power Type |
Guidelines |
||
|---|---|---|---|
|
External power: Provided through the CP-PWR-CUBE-4= external power supply |
The Cisco Desktop Collaboration Experience DX600 series phone uses the CP-PWR-CUBE-4 power supply.
|
||
|
External power—Provided through the Cisco Unified IP Phone Power Injector |
The Cisco Unified IP Phone Power Injector may be used with any Cisco Desktop Collaboration Experience phone. Functioning as a midspan device, the injector delivers inline power to the attached phone. The Cisco Unified IP Phone Power Injector connects between a switch port and the phone, and supports a maximum cable length of 100m between the unpowered switch and the phone. |
||
|
PoE power—Provided by a switch through the Ethernet cable attached to the phone |
Cisco Desktop Collaboration Experience DX600 series devices support IEEE 802.3af Class 3 power on signal pairs and spare pairs. Cisco Desktop Collaboration Experience DX600 series devices support IEEE 802.3at for external add-on devices. To ensure uninterruptible operation of the phone, make sure that the switch has a backup power supply. Make sure that the CatOS or IOS version that runs on your switch supports your intended phone deployment. See the documentation for your switch for operating system version information. Support for NG-PoE+: The Cisco Desktop Collaboration Experience DX600 series devices can draw more power than IEEE 802.3at, as long as there is NG-PoE+ switch support. |
Power Outage
Your access to emergency service through the phone requires the phone to receive power. If an interruption in the power supply occurs, Service and Emergency Calling Service dialing do not function until power is restored. In the case of a power failure or disruption, you may need to reset or reconfigure equipment before you can use the Service or Emergency Calling Service dialing.
Phone Power Reduction
You can reduce the amount of energy that the Cisco Desktop Collaboration Experience DX600 series device consumes by using Power Save or EnergyWise (Power Save Plus) mode.
Power Save Mode
In Power Save mode, the backlight on the screen is not lit when the phone is not in use. The phone remains in Power Save mode for the scheduled duration or until the user lifts the handset or presses any button. In the Product Specific Configuration area of the Phone Configuration window on Cisco Unified Communications Manager Administration, configure the following parameters:
- Days Display Not Active
-
Specifies the days that the backlight remains inactive.
- Display on Time
-
Schedules the time of day that the backlight automatically activates.
- Display on Duration
-
Indicates the length of time that the backlight is active after the backlight is enabled by the programmed schedule.
EnergyWise Mode
In addition to Power Save mode, the Cisco Desktop Collaboration Experience DX600 series phone supports Cisco EnergyWise (Power Save Plus) mode. When your network contains an EnergyWise (EW) controller (for example, a Cisco switch with the EnergyWise feature enabled), you can configure these phones to sleep (power down) and wake (power up) on a schedule to further reduce power consumption.
Set up each phone to enable or disable the EnergyWise settings. If EnergyWise is enabled, configure a sleep and wake time, as well as other parameters. These parameters are sent to the phone as part of the phone configuration XML file. In the Phone Configuration window in Cisco Unified Communications Manager Administration, configure the following parameters:
- Enable Power Save Plus
-
Selects the schedule of days for which the phone powers down.
- Phone On Time
-
Determines when the phone automatically turns on for the days that are selected in the Enable Power Save Plus field.
- Phone Off Time
-
Determines the time of day that the phone powers down for the days that are selected in the Enable Power Save Plus field.
- Phone Off Idle Timeout
-
Determines the length of time that the phone must be idle before the phone powers down.
- Enable Audio Alert
-
When enabled, instructs the phone to play an audible alert starting 10 minutes before the time that the Phone Off Time field specifies.
- EnergyWise Domain
-
Specifies the EnergyWise domain that the phone is in.
- EnergyWise Secret
-
Specifies the security secret password that is used to communicate within the EnergyWise domain.
- Allow EnergyWise Overrides
-
Determines whether you allow the EnergyWise domain controller policy to send power-level updates to the phones.
When a phone is sleeping, the power sourcing equipment (PSE) provides minimal power to the phone to illuminate the Lock button, and the Lock button can be used to wake up the phone when it is sleeping.
Power Negotiation Over LLDP
The phone and the switch negotiate the power that the phone consumes. Cisco Desktop Collaboration Experience DX600 series devices operate at multiple power settings, which lowers power consumption when less power is available.
After a phone reboots, the switch locks to one protocol (CDP or LLDP) for power negotiation. The switch locks to the first protocol (containing a power Threshold Limit Value [TLV]) that the phone transmits. If the system administrator disables that protocol on the phone, the phone cannot power up any accessories, because the switch does not respond to power requests in the other protocol.
Cisco recommends that Power Negotiation always be enabled (default) when the phone connects to a switch that supports power negotiation.
If Power Negotiation is disabled, the switch may disconnect power to the phone. If the switch does not support power negotiation, disable the Power Negotiation feature before you power up accessories over PoE. When the Power Negotiation feature is disabled, the phone can power the accessories up to the maximum that the IEEE 802.3af-2003 standard allows.
Note | When CDP and Power Negotiation are disabled, the phone can power the accessories up to 15.4 W. |
Wi-Fi Power Management
The Cisco Desktop Collaboration Experience DX650 uses Unscheduled Auto Power Save Delivery (U-APSD) for power management if Wi-Fi Multimedia (WMM) is enabled and U-APSD is supported. If WMM is disabled, or U-APSD is not available, the Cisco DX650 uses Power Save Poll (PS-POLL) for power management. For more information, see the Cisco Desktop Collaboration Experience DX600 Series Wireless LAN Deployment Guide.
Additional Information About Power
The documents in the following table provide more information on the following topics:
-
Cisco switches that work with Cisco Unified IP Phones
-
Cisco IOS releases that support bidirectional power negotiation
-
Other requirements and restrictions about power
|
Document Topic |
URL |
|---|---|
|
Cisco Unified IP Phone Power Injector |
http://www.cisco.com/en/US/products/ps6951/index.html |
|
PoE Solutions |
|
|
Cisco Catalyst Switches |
http://www.cisco.com/cisco/web/psa/default.html?mode=prod http://www.cisco.com/en/US/products/hw/switches/index.html |
|
Integrated Service Routers |
http://www.cisco.com/en/US/products/hw/routers/index.html |
|
Cisco IOS Software |
Phone Configuration Files
The TFTP server stores the phone configuration files that define parameters for connecting to Cisco Unified Communications Manager. In general, any time you make a change in Cisco Unified Communications Manager that requires the phone to be reset, a change is automatically made to the configuration file for the phone.
Configuration files also contain information about the image load that the phone should be running. If this image load differs from the one that is currently loaded on a phone, the phone contacts the TFTP server to request the required load files.
A phone accesses a default configuration file, named XmlDefault.cnf.xml, from the TFTP server when the following conditions exist:
-
You enable autoregistration in Cisco Unified Communications Manager.
-
You have not added the phone to the Cisco Unified Communications Manager database.
-
The phone is registering for the first time.
Note | If the device security mode in the configuration file is set to Authenticated or Encrypted, but the phone has not received a CTL or ITL file, the phone makes four attempts to obtain the file so the phone can register securely. |
If autoregistration is not enabled and Cisco DX650 has not been added to the Cisco Unified Communications Manager database, Cisco DX650 registration request will be rejected. Cisco DX650 displays either Telephone service is unavailable or Lost connection to the server on the screen.
Cisco DX650 accesses the configuration file named SEPmac_address.cnf.xml, where mac_address is the Ethernet MAC address of Cisco DX650. The description field in the Phone Configuration window of Cisco Unified Communications Manager Administration is prepopulated when the device is first configured. The MAC address uniquely identifies the Cisco DX650 device.
Phone Startup Process
When connecting to the VoIP network, the Cisco Desktop Collaboration Experience DX600 series phone goes through a standard startup process. Depending on your specific network configuration, only some of these steps may occur on your Cisco DX650.
-
Obtain power from the switch. If a phone is not using external power, the switch provides inline power through the Ethernet cable that is attached to the phone. The Detecting network... screen appears for about 30 seconds.
The phone attempts to detect an Ethernet connection. If an Ethernet connection is detected but there is no IP address assigned, the user is prompted to contact the administrator for assistance. If an Ethernet connection is not found, the phone attempts to establish a wireless network connection.
For more information, see Cisco Unified Communications Manager Phone Addition Methods.
-
(For a Cisco DX650 in a wireless LAN only) Scan for an access point. The Cisco DX650 scans the RF coverage area with the radio. The phone searches the network profiles and scans for access points that contain a matching Service Set Identifier (SSID) and authentication type. The phone associates with the access point with the highest RSSI that matches with the network profile.
For more information, see Cisco Unified Wireless AP Interactions.
-
(For a Cisco DX650 in a wireless LAN only) Authenticate with the access point. The Cisco DX650 begins the authentication process. The following table describes the authentication process:
Authentication Type
Key Management Options
Description
Open
None
Any device can authenticate to the access point. For added security, static WEP encryption might optionally be used.
Shared Key
None
The phone encrypts the challenge text by using the WEP key and the access point must verify the WEP key that was used to encrypt the challenge text before network access is available.
LEAP or EAP-FAST
None
The RADIUS server authenticates the username and password before network access is available. For more information about name and password authentication, see Wireless LAN Setup.
Auto (AKM)
WPA, WPA2, or CCKM
The phone searches for an access point with one of the key management options enabled. The username and password are authenticated by the RADIUS server before network access is available.
Auto (AKM)
WPA-Pre-shared key, WPA2-Pre-shared key
The phone looks for an access point that has one of the key management options enabled. Authentication uses the configured WPA-Pre-shared key or WPA2-Pre-shared key
For more information, see Authentication Methods.
-
Load the stored phone image. The Cisco DX650 has nonvolatile flash memory in which the phone stores firmware images and user-defined preferences. At startup, the phone runs a bootstrap loader that loads a phone firmware image that is stored in flash memory. Using this image, the phone initializes the software and hardware.
-
Configure the VLAN. If the Cisco DX650 is connected to a Cisco Catalyst switch, the switch next informs the phone of the voice VLAN that is defined on the switch. The phone needs the VLAN membership information before it can proceed with the Dynamic Host Configuration Protocol (DHCP) request for an IP address.
For more information, see Ethernet Settings Menu.
-
Obtain an IP address. If the Cisco DX650 is using DHCP to obtain an IP address, the phone queries the DHCP server to obtain one. If you are not using DHCP in your network, you must assign static IP addresses to each phone locally.
For more information, see Ethernet Settings Menu.
-
Request the CTL file. The TFTP server stores the CTL file. This file contains the certificates that are necessary for establishing a secure connection between the phone and Cisco Unified Communications Manager.
For more information, see the Cisco Unified Communications Manager Security Guide, "Configuring the Cisco CTL Client" chapter.
-
Request the ITL file. The phone requests the ITL file after it requests the CTL file. The ITL file contains the certificates of the entities that the phone can trust. The certificates are used to authenticate a secure connection with the servers or to authenticate a digital signature that is signed by the servers. Cisco Unified Communications Manager 8.5 and later supports the ITL file.
-
Access a TFTP server. In addition to assigning an IP address, the DHCP server directs the phone to a TFTP Server. If the phone has a statically defined IP address, you must configure the TFTP server locally on the phone; the phone then contacts the TFTP server directly. If the TFTP server is not found, the user is prompted to enter a TFTP server address.
Note
You can also assign an alternate TFTP server to use instead of the one that DHCP assigns.
For more information, see Ethernet Settings Menu.
-
Request the configuration file. The TFTP server has configuration files, which define parameters for connecting to Cisco Unified Communications Manager and other information for the phone.
For more information, see Cisco Unified Communications Manager Phone Addition Methods.
-
Contact Cisco Unified Communications Manager. The configuration file defines how the Cisco DX650 communicates with Cisco Unified Communications Manager and provides a phone with the load ID. After it obtains the file from the TFTP server, the phone attempts to make a connection to the highest-priority Cisco Unified Communications Manager on the list.
If the security profile of the phone is configured for secure signaling (encrypted or authenticated) and the Cisco Unified Communications Manager is set to secure mode, the phone makes a TLS connection. Otherwise, the phone makes a nonsecure TCP connection.
If the phone was manually added to the database, Cisco Unified Communications Manager identifies the phone. If the phone was not manually added to the database and autoregistration is enabled in Cisco Unified Communications Manager, the phone attempts to autoregister in the Cisco Unified Communications Manager database.
Note
Autoregistration is disabled when you configure the CTL client. In this case, you must add the phone to the Cisco Unified Communications Manager database manually.
-
If the phone is booting for the first time, display the Welcome screen and run the Setup Assistant.
Cisco Unified Communications Manager Phone Addition Methods
Before installing the Cisco DX650, you must choose a method for adding phones to the Cisco Unified Communications Manager database.
The following table provides an overview of the methods for adding phones to the Cisco Unified Communications Manager database.
|
Method |
Requires MAC Address? |
Notes |
|---|---|---|
|
Autoregistration |
No |
Results in automatic assignment of directory numbers. |
|
Autoregistration with Tool for Autoregistered Phones Support (TAPS) |
No |
Requires autoregistration and the Bulk Administration Tool; updates information in the Cisco DX600 series phone and in Cisco Unified Communications Manager Administration. |
|
Using the Cisco Unified Communications Manager Administration |
Yes |
Requires phones to be added individually. |
|
Using Cisco Unified Communications Manager Bulk Administration Tool |
Yes |
Allows for simultaneous registration of multiple phones. |
Autoregistration Phone Addition
By enabling autoregistration before you begin installing phones, you can:
-
Add phones without first gathering MAC addresses from the phones.
-
Automatically add a Cisco Desktop Collaboration Experience DX600 series phone to the Cisco Unified Communications Manager database when you physically connect the phone to your IP telephony network. During autoregistration, Cisco Unified Communications Manager assigns the next available sequential directory number to the phone.
-
Quickly enter phones into the Cisco Unified Communications Manager database and modify any settings, such as the directory numbers, from Cisco Unified Communications Manager.
-
Move autoregistered phones to new locations and assign them to different device pools without affecting their directory numbers.
Note
Cisco recommends that you use autoregistration to add fewer than 100 phones to your network. To add more than 100 phones to your network, use the Bulk Administration Tool.
Autoregistration is disabled by default. In some cases, you might not want to use autoregistration; for example, if you want to assign a specific directory number to the phone, or if you want to use a secure connection with Cisco Unified Communications Manager as described in Cisco Unified Communications Manager Security Guide. For information about enabling autoregistration, see the "Enabling Autoregistration" section in the Cisco Unified Communications Manager Administration Guide.
Autoregistration and TAPS Phone Addition
You can add phones with autoregistration and TAPS, the Tool for Autoregistered Phones Support, without first gathering MAC addresses from phones.
TAPS works with the Bulk Administration Tool to update a batch of phones that were already added to the Cisco Unified Communications Manager database with dummy MAC addresses. Use TAPS to update MAC addresses and to download predefined configurations for phones.
Note | Cisco recommends that you use autoregistration and TAPS to add fewer than 100 phones to your network. To add more than 100 phones to your network, use the Bulk Administration Tool. |
To implement TAPS, you or the end user dials a TAPS directory number and follows voice prompts. After the process is complete, the phone contains the directory number and other settings, and the phone is updated in Cisco Unified Communications Manager Administration with the correct MAC address.
Autoregistration must be enabled in Cisco Unified Communications Manager Administration () for TAPS to function.
Note | When you configure the cluster for mixed mode through the Cisco CTL client, autoregistration is automatically disabled. When you configure the cluster for nonsecure mode through the Cisco CTL client, autoregistration is not enabled automatically. |
For more information, see the Cisco Unified Communications Manager Bulk Administration Guide.
Cisco Unified Communications Manager Administration Phone Addition
You can add Cisco Desktop Collaboration Experience DX600 series devices individually to the Cisco Unified Communications Manager database by using Cisco Unified Communications Manager Administration. To do so, you first must obtain the MAC address for each Cisco Desktop Collaboration Experience phone. For information about determining a MAC address, see the Cisco Desktop Collaboration Experience DX600 Series Phone MAC Address Determination.
To add Cisco DX650 to the Cisco Unified Communications Manager, follow these steps.
| Step 1 | After you have collected MAC addresses, in Cisco Unified Communications Manager Administration, choose . | ||
| Step 2 | Click Add New. | ||
| Step 3 | If you are
adding a
Cisco Desktop Collaboration Experience DX600 Series phone, choose
Cisco
DX650 from the
Phone
Type drop-down list box.
| ||
| Step 4 | Click Next. | ||
| Step 5 | Enter the details of Cisco DX650-specific parameters (Device Pool, Phone Button Template, Device Security Profile, and so on). | ||
| Step 6 | Click
Save.
For complete instructions and conceptual information about Cisco Unified Communications Manager, go to the System configuration overview chapter in the Cisco Unified Communications Manager System Guide. |
Phone Addition with Bulk Administration Tool Phone Template
The Cisco Unified Communications Manager Bulk Administration Tool enables you to perform batch operations, including registration of multiple phones.
To add phones using Bulk Administration Tool only (not in conjunction with TAPS), you must obtain the appropriate MAC address for each phone.
For detailed instructions about adding phones through the Bulk Administration menu, see the Cisco Unified Communications Manager Bulk Administration Guide, “Inserting Phones” chapter.
For more information about using Bulk Administration Tool, see the Cisco Unified Communications Manager Bulk Administration Guide. For more information about creating of Bulk Administration Tool Phone Templates, see the "Phone Template" section in the Cisco Unified Communications Manager Bulk Administration Guide.
To add a phone to the Cisco Unified Communications Manager, follow these steps.
Cisco Desktop Collaboration Experience DX600 Series Phone MAC Address Determination
This guide describes several procedures that require you to determine the MAC address of a Cisco DX600 series phone. You can determine the MAC address of a phone in these ways:
Feedback