Datasheet

Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com

Page 11 of 18

– Dynamic H.323 addressing (E.164 addressing)—H.323 clients can be configured in Cisco CallManager via an E.164 address. This

simplifies H.323 client administration for deployments where H.323 clients are configured for DHCP. E.164 addressing can be paired with

an Cisco IOS Software Release 12.3(8)T gatekeeper to simplify H.323 client dialing.

System Capability Enhancements

• BRI support—Support for secure communications using legacy BRI and analog secure endpoints (STE/STU) and support for IP-STE.

– V.150.1 Modem-Relay-over-IP support—Cisco CallManager will respond to the Session Description Protocol (SDP) sent by the gateway

with default parameters. V.150.1 is required by the secure mode of IP-STEs and BRI-STEs.

– BRI station pre-emption.

• Call coverage—Cisco CallManager Version 4.1 provides the ability to set up coverage paths to route calls to individuals or groups, helping to

ensure that calls are answered. Call coverage features include:

– Forwarding out of a coverage path.

– Ability to set up different coverage paths based on time of day, day of week, or day of year.

– Ability to provide separate forwarding treatment for internal versus external Call Forward No-Answer (CFNA) calls.

– Ability to provide separate forwarding treatment for internal versus external Call Forward Busy (CFB) calls.

– Support of a maximum timer for hunt lists.

– Ability to allow a line to appear in multiple line groups, which was a limitation in previous versions of Cisco CallManager.

– Ability to allow a gateway to appear in multiple route groups, which was a limitation in previous versions of Cisco CallManager.

– Ability to divert to a final forwarding location when a hunt list terminates, either through exhaustion or expiration of its maximum hunt

timer. This location may be a dialed number (voicemail pilot, another hunt pilot, a route pilot, or any allowed dialed number) or a checkbox

to select personal treatment based on settings for the original called party’s line.

– Splitting the existing route-list/hunt-list GUI into two separate forms—one for hunt list and one for route list.

• Call display restrictions—Ability for the system administrator to block calling/called/connected name/number between certain phones. This is

frequently used in areas where, for security reasons, this calling information cannot be displayed on phones. A hotel is an example where calls

from room to room would not display calling information.

• Forced authorization codes/client matter codes

– Forced authorization codes—Allows a system administrator to require that an authorization code be entered prior to extending a call to a

specific route pattern. This is often used as a mechanism to prevent fraudulent toll calls by individuals that might have access to the phones.

The system administrator can assign authorization levels to allow some codes to have full calling capability and others to not be able to call

certain numbers.

– Client matter codes or account codes—Ability for a system administrator to require that a client matter code be entered prior to extending a

call to a specific route pattern. This code is often used by companies to track calls made to specific accounts and use this data for billing

purposes.

– Client matter code and forced authorization code (CMC/FAC) information is recorded in the Cisco CallManager CDR database.