Contents

• Device support
• Supported devices
• Device configuration files
• Device firmware loads
• Update device loads
• Device pools
• Call preservation
• Call preservation scenarios

Device support

---

This chapter provides general information about how Cisco Unified Communications Manager interacts with Cisco Unified Communications devices in your network.

• Supported devices
• Device configuration files
• Device firmware loads
• Device pools
• Call preservation

Supported devices

The Cisco Unified Communications Manager supports many types of devices, including those in the following list:

• Cisco Unified IP Phones
• Analog gateway ports
• T1 gateway
• E1 gateway
• Transcoding resource
• Software Media Termination Point (MTP)
• Annunciator
• Conference resource (hardware)
• Conference resource (software)
• CTI port (TAPI and JTAPI)
• Cisco IP Softphone
• Messaging (voice mail)
• Intercluster trunk
• SIP trunks
• Video inputs

Device configuration files

The Cisco Trivial File Transfer Protocol (Cisco TFTP) builds configuration files from information that is found in the Cisco Unified Communications Manager database.

The device-specific configuration files use the name format SEP, SAA, SDA, CFB, VGC, or MTP + MAC address:

• SEP-Selsius Ethernet Phone (Cisco IP Phone 12 SP+, Cisco IP Phone 30 VIP, Cisco Unified IP Phone 7902, Cisco Unified IP Phone 7905, Cisco Unified IP Phone 7906, Cisco Unified IP Phone 7910, Cisco Unified IP Phone 7911, Cisco Unified IP Phone 7912, Cisco Unified IP Phone 7920, Cisco Unified IP Phone 7921, Cisco Unified IP Phone 7931, Cisco Unified IP Phone 7935, Cisco Unified IP Phone 7936, Cisco Unified IP Phone 7940, Cisco Unified IP Phone 7941, Cisco Unified IP Phone 7960, Cisco Unified IP Phone 7961, Cisco Unified IP Phone 7970, and Cisco Unified IP Phone 7971)
• SAA-Selsius Analog Access (Cisco Catalyst 6000 24 Port FXS Analog Interface Module)
• SDA-Selsius Digital Access (Cisco Catalyst 6000 8 Port Voice E1/T1)
• VGC-Cisco VG248 Analog Phone Gateway (Cisco VG248 ports and units appear as distinct devices in the same Cisco Unified Communications Manager. All 48 device ports register within the same Cisco Unified Communications Manager as device type "Cisco VGC Phone.")
• MTP-Media Termination Point

Configuration files also contain a list of Cisco Unified Communications Managers in priority order. Network addresses comprise either the fully qualified domain name, for example, "cm1.cisco.com," or dotted IP address "172.116.21.12" plus a TCP port. See the Cisco TFTP for more information.

When a device needs to get its configuration file, the device sends a TFTP request for the device-specific configuration filename.

Note	You can specify button URLs in device configuration for Cisco Unified IP Phone 7970, 7960, and 7940. If the URL is blank, Cisco Unified Communications Manager uses the enterprise values.

Device firmware loads

Loads comprise files that contain updated firmware for devices. Four types of firmware loads exist: phone loads, gateway loads, MTP loads, and conference bridge loads. During installation or upgrade, Cisco Unified Communications Manager provides the latest loads; however, you can also receive a load between releases that can contain patches or other information that is important to the devices that use loads, such as phones or gateways.

The /usr/local/cm/tftp subdirectory stores these load files as *.bin, .zup, or .sbin files; for example, D501A022.bin. During installation or upgrade, this location stores the latest loads. You must copy new loads that you receive between releases to this location for the system to access them.

To view the most current information on load descriptions for each device type, choose Device > Device Settings > Device Defaults and click the ? button.

• Update device loads

Update device loads

You can apply a new load to a single device before applying it as a systemwide default. This method can prove useful for testing purposes. Remember, however, that only the device that you have updated with the new load will use that load. All other devices of that type use the old load until you update the systemwide defaults for that device with the new load.

Device pools

Device pools scale and simplify the distribution of Cisco Unified Communications Manager redundancy groups. Device pools allow you to assign the same configuration to a group of devices; for example, you can assign the device pool to phones, gateways, trunks, or CTI route points. In general, device pools allow you to configure common parameters that need to be applied to a device; for example, Cisco Unified Communications Manager Group, region, SRST reference, and so on. For phones, you may need to configure the device pool, the common phone profile, and the common device configuration, which work similarly to device pools (that is, they allow you to apply the same configuration to a group of phones). Be aware that some configuration settings in the device pool may not apply to all device types that use device pools; for example, the incoming called party settings apply only to H.323 trunks and gateways.

Tip

Optional calling search space can prevent rogue installations of IP phones on your network. For example, rogue phones that are plugged into the network autoregister in a device pool that has a calling search space that is restricted only to the Cisco Unified Communications Manager administrator. This search space can have a Primary Line Automatic Ringdown that is assigned to it, so, when the user goes off hook, the call immediately connects to security or the Cisco Unified Communications Manager administrator.

Typically, the following scenario applies with respect to configuring device pools. The deployment model drives the exact model of clustering and device pools that are used:

• Region requirements for single-site cluster-This scenario does not require use of regions because all calls use the G.711 codec for calls.
• Total device pools = Number of sites x regions. Total device pools = Regions x Cisco Unified Communications Manager redundancy groups.

Call preservation

The call preservation feature of Cisco Unified Communications Manager ensures that an active call does not get interrupted when a Cisco Unified Communications Manager fails or when communication fails between the device and the Cisco Unified Communications Manager that set up the call.

Cisco Unified Communications Manager supports full call preservation for an extended set of Cisco Unified Communications devices. This support includes call preservation between Cisco Unified IP Phones, Media Gateway Control Protocol (MGCP) gateways that support Foreign Exchange Office (FXO) (non-loop-start trunks) and Foreign Exchange Station (FXS) interfaces, and, to a lesser extent, conference bridge, MTP, and transcoding resource devices.

Enable H.323 call preservation by setting the advanced service parameter, Allow Peer to Preserve H.323 Calls, to True.

The following devices and applications support call preservation. If both parties connect through one of the following devices, Cisco Unified Communications Manager maintains call preservation:

• Cisco Unified IP Phones
• SIP trunks
• Software conference bridge
• Software MTP
• Hardware conference bridge (Cisco Catalyst 6000 8 Port Voice E1/T1 and Services Module, Cisco Catalyst 4000 Access Gateway Module)
• Transcoder (Cisco Catalyst 6000 8 Port Voice E1/T1 and Services Module, Cisco Catalyst 4000 Access Gateway Module)
• Non-IOS MGCP gateways (Catalyst 6000 24 Port FXS Analog Interface Module, Cisco DT24+, Cisco DE30+, Cisco VG200)
• Cisco IOS H.323 gateways (such as Cisco 2800 series, Cisco 3800 series)
• Cisco IOS MGCP Gateways (Cisco VG200, Catalyst 4000 Access Gateway Module, Cisco 2620, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 3810)
• Cisco VG248 Analog Phone Gateway

The following devices and applications do not support call preservation:

• Annunciator
• H.323 endpoints such as NetMeeting or third-party H.323 endpoints
• CTI applications
• TAPI applications
• JTAPI applications

• Call preservation scenarios

Call preservation scenarios

Table 9-1 lists and describes how call preservation is handled in various scenarios.

Table 1 Call Preservation Scenarios

Scenario	Call Preservation Handling
Cisco Unified Communications Manager fails.	A Cisco Unified Communications Manager failure causes the call-processing function for all calls that were set up through the failed Cisco Unified Communications Manager to be lost. Cisco Unified Communications Manager maintains affected active calls until the end user hangs up or until the devices can determine that the media connection has been released. Users cannot invoke any call-processing features for calls that are maintained as a result of this failure.
Communication failure occurs between Cisco Unified Communications Manager and device.	When communication fails between a device and the Cisco Unified Communications Manager that controls it, the device recognizes the failure and maintains active connections. The Cisco Unified Communications Manager recognizes the communication failure and clears call-processing entities that are associated with calls in the device where communication was lost. The Cisco Unified Communications Managers still maintain control of the surviving devices that are associated with the affected calls. Cisco Unified Communications Manager maintains affected active calls until the end user hangs up or until the devices can determine that the media connection has been released. Users cannot invoke any call-processing features for calls that are maintained as a result of this failure.
Device failure (Phone, gateway, conference bridge, transcoder, MTP)	When a device fails, the connections that exist through the device stop streaming media. The active Cisco Unified Communications Manager recognizes the device failure and clears call-processing entities that are associated with calls in the failed device. The Cisco Unified Communications Managers maintain control of the surviving devices that are associated with the affected calls. Cisco Unified Communications Manager maintains the active connections (calls) that are associated with the surviving devices until the surviving end users hang up or until the surviving devices can determine that the media connection has been released.