Datasheet

All contents are Copyright © 1992–2006 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 6 of 18
Call diversion (SS-CFB (busy), SS-CFNR (no answer), and SS-CFU (unconditional); service ISO/IEC 13872 and ISO/IEC
13873, first edition 1995—call diversion by forward switching and by reroute
Call transfer by join
H.323 Annex M.1 (Q.SIG over H.323)—ITU recommendation for Annex M.1
**H.323 Annex M.1 support for H.323 gateways and H.225 trunks
Identification restriction (Calling Name Identification Restriction (CNIR], Connected Line
Identification Restriction (COLR), and Connected Name Identification Restriction (CONR)
Loop prevention, diversion counter and reason, loop detection, diverted to number, diverting number, original called name and
number, original diversion reason, and redirecting name
Message waiting indicator (MWI)
Path replacement ISO/IEC 13863: 2nd Ed. 1998 and ISO/IEC 13974: 2nd Ed. 1999
Redundancy and automated failover on call-processing failure
Call preservation on call-processing failure
Station to station calls
Station through trunk calls (Media Gateway Control Protocol [MGCP] gateways)
JTAPI and TAPI applications enabled with automated failover and automatic update
Triple Cisco Unified CallManager redundancy per device (phones, gateway, and applications) with automated failover and
recovery
Trunk groups
MGCP BRI support (ETSI BRI basic-net3 user-side only)
Security
Configurable operation modes—Nonsecure or secure.
Device authentication—New model phones have an embedded X.509v3.
Certificate; a certificate authority proxy function (CAPF) is used to install a locally significant certificate in phones.
Data integrity—TLS cipher “NULL-SHA” supported; messages are appended with SHA1 hash of the message to ensure that the
message is not altered on the wire and can be trusted.
HTTPS support for the following applications—Cisco Unified CallManager Admin, Cisco Unified CallManager Serviceability,
Cisco Unified CallManager User, RTMT, Cisco Unified CallManager TraceAnalysis, Cisco Unified CallManager Service, the
Cisco Unified CallManager Trace Collection tool, and the Cisco Unified CallManager CAR tool all have HTTPS support.
Privacy—Cisco Unified CallManager supports encryption of signaling and media. Phone types include Cisco Unified IP Phone
7940G, 7941G, 7941G-GE, 7960G, 7961G, 7961G-GE, 7970G and 7971G; Survivable Remote Site Telephony (SRST) and
MGCP gateways are supported.
Secure Sockets Layer (SSL) for directory—Supported applications include BAT, CAR, Cisco Unified CallManager Admin User
Pages, Cisco Unified CallManager Assistant Admin Pages, Cisco Unified CallManager User Pages and IP Phone Options Pages,
Cisco Conference Connection, CTI Manager, Extension Mobility, Cisco Unified CallManager Assistant, and Multilevel
Administration (MLA).
A USB eToken containing a Cisco rooted X.509v3 certificate is used to generate a Certificate Trust List (CTL) file for the
phones as well as configuring the security mode of the cluster.