|
Table Of Contents
Release Notes for Cisco CallManager Release 3.0(2d)
New Hardware and Software Features in Release 3.0(2d)
New Hardware and Software Features in Release 3.0
Address Assignments (Route Pattern)
Call Pickup and Group Call Pickup
Select Ringing State for a Phone Device
Intra-Cluster Distributed Cisco CallManager Feature Transparency
Inter-Cluster Distributed Cisco CallManager Feature Transparency
Distributed Cisco CallManager Scalability
Cisco CallManager Redundancy on the Cisco ICS 7750
Digit Analysis Toll Restriction
IP Voice Streaming Application
Bulk Administration Tool (BAT)
DtSilenceFlag Service Parameter
Resolved Caveats - Release 3.0(2d)
Open Caveats for Cisco CallManager Release 3.0(2d)
Configuring the Microsoft Telnet Daemon for Bridged Telnet
Default Value Changed for SdlTraceTotalNumFiles Service Parameter
Cisco CallManager Service Parameters
Cisco Messaging Interface Service Parameters
Cisco IP Voice Media Streaming Service Parameters
Cisco Enterprise Service Parameters
Incorrect Name of MwiSearchSpace Service Parameter
Incorrect Definition for HoldType and ToneOnHoldTime
Obtaining Technical Assistance
Release Notes for Cisco CallManager Release 3.0(2d)
August 15, 2000
These release notes describe the new features and caveats for Cisco CallManager Release 3.0(2d). Use these release notes in conjunction with the Installing Cisco CallManager Release 3.0 on the Cisco Media Convergence Server document, located on Cisco Connection Online (CCO), and the Cisco Documentation CD-ROM. The Installing Cisco CallManager Release 3.0 on the Cisco Media Convergence Server document is also packaged with your CDs or convergence server.
The latest software upgrades and release notes for Cisco CallManager 3.0(2d) are available on Cisco Connection Online (CCO) at:
http://www.cisco.com/public/sw-center/internet/callmgr/callmgr.html
Contents
These release notes discuss the following topics:
•Obtaining Technical Assistance
Introduction
Cisco CallManager is a network business communication system providing high-quality telephony over IP networks. Cisco CallManager enables the conversion of conventional, proprietary circuit-switched PBXs to multi-service, open LAN systems.
System Requirements
Cisco CallManager Release 3.0 must be installed and configured on a Cisco Media Convergence Server. For system hardware component information and system requirements, refer to Installing Cisco CallManager Release 3.0 on the Cisco Media Convergence Server.
New and Changed Information
New Hardware and Software Features in Release 3.0(2d)
Cisco CallManager Release 3.0(2d) is a maintenance release that addresses Cisco Media Convergence Server installation issues and resolves other high-priority Caveats. No new features have been added. Refer to the "Resolved Caveats" section for more information.
New Hardware and Software Features in Release 3.0
The following sections contain new and changed hardware and software features in Release 3.0 of Cisco CallManager.
Distributed Call Processing
Cisco CallManager (Release 3.0 and later) provides the capability for distributed call processing. With this feature, you can distribute the call processing load of your system across multiple Cisco CallManagers in a cluster. This feature allows for redundancy, feature transparency, and scalability in a distributed environment.
To support this functionality, a new distributed, replicated database layer has been added to the Cisco CallManager system. This layer allows for the transparent replication of configuration information across the coordinating Cisco CallManagers. The layer manages database consistency and recoverability. Configuration is simplified through a single web interface to the database for the entire system.
Digit Analysis Replication
Digit analysis is the process used by Cisco CallManager to collect, parse, and translate dialed numbers to destination device IP addresses. In Cisco CallManager Release 3.0 and later, the digit analysis function is distributed across all Cisco CallManager servers in a cluster. This distribution allows scalability, load balancing, and redundancy across the cluster.
Multiple Line Appearance
Cisco CallManager supports distributed multiple line appearance which allows multiple phones attached to multiple Cisco CallManagers to share one directory number (DN).
Route Lists and Route Groups
Release 3.0 introduces multiple Cisco CallManager nodes in a system. Access devices (gateways) may be registered in any of the nodes of the system, but must still be reachable using the configured Route Plan. Route Lists (which were called Route Points in Cisco CallManager Release 2.4 and earlier) and Route Groups are configured in the same manner as in Cisco CallManager Release 2.4 and earlier, with the same associations.
Address Assignments (Route Pattern)
This feature allows addresses of devices and virtual endpoints to be specified using a format that allows easy assignment of a range of matching values. This allows ranges of addresses to be easily routed or blocked. New to Release 3.0 is the ability to associate a route pattern to a device through partitions and calling search spaces.
Number Transformations
This new feature allows both called and calling numbers to be modified by truncation, replacement of individual digits, discarding named sub-strings (called number only), or by prepending or appending digits before digit analysis.
Data Driven Dial Plan
The new Dial Plan Wizard enables you to create a dial plan quickly and easily. Also, pre-configured, pre-tested, country-specific dial plans may be created and substituted for the NANP files.
Dial Plan Report
A new Dial Plan Report allows you to see the dial plan configuration at a glance. For each route partition, it lists the call park numbers, call pickup numbers, and conference numbers associated with the partition. For each route pattern, it shows the usage, route list, route group, device, and port numbers associated with the route pattern.
Call Pickup and Group Call Pickup
Two types of call pickup can be configured with Cisco CallManager Release 3.0:
•Call Pickup allows users to pick up incoming calls within their own group. The appropriate call pickup group number is dialed automatically when a user activates this feature.
•Group Call Pickup allows users to pick up incoming calls within their own group or in other groups. Users must dial the appropriate call pickup group number when using this feature.
Select Ringing State for a Phone Device
This new feature allows ringing to be either enabled or disabled on any Cisco IP phone in the database. If ringing is enabled, an incoming call is presented on the phone through the display and/or lights as appropriate for that particular device, and by ringing the phone. If ringing is disabled, an incoming call is presented on the phone through the display and/or lights as appropriate for that particular device, but the phone does not ring audibly.
Disable Ring Per Line
If a DN appears on multiple phones, the database can be set to control which phone will ring or which will just flash, indicating that the phone is ringing, on a phone-by-phone basis.
Database Layer/Replication
The database layer provides an abstraction layer between Cisco CallManager and supporting applications. The abstraction layer provides for single-point system configuration while hiding automated, underlying data store replication.
Device Reset Control
This release of Cisco CallManager significantly reduces the number of database changes that require a Cisco CallManager restart in order to take effect.
Device Recovery
This section applies to Cisco CallManager through Media Gateway Control Protocol (MGCP), as well as Cisco CallManager to Cisco CallManager connections. Each Cisco CallManager device uses the steps in the following list to connect or reconnect to Cisco CallManagers:
•A configuration component provides a list of Cisco CallManagers for the device to use. The maximum number of Cisco CallManagers on the redundancy list is three.
•A TCP connection to two Cisco CallManagers in the list is maintained. Keep-alive messages are sent to both the active and the standby Cisco CallManager.
•If the active Cisco CallManager fails, an IP phone to IP phone call stays active if both phones are on the same Cisco CallManager. If the two IP phones are on different Cisco CallManagers, the call is dropped. IP phone to a gateway calls are also dropped regardless of which Cisco CallManagers the devices are registered. As soon as the IP phone to IP phone call ends, the phones register with their standby Cisco CallManager. This backup is only temporary, until the primary Cisco CallManager is restored.
•When keep-alive messages fail to the active Cisco CallManager, the device attempts to register with the standby Cisco CallManager. The device attempts to keep two TCP connections open and always tries to re-connect to the highest priority, available Cisco CallManager.
•If a registered device is not registered with the primary, available Cisco CallManager, and no calls are active, the device follows the list starting with the first Cisco CallManager on the list and attempts to re-make a TCP connection. Upon a successful connection, the device de-registers with the current active Cisco CallManager and registers with the new Cisco CallManager.
Intra-Cluster Distributed Cisco CallManager Feature Transparency
The intra-cluster feature transparency provided in Cisco CallManager Release 3.0 allows features such as device display management, device lamp management, media management, call hold and transfer capabilities, call park and pickup capabilities, distributed dial plan, and shared route plan (in the form of partitions and calling search spaces) to be configured and shared across all Cisco CallManagers within a cluster.
Note MTP is not required for intra-cluster communication.Inter-Cluster Distributed Cisco CallManager Feature Transparency
Clusters of Cisco CallManagers interconnect using H.323 protocol. A given cluster views another cluster as another H.323 device. When configuring one cluster to talk to another, the Configuration Database has an H.225 device configured that points to one of the Cisco CallManagers in the remote cluster. The Dial Plan structure associates the remote cluster's E.164 address range to the H.225 device and signals the remote cluster just as it would an H.323 gateway. New to Release 3.0 are minor bug fixes and support for intercluster transfer, hold, and conferencing through the H.323 empty capabilities set.
Distributed Cisco CallManager Scalability
Beginning with Release 3.0, multiple Cisco CallManagers can be supported per configuration database. This feature allows load distribution for registered devices, call processing, and other functions across all Cisco CallManager servers in a cluster.
Six Cisco CallManagers can reside in a Cisco CallManager cluster. The maximum number of users in a Cisco CallManager cluster is 10,000. A single Cisco CallManager can handle 2,500 phones. When multiple Cisco CallManagers are present in a cluster, the number of IP phones assigned to each Cisco CallManager in a normal state must be such that they can absorb the IP phones from a failed Cisco CallManager so that 2,500 phones on any Cisco CallManager is not exceeded.
Note For redundancy purposes, you could have a Cisco CallManager that only serves as a backup Cisco CallManager, and during normal operations, would have no registered phones. You can also install the Publisher database and TFTP servers on stand-alone platforms if desired.
For the most current information about Cisco IP telephony system design guidelines, refer to the Voice Product Documentation page on Cisco Connection Online, located at http://www.cisco.com/univercd/cc/td/doc/product/voice/Cisco CallManager Redundancy on the Cisco ICS 7750
Cisco CallManager redundancy is handled differently on the Cisco ICS 7750 than it is in a clustered environment. Only one instance of Cisco CallManager is active at any time on the Cisco ICS 7750. When a redundant System Processing Engine (SPE) runs a secondary instance of Cisco CallManager, the secondary instance is never active unless the primary Cisco CallManager fails. If a failover occurs, the secondary Cisco CallManager becomes active and takes over all call processing and Cisco CallManager database functions. Since only one instance of Cisco CallManager is active on the Cisco ICS 7750, load-balancing is not available, and each Cisco ICS 7750 must be administered separately. For more information about implementing and configuring Cisco CallManager on the Cisco ICS 7750, please refer to the Cisco ICS 7750 documentation.
Note Cisco CallManager clusters are not supported on the Cisco ICS 7750.Digit Analysis Multi-Tenant
Through partitions, the Cisco CallManager is able to support multiple instances of the same DN at a single site which are treated as independently reachable DNs. Using translation patterns, inbound calls to different direct inward dialing (DID) numbers with common subscriber line identifiers (extensions) can be configured.
Digit Analysis Multi-Location
The Cisco CallManager is able to support routing for devices that are in different geographical regions, of which belong to different area codes within the North American Numbering Plan (NANP). You can configure your dial plan in order to bypass the public network when feasible, and also to fall back to long distance routes when WAN or intranet is unavailable.
Digit Analysis Toll Restriction
Cisco CallManager is able to allow or prohibit types of calls based on the class of the individual device or DN.
MGCP Support for VG200
Cisco CallManager is more tightly integrated with the VG200 series of gateways through Media Gateway Control Protocol (MGCP). MGCP is used to provide inter-working between Cisco CallManager and VG200 gateways. The Cisco CallManager is able to control analog interfaces (FXS and FXO) directly.
MGCP Listen Port
MGCP messages are transmitted over TCP. The MGCP listen port represents the Cisco CallManager TCP listen port. The default for this port should be set to 2427.
MGCP Keep-alive Port
The VG200 gateways use TCP as a keep-alive mechanism with Cisco CallManagers. Each gateway can be configured with one active Cisco CallManager and up to two backup Cisco CallManagers. One TCP keep-alive connection exists between a gateway and an active or backup Cisco CallManager. The MGCP keep-alive port represents the Cisco CallManager TCP server port used for this keep-alive mechanism. The default for this port should be set to 2428.
MGCP Device Recovery
Cisco CallManager health monitoring is the responsibility of the gateway. Inter Cisco CallManager and gateway keep-alives track the health condition of the controlling Cisco CallManager. Once the gateway has detected an outage of the primary Cisco CallManager, it rehomes to the next highest priority Cisco CallManager.
Cisco IP Phone 7960 Support
The Cisco IP Phone 7960 uses the Skinny Station protocol with additional messages as required to support the new functionality of the Cisco IP Phone 7960. The Cisco CallManager controls the display on the Cisco IP Phone 7960 indirectly, by providing call and state information to the phone. The phone display processing itself is stateless. The Cisco IP Phone 7960 supports the G.711 u-law and a-law and the G.729, G.729B Codecs.
Comfort Noise
The Cisco IP Phone 7960 supports comfort noise. When Voice Activity Detection (VAD) is enabled, the Cisco IP Phone 7960 generates a low level white noise hiss to simulate the background circuit noise users experience on non-IP connections. Generated comfort noise is only heard on the handset of the station generating the noise; it is not transmitted to the station at the other end of the call. If VAD is disabled, the Cisco IP Phone 7960 provides a continuously streaming, end-to-end connection. VAD is enabled by default.
Caution If VAD is disabled on a network that exhibits a significant amount of jitter (for example, greater than 100 milliseconds per second), latency becomes noticeable to the user in the forms of delay and packet loss. Also, if the codec clocks are out of sync among the devices participating in the call, latency increases for the duration of the call. For example, if the codec clock at the transmitting end is 100 parts per million faster than the codec clock at the receiving end, latency increases to one-half second over the course of a one hour long connection (at 8 kHz).The comfort noise level is determined either by information contained in Silence Information Description (SID) frames or by calculations performed on previous information packets. If a call is made from one Cisco IP Phone 7960 to another Cisco IP Phone 7960, the transmitting device sends SID frames that enable the comfort noise generator on the receiving device to generate the proper level of comfort noise. If a call is made between a Cisco IP Phone 7960 and a device that does not send SID frames, the Cisco IP Phone 7960 calculates and generates the proper comfort noise level based on the background noise of previous information packets.
IP Voice Streaming Application
The IP Voice Streaming Application (Media Application) combines the Conference Bridge and the Media Termination Point (MTP) components that were in the previous versions of the Cisco CallManager. The Media Application consists of two parts: a Windows NT service and Windows NT kernel mode driver. The Windows NT service is responsible for registering with the Cisco CallManager and handling Device Recovery. The kernel driver processes and controls the voice data packets.
Services Management
The list of software processing services for the Cisco IP Telephony Solutions for the Enterprise is Cisco CallManager, TFTP Server, Cisco Messaging Interface (CMI), and IP Streaming Application (replaces the previously separate applications for Conference Bridge and MTP). Each of the processing elements are managed consistently using well-known Windows NT system administration tools.
Service Parameters
The behavior of system services is controlled by parametric value adjustment. In Cisco CallManager Release 3.0, the interface to these settings has been consolidated into two Cisco CallManager Administration web pages. These parameters can now be obtained from the database. In earlier versions of Cisco CallManager, these settings were adjusted in .ini files or the Registry, or presented in application configuration dialogs.
Enterprise Parameters
This feature provides system-wide parametric value adjustment for all services within the enterprise.
Global Directory User Pages
In Release 3.0, an embedded Directory (instead of the relational database) is used to store user data (for example, information such as name and DN). The information in this directory is accessed by a variety of applications. This release provides password protected user access to speed dial and Call Forward All numbers.
Empty Terminal Capability Set
This feature allows the start and stop (re-direct) of streaming on an H.323 device without the use of MTP. This allows the use of supplementary services without losing the call or voice stream.
Empty Capabilities set is a technique used in H.323v2 to allow the Cisco CallManager to instruct an H.323 gateway to transfer a call to a new endpoint in mid-call. This is typically done upon no answer or if the IP phone user presses the transfer button. Prior to this capability, it was necessary to send H.323 calls to an intermediate Media Termination Point (MTP) application before connecting to the IP phone.
Note The minimum IOS release required for Empty Terminal Capability set is 12.1(3)T.CDR Modifications
Even when there are two or more Cisco CallManagers in a cluster, CDR records are written to a common database store. There may be more than one record logged per call.
Hold Feature Modifications
Table 1 contains the hold feature modifications with Release 3.0:
E-911 Support
The Cisco CallManager supports delivering the ANI (Automatic Number Identification) through an H.323 interface to the PSTN using two methods: PRI/ISDN trunks and third-party CAMA (Centralized Automated Message Accounting) gateways.
VG200 Hook Flash Transfer
Cisco CallManager Release 3.0 provides the ability to initiate a hook-flash blind transfer from POTS devices connected to any VG200 FXS port that is controlled by Cisco CallManager through MGCP.
AMIS-A Support
AMIS-A (Audio Messaging Interface Specification-Analog) support allows VoIP devices to exchange AMIS-A Dual Tone Multi-Frequency (DTMF) tones (A, B, C, and D) with the Cisco CallManager, in an out of band signal. The purpose of AMIS-A support is to facilitate Cisco uOne voice mail message exchange and feature transparency with legacy voice mail systems.
AMIS-A DTMF tones (A, B, C, and D) are transported in two different schemes. On the IP side, the tones are detected and generated in an out of band signaling format, whereas on the destination side of the gateways, the tones are detected and generated inband along with the voice path.
The main role of Cisco CallManager is to make sure that DTMF digits received from the sending device are correctly mapped to the corresponding signal format (or API) of the terminating device.
The following existing APIs are impacted to include the AMIS-A DTMF tones (A, B, C, and D):
•Skinny Station Protocol—StationKeyPadButton and StationOutputKeyPadButton
•Skinny Gateway Protocol—GatewayToDeviceReportDigit, DeviceToGatewayPlayTone, and Q.931 and Information message (for analog access gateway).
•H323 Protocol—H245 User Input Indication (h245-signal)
•MGCP Protocol—NTFY and RQNT
Bulk Administration Tool (BAT)
The Bulk Administration Tool (BAT) is a plug-in application to the Cisco CallManager. BAT enables you to add up to 10,000 phones and users to the Cisco CallManager application. Using BAT, you can also perform bulk modifications to phones and delete several phones at one time. Launch BAT from the Cisco CallManager Administration main window by selecting Application and click on BAT. For more information, refer to the Configuring the Bulk Administration Tool (BAT) document (OL-4086-01).
DtSilenceFlag Service Parameter
The DtSilenceFlag service parameter controls whether or not silence is sent while a caller waits for the phone to be answered at the other end. By default, the DtSilenceFlag service parameter is set to False (disabled). When this parameter is set to False, the audio stream is sent on call proceeding instead of waiting for a connect from the other end. When this parameter is set to True, silence is sent until a connect is received from the phone at the other end.
There is, however, one side effect that occurs when the DtSilenceFlag parameter is set to 0 (disabled). When the DtSilenceFlag parameter is disabled and you are calling an analog phone, you may hear loopback (echo) of your audio until the phone on the other end is answered.
To eliminate this echo, you can manually add the DtSilenceFlag service parameter to the list of CallManager service parameters for each Cisco CallManager and set its value to T (enabled). The DtSilenceFlag service parameter does not automatically appear in the list of Cisco CallManager service parameters.
Caution Setting the DtSilenceFlag service parameter to T can result in one-way audio on 911 calls depending on the local carrier's configuration of the Central Office switch. The problem will only occur if the 911 switch fails to send a connect. If the 911 switch fails to send a connect, the calling phone continues to send silence, and the audio stream from the calling phone is never sent.
Therefore, it is strongly recommended that you schedule a test 911 call with your 911 service provider to verify that this problem does not occur. The test scenario should include the following steps:
1. Schedule a test call with your 911 service provider during off-peak hours.
2. Make sure that the test call will be routed over a Cisco Access Digital Trunk Gateway or a Catalyst 6000 T1/E1 8 Port Voice Service Module.
3. Enable the DtSilenceFlag parameter.
4. Make the 911 call.
5. If the 911 operator can hear you, the test passed, and you can leave the DtSilence setting enabled. If not, disable it immediately.Perform the following steps only if you wish to enable the DtSilenceFlag service parameter:
Step 1 Open Cisco CallManager Administration.
Step 2 Select Service > Service Parameters
Step 3 Select Cisco CallManager from the list of Configured Services.
Step 4 Type DtSilenceFlag in the Param field. The service parameters are case-sensitive, so it must be typed exactly as it appears.
Step 5 Choose Boolean from the Type drop-down list.
Step 6 Choose T from the Value drop-down list to set it to True (enabled).
Step 7 Click Update.
The DtSilenceFlag service parameter is now added to the list of service parameters and its value is set to T (enabled).
Modems and Faxes
The following list contains the modems and faxes that are either supported or not in Release 3.0:
•g.723.1 fax between as/at/dt gateways = not supported
•g.711 fax between as/at/dt gateways = not supported
•g.729 fax-relay between IOS gateways = supported
•g.711 fax-relay between IOS gateways = supported
•g.729 fax-relay between cat6k gateways = supported
•g.711 fax passthrough between cat6k gateways = supported
•g.711 modem passthrough between cat6k gateways = supported
End User Interface
The end user interface for Cisco CallManager Release 3.0 database administration has changed. The new interface provides a system page divided into more precise categories, more links from one page to another, and faster search engines for devices (phones, gateways, etc.).
The main menu of the Cisco CallManager Administration user interface consists of the following:
•System
•Route Plan
•Service
•Feature
•Device
•User
•Application
•Help
Some configuration screens contain data that are associated with a particular Cisco CallManager. A drop-down menu with all Cisco CallManager names is displayed. To see the data associated with a particular Cisco CallManager, choose the Cisco CallManager from the drop-down list. Data is displayed accordingly.
The following sections contain the grouping of the different menu categories for the Cisco CallManager Database Administration.
System
The System category includes any system-related configurations that set the system's behaviors and options. It includes the following configurations:
•Server—Any machine that runs the Cisco CallManager and its application needs to be added in the Server Configuration page. The installation program automatically adds an entry on this page for the machine on which the Cisco CallManager is installed. A unique DNS host name or IP address is needed for each server.
•Cisco CallManager—Allows you to define Cisco CallManagers in the system. Each server defined in the system (under Server Configuration) can have only one Cisco CallManager running on it. Therefore, you must define the server on which the Cisco CallManager resides before defining the Cisco CallManager. In every system, there must be one primary Cisco CallManager. You can also configure the auto-registration and port settings for the Cisco CallManager.
•Cisco CallManager Group—This configuration page allows you to define groups of Cisco CallManagers. Only one Cisco CallManager Group in the system can be the default Cisco CallManager used by Trivial File Transfer Protocol (TFTP). A Cisco CallManager Group can have up to three Cisco CallManagers in a group.
•Date/Time Group—The Date/Time Group configuration page allows you to add, update and delete Date/Time groups. Each group contains time zone, and date and time format preferences. There should be at least one Date/Time group in the system.
•Device Defaults—For each Cisco CallManager, this is a load ID, keypad template, and device pool associated with each model type. When a device is created in the system, the system can automatically identify the appropriate load ID (if applicable), keypad template (if applicable), and device pool for the device based on the Cisco CallManager of which it is registered. This configuration page can be viewed based on each Cisco CallManager.
•Region—The Regions feature in Data Administration can be used by Cisco CallManager to automatically select the type of call compression used between devices that are assigned to different (or the same) regions. The configuration pages allow you to define a region and set the type of compression within the region and between the new region and all existing regions.
•Device Pool—All devices in the Cisco CallManager system associate with a device pool. A device pool contains the region, Date/Time group, Cisco CallManager Group, and calling search space for auto-registration. You can create different device pools for devices in different regions, time zones for each Cisco CallManager Group, and calling search space combinations.
•Enterprise Parameters—This configuration page allows you to set parameter values for firmware load of all device types, LDAP settings, and Cisco IP Phone 7960-related settings in the system.
•Location—This configuration page allows you to define logical locations in the system and define bandwidth settings for the location.
Route Plan
This category allows you to configureroute plans, partitions, and so on. It includes the following menu items:
•Partition—A partition is a collection of route patterns or call pickup group numbers. You can create route partitions and view a list of patterns and numbers associated with a specific partition.
•Calling Search Space—A Calling Search Space contains a list of partitions. In each partition, there is a list of DNs that a device can call. When a device is assigned to a calling search space, this device can call any number which is contained in its calling search space partition list. The ordering of partitions in a calling search space can be modified.
•Route Filter—A route filter allows you to control which dial patterns are routed or blocked. The tags associated with the route filters can only be used by North American Numbering Plan (NANP) patterns. Modification to the database is needed if other numbering plans need to be supported.
•Route Group—A route group allows you to order a list of gateways and ports for outgoing trunk preference. Devices that can belong to a route group are: Analog Access ports, Digital Access PRI, Digital Access T1, and H.323 (network side) devices. All devices in a route group must have the same route pattern.
•Route List—A route list allows you to specify the order in which route groups are used.
•Route Pattern—You define the route patterns for the Cisco CallManager system. The Cisco CallManager uses the route patterns to route internal and outgoing calls.
•Translation Pattern—You define the translation patterns for the Cisco CallManager system.
•External Route Plan Wizard—The route plan wizard guides you through a number of configuration pages to configure the route plan. It creates route plans for NANP patterns only.
•Route Plan Report—Lists all the call park, call pickup, conference, route pattern, and translation patterns defined in the system. You select the pattern or DN and the corresponding configuration page is shown. Since this page can potentially show a long list of records, we recommend viewing only 50 records at a time. You can choose to view all items by clicking on the All button.
Service
The Service category includes any applications that are add-on components, such as the following:
•Cisco Messaging Interface—Allows you to configure trace and command line parameter settings for any server, and is most commonly used to interface via SMDI to a third-party voice mail system.
•Cisco TFTP—This configuration page allows you to configure Trivial File Transfer Protocol (TFTP) service parameters. The TFTP service must be installed on a server defined in the Server Configuration page.
•Conference Bridge—Allows you to define software and hardware conference bridge solutions, as well as Meet-Me numbers/patterns in the system. The initial page shows the Conference Bridge Configuration page. To navigate to other conference bridge-related configuration pages, select the links in the upper right corner. To set up conference bridge, you must define either a conference bridge software or hardware type. The hardware type supports more capabilities than the software type.
–Conference Bridge Parameters—Allows you to set the maximum number of users in one ad hoc conference, and the maximum number of users in one Meet-Me conference using Unicast for each Cisco CallManager. You must select the device pool, and the Cisco CallManager belonging to the selected device pool is shown on the item list.
–Meet-Me Number/Pattern—Allows you to configure the Meet-Me numbers and ranges for conference bridge calls.
Note You cannot have both hardware and software conference bridge or MTP devices on the same Cisco CallManager. If both exist, the Cisco CallManager will disable the software version.•Media Termination Point—Allows you to configure the Media Termination Point (MTP) settings.
•Service Parameters—The configuration page allows you to configure settings for the services installed in the system. By selecting a server in the item list, the configuration page shows all the services that are installed on the selected server. You can select a service of the selected server and configure the service parameter settings. A server must be defined in the Server Configuration page and the services must be installed from the Install Plugins page.
•Trace—Allows you to configure trace settings for the services installed in the system. You can display all configured services that are installed on the selected server by selecting a server in the item list. You can select a service from the Configured Services drop-down list box and configure the trace settings for the selected service. A server must be defined in the Server Configuration page and the services must be installed from the Install Plugins page.
•Transcoder—Allows you to configure transcoder devices.
•Control Center—Allows you to stop and start any services on a selected server.
Feature
The Feature category contains configurations to add phone features and feature-related parameters to the system. It includes the following configurations:
•Call Park—This configuration page allows you to specify call a park number or range in the system. Each partition has its own call park number/range.
•Call Pickup—This configuration page allows you to specify a call pickup number or range in the system. Each partition has its own call pickup number or range.
Device
The Device category contains configuration pages to configure devices (phones, gateways, and so on.) for the Cisco CallManager. It includes the following configurations:
•Add a New Device—This page replaces the Device Wizard in Release 2.4. You can add a gateway, MGCP gateway, phone, or Cisco uOne port from this configuration page. Based on the device type selected, the corresponding configuration page is displayed. Complete the information and click the Insert button to add the device.
•Cisco uOne Port—The Cisco Unified Open Network Exchange (uOne) optional software, available as part of Cisco IP Telephony Solutions, provides voice messaging capability to users when they are unavailable to answer calls. This page enables administrators to add, update, and delete Cisco uOne ports in the Cisco CallManager database.
For more information about configuring Cisco CallManager with Ciscu uOne, refer to uOne Installation and Configuration, Corporate Edition 4.1E for CallManager 3.0 (OL-0489-01) and other documention and online help included Cisco uOne.
•Gateway—The Release 2.4 Gateway configuration pages included limited devices only. In Release 3.0, the Gateway section of the user interface includes all gateways, including H.323 devices. Specific pages are used to configure different types of gateways. The overall structure of the Gateways user interface is similar to the new Phone interface.
–Selecting Gateways—The method of selecting gateways (listing all gateways in a separate menu frame) from Release 2.4, has been replaced with a basic lookup function. The lookup allows you to search for gateways by the following categories: device name, description, DN, calling search space, or device pool. For each category, you can specify whether the content of the selected category begins with specific letters, contains specific letters, ends with specific letters, matches specific letters, contains no empty strings, or contains empty strings. The results are shown in a list of devices from which you can select.
–Configuring Gateways—You can select a device from the list of devices that the lookup gives you, and click a link or button to show a detailed view of the device in a secondary window. Any information that can be modified is displayed with a form element so that it can be updated immediately. The only exceptions are the port, span, and trunk configuration details, which are not all shown at once. Instead, a summary of the ports is shown with links to edit the port details (for example, for an Analog Access device, a list of ports that have been configured and each port's type, Loop Start, POTS, and so on.). The actual look and feel of the Gateway configuration pages are similar to what is shown for Phones and Users.
–Adding Gateways—A New Gateway device option is included in the menu for Gateways. Clicking the link takes you to the Add a New Gateway page, where you can add a new gateway.
–Deleting Gateways—The interface provides a toolbar button in the configuration page for deleting the current device. A confirmation prompt asks if you are sure, and runs the delete script if you respond with yes. If you respond with no, you are returned to the configuration page and no changes are made.
•MGCP—Due to the complexity of the MGCP gateways, the MGCP configuration is separated from the other gateway configurations.
•Phone—In Release 3.0, the phone list is limited to devices that can be classed appropriately as phones; that is, end user terminal devices. This includes the existing Cisco Phones and the new Cisco IP Phone 7960. Also included in this category is the H.323 Client (for example, NetMeeting), which is used as a phone.
•Phone Button Template—Allows you to select a phone button template based on an existing phone template, or to create a new button layout.
User
The User category contains configuration pages that allow you to display and maintain information about users on the network. This category includes the following configurations:
•Add a New User—Allows you to complete information for specific users and associate devices with those users.
•Global Directory—Allows you to use a basic or advanced search to locate users. The Global Directory contains every user within a Cisco CallManager directory. The Cisco CallManager directory is a Lightweight Directory Access Protocol (LDAP) directory that imports device and extension information from the database. Its primary purpose is to maintain the associations of devices with users.
Application
All plug-in applications are listed under the Application menu. Once the application is installed, the application name is shown under the application menu.
Help
The Help menu includes the following categories: Contents and Index, For this Page, and About Cisco CallManager.
•Contents and Index—This window shows an online documentation page. The documentation displayed here is not context-sensitive. It displays the top-level topics of the Cisco CallManager Administration Guide.
•For this Page (context-sensitive help)—Context sensitive online documentation is provided for all the Cisco CallManager Administration Guide pages. When you click on this menu item, the documentation related to the selected configuration page is shown in a separate window.
•About Cisco CallManager—This menu displays general information about Cisco CallManager. When the Details button is clicked, a list box shows the Cisco CallManager System version number (which is the Installation version), Cisco CallManager Administration version number, database information, and database dynamic link library (DLL) version numbers.
Important Notes
You should perform regular system backups as described in the section "Performing Backup and Restore Procedures," of the Installing Cisco CallManager Release 3.0 on the Cisco Media Convergence Server document.
Resolved Caveats
Resolved Caveats - Release 3.0(2d)
Table 2 lists and describes Caveats that are resolved in Cisco CallManager Release 3.0(2d).
Open Caveats
This section lists unresolved caveats for this release of Cisco Call Manager. Caveats describe unexpected behavior or defects in Cisco CallManager software and related hardware.
Open Caveats for Cisco CallManager Release 3.0(2d)
Table 3 describes possible unexpected behaviors by Cisco CallManager Release 3.0(2d). Unless otherwise noted, these caveats apply to all Cisco CallManager 3.0 releases up to and including Cisco CallManager Release 3.0(2d).
Troubleshooting
For specific troubleshooting information, refer to the Cisco IP Telephony Troubleshooting Guide for Release 3.0. You can access this guide at the following website address:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_0/index.htm
Documentation Updates
This section contains the latest documentation updates for Release 3.0 of the Cisco CallManager. Included in these updates are any changes or late-breaking information that occurred after production of the Release 3.0 Cisco CallManager Administration Guide, Configuring Remote Serviceability for Cisco CallManager Release 3.0, and/or the online help for the Cisco CallManager application, as well as any information that was omitted from the Release 3.0 documents.
New Service Parameters
Table 4 contains new Cisco CallManager service parameters, with descriptions, that were not included in the Release 3.0 Cisco CallManager Administration Guide or the online help for the Cisco CallManager application.
Caution Please do not modify any of the defaults or settings of the following parameters without the assistance of the Cisco Technical Assistance Center (TAC).
Table 4 Cisco CallManager Service Parameters Not Included in Release 3.0 Documentation
ParamName DescriptionEnableSNMP
This parameter enables the collection of SNMP data from the Cisco CallManager.
EnableStatistics
This parameter enables or disables collection of performance monitor statistics by the Cisco CallManager.
Table 5 contains new Cisco Messaging Interface (CMI) service parameter definitions that were not included in the Release 3.0 Cisco CallManager Administration Guide or the online help for the Cisco CallManager application.
Caution Please do not modify any of the defaults or settings of the following parameters without the assistance of the Cisco Technical Assistance Center (TAC).
Table 5 CMI Service Parameters Not Included in Release 3.0 Documentation
ParamName DescriptionBackupCallManagerName
This parameter is used to define the names of the Cisco CallManagers that are going to be used for the CMI backup. You can use either the name of a Cisco CallManager or its IP address.
BaudRate
Cisco CMI connects to the voice mail system via an RS-232 connection. This parameter defines that connection.
Recommended default value: 9600
Note Many voice mail systems can be configured to use different baud rates, but the one shown here will frequently be correct.CallManagerName
This parameter is used to define the names of the Cisco CallManagers that are going to be used for the CMI primary. You can use either the name of a Cisco CallManager or its IP address.
DataBits
CMI connects to the voice mail system via an RS-232 connection. This parameter defines that connection.
Recommended default value: 7
DialingPlan
This parameter is one of four that are required by CMI to register an intercept for the voice mail system with which CMI is going to work.
Note Small systems without a complex dialing plan usually only need the VoiceMailDn parameter. The remaining parameters, DialingPlan, RouteFilter, VoiceMailPartition will default to empty strings.InputDnSignificantDigits
This parameter is designed to accommodate the differences between voice mail mailbox numbers and DNs. If a legacy voice mail system has mailbox numbers that are longer than the DNs on the system, this parameter can be used to strip the most significant digits. The numeric value of this parameter indicates how many digits should be used.
Note There is no provision for stripping digits other than leading ones.Recommended default value: 10
KeepAliveDn
This is a string parameter. For most voice mail systems a value of F is acceptable. However, some Octel systems periodically send an invalid DN specifically for the purpose of verifying that the attached Cisco CallManager is functioning properly. In this case, you can turn off ValidateDns if you know the DN that the Octel system will use as a keep-alive. By programming that DN into the KeepAliveDn parameter, you will ensure that the invalid DN message is returned to the voice mail system when needed.
OutputDnFormat
This parameter is used to format the DNs sent to the voice mail system. Most numbers passed to the voice mail system are formatted using this parameter.
Default value: %010s
OutputExternalFormat
This parameter is also used to format the DNs sent to the voice mail system. Calling party DNs that are seven digits or longer are formatted using this parameter.
Default value: %010s
Parity
Cisco CMI connects to the voice mail system via an RS-232 connection. This parameter defines that connection.
Recommended default value: Even
Note The parity settings can be None, Even, Odd, Mark, or Space. Settings are usually Even and None, with Mark and Space rarely being used. Just using the first character of the parity name also works.RouteFilter
This parameter is one of four that are required by CMI to register an intercept for the voice mail system with which CMI is going to work.
Note Small systems without a complex dialing plan usually only need the VoiceMailDn parameter. The remaining parameters, DialingPlan, RouteFilter, VoiceMailPartition will default to empty strings.SerialPort
Cisco CMI connects to the voice mail system via an RS-232 connection. This parameter defines that connection.
Recommended default value: COM1
Note The SerialPort name should be the same name that you see in Device Manager under NT.SsapiKeepAliveInterval
This is a numeric parameter. During normal operations, CMI will be attached to a Cisco CallManager. When this is the case, CMI sends a keep-alive message to the Cisco CallManager at the rate specified by this parameter.
Default value: 30 seconds
Caution This parameter should not be changed from the default value unless directed by the Cisco Technical Assistance Center (TAC).StopBits
Cisco CMI connects to the voice mail system via an RS-232 connection. This parameter defines that connection.
Recommended default value: 1
ValidateDns
When CMI receives incoming lamp commands from the voice mail system, it normally validates the DN against the NumPlan table. This is an attempt to verify that the DN matches an existing DN known to Cisco CallManager. If the DN is not found in NumPlan, an invalid DN message is sent to the voice mailbox.
Default value: T
Note On a system with a lot of traffic to and from the voice mail system, you may choose to skip this validation process by setting the ValidateDns parameter default to F.VoiceMailPartition
This parameter is one of four that are required by CMI to register an intercept for the voice mail system with which CMI is going to work.
Note Small systems without a complex dialing plan usually only need the VoiceMailDn parameter. The remaining parameters, DialingPlan, RouteFilter, VoiceMailPartition will default to empty strings.
Configuring the Microsoft Telnet Daemon for Bridged Telnet
To make it possible for the Cisco Service Engineer (CSE) to log into the Telnet service on your Cisco CallManager system, you must configure the Microsoft Telnet daemon.
Use the tlntadmn command to accomplish this task.
Step 1 Select Start > Programs > Command Prompt
Step 2 In the command window, enter the Telnet administration command:
tlntadmn
Step 3 Enter the following options from the lists displayed at the prompt.
a. From the first list, select option number 3, Display/change registry settings
b. From the second list, select option number 7, NTLM
Step 4 Next, set the value of NTLM to zero by responding to the prompts.
Current value of NTLM = 2Do you want to change this value ? [y/n]yNTLM [ current value = 2; acceptable values 0, 1 or 2 ] :0Are you sure you want to set NTLM to :0 ? [y/n]yStep 5 To finish, enter the following options from the lists displayed at the prompt.
a. From the first list, select option number 0, Exit this menu.
b. From the second list, select option number 0, Quit this application.
Step 6 Restart the Telnet service to enable the setting to take effect.
Server Name Change
Change the CiscoWorks2000 server name by editing the SAenvproperties.ini file manually, then restarting the Cisco Syslog Collector service. In future releases, an administrative interface will be available for this purpose.
Running Show Tech
To run show tech correctly, use this example to construct your command:
show -f output.txt -v -w480 dbThe example given in the Show Command chapter of Configuring Remote Serviceability for Cisco CallManager 3.0 (page 3-2) lacks a space before "db".
Changes
This section contains changes that have occurred since the original release of the Cisco CallManager Administration Guide Release 3.0. These changes do not currently appear in the Release 3.0 Cisco CallManager Administration Guide or the online help for the Cisco CallManager application.
Default Value Changed for SdlTraceTotalNumFiles Service Parameter
SdlTraceTotalNumFiles is a service parameter for the Cisco CallManager service type. The default has been changed to 250. This is the correct default for this service parameter.
Omissions
This section contains lists of service parameters for the Cisco CallManager that were not included in the initial production of the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application. These parameters will be defined in a later release of the document.
Caution Please do not modify any of the defaults or settings of the following parameters without the assistance of the Cisco Technical Assistance Center (TAC).Cisco CallManager Service Parameters
The following list contains the service parameters that can be configured for the Cisco CallManager service type that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application:
•AlwaysUsePrimeLine
•CallAcceptTimer
•CallerId
•CgpnScreeningIndicator
•CtiApplicationHeartBeatTime
•DeviceStatusPollInterval_msec
•DialPlanPath
•EnableSNMP
•EnableStatistics
•FlashHookDuration_msec
•GatekeeperRefresh
•H225BlockSetupDestination
•MaxDaResponseTimeoutErrorCount
•MaxNumberOf723Calls
•MGCPConnectTime
•MGCPRespTimeout
•MGCPTimeout
•RASInboundLRQFlag
•RASOutboundLRQFlag
•SdlListeningPort
•SdlTraceDataFlags
•SdlTraceDataSize
•SdlTraceFilePath
•SdlTraceFlag
•SdlTraceTypeFlags
•SendingCompleteIndicator
•ToneOnCallForward
•TypeOfCalledNumberForH225Devices
•VoiceMail
Cisco TFTP Service Parameters
The following list contains the service parameters that can be configured for the Cisco TFTP service type that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application:
•AlternateFileLocation1
•AlternateFileLocation2
•AlternateFileLocation3
•AlternateFileLocation4
•AlternateFileLocation5
•AlternateFileLocation6
•AlternateFileLocation7
•AlternateFileLocation8
•AlternateFileLocation9
•AlternateFileLocation10
Cisco Messaging Interface Service Parameters
The following list contains the service parameters that can be configured for the Cisco Messaging Interface (CMI) service type that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application.
•BackupCallManagerName
•BaudRate
•CallManagerName
•DataBits
•DialingPlan
•InputDnSignificantDigits
•KeepAliveDn
•OutputDnFormat
•OutputExternalFormat
•Parity
•RouteFilter
•SsapKeepAliveInterval
•StopBits
•ValidateDns
•VoiceMailParition
Cisco IP Voice Media Streaming Service Parameters
The following list contains the service parameters that can be configured for the Cisco IP Voice Media Streaming service type that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application:
•CFB:CallCount
•CFB:RunFlag
•MTP:CallCount
Cisco Enterprise Service Parameters
The following list contains the service parameters that can be configured for the Cisco Enterprise service type that were omitted from the Release 3.0 Cisco CallManager Administration Guide and Online Help:
•DBL:DatabaseVersion
•MessageWaitingDirn
Errors
This section contains any errors contained in the Cisco CallManager Administration Guide for Release 3.0 and/or the online help for the Cisco CallManager application. These errors will be corrected in the upcoming release of the document and online help application.
Incorrect Name of MwiSearchSpace Service Parameter
The name of the Cisco Messaging Interface (CMI) service parameter appears incorrectly in the documentation and online help application. The parameter name should be MwiSearchSpace. The documentation is also missing a description of the value to be entered. The value to enter for MwiSearchSpace is a colon-separated list of partition names. For example, dallas01:dallas02:dallas03, where dallas01, dallas02, and dallas03 are names of partitions.
Incorrect Definition for HoldType and ToneOnHoldTime
The definitions for the Cisco CallManager HoldType and ToneOnHoldTime service parameters are incorrect in the Cisco CallManager Administration Guide and online help for Cisco CallManager Release 3.0. The correct definitions are as follows:
•HoldType — Determines whether the hold light flashes more rapidly for the user who placed a call on hold in the case where two different phones share the same directory number. The default value is still F.
•ToneOnHoldTime — Determines the time interval between tones when a call is on hold. The default is 10 seconds, and the value range is 3 to 99999.
Service and Support
For service and support, contact Cisco Technical Assistance Center (TAC) at:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Obtaining Documentation
This section provides different methods of obtaining Cisco documentation.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Ordering Documentation
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/pcgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Obtaining Technical Assistance
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco Connection Online
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
•WWW: www.cisco.com
•Telnet: cco.cisco.com
•Modem using standard connection rates and the following terminal settings: VT100 emulation; 8 data bits; no parity; and 1 stop bit.
–From North America, call 408 526-8070
–From Europe, call 33 1 64 46 40 82
You can e-mail questions about using CCO to cco-team@cisco.com.
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
Language E-mail AddressEnglish
tac@cisco.com
Hanzi (Chinese)
chinese-tac@cisco.com
Kanji (Japanese)
japan-tac@cisco.com
Hangul (Korean)
korea-tac@cisco.com
Spanish
tac@cisco.com
Thai
thai-tac@cisco.com
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate and value your comments.
Access Registrar, AccessPath, Any to Any, Are You Ready, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, IQ Breakthrough, IQ Expertise, IQ FastTrack, IQ Readiness Scorecard, The IQ Logo, Kernel Proxy, MGX, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, RateMUX, ReyMaster, ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, VlanDirector, Voice LAN, Wavelength Router, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and Aironet, ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, CollisionFree, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document 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. (0005R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.