Introduction This Solution Reference Network Design (SRND) document provides design considerations and guidelines for deploying the following components of the Cisco Unified Communications System: Cisco Unified CallManager, Cisco Unified MeetingPlace, Cisco Unified MeetingPlace Express, Cisco Unity, Cisco Unified Presence, Cisco Unified Video Advantage, and Cisco Unified MobilityManager.     ... View more

    Cisco Unity Visual Messaging Interface The Cisco Unity Visual Messaging Interface (VMI) website lets subscribers listen to, compose, reply to, forward, and delete voice messages from a "virtual" Inbox. A subscriber can access Cisco Unity VMI at the following URL: http://<server name>/web/vmi. Note that the Cisco Unity VMI is not available across a firewall.   To view the Cisco Unity VMI pages, the computer that a subscriber uses to access the site must be configured so that:   •Microsoft Internet Explorer allows the scripting of Java applets and Active Scripting, and has Java permissions enabled.   •If the virus scanner scans downloaded files, it scans only program files.   When accessing Cisco Unity VMI over a modem connection for the first time, note that the Cisco Unity VMI file is more than 1 MB in size and, therefore, may take longer for a subscriber to download than expected. Detailed instructions on using Cisco Unity VMI are available to subscribers in online Help. The Cisco Unity VMI is a class of service licensed feature. For information on setting it up for subscribers, refer to the "Class of Service Licensed Features Settings" section in the "Class of Service Settings" chapter of the Cisco Unity System Administration Guide. The guide is available on Cisco.com at Cisco Unity Maintain and Operate Guides. Establish trusts across domains so that subscribers do not have to log on each time that they want to play a message.   The Cisco Unity VMI is a system key-controlled feature and can be accessed only if it is purchased. ... View more

      Introduction Cisco® Unified Communications Solutions unify voice, video, data, and mobile applications on fixed and mobile networks, delivering a media-rich collaboration experience across business, government agency, and institutional workspaces. These applications use the network as the platform to enhance comparative advantage by accelerating decision time and reducing transaction time. The security, resilience, and scalability of the network enable users in any workspace to easily connect anywhere, anytime, and anyplace, using any media, device, or operating system. Cisco Unified Communications is part of a comprehensive solution that includes network infrastructure, security, wireless, management applications, lifecycle services, flexible deployment and outsourced management options, and third-party applications.   The Cisco Unified Communications messaging portfolio provides three options: • Cisco Unity®: Scales to meet the needs of large enterprise organizations and delivers voice, integrated messaging, and unified messaging options that transparently integrate with Microsoft Exchange, Lotus Domino, and Novell GroupWise.   • Cisco Unity Connection: Combines integrated messaging, voice recognition, and call transfer rules into an easy-to-manage system for medium-sized businesses with up to 7500 users. For organizations with up to 500 users, Cisco Unity Connection is available as a single-server solution with Cisco Unified Communications Manager Business Edition.   • Cisco Unity Express: Provides cost-effective voice and integrated messaging, automated-attendant, and interactive voice response (IVR) capabilities in select Cisco integrated services routers for small and medium-sized businesses and enterprise branch offices with up to 250 users.   Cisco Unity with Speech Connect allows people to quickly connect with their colleagues using only their voice. Speech Connect for Cisco Unity is a Speech-Enabled Automated Attendant (SEAA) for the enterprise. Internal or external callers speak the name of an employee into the phone and are connected to that employee. The Speech Connect solution delivers superior voice-recognition performance and uses enhanced software to store user preferences and fine-tune pronunciations, improving its accuracy over time. Users can collaborate more quickly and easily by connecting with each other without having to know multiple phone numbers. With the proliferation of mobile devices, flexible workspaces, and employee turnover, removing the need to know numbers greatly simplifies communications. If there are multiple employees with the same name or Speech Connect does not have a perfect match for the name spoken by the caller, Speech Connect will present a number of name choices for the caller and include additional information, such as the employee's location or department. This process is called disambiguation. Speech Connect will also play the person's recorded name in their own voice, making it easier for the caller to choose among the multiple names selected through the disambiguation process. Furthermore, Speech Connect performance improves over time through a self-learning mechanism that is included with the optional Names Tuning Service described in further detail below.   Speech Connect can be configured to respond to a number of different voice commands, not just employee names. For example, if you deploy product names in the Speech Connect grammar logic, customers can speak the name of a product and reach a person responsible for that product. Employee names, departments, conference rooms, product names, and any other entity that steers a caller to a phone number can enhance the value of Speech Connect to your employees and customers. While Speech Connect allows for faster, easier connections over the phone, Cisco Unity improves productivity by allowing employees to access messages anytime and anywhere, thereby enabling them to respond faster to messages.   Features and Benefits Table 1. Features and Benefits of Speech Connect     Feature Benefit Support for up to 200,000 names Supports the scale required by large enterprises. Advanced disambiguation Speech Connect stores caller preferences over time, expediting transfers as it builds knowledge about a caller's community-of-interest when given choices among similar names. Names Tuning service This service monitors results in an automated manner, inserting improvements and updated pronunciations within 72 hours of a failed utterance. Speed dial Speech Connect can be configured as a speed-dial soft key on Cisco Unified IP phones. Name response collection Allows the caller to hear the contact's name in the contact's own recorded voice to help determine proper pronunciation.   Note: Speech Connect for Cisco Unity is only available in installations that include a Cisco Unity or Cisco Unity Connection system.   Services: Speech Connect Names Tuning   As employees join and leave your company, there are frequent changes such as new names and pronunciations in your directory. To protect the performance and your investment in Speech Connect, Cisco provides an optional service called the Speech Connect Names Tuning service, which automatically corrects in the background, without you having to report issues to a technical support team. The Names Tuning service also includes professional linguists to correct problems relating to nuances in speech recognition - problems that cannot be solved automatically by any speech engine. This service not only fine-tunes the variety of employee name pronunciations within your corporate directory, it also provides support, monitoring, and reporting. The Names Tuning Service continuously improves the performance of Speech Connect to deliver superior, intelligent speech recognition capabilities.   A customer who subscribes to Speech Connect Names Tuning service receives: • Enhanced linguistic support for 30 days post-installation   • Ongoing, automated monitoring and corrections (corrections generally appear within 72 hours of receipt)   • Cisco Help Desk support for recognition issues - the Cisco Technical Assistance Center (TAC) will prioritize any cases relating to linguistic analysis and correction and put you in contact immediately with a Speech Connect expert   • Monthly reporting of Names Tuning corrections and updates   • Alerts notifying your Speech Connect administrator of corrective actions to be taken The Speech Connect Names Tuning service provides immediate benefits to your global enterprise. While it may be easy for employees to pronounce the name of their co-workers in their own country, proper pronunciation can be a real challenge when dealing with unfamiliar names from other parts of the world. The Names Tuning service monitors the performance of speech servers over the unified messaging network, correcting for pronunciation variances and errors within hours. This service helps ensure that Speech Connect is a valuable collaboration tool across borders and time zones no matter who is calling and no matter the name of the person on the other end of the connection.   Table 2. Speech Connect Names Tuning Service   Issue Definition Action Out-of-grammar (entire name) Speech Connect returns with no choices or presents incorrect choices.  Cause: the name spoken is not in the corporate directory, often because of timing issues with the accurate import of new employee records. A Speech Connect Names Tuning service linguist identifies the missing employee record and reports absence to Speech Connect administrator. Out-of-grammar (First name or last name) There is an employee record for the desired contact, but results are poor because the first or last name has alternative pronunciations. A Names Tuning service linguist adds nickname, preferred name, synonym, alternative pronunciation, or improved phonetic definition. Low confidence score Callers are being presented with many incorrect choices; there are too many choices to disambiguate. "Did you mean John Smith?" A Names Tuning service linguist adds alternative pronunciations or improved phonetic definitions. If the poor results are due to audible voice quality issues, the issue is reported to the Speech Connect administrator. Caller cancels or does not confirm Caller is offered choices but says "cancel," hangs up, or transfers to the operator. A Names Tuning service linguist adds nickname, preferred name, synonym, alternative pronunciation, or improved phonetic definition.   Product Architecture This first release of Speech Connect runs on a separate Cisco speech server (Cisco MCS 7825, 7835, or 7845 Media Convergence Server) as an independent application. If you have deployed a speech server for Cisco Unity 5.x to take advantage of its speech-recognition features, another speech server will be required to support Speech Connect. Future releases of Speech Connect and Cisco Unity speech-recognition capabilities will merge onto a single speech server.   Table 3. Product Specifications   Product compatibility Speech Connect is compatible with Cisco Unified Communications Manager versions 4.x, 5.x, and 6.x, Cisco Unity versions 4.x and 5.x, and Cisco Unity Connection version 2.x. Software compatibility There are no specific software requirements for Cisco Unified Communications Manager and Cisco Unity solutions because Speech Connect, in this initial release, operates independently. Company directory records can be imported into Speech Connect from any directory source, including Active Directory and Lightweight Directory Access Protocol (LDAP). Protocols Speech Connect supports SIP integrations. Components Speech Connect is an application that installs on a Cisco Unity Messaging Product Server for server (Cisco MCS 7825, 7835, or 7845 Media Convergence Server) running Redhat Linux and the Nuance 9.0 speech engine. Ports The speech server (Cisco MCS) is configured with the number of telephony ports required to support the desired call volumes based on the Cisco MCS server platform. See Table 4. Integrations Speech Connect will integrate to the local Cisco Unified Communications Manager or PBX over a SIP connection or through traditional TDM connections (using Cisco PIMG or TIMG). Options The Names Tuning service is the only optional SKU related to Speech Connect. Performance See Table 4 for name directory size and port considerations. Programming interfaces Speech Connect does not provide a programming interface, such as VoiceXML, for the building of voice applications on the same server. Language support Speech Connect supports U.S. English only.   Table 4. Supporting Hardware   Call Volume per Month Company Directory Size Recommended Server Notes 1 - 20,000 1 - 5,000 Cisco MCS 7825 Will not migrate to speech server for future Cisco Unity releases 1 - 60,000 1 - 50,000 Cisco MCS 7835 Can be field upgraded to speech server for Cisco Unity releases 1 - 200,000* 1 - 200,000 Cisco MCS 7845 Can be field upgraded to speech server for Cisco Unity releases Assumptions Busy Hour (15%) If you anticipate greater than 20% of daily calls to fall within one busy hour, increase configuration to next server level. Steady Call Levels If you have bursts of activity and calls are not evenly distributed over the month, increase configuration to next server level. Blocking (P.01) These recommendations assume potential blocking of 1% of calls during the busy hour. If you require a lower level of blocking, increase configuration to next server level. * For higher call volumes, order multiple speech servers.   Cisco Unified Communications Services Cisco and its certified partners can help you deploy a secure, resilient Cisco Unified Communications solution, meeting aggressive deployment schedules and accelerating business advantage. Cisco's portfolio of services is based on proven methodologies for unifying voice, video, data, and mobile applications on fixed and mobile networks. Cisco's unique lifecycle approach to services defines the requisite activities at each phase of the solution lifecycle. Customized planning and design services focus on creating a solution that meets your business needs. Award-winning technical support increases operational efficiency. Remote management services simplify day-to-day operations, and optimization services enhance solution performance as your business needs change.   Conclusion Speech Connect enables a "numberless enterprise" where names are all that an employee, customer, or business partner needs to bridge the gap created by the proliferation of communications devices. Cisco provides the software and services to create this numberless enterprise, in addition to delivering speech-accuracy enhancements so that connections between logical people and teams become more accurate and instantaneous over time. In addition, Cisco Unity amplifies your productivity with an enterprise-ready voice and unified messaging platform as part of a unified communications solution. This system improves productivity by allowing employees to access messages anytime and anywhere, thereby allowing them to respond faster to messages for increased customer intimacy, service, and organizational agility. Cisco Unity with Speech Connect is an essential component of a unified communications strategy that enables collaboration across complex enterprises and across the human network.   For More Information For more information about Cisco Unity with Speech Connect, visit http://www.cisco.com/en/US/products/sw/voicesw/ps2237/index.html or contact your Cisco account representative. ... View more

    Introduction One of the key benefits of Cisco Unity is that it integrates closely with Microsoft Exchange Server to provide Unified Messaging. However, because of this tight relationship, Cisco Unity is very sensitive to issues related to network security, network topology, and Exchange Server installations. A key step in troubleshooting Cisco Unity issues is distinguishing between an anomaly in the Cisco Unity software itself or in the environment it resides in. Once that has been determined, it is much easier to determine the proper subsequent steps to take. To aid in this determination, the MapiNotify.exe utility was created. This is a simple console application written straight to Microsoft’s Messaging Application Programmer’s Interface (MAPI). After you enter some information, MapiNotify.exe tries to logon to a mail user’s mailbox, and register for Exchange notifications of changes to that mail user’s inbox. There’s actually a few different ways that an application can request notifications from Exchange. MapiNotify.exe requests notifications in the exact same manner that the Unity component the Exchange Monitor does.   To run MapiNotify.exe 1. Copy MapiNotify.exe to a place on the Cisco Unity server’s hard drive.   2. If the Unity system version 3.1.5 or higher, the Exchange Monitor resides in the AvMsgStoreMonitorSvr service. If the Unity system version is less than 3.1.5, the Exchange Monitor resides in the AvCsMgr service. To accurately test for the reception of notifications, MapiNotify.exe should be run under the same security context as the Exchange Monitor. Note which service contains the Exchange Monitor.   3. On the Windows 2000 Start Menu, click Settings> Control Panel > Administrative Tools> Services. Look for the service that contains the Exchange Monitor (specified by step 2) and note what the “Log On As” value is set to for this service. Specifically, note if it is the “LocalSystem” or a domain account.   4. Verifiy service level of Service Applicaiton a. If service that contains the Exchange Monitor (specified by step 2) is running as LocalSystem, skip down to step 8 and continue. b. If service that contains the Exchange Monitor (specified by step 2) is running as a domain account, continue with step 5.     If the Exchange Monitor is running as a domain account 5. If the Exchange Monitor is running as a domain account, proceed with one of the following options: a. Log off the current windows session and log back on as the same account that the service that contains the Exchange Monitor is running. b. Use the Windows “runas” command to run MapiNotify.exe under the same security context as the service that contains the Exchange Monitor is running. c. If connected to Unity via a Windows Terminal Session AND, step 1 cannot be done, use WTSLaunch.exe (available from the CPR website) to start MapiNotify.exe.   6. Skip to step 11.   If the Exchange Monitor is running as the local system account 8. If the Exchange Monitor is running as the local system account, on the Windows 2000 Start Menu, click Run, and run the following command (assuming the system32 drive is on C:\; adjust the statement if not): C:\> at HH:MM /interactive "C:\WINNT\SYSTEM32\CMD.EXE"   Where HH:MM is in 24-hour format. Enter a time that is one minute later than the time shown in the status tray in the lower right hand corner. The goal is to get the scheduler to run the command one minute from now. For example, if the current time is 1:00 pm, use 13:01.   9. When the new console window appears (up to a minute after you ran the command in step 8), in the console window type the path to MapiNotify.exe and run it.   10. Continue with step 11.   Running MapiNotify.exe 11. Enter the Exchange Organization that the mail user under test resides in and press Enter. This is information is available in Exchange 5.5 Administrator program, or the Exchange 2000 System Manager. 12. Enter the Exchange Site that the mail user under test resided in and press Enter. 13. Enter the Exchange Server that the mail user’s mailbox resides on and press Enter. 14. Enter the Alias of the mail user under test to open their mailbox and press Enter. 15. At this point, the application will attempt to logon to the mailbox and denote success if applicable. 16. MapiNotify.exe will attempt to register the mail user for MAPI notifications. When a notification is received, it will be displayed on the console. Note: If you are logged in remotely via WTS and the "Log On As" value for the services is not set to a domain account, you will be unable to run MapiNotify.Exe remotely. This is because steps 8 and 9 will not work via WTS because a command prompt cannot be opened in the WTS window by using the AT command.   MapiNotify.exe Features 1. By default, MapiNotify.exe will use the “Unity System Profile” for MAPI initialization and logon. To use a different profile, start MapiNotify.exe with the “-p” command line switch. MapiNotify.exe will prompt for the profile name to be used. This is useful when running MapiNotify.exe on a MAPI enabled client machine other than Unity. 2. Upon running MapiNotify.exe, a diagnostic file will be generated. The file will be located in the same directory from where MapiNotify.exe was run. The diagnostic file will append diagnostics from successive runs of MapiNotify.exe (if the application is run three separate times, the same log file contains diagnostics for each MapiNotify.exe session).   How to Interpret Errors Unfortunately, MAPI errors are fairly generic, and don’t give good direction to what is wrong. However, the fact that an error occurs at all indicates there is an issue outside of Cisco Unity.   The table below describes some of the errors that are reported by MapiNotify.exe.   Table 1. Error Codes, their description and assocated problems   Error Description Associated Problems 80040111 MAPI_E_LOGON_FAILED The information input to mbxtest.exe is invalid RUS hasn’t completed. Security Descriptor is missing from mailbox. Profile may be misconfigured. Check step 3 to ensure that steps 5 through 10 were run appropriately. 8004011d MAPI_E_FAILONEPROVIDER The information input to mbxtest.exe is invalid Account mbxtest.exe is running on doesn’t have rights to logon to the mailbox. The Exchange Server Message Store is dismounted. The Exchange Server is out of licenses. 80040115 MAPI_E_NETWORKERROR Lost connectivity to the Exchange Server. 8004005 E_FAIL Any of the above symptoms could have occurred. ... View more

  'Guidance for Headsets and Handsets''''   Cisco is pleased to announce the addition of new vendors into the Cisco Technology Developer Program. These new vendors offer headsets for use with Cisco IP Communicator. Their products have passed lab testing and met interoperability criteria, ensuring that Cisco product specifications have been reached. With the Cisco Technology Developer Program, customers can quickly and efficiently deploy business solutions with verified compatibility.   A list of vendor products successfully completing Cisco IP Communicator lab tests can be found at: Cisco IP Communicator Vendor Products List   Using Third-Party Headsets and Handsets with Cisco IP Communicator   While Cisco does perform basic testing of third-party headsets and handsets for use with Cisco IP Communicator, it is ultimately the customer's responsibility to test this equipment in their own environment to determine suitable performance. Due to the many inherent environmental and hardware inconsistencies in the locations where Cisco IP Communicator is deployed, there is not a single "best" solution that is optimal for all environments.   Before customers begin deploying any headsets or handsets (especially deployment in quantity) in their production network, Cisco recommends thorough testing at the customer site to check for voice quality issues, especially hum and echo.   The primary reason that support of a headset or handset would be inappropriate for an installation is the potential for an audible hum. This hum can either be heard by the remote party or by both the remote party and the Cisco IP Communicator user. Causes for this humming sound range from electrical lights near the PC to the PC power source itself. In some cases, a hum experienced by a user plugged directly into the PC Universal Serial Bus (USB) port may be reduced or eliminated by using a powered USB hub. In some instances, the mechanics or electronics of various headsets can cause remote parties to hear an echo of their own voice when they speak to Cisco IP Communicator users. The Cisco IP Communicator user will not be aware of this echo.   Finally, some analog headsets do not match the electrical characteristics for which some soundcards are designed. The microphones on such headsets are frequently too sensitive, even when the input levels in Cisco IP Communicator are reduced to their lowest values; the users of such headsets will sound distorted to remote parties.   It is important to ask Cisco IP Communicator users whether a particular headset sounds good to them. In addition, remote parties should be queried as to the reception from Cisco IP Communicator when using a particular headset.   Additional Information   Cisco® Technology Developer Program members provide complementary and compatible technologies, enabling Cisco to continuously expand its solution offerings to customers of all sizes.   With Cisco Technology Developer Program member offerings, customers can:   • Rapidly deploy applications and services • Install products and services with verified interoperability • Maximize their investments in existing Cisco network infrastructure • Select a solution that integrates with and enhances their company's Cisco network • Increase network application flexibility and choice • Use open standards technology for greater interoperability • Rely on coordinated customer support from both Cisco Systems and Cisco Technology Developer Program Members Cisco and program members work together to help ensure that customers receive consistent levels of service and support for interoperable applications and services. Both groups have direct access to each organization's technical-support facilities to provide timely and satisfactory resolution of customer support calls.   For your reference, below is a list of headset and handset vendors who may or may not be a Cisco Technology Developer Program member:   • Actiontec: [1] • Clarisys: [2] • CommuniTech: [3] • Danacom: [4] • Eutectics: [5] • GNNetcom: [6] • Phoenix Audio Technologies: [7] • Plantronics: [8] • Sumisho Electronics (for Japan only): http://www.scs.co.jp/ • Technology Link (for Japan only): http://www.link-corp.co.jp • VXI: http://www.vxicorp.com   For more information about Cisco IP Communicator, visit http://www.cisco.com/en/US/products/sw/voicesw/ps5475/index.html or contact your local account representative. ... View more

    Introduction Cisco netManager Unified Communications 1.0 is part of the Cisco netManager family of products, built to manage small and medium-sized voice and data networks up to 1000 phones or users. It provides easy-to-use monitoring and diagnostics for small and medium-sized deployments of Cisco Unified Communications systems with Cisco Unified Communications Manager, Cisco Unified Communications Manager Business Edition, or Cisco Unified Communications Manager Express.   Detailed Description Cisco netManager-Unified Communications 1.0 monitors all components of small and medium-sized Cisco Unified Communications systems including the underlying IP transport infrastructure and Cisco as well as third-party devices that may exist in the network and provides the current operational status of all the elements in the network. It features built-in rules and thresholds as well as automatic device identification and data collection to help enable easy setup and immediate monitoring of the managed network. It continuously monitors the different elements of the system including Cisco Unified Communications Manager, Cisco Unified Communications Manager Business Edition, Cisco Unified Communications Manager Express, Cisco Unity® systems, Cisco Unity Express, Cisco Unity Connection, Cisco Unified Contact Center Express, Cisco Unified Presence Server, Cisco Unified MeetingPlace® Express, as well as Cisco gateways, routers, and switches. Cisco netManager-Unified Communications also monitors any third-party devices that may exist in the network such as servers, workstations, printers, and other networking devices and provides basic availability monitoring for each of these devices. It also features an extensible monitoring framework through which coverage may be extended by adding different active monitors based on supported protocols like HTTP, Simple Network Management Protocol (SNMP), Windows Management Instrumentation (WMI), and so on that help enable custom monitoring for both Cisco and third-party devices. Cisco netManager-Unified Communications does not require deployment of any agent software on the devices being monitored and thus is completely nondisruptive to system operations. It relies on open supported interfaces such as HTTP, SNMP, and WMI to collect status information from monitored devices.   Applications Cisco netManager-Unified Communications 1.0 is recommended for monitoring Cisco Unified Communications systems based on Cisco Unified Communications Manager, Cisco Unified Communications Manager Business Edition, or Cisco Unified Communications Manager Express for up to 1000 users. A single Windows-based server/workstation running Cisco netManager-Unified Communications 1.0 software can monitor the entire Cisco Unified     Features and Benefits Cisco netManager-Unified Communications 1.0: • Monitors and evaluates the current operational status of all the key components of the Cisco Unified Communications system, including the underlying transport infrastructure. Monitored components include Cisco Unified Communications Manager, Cisco Unified Communications Manager Business Edition, Cisco Unified Communications Manager Express, Cisco Unity software, Cisco Unity Connection, Cisco Unity Express, Cisco Unified Contact Center Express, Cisco Unified MeetingPlace Express, Cisco Unified Presence Server, as well as Cisco gateways, routers, and switches.   • Presents the current operational status of the Cisco Unified Communications system through service-level views of the network and provides contextual tools to view current alert status and historical information and to determine the service impacts of any outages.   • Provides visibility into network connectivity and related information by means of an autogenerated real-time physical connectivity view that not only shows interconnections between different devices but also presents the current operational status of each of the devices and applications in the network.   • Increases productivity of network managers and facilitates faster trouble isolation by providing contextual diagnostic tools and easy one-click access to embedded device management systems.   • Provides current information about connectivity-related and registration-related outages affecting all the IP phones (both Session Initiation Protocol [SIP]-based and Skinny Client Control Protocol [SCCP]-based phones) in the system and provides additional contextual information to help enable the location and identification of the IP phones.   • Facilitates tracking of Cisco Unified Communications devices and IP phone inventory, tracks IP phone status changes, and creates a variety of reports that conveniently summarize move, add, and change operations on IP phones in the network.   • Helps enable easy integration into customer monitoring and troubleshooting workflows by means of notification mechanisms such as SNMP traps, Short Message Service (SMS), and e-mails.   • Provides a single interface through which all the devices in the network (both Cisco devices and third-party devices) may be monitored. Basic availability/reachability status is monitored on devices such as servers, workstations, printers, and other networking devices. It also features an extensible monitoring framework through which monitoring coverage may be extended by adding different active monitors based on supported protocols like HTTP, SNMP, WMI, and so on that enable custom monitoring for both Cisco and third-party devices.   • It features a rich array of real-time reports and historical reports. Reports are divided into a variety of areas and provide specific information on each of these areas. The following lists the different categories of reports:   –Device reports: Focus on performance and availability data for the selected device –Device group reports: Focus on performance and availability data for the selected device group –Phone reports: Provide IP phone inventory and status information for all the IP phones in the deployment –Performance reports: Focus on performance data for the selected device or device group –Problem areas: Display alerts reported across the network across different data sources (traps, syslogs, event logs, performance errors, top N outages, and so on) –Event history: Provides historical reports of all events generated by Cisco netManager for the given device or device group –General: Provides reports on application logs, user activity, and so on   • Provides real-time and historical performance reporting options for easy access and customization. All the collected performance data is summarized and maintained for up to 30 days. Data beyond 30 days is automatically purged. The collected performance data may be displayed in real-time graphical trend charts. The following is a sample of predefined reports that are available without requiring any agents:   –CPU Utilization –Memory Utilization –Interface Utilization (Bandwidth) –Ping Availability –Hard Disk Drive Utilization     Cisco netManager-Unified Communications 1.0 has a Web-based user interface (UI). There is no need to download and install any client applications. Users could be anywhere in the world, and as long as the users have network connectivity to Cisco netManager-Unified Communications 1.0 workstation/server, they can open up Internet Explorer and connect to the Cisco netManager Web interface, authenticate themselves, and verify the system network status.   Furthermore, the Cisco netManager-Unified Communications 1.0 user interface is based on portal technology. This means that users can customize their views and client interfaces to their specific needs by adding/configuring needed content and removing unwanted content. All user customization settings are stored as user preferences and will be remembered the next time the user logs in. The entire Web-based user interface is real time/autorefresh in nature, and users can rest assured that the information they see on the user interface reflects the latest status from the devices. Cisco netManager-Unified Communications 1.0 is available in two distinct license modes: Perpetual right-to-use (RTU) license (no expiration date) and Annual RTU license (valid for one year from the date of registration). Furthermore, within each of these editions, Cisco netManager-Unified Communications 1.0 can be licensed at different deployment scales and is appropriate for commercial class deployments of various sizes. Licensing is controlled by means of a license file, and network administrators can upgrade the license as their Cisco Unified Communications deployment grows without disrupting the monitoring or having to decommission their server. Upgrading the license is as simple as logging on to the Cisco Website, procuring a new license, and deploying it on the server. Licenses are available for monitoring 250 phones, 500 phones, and increments of 250 phones up to a maximum of 1000 phones per Cisco netManager-Unified Communications 1.0 server.   Cisco Unified Communications Services and Support   Using the Cisco Lifecycle Services approach, Cisco and its partners offer a broad portfolio of end-to-end services to support the Cisco Unified Communications system. These services are based on proven methodologies for deploying, operating, and optimizing IP communications solutions. Initial planning and design services, for example, can help you meet aggressive deployment schedules and minimize network disruption during implementation. Operate services reduce the risk of communications downtime with expert technical support, and optimize services enhance solution performance for operational excellence. Cisco and its partners offer a system-level service and support approach that can help you create and maintain a resilient, converged network that meets your business needs. ... View more

    Log In To Cisco Unified Communications Operating System Administration This section describes the procedure for accessing the Cisco Unified Communications Operating System Administration and also provides procedures for recovering a lost password.   Logging In To Cisco Unified Communications Operating System Administration  To access Cisco Unified Communications Operating System Administration and log in, follow this procedure.   NOTE: Do not use the browser controls (for example, the Back button) while you are using Cisco Unified Communications Operating System Administration.   Procedure   Step 1 Log in to Cisco Unified Communications Manager Administration.   Step 2 From the Navigation menu in the upper, right corner of the Cisco Unified Communications Manager Administration window, choose Cisco Unified OS Administration and click Go. The Cisco Unified Communications Operating System Administration Logon window displays. NOTE: You can also access Cisco Unified Communications Operating System Administration directly by entering the following URL: http://server-name/cmplatform   Step 3 Enter your Administrator username and password.   NOTE: The Administrator username and password get established during installation or created by using the command line interface.   Step 4 Click Submit. The Cisco Unified Communications Operating System Administration window displays.   Recovering the Administrator Password If you lose the Administrator password and cannot access the system, use the following procedure to reset the Administrator password.   NOTE: During this procedure, you will be required to remove and then insert a valid CD or DVD in the disk drive to prove that you have physical access to the system. Procedure   Step 1 Log in to the system with the following username and password: • Username: pwrecovery   • Password: pwreset   The Welcome to admin password reset window displays. Step 2 Press any key to continue.   Step 3 If you have a CD or DVD in the disk drive, remove it now.     Step 4 Press any key to continue. The system tests to ensure that you have removed the CD or DVD from the disk drive. Step 5 Insert a valid CD or DVD into the disk drive. The system tests to ensure that you have inserted the disk. Step 6 After the system verifies that you have inserted the disk, you get prompted to enter a new Administrator password. NOTE: The system resets the Administrator username to admin. If you want to set up a different Administrator username and password, use the CLI command set password. For more information "Command Line Interface." Step 7 Re-enter the new password. The system checks the new password for strength. If the password does not contain enough different characters, you get prompted to enter a new password. Step 8 After the system verifies the strength of the new password, the password gets reset, and you get prompted to press any key to exit the password reset utility. ... View more

Description In wireless, provides the control functions and physical links between the MSC and BTS in a GSM mobile wireless network. The BSC controls the interface between the SGSN and the BTS in a GPRS network. The BSC is a high-capacity telephony switch that provides hands-off functions and cell configuration data, and controls radio frequency power levels in BTSs. The combined functions of the BSC and the BTS are referred to as the BSS. Complete Description Wikipedia Base Station Controller http://en.wikipedia.org/wiki/Base_station_subsystem#Base_station_controller ... View more

    Installation Overview Because the 6.0(1) release of Cisco Unified Communications Manager uses a different installation framework than previous releases of Cisco Unified Communications Manager, review all installation instructions carefully before you install Cisco Unified Communications Manager 6.0(1). This guide includes information about installing Cisco Unified Communications Manager Release 6.0(1) on one server or many servers in a cluster environment. For information about upgrading from a Windows-based release (4.x) of Cisco Unified Communications Manager to an appliance-based release (5.0 and higher), refer to Upgrading Cisco Unified Communications Manager. Note: This guide describes only the first two installation types: Basic Install and Upgrade During Install. For information on performing a Windows Upgrade, refer to Upgrading Cisco Unified CallManager.   Important Considerations Before you proceed with the Cisco Unified Communications installation, consider the following requirements and recommendations:   • Be aware that when you install on an existing server, the hard drive gets formatted, and all existing data on the drive gets overwritten.   • Install the Cisco Unified Communications Manager software on the first node or publisher server first and then on the subsequent nodes.   • Make sure that the subsequent node servers that you are installing can connect to the first node server during the installation.   • Enter the same security password on all servers in the cluster.   • Install the Cisco Unified Communications Manager software during off-peak hours or a maintenance window to avoid impact from interruptions.   • Configure the server by using static IP addressing to ensure that the server obtains a fixed IP address and that the Cisco Unified IP Phones can register with the application when you plug the phones into the network.   • Do not attempt to perform any configuration tasks during the installation.   • Do not install any Cisco-verified applications until you complete the installation of Cisco Unified Communications Manager.   • Directory names and filenames that you enter while running the installation program are case-sensitive.   • Carefully read the instructions that follow before you proceed with the installation   Frequently Asked Questions About the Cisco Unified Communications Manager Installation The following section contains information about commonly asked questions and responses. Review this section carefully before you complete the Cisco Unified Communications Manager installation.   How long does it take to perform the Cisco Unified Communications Manager installation? The entire installation process, excluding pre- and post-installation tasks, takes 45 to 90 minutes per server, depending on your server type. Before you install Cisco Unified Communications Manager, consider the size of your cluster.   What Passwords do I Need to Specify? During the Cisco Unified CallManager installation, you must specify the following user names and passowords:   • Administrator account   You use the Administrator username and password to log in to the following areas:   – Cisco Unified Communications Operating System Administration   – Disaster Recovery System   – Command Line Interface   The Administrator login must start with an alphabetic character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. You can change the Administrator password or add a new Administrator account by using the command line interface. See the Cisco Unified Communications Operating System Administration Guide for more information.   • Application User password   You use the Application User password for the following default application user names:   – CCMAdministrator   – CCMSysUser   – WDSysUser   – CCMQRTSysUser   – IPMASysUser   – WDSecureSysUser   – CCMQRTSecureSysUser   – IPMASecureSysUser   You can change the application user password for each application through Cisco Unified CallManager Administration. See the Cisco Unified CallManager Administration Guide for more information.   • Database Access Security Password   The system uses this password to authorize communications between nodes, and you must ensure that this password is identical on all nodes in the cluster.   The Database Access Security password must start with an alphanumeric character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores.   Which servers does Cisco support for this installation? For information about the supported servers, refer to the release notes for your version of Cisco Unified CallManager. Click here for Cisco Product Release Notes.   May I install other software besides Cisco Unified CallManager on the server? You must do all software installations and upgrades by using Cisco Unified Communications Operating System Administration. The system can upload and process only software that Cisco Systems approved.   You cannot install or use third-party or Windows-based software applications that you may have been using with a previous version of Cisco Unified Communications Manager with Cisco Unified Communications Manager 6.0(1).     Browser Requirements You can access Cisco Unified CallManager Administration, Cisco Unified CallManager Serviceability, and Cisco Unified Communications Administration by using the following browsers:   • Microsoft Internet Explorer version 6.0 or later   • Netscape Navigator version 7.1 or later Note: Cisco does not support or test other browsers, such as Mozilla Firefox.   Configuring the Hardware As a part of software installation, the system installer configures the system BIOS and RAID settings for the new operating system and Cisco Unified CallManager application. See Table 2 for the BIOS settings and Table 3 for the RAID settings that are set up during installation. Note: If the hardware configuration process fails during installation, you can use boot-time utilities that are found on both the IBM and HP servers to manually configure the RAID and BIOS settings, as shown in Table 2 and Table 3. Table 2 BIOS Configuration Settings for HP and IBM Servers   HP Servers IBM Servers OS Selection: Linux (not applicable on newer                           models) OS Selection: Not Applicable Boot Order: CD, C:, Floppy Boot Order: CD, C:,                           Floppy Post F1 prompt: Delayed Post F1 prompt:                           Delayed Hyperthreading: Enabled Hyperthreading:                           Enabled Table 3 RAID Settings   MCS 7825 Servers (HP and                 IBM) MCS 7835 Servers (HP and                 IBM) MCS 7845 Servers (HP and IBM) Software Raid Logical Drives: 1 Logical Drives:                 2 Software Raid Note For the HP 7825H1 and the IBM 7825I1, SATA RAID is enabled, and the RAID type specifies 1(1+0), with one logical drive RAID type: 1(1+0) RAID type: 1(1+0) For more detailed descriptions of each installation field, see Table 4.   Gathering Information for an Installation Use Table 4 to record the information about your Cisco Unified CallManager server. Gather this information for each Cisco Unified CallManager server that you are installing in the cluster. You may not need to obtain all the information; gather only the information that is pertinent to your system and network configuration. You should make copies of this table and record your entries for each server in a separate table, even if you are planning to use the DMABackupInfo.inf file to configure your system.   Note: Because some of the fields are optional, they may not apply to your configuration. For example, you choose not to set up an SMTP host.   Caution: You cannot change some of the fields after installation without reinstalling the software, so be sure to enter the values that you want.   The last column in the table shows whether a field can be changed after installation, and if so, whether you can change it through Cisco Unified Communications Operating System Administration or through the Command Line Interface (CLI). Table 4 Configuration Data   Configuration Data Your                 Entry Can Entry Be Changed After                 Installation Administrator Password   Yes. CLI>                 set password admin Application User Password   Yes. CLI>                 set password Country   Yes. CLI>set                 web-security DHCP   Yes. CLI> set network                 dhcp DNS Primary   Yes. CLI>set                 network dns DNS Secondary   Yes. CLI>set                 network dns Domain   Yes. CLI>set network                 domain Domain Name Service DNS Enable   NO. Gateway Address   Yes Use OS Adminstration > Settings>IP or CLI > set network gateway Host Name   NO. IP Address   Yes Use OS Adminstration > Settings>IP or CLI > set network IP IP Mask   Yes Use OS Adminstration > Settings>IP or CLI > set network ip eth0 Location   Yes. CLI>set                 web-security Master Administrator ID   NO. NTP Server IP Address Note You can enter up to five NTP servers.   Yes Use OS Administration >                 Settings>NTP Servers Organization   Yes CLI> set                 web-security Security Password   Yes CLI>                 set password security SMTP Location   Yes CLI>                 set smtp State   Yes CLI> set                 web-security Time Zone   Yes CLI> set                 timezone Unit   Yes CLI> set                 web-security   For more detailed descriptions of each installation field, see Table 5.   Table 5 Installation Field Definitions   Field Description Usage Administrator ID This field specifies the name that you                 want to assign to this account. Ensure the name is unique; it can contain lowercase, alphanumeric characters, hyphens, and underscores. It must                 start with a lowercase alphanumeric character. For this mandatory                 field, you should record it for use when logging in to the CLI or into Cisco Unified Communications Operating System Administration. Administrator Password This field specifies the password that you use for logging into the the CLI on the platform and for logging into Cisco Unified Communications Operating System Administration. Ensure the password is at least six characters long; it can contain alphanumeric                 characters, hyphens, and underscore. For this mandatory field, you should                 record it for use when logging in to the CLI or into Cisco Unified Communications Operating System Administration. DHCP Dynamic Host Configuration Protocol Choose Yes if you want to use DHCP to automatically configure the network settings on your server. If you choose No, you must enter a hostname, IP Address, IP Mask, and Gateway. DNS Enabled A DNS server represents a device that resolves a hostname into an IP address or an IP address into a hostname. If you do not have a DNS server, enter No. When DNS is not enabled, you should only enter IP addresses (not hostnames) for all network devices in                 your Cisco Unified Communications network. If you have a DNS server,                 Cisco recommends that you enter Yes to enable DNS. Disabling DNS limits the system ability to resolve some domain names. DNS Primary The server contacts this DNS server                 first when it attempts to resolve host names. Enter the IP address of the DNS server that you want to specify as the primary DNS server. Enter the IP                 address in dotted decimal format as ddd.ddd.ddd.ddd where ddd can have a value                 between 0 and 255 (except 0.0.0.0). Consider this field mandatory if DNS is set to yes. DNS Secondary When a primary DNS server fails, the                 server will attempt to connect to the secondary DNS server. In this optional field, enter the IP address of the secondary DNS. Enter the IP address                 in dotted decimal format as ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0). Domain This field represents the name of the domain                 in which this machine is located. Consider this field mandatory if DNS                 is set to yes. First Cisco Unified Communications Manager                 Node This field specifies the first Cisco Unified Communications Manager node that contains the database. Subsequent nodes connect to                 the first node to access database content. The first node also                 synchronizes with an external NTP server and provides time to the other nodes. Choose Yes if you are configuring the first Cisco Unified Communications Manager node in the cluster. If you are configuring subsequent nodes, see Table 4 for information on the different fields. Gateway Address A gateway represents a network point that acts as an entrance to another network. Outbound packets get sent to the gateway that will forward them to their final destination. Enter the IP address of the gateway in the format ddd.ddd.ddd.ddd where ddd can have                 a value between 0 and 255 (except 0.0.0.0) If you do not have a                 gateway, you must still fill in this field by setting it to 255.255.255.255.                 Not having a gateway may limit you to only being able to communicate with devices on your subnet. Host Name A host name represents an alias that is                 assigned to an IP address to identify it. Enter a host name that is unique to your network. The host name can comprise up to 64 characters                 and can contain alphanumeric characters and hyphens. If DHCP is set to No, consider this field mandatory. IP Address This field specifies the IP address of this machine. It will uniquely identify the server on this network. Ensure another machine in this network does not use this IP address. Enter the IP address in the form ddd.ddd.ddd.ddd where ddd can have a value between 0                 and 255 (except 0.0.0.0). If DHCP is set to No, consider this field mandatory. IP Mask This field specifies the IP subnet mask of this machine. The subnet mask together with the IP address define the network address and the host address. Enter the IP mask in the form ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0).                 A valid mask should have contiguous '1' bits on left side and                 contiguous '0' bits on the right. For example, a valid mask follows:                 255.255.240.0 (11111111.11111111.11110000.00000000) An invalid mask follows: 255.255.240.240 (11111111.11111111.11110000.11110000) NIC Speed This field specifies the speed of the                 server network interface card (NIC) in megabits per second. The                 possible speeds include 10 or 100. NIC Duplex This field specifies the duplex setting                 of the server NIC. The possible settings include half and full. NTP Server This field identifies the NTP servers                 with which you want to synchronize. Enter the hostname or IP address of one or more NTP server(s). Note You can add additional NTP servers or make changes to the NTP server list at a later time NTP Server Enable When enabled, this server will act as a NTP server and provide time updates to the subsequent nodes in the cluster. Choose Yes if you want to enable this machine to be an NTP server. This option is available only on the first node in a cluster. Security Password Servers in the cluster use the security password to communicate with one another. You will be asked to                 enter the same security password for each subsequent node in the cluster. Enter the security password. Enter the same password in the confirm password field. The password must contain at least six                 alphanumeric characters. It can contain hyphens and underscores, but it must start with an alphanumeric character. Caution You must enter the same password for all nodes in the cluster. Set Hardware Clock This field specifies the date                 and local time for the machine. Note If you set the hardware clock manually, the node does not use an external NTP server for time synchronization. Choose Yes if you want to set the date and local time for the time zone that you chose. Enter the hours based on a                 24-hour format. Note If you configure an external NTP server, the hardware clock gets set automatically. SMTP This field specifies the name of the SMTP host                 that is used for outbound e-mail. Enter the hostname or dotted IP address for the SMTP server. For a host, it can contain alphanumeric                 characters, hyphens, or periods. For a host name, it must start with an                 alphanumeric character. You must fill in this field if you plan to use electronic notification. If not, you can leave it blank. Subnet IP Address By entering a subnet address, you can specify a range of IP Addresses that will be granted access to query this NTP server. Enter an IP subnet that will be granted access to the NTP server During installation, you can only enter two subnets. Subnet Mask This field specifies the subnet mask                 for the subnet address. Enter the subnet mask for the IP subnet. Time zone This field specifies the local                 time zone and offset from Greenwich Mean Time (GMT). Choose Yes if you want to change the time zone. Choose the time zone that most closely matches the location of your machine.   Using the Cisco Unified Communications Answer File Generator Cisco Unified Communications Answer File Generator, a web application, generates answer files for unattended installations of Cisco Unified Communications Manager Business Edition. Individual answer files get copied to a USB key or a floppy diskette that accompanies the Cisco Unified Communications Manager Business Edition DVD during the installation process. The web application supports the following features: • Allows simultaneous generation and saving of answer files for unattended installs on the publisher server and all subscriber servers.   • Provides syntactical validation of data entries.   • Provides online help and documentation. The following usage requirements apply: • The web application supports only fresh installs (for example, it does not include upgrades).   • If DHCP client is being used on the publisher server, and subscriber server answer files are also being generated, you must specify the publisher server IP address. You can access the Cisco Unified Communications Answer File Generator at the following URL: http://www.cisco.com/web/cuc_afg/index.html   The Cisco Unified Communications Answer File Generator supports Internet Explorer version 6.0 or higher and Mozilla version 1.5 or higher.   If a USB key is being used to perform an unattended installation of Cisco Unified Communications Manager Business Edition, you may need to reformat the USB key to the FAT32 file system beforehand. You need to reformat especially in the case of USB keys with larger storage capacity (for example, 1 Gigabyte) that are formatted with the FAT file system.   You can use the Windows XP Disk Management Utility to reformat a USB key to the FAT32 file system as follows (you might need to be logged in as an administrator or a member of the Administrators group to perform these tasks): Procedure Step 1 Insert the USB key into a USB slot on the Windows XP PC.   Step 2 Choose Start > Control Panel > Administrative Tools and then double-click Computer Management.   Step 3 Expand the Storage tree and click Disk Management.   Step 4 Right-click the Removable Disk icon and click Format.   Step 5 You may be asked whether you are sure that you want to format this partition; click Yes.   Step 6 Click the File System: pull down and select FAT32.   Step 7 Click OK. When prompted to format the volume, click OK again.   The Removable Disk icon text should now show the file system format as FAT32.     Handling Network Errors During Installation During the installation process, the installation program verifies that the server can successfully connect to the network by using the network configuration you enter. If it cannot, a message displays, and you get prompted to select one of the following options:   • RETRY — The installation program tries to validate networking again. If validation fails again, the error dialog box displays again.   • REVIEW (Check Install)— Allows you to review and modify the networking configuration. The installation program returns to the network configuration windows. Networking gets validated after you complete each networking window, so the message might display multiple times. If the message displays while you are reviewing the network configuration windows, choose IGNORE to move to the next window. If you choose REVIEW, the first network configuration window displays again. • HALT — The installation halts. You can copy the installation log files to a USB disk to aid troubleshooting of your network configuration.   • IGNORE — The installation continues. The networking error gets logged. In some cases, the installation program validates networking multiple times, so this error dialog box might display multiple times. Note: Networking is validated after you complete each networking window, so the message might display multiple times. If the message displays while you are reviewing the network configuration windows, choose IGNORE to move to the next window. If you choose REVIEW, the first network configuration window appears again.   Installing the New Operating System and Application NOTE: This document describes only the first two installation types: Basic Install and Upgrade During Install. For information on performing a Windows Upgrade, refer to Upgrading Cisco Unified Communications Manager.   Starting the Installation Step 1 Insert the installation DVD into the tray and restart the server, so it boots from the DVD. After the server completes the boot sequence, the DVD Found window displays.   Step 2 To perform the media check, choose Yes, or to skip the media check, choose No. The media check checks the integrity of the DVD. If your DVD has passed the media check previously, you might choose to skip the media check.   Note: If you have a new server with Cisco Unified Communications Manager Business Edition preinstalled, you do not need to install from a DVD, unless you want to reimage the server with a later product release. You can go directly to the "Entering Preexisting Configuration Information" procedure.   Step 3 If you choose Yes to perform the media check, the Media Check Result window displays. Perform these tasks:  a. If the Media Check Result displays Pass, choose OK to continue the installation.   b. If the media fails the Media Check, either download another copy from Cisco.com or obtain another disc directly from Cisco.   Step 4 The system installer performs the following hardware checks to ensure that your system is correctly configured. If the installer makes any changes to your hardware configuration settings, you will get prompted to restart your system. Leave the DVD in the drive during the reboot:   • First, the installation process checks for the correct drivers, and you may see the following warning:   No hard drives have been found. You probably need to manually choose device drivers for install to succeed. Would you like to select drivers now?   To continue the installation, choose Yes.   • The installation next checks to see whether you have a supported hardware platform. If your server does not meet the exact hardware requirements, the installation process fails with a critical error. If you think this is not correct, capture the error and report it Cisco support.   • The installation process next verifies RAID configuration and BIOS settings.   NOTE: If this step repeats, choose Yes again.   After the hardware checks complete, Product Deployment Selection window displays.   Step 5 In the Product Deployment Selection window, select the product to install; then, choose OK. You can choose from the following options:   • Cisco Unified Communications Manager   • Cisco Unity Connection   • Cisco Unified Communications Manager Business Edition (includes Cisco Unified Communications Manager and Cisco Unity Connection)   NOTE: Only the products that are supported on your server appear in the list.   Step 6 If software is currently installed on the server, the Overwrite Hard Drive window opens and displays the current software version on your hard drive and the version on the DVD. Choose Yes to continue with the installation or No to cancel.   CAUTION: If you choose Yes on the Overwrite Hard Drive window, all existing data on your hard drive gets overwritten and destroyed.   The Platform Installation Wizard window displays. Step 7 To configure the platform now, choose Proceed. If you want to configure the platform later, choose Skip.   • If you want to install and configure the software at this time, choose Proceed and continue with this procedure.   • If you want to install the software now and configure it later or if you have a server that has Cisco Unified Communications Manager Business Edition preinstalled, choose Skip and continue with the "Entering Preexisting Configuration Information" section.   Step 8 Choose the type of installation to perform by doing the following steps. See Table 6 for more information on installation options:   a. In the Apply Additional Release window, choose one of the options:   • To upgrade to a later Service Release of the software during installation, choose Yes. Continue with the "Upgrading During Installation" section.   • To skip this step, choose No.   • To return to the previous window, choose Back.   b. In the Import Windows Data window, choose No.   NOTE: To perform a Windows Upgrade, that is, to upgrade from a Windows version of Cisco Unified Communications Manager to Cisco Unified Communications Manager 6.0(1), see Upgrading Cisco Unified Communications Manager for more information.   Step 9 In the Basic Install window, choose Continue to install the software version on the DVD or configure the preinstalled software. Continue with the "Performing the Basic Installation" section.   Entering Preexisting Configuration Information   Start here if you have a server that has the product preinstalled or if you chose Skip in the Platform Installation Wizard window. Step 1 After the system restarts, the Preexisting Installation Configuration window displays.   Step 2 If you have preexisting configuration information, generated by the Answer File Generator, that is stored on a floppy disc or a USB key, insert the disc or the USB key now and choose Continue. The installation wizard will read the configuration information during the installation process.   Step 3 To continue with the Platform Installation Wizard, choose Proceed.   Step 4 Choose the type of installation to perform by doing the following steps. See Table 6 for more information on installation options:   a. In the Apply Additional Release window, choose one of the options:   • To upgrade to a later Service Release of the software during installation, choose Yes. Continue with the "Upgrading During Installation" section.   • To skip this step, choose No.   • To return to the previous window, choose Back.   b. In the Import Windows Data window, choose No.   NOTE: To perform a Windows Upgrade, that is, to upgrade from a Windows version of Cisco Unified Communications Manager to Cisco Unified Communications Manager 6.0 see Upgrading Cisco Unified Communications Manager for more information.   Step 5 In the Basic Install window, choose Continue. Continue with the "Performing the Basic Installation" section.   Upgrading During Installation   If you choose Yes in the Upgrade During Install window, the installation wizard installs the software version on the DVD first and then restarts the system. You must obtain the appropriate upgrade file from Cisco.com before you can upgrade during installation.   If you are upgrading from Cisco Unified Communications Manager release 5.x, the upgrade file name has the following format: cisco-ipt-k9-patchX.X.X.X-X.tar.gz.sgn Where X.X.X.X-X represents the release and build number.   NOTE: Do not rename the patch file before you install it because the system will not recognize it as a valid file. NOTE: Do not unzip or untar the file. If you do, the system may not be able to read the upgrade files.   If you are upgrading from Cisco Unified Communications Manager release 6.x, the upgrade file has the extension sgn.iso. You can access the upgrade file during the installation process from either a local disk (CD or DVD) or from a remote FTP or TFTP server. : Step 1 After the system restarts, the Platform Installation Wizard window displays. To continue the installation, choose Proceed. The Upgrade During Install window displays.   NOTE: If the installer pops up a window that states that it detected new hardware, press any key and then choose Install from the next window.   Step 2 Choose Yes.   : Step 3 Choose the upgrade retrieval mechanism to use to retrieve the upgrade file:   • SFTP — Retrieves the upgrade file from a remote server by using the Secure File Transfer Protocol (SFTP). Skip to the "Upgrading from a Remote Server" section.   • FTP — Retrieves the upgrade file from a remote server by using File Transfer Protocol (FTP). Skip to the "Upgrading from a Remote Server" section.   • LOCAL — Retrieves the upgrade file from a local CD or DVD. Continue with the "Upgrading from a Local Disk" section.   Upgrading from a Local Disk Before you can upgrade from a local disk, you must download the appropriate patch file from Cisco.com and copy the file to a CD or DVD. Because of the size of the patch files, you will need to copy it to a DVD in most cases.   •If you are using an upgrade file with the tar.gz.sgn extension, copy the upgrade file to a writeable CD or DVD. •If you are using an upgrade file with the sgn.iso extension, you must create an ISO image on the DVD from the upgrade file. Step 1 When the Local Patch Configuration window displays, enter the patch directory and patch name, if required, and choose OK.   NOTE: You only need to enter the patch directory when the patch is not stored in the root directory of the CD or DVD. If the patch is stored in the root directory, enter a slash (/) in the directory field. NOTE: This step does not apply if you are using an upgrade file with the sgn.iso extension.   The Install Upgrade Patch Selection Validation window displays.   Step 2 The window displays the patch file that is available on the CD or DVD. To update the system with this patch, choose Continue.   Step 3 Choose the upgrade patch to install. The system installs the patch, then restarts the system running the upgraded software version. After the system restarts, the Preexisting Configuration Information window displays. Skip to the "Entering Preexisting Configuration Information" section.   Upgrading from a Remote Server If you chose to upgrade through an FTP or SFTP connection to a remote server, you must first configure the network settings. Step 1 The Auto Negotiation Configuration window displays.   Step 2 The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) by using automatic negotiation. You can change this setting after installation.   • To enable automatic negotiation, choose Yes. The DHCP Configuration window displays.   NOTE: To use this option, your hub or Ethernet switch must support automatic negotiation.   •To disable automatic negotiation, choose No. The NIC Speed and Duplex Configuration window displays.   Step 3 If you chose to disable automatic negotiation, manually choose the appropriate NIC speed and duplex settings now and choose OK to continue.   The DHCP Configuration window displays.   Step 4 For network configuration, you can choose to either set up static network IP addresses for the node and gateway or to use Dynamic Host Configuration Protocol (DHCP).   • If you have a DHCP server that is configured in your network and want to use DHCP, choose Yes. The system restarts and checks for network connectivity. Skip to Step 7.   • If you want to configure static IP addresses for the node, choose No. The Static Network Configuration window displays.   Step 5 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 5 for field descriptions.   The DNS Client Configuration window displays.   Step 6 To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 5 for field descriptions.   After the system configures the network and checks for connectivity, the Remote Patch Configuration window displays.   Step 7 Enter the location and login information for the remote file server. See Table 5 for field descriptions. After the network restarts, the system connects to the remote server and retrieves a list of available upgrade patches.   If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path. For example, if the upgrade file is in the patches directory, you must enter /patches. If the upgrade file is located on a Windows server, check with your system administrator for the correct directory path.   The Install Upgrade Patch Selection window displays.   Step 8 Choose the upgrade patch to install. The system downloads, unpacks, and installs the patch and then restarts the system running the upgraded software version. After the system restarts, the Preexisting Configuration Information window displays. Continue with the "Entering Preexisting Configuration Information" section.   Performing the Basic Installation Step 1 When the Timezone Configuration displays, choose the appropriate time zone for the server and then choose OK.   The Auto Negotiation Configuration window displays.   Step 2 The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) by using automatic negotiation. You can change this setting after installation.   • To enable automatic negotiation, choose Yes. The DHCP Configuration window displays.   NOTE: To use this option, your hub or Ethernet switch must support automatic negotiation.   • To disable automatic negotiation, choose No. The NIC Speed and Duplex Configuration window displays.   Step 3 If you chose to disable automatic negotiation, manually choose the appropriate NIC speed and duplex settings now and choose OK to continue.   The DHCP Configuration window displays.   Step 4 For network configuration, you can choose to either set up static network IP address for the node or to use Dynamic Host Configuration Protocol (DHCP).   • If you have a DHCP server that is configured in your network and want to use DHCP, choose Yes. The network restarts, and the Administrator Login Configuration window displays.   • If you want to configure static IP address for the node, choose No. The Static Network Configuration window displays.   Step 5 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 5 for field descriptions.   The DNS Client Configuration window displays.   Step 6 To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 5 for field descriptions.   The network restarts by using the new configuration information, and the Administrator Login Configuration window displays.   Step 7 Enter your Administrator login and password from Table 4.   NOTE: The Administrator login must start with an alphabetic character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. You will need the Administrator login to log in to Cisco Unified Communications Operating System Administration, the command line interface, and the Disaster Recovery System.   The Certificate Information window displays.   Step 8 Enter your certificate signing request information and choose OK.   The First Node Configuration window displays.   Step 9 You can configure this server as either the first node in a Cisco Unified Communications Manager cluster or as a subsequent node.   • To configure this server as the first Cisco Unified Communications Manager node, choose Yes and continue with the "Configuring the First Node" section.   • To configure this server as a subsequent node in the cluster, choose No and continue with the "Configuring a Subsequent Node" section.   Configuring the First Node   After you finish the basic installation, follow this procedure to configure the server as the first node in the cluster. Step 1 The Network Time Protocol Client Configuration window displays.   Cisco recommends that you use an external NTP server to ensure accurate system time on the first node. Ensure the external NTP server is stratum 9 or higher (meaning stratums 1-9). Subsequent nodes in the cluster will get their time from the first node.   Step 2 Choose whether you want to configure an external NTP server or manually configure the system time.   • To set up an external NTP server, choose Yes and enter the IP address, NTP server name, or NTP server pool name for at least one NTP server. You can configure up to five NTP servers, and Cisco recommends that you use at least three. Choose Proceed to continue with the installation.   The system contacts an NTP server and automatically sets the time on the hardware clock.   NOTE: If the Test button displays, you can choose Test to check whether the NTP servers are accessible.   • To manually configure the system time, choose No and enter the appropriate date and time to set the hardware clock. Choose OK to continue with the installation.   The Database Access Security Configuration window displays.   Step 3 Enter the Database Access Security password from Table 4.   NOTE: The Database Access Security password must start with an alphanumeric character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. The system uses this password to authorize communications between nodes, and you must ensure this password is identical on all nodes in the cluster.   The SMTP Host Configuration window displays.   Step 4 If you want to configure an SMTP server, choose Yes and enter the SMTP server name.   NOTE: You must configure an SMTP server to use certain platform features; however, you can also configure an SMTP server later by using the platform GUI or the command line interface.   Step 5 Choose OK. The Application User Configuration window displays.   Step 6 Enter the Application User Username and Password from Table 4 and confirm the password by entering it again.   Step 7 Choose OK. The Platform Configuration Confirmation window displays.   Step 8 To continue with the installation, choose OK; or to modify the platform configuration, choose Back.   The system installs and configures the software. The DVD drive ejects and the server reboots. Do not reinsert the DVD.   Step 9 When the installation process completes, you get prompted to log in by using the Administrator account and password.   Step 10 Complete the post-upgrade tasks that are listed in the "Post-Installation Tasks" section.   Configuring a Subsequent Node To configure a subsequent node in the cluster, follow these steps.   CAUTION: You must configure a subsequent node on the first node using Cisco Unified Communications Manager Administration before you install the subsequent node. For more information, see the Cisco Unified Communications Manager Administration Guide.   Step 1 The First Node Access Configuration window displays.   Step 2 Enter the First Node Access Configuration information from Table 4.   The SMTP Host Configuration window displays.   Step 3 If you want to configure an SMTP server, choose Yes and enter the SMTP server name.   NOTE: You must configure an SMTP server to use certain platform features. However, you can also configure an SMTP server later by using the platform GUI or the command line interface.   The Platform Configuration Confirmation window displays.   Step 4 To start installing the software, choose OK, or, if you want to change the configuration, choose Back.   Step 5 When the installation process completes, you get prompted to log in by using the Administrator account and password.   Step 6 Complete the post-upgrade tasks that are listed in the "Post-Installation Tasks" section ... View more

  Troubleshooting Overview This section provides the necessary background information and available resources to troubleshoot the Cisco Unified CallManager. The section covers following topics: •  Cisco Unified CallManager Serviceability   •  Cisco Unified Communications Operating System Administration   • General Model of Problem Solving   • Network Failure Preparation   Cisco Unified CallManager Serviceability Cisco Unified CallManager Serviceability, a web-based troubleshooting tool for Cisco Unified CallManager, provides the following functionality to assist administrators troubleshoot system problems: •Saves Cisco Unified CallManager services alarms and events for troubleshooting and provides alarm message definitions.   •Saves Cisco Unified CallManager services trace information to various log files for troubleshooting. Administrators can configure, collect, and view trace information.   •Monitors real-time behavior of the components in a Cisco Unified CallManager cluster through the real-time monitoring tool (RTMT).   •Generates reports for Quality of Service, traffic, and billing information through Cisco Unified CallManager CDR Analysis and Reporting (CAR).   •Provides feature services that you can activate, deactivate, and view through the Service Activation window.   •Provides an interface for starting and stopping feature and network services.   •Archives reports that are associated with Cisco Unified CallManager Serviceability tools.   •Allows Cisco Unified CallManager to work as a managed device for SNMP remote management and troubleshooting.   •Monitors the disk usage of the log partition on a server (or all servers in the cluster). Access Cisco Unified CallManager Serviceability from the Cisco Unified CallManager Administration window by choosing Cisco Unified CallManager Serviceability from the Navigation drop-down list box. Installing the Cisco Unified CallManager software automatically installs Cisco Unified CallManager Serviceability and makes it available.   Cisco Unified Communications Operating System Administration Cisco Unified Communications Operating System Administration allows you to perform the following tasks to configure and manage the Cisco Unified Communications Operating System: •Check software and hardware status.   •Check and update IP addresses.   •Ping other network devices.   •Manage Network Time Protocol servers.   •Upgrade system software and options.   •Restart the system.   General Model of Problem Solving When troubleshooting a telephony or IP network environment, define the specific symptoms, identify all potential problems that could be causing the symptoms, and then systematically eliminate each potential problem (from most likely to least likely) until the symptoms disappear. The following steps provide guidelines to use in the problem-solving process. Procedure Step 1 Analyze the network problem and create a clear problem statement. Define symptoms and potential causes.   Step 2 Gather the facts that you need to help isolate possible causes.   Step 3 Consider possible causes based on the facts that you gathered.   Step 4 Create an action plan based on those causes. Begin with the most likely problem and devise a plan in which you manipulate only one variable.   Step 5 Implement the action plan; perform each step carefully while testing to see whether the symptom disappears.   Step 6 Analyze the results to determine whether the problem has been resolved. If the problem was resolved, consider the process complete.   Step 7 If the problem has not been resolved, create an action plan based on the next most probable cause on your list. Return to Step 4 and repeat the process until the problem is solved. NOTE: Make sure that you undo anything that you changed while implementing your action plan. Remember that you want to change only one variable at a time. NOTE: If you exhaust all the common causes and actions (either those outlined in this document or others that you have identified in your environment), contact Cisco TAC.   Network Failure Preparation You can always recover more easily from a network failure if you are prepared ahead of time. To determine if you are prepared for a network failure, answer the following questions: •Do you have an accurate physical and logical map of your internetwork that outlines the physical location of all of the devices on the network and how they are connected as well as a logical map of network addresses, network numbers, and subnetworks?   •Do you have a list of all network protocols that are implemented in your network for each of the protocols implemented and a list of the network numbers, subnetworks, zones, and areas that are associated with them?   •Do you know which protocols are being routed and the correct, up-to-date configuration information for each protocol?   •Do you know which protocols are being bridged? Are any filters configured in any of these bridges, and do you have a copy of these configurations? Is this applicable to Cisco Unified CallManager?   •Do you know all the points of contact to external networks, including any connections to the Internet? For each external network connection, do you know what routing protocol is being used?   •Has your organization documented normal network behavior and performance, so you can compare current problems with a baseline? If you can answer yes to these questions, faster recovery from a failure results.   Troubleshooting Tools This section addresses the tools and utilities that you use to configure, monitor, and troubleshoot Cisco Unified CallManager and provides general guidelines for collecting information to avoid repetitive testing and recollection of identical data. NOTE: To access some of the URL sites that are listed in this document, you must be a registered user, and you must be logged in. This section contains the following topics: •Cisco Unified CallManager Serviceability Troubleshooting Tools   •  Command Line Interface   • CiscoWorks2000   •  Sniffer Traces   •  Debugs   •  Cisco Secure Telnet   •  Packet Capture   •  Troubleshooting Perfmon Data Logging   •  Common Troubleshooting Tasks, Tools, and Commands   •  Troubleshooting Tips   •  Verify Cisco Unified CallManager Services Are Running     Cisco Unified CallManager Serviceability Troubleshooting Tools Refer to the Cisco Unified CallManager Serviceability Administration Guide and the Cisco Unified CallManager Serviceability System Guide for detailed information of the following different types of tools that Cisco Unified CallManager Serviceability provides to monitor and analyze the various Cisco Unified CallManager systems.       Command Line Interface Use the command line interface (CLI) to access the Cisco Unified CallManager system for basic maintenance and failure recovery. Obtain access to the system by either a hard-wired terminal (a system monitor and keyboard) or by performing a SSH session.   The account name and password get created at install time. You can change the password after install, but you never can change the account name.   A command represents a text instruction that caused the system to perform some function. Commands may be stand alone, or they can have mandatory or optional arguments or options.   A level comprises a collection of commands; for example, show designates a level, whereas show status specifies a command. Each level and command also includes an associated privilege level. You can execute a command only if you have sufficient privilege level.   For complete information on the Cisco Unified CallManager CLI command set, see the Cisco Unified CallManager Administration Guide, Release 5.1.   CiscoWorks2000 CiscoWorks2000 serves as the network management system of choice for all Cisco devices including Cisco Unified CallManager. Because CiscoWorks2000 is not bundled with Cisco Unified CallManager, you must purchase it separately. Use the following tools with CiscoWorks2000 for remote serviceability:   • System Log Management • Cisco Discovery Protocol Support • Simple Network Management Protocol Support   System Log Management Although it can be adapted to other network management systems, Cisco Syslog Analysis, which is packaged with CiscoWorks2000 Resource Manager Essentials, provides the best method to manage Syslog messages from Cisco devices.   Cisco Syslog Analyzer serves as the component of Cisco Syslog Analysis that provides common storage and analysis of the system log for multiple applications. The other major component, Syslog Analyzer Collector, gathers log messages from Cisco Unified CallManager servers.   These two Cisco applications work together to provide a centralized system logging service for Cisco Unified Communications Solutions.   Cisco Discovery Protocol Support The Cisco Discovery Protocol Support enables discovery of Cisco Unified CallManager servers and management of those servers by CiscoWorks2000.   Simple Network Management Protocol Support Network management systems (NMS) use SNMP, an industry-standard interface, to exchange management information between network devices. A part of the TCP/IP protocol suite, SNMP enables administrators to remotely manage network performance, find and solve network problems, and plan for network growth. An SNMP-managed network comprises three key components: managed devices, agents, and network management systems. •A managed device designates a network node that contains an SNMP agent and resides on a managed network. Managed devices collect and store management information and make it available by using SNMP.   •An agent, as network management software, resides on a managed device. An agent contains local knowledge of management information and translates it into a form that is compatible with SNMP.   •A network management system comprises an SNMP management application together with the computer on which it runs. An NMS executes applications that monitor and control managed devices. An NMS provides the bulk of the processing and memory resources that are required for network management. The following NMSs share compatibility with Cisco Unified CallManager:   – CiscoWorks2000   – HP OpenView   – Third-party applications that support SNMP and Cisco Unified CallManager SNMP interfaces   Sniffer Traces Typically, you collect sniffer traces by connecting a laptop or other sniffer-equipped device on a Catalyst port that is configured to span the VLAN or port(s) (CatOS, Cat6K-IOS, XL-IOS) that contains the trouble information. If no free port is available, connect the sniffer-equipped device on a hub that is inserted between the switch and the device. TIP: To help facilitate reading and interpreting of the traces by the TAC engineer, Cisco recommends using Sniffer Pro software because it is widely used within the TAC. Have available the IP/MAC addresses of all equipment that is involved, such as IP phones, gateways, Cisco Unified CallManagers, and so on.   Debugs The output from debug privileged EXEC commands provides diagnostic information about a variety of internetworking event that relate to protocol status and network activity in general.   Set up your terminal emulator software (such as HyperTerminal), so it can capture the debug output to a file. In HyperTerminal, click Transfer; then, click Capture Text and choose the appropriate options.   Before running any IOS voice gateway debugs, make sure that service timestamps debug datetime msec is globally configured on the gateway. NOTE: Avoid collecting debugs in a live environment during operation hours. Preferably, collect debugs during non-working hours. If you must collect debugs in a live environment, configure no logging console and logging buffered. To collect the debugs, use show log.   Because some debugs can be lengthy, collect them directly on the console port (default logging console) or on the buffer (logging buffer). Collecting debugs over a Telnet session may impact the device performance, and the result could be incomplete debugs, which requires that you re-collect them.   To stop a debug, use the no debug all or undebug all commands. Verify that the debugs have been turned off by using the command show debug.   Cisco Secure Telnet Cisco Secure Telnet allows Cisco Service Engineers (CSE) transparent firewall access to the Cisco Unified CallManager node on your site. Using strong encryption, Cisco Secure Telnet enables a special Telnet client from Cisco Systems to connect to a Telnet daemon behind your firewall. This secure connection allows remote monitoring and troubleshooting of your Cisco Unified CallManager nodes, without requiring firewall modifications. NOTE: Cisco provides this service only with your permission. You must ensure that a network administrator is available at your site to help initiate the process.   Packet Capture This section contains information on the following topics:   • Packet Capturing Overview • Configuration Checklist for Packet Capturing • Adding an End User to the Standard Packet Sniffer Users Group • Configuring Packet-Capturing Service Parameters • Configuring Packet Capturing in the Phone Configuration Window • Configuring Packet Capturing in Gateway and Trunk Configuration Windows • Packet-Capturing Configuration Settings • Analyzing Captured Packets     Packet Capturing Overview Because third-party troubleshooting tools that sniff media and TCP packets do not work after you enable encryption, you must use Cisco Unified CallManager Administration to perform the following tasks if a problem occurs:   •Analyze packets for messages that are exchanged between Cisco Unified CallManager and the device (Cisco Unified IP Phone, Cisco Unified SIP IP Phone, Cisco IOS MGCP gateway, H.323 gateway, H.323/H.245/H.225 trunk, or SIP trunk).   •Capture the Secure Real Time Protocol (SRTP) packets between the devices.   •Extract the media encryption key material from messages and decrypt the media between the devices. TIP: Performing this task for several devices at the same time may cause high CPU usage and call-processing interruptions. Cisco strongly recommends that you perform this task when you can minimize call-processing interruptions. For more information, see the Cisco Unified CallManager Security Guide.   Configuration Checklist for Packet Capturing Extracting and analyzing pertinent data includes performing the following tasks in Table 2-2: Table 2-2 Configuration Checklist for Packet Capturing   Packet-Capturing Configuration Settings Use Table 2-3, which describes the Packet Capture Mode and Packet Capture Duration settings, with the following sections: • Configuring Packet Capturing in the Phone Configuration Window   • Configuring Packet Capturing in Gateway and Trunk Configuration Windows Table 2-3 Packet-Capturing Configuration Settings   Adding an End User to the Standard Packet Sniffer Users Group End users that belong to the Standard Packet Sniffer Users group can configure the Packet Capture Mode and Packet Capture Duration settings for devices that support packet capturing. If the user does not exist in the Standard Packet Sniffer Users group, the user cannot initiate packet capturing.   The following procedure, which describes how to add an end user to the Standard Packet Sniffer Users group, assumes that you configured the end user in Cisco Unified CallManager Administration, as described in the Cisco Unified CallManager Administration Guide.   Procedure Step 1 Find the user group, as described in the Cisco Unified CallManager Administration Guide.   Step 2 After the Find/List window displays, click the Standard Packet Sniffer Users link.   Step 3 Click the Add Users to Group button.   Step 4 Add the end user, as described in the Cisco Unified CallManager Administration Guide.   Step 5 After you add the user, click Save.     Configuring Packet-Capturing Service Parameters To configure parameters for packet capturing, perform the following procedure: Procedure Step 1 In Cisco Unified CallManager Administration, choose System > Service Parameters.   Step 2 From the Server drop-down list box, choose an Active server where you activated the Cisco Unified CallManager service.   Step 3 From the Service drop-down list box, choose the Cisco CallManager (Active) service.   Step 4 Scroll to the TLS Packet Capturing Configuration pane and configure the packet capturing settings. TIP: For information on the service parameters, click the name of the parameter or the question mark that displays in the window. NOTE: For packet capturing to occur, you must set the Packet Capture Enable service parameter to True. Step 5 For the changes to take effect, click Save.   Step 6 To continue packet-capturing configuration, see one of the following sections:   • Configuring Packet Capturing in the Phone Configuration Window   • Configuring Packet Capturing in Gateway and Trunk Configuration Windows     Configuring Packet Capturing in the Phone Configuration Window After you enable packet capturing in the Service Parameter window, you can configure packet capturing on a per-device basis in the Phone Configuration window of Cisco Unified CallManager Administration. You enable or disable packet capturing on a per-phone basis. The default setting for packet capturing equals None. TIP: Cisco strongly recommends that you do not enable packet capturing for many phones at the same time because this task may cause high CPU usage in your network. If you do not want to capture packets or if you completed the task, set the Packet Capture Enable service parameter to False. To configure packet capturing for phones, perform the following procedure: Procedure Step 1 Before you configure the packet-capturing settings, see the  Configuration Checklist for Packet Capturing  section.   Step 2 Find the SIP or SCCP phone, as described in the Cisco Unified CallManager Administration Guide.   Step 3 After the Phone Configuration window displays, configure the troubleshooting settings, as described in Table 2-3.   Step 4 After you complete the configuration, click Save.   Step 5 In the Reset dialog box, click OK. TIP: Although Cisco Unified CallManager Administration prompts you to reset the device, you do not need to reset the device to capture packets. Additional Steps - Capture SRTP packets by using a sniffer trace between the affected devices.   - After you capture the packets, set the Packet Capture Enable service parameter to False.   - See the  Analyzing Captured Packets section.     Configuring Packet Capturing in Gateway and Trunk Configuration Windows The following gateways and trunks support packet capturing in Cisco Unified CallManager Administration: •Cisco IOS MGCP gateways   •H.323 gateways   •H.323/H.245/H.225 trunks   •SIP trunks TIP: Cisco strongly recommends that you do not enable packet capturing for many devices at the same time because this task may cause high CPU usage in your network. If you do not want to capture packets or if you completed the task, set the Packet Capture Enable service parameter to False. To configure packet-capturing settings in the Gateway or Trunk Configuration window, perform the following procedure:   Procedure Step 1 Before you configure the packet-capturing settings, see the "Configuration Checklist for Packet Capturing" section.   Step 2 Perform one of the following tasks:   •Find the Cisco IOS MGCP gateway, as described in the Cisco Unified CallManager Administration Guide.   •Find the H.323 gateway, as described in the Cisco Unified CallManager Administration Guide.   •Find the H.323/H.245/H.225 trunk, as described in the Cisco Unified CallManager Administration Guide.   •Find the SIP trunk, as described in the Cisco Unified CallManager Administration Guide.   Step 3 After the configuration window displays, locate the Packet Capture Mode and Packet Capture Duration settings. TIP: If you located a Cisco IOS MGCP gateway, ensure that you configured the ports for the Cisco IOS MGCP gateway, as described in the Cisco Unified CallManager Administration Guide. The packet-capturing settings for the Cisco IOS MGCP gateway display in the Gateway Configuration window for endpoint identifiers. To access this window, click the endpoint identifier for the voice interface card. Step 4 Configure the troubleshooting settings, as described in Table 2-3.   Step 5 After you configure the packet-capturing settings, click Save.   Step 6 In the Reset dialog box, click OK. TIP: Although Cisco Unified CallManager Administration prompts you to reset the device, you do not need to reset the device to capture packets. Additional Steps - Capture SRTP packets by using a sniffer trace between the affected devices.   - After you capture the packets, set the Packet Capture Enable service parameter to False.   - See the  Analyzing Captured Packets section.     Packet-Capturing Configuration Settings Use Table 2-3, which describes the Packet Capture Mode and Packet Capture Duration settings, with the following sections: • Configuring Packet Capturing in the Phone Configuration Window • Configuring Packet Capturing in Gateway and Trunk Configuration Windows Table 2-3 Packet-Capturing Configuration Settings   Analyzing Captured Packets Cisco Technical Assistance Center (TAC) analyzes the packets by using a debugging tool. Before you contact TAC, capture SRTP packets by using a sniffer trace between the affected devices. Contact TAC directly after you gather the following information: •Packet Capture File— Insert non-formatted text here https://<IP address or server name>/pktCap/pktCap.jsp?file=mm-dd-yyyy.pkt, where you browse into the server and locate the packet-capture file by month, date, and year (mm-dd-yyyy) •Key for the file— Insert non-formatted text here https://<IP address or server name>/pktCap/pktCap.jsp?key=mm-dd-yyyy.pkt, where you browse into the server and locate the key by month, date, and year (mm-dd-yyyy) •User name and password of end user that belongs to the Standard Packet Sniffer Users group For more information, see the Cisco Unified CallManager Security Guide.   Troubleshooting Perfmon Data Logging CAUTION: ENABLING THE TROUBLEHSOOTING PERFMON DATA LOGGING FEATURE IMPACTS SYSTEMS PERFORMANCE ON THE SELECTED NODE. DO NOT ENABLE THIS PARAMETER UNLESS CISCO TECHNICAL CENTER DIRECTS YOU TO DO SO.. The troubleshooting perfmon data logging feature assists Cisco TAC in identifying system problems. When you enable troubleshooting perfmon data logging, you initiate the collection of a set of Cisco Unified CallManager and operating system performance statistics on the selected node. The statistics that are collected include comprehensive information that can be used for system diagnosis and information from a set of counters that is not a part of the current set of preconfigured counters in the Real-Time Monitoring Tool. Because an extensive amount of information is collected in a short time, Cisco recommends that you do not enable the troubleshooting perfmon data logging for any extended time and that you enable the Log Partitioning Monitor to monitor disk usage while troubleshooting perfmon data logging is enabled. When you enable the troubleshooting perfmon data logging feature on a system with no active phone calls and you use the default setting for the troubleshooting perfmon data-logging parameters, Cisco estimates that the system experiences a less than 5-percent increase in CPU utilization and an insignificant increase in the amount of memory that is being used, and it writes approximately 50 MB of information to the log files daily. You can perform the following administrative tasks with the troubleshooting perfmon data-logging feature: •Enable and disable the trace filter for Troubleshooting perfmon data logging.   •Monitor a set of predefined System and Cisco Unified CallManager performance objects and counters on each server.   •Log the monitored performance data in CSV file format on the local server in the active log partition in the var/log/active/cm/log/ris/csv directory. The log file uses the following naming convention: PerfMon_<node>_<month>_<day>_<year>_<hour>_<minute>.csv; for example, PerfMon_172.19.240.80_06_15_2005_11_25.csv.   •Specify the polling rate. This rate specifies the rate at which performance data gets gathered and logged. You can configure the polling rate down to 5 seconds. Default polling rate equals 15 seconds.   •Specify the maximum number of log files that will be stored on disk. Log files exceeding this limit get purged automatically by removal of the oldest log file. The default specifies 50 files.   •Specify the rollover criteria of the log file based on the maximum size of the file in megabytes. The default value specifies 2 MB.   •Collect the SOAP log file by using the Trace & Log Central feature of the Real-Time Monitoring Tool or Command Line Interface.   •Collect the Cisco RIS Data Collector PerfMonLog log file by using the Trace & Log Central feature of the Real-Time Monitoring Tool or Command Line Interface.   •View the log file in graphical format by using the Microsoft Windows performance tool as described in "Viewing the Perfmon Log Files with the Microsoft Performance Tool" section or by using the Real-Time Monitoring Tool as described in the Cisco Unified CallManager Serviceability Administration Guide. The troubleshooting perfmon data-logging feature collects information from the following counters within the following perfmon objects. Refer to the "Performance Objects and Counters" chapter in Cisco Unified CallManager Serviceability System Guide for a description on the counters: •Cisco CallManager Object:   –CallManagerHeartBeat   –CallsActive   –CallsAttempted   –CallsCompleted   –InitializationState   –RegisteredHardwarePhones   –RegisteredMGCPGateway   •Cisco CallManager System Performance Object:   –AverageExpectedDelay   –CallsRejectedDueToThrottling   –QueueSignalsPresent 1-High   –QueueSignalsPresent 2-Normal   –QueueSignalsPresent 3-Low   –QueueSignalsPresent 4-Lowest   –QueueSignalsProcessed 1-High   –QueueSignalsProcessed 2-Normal   –QueueSignalsProcessed 3-Low   –QueueSignalsProcessed 4-Lowest   –QueueSignalsProcessed Total   –TotalCodeYellowEntry   •Cisco TFTP   –BuildAbortCount   –BuildCount   –BuildDeviceCount   –BuildDialruleCount   –BuildDuration   –BuildSignCount   –BuildSoftkeyCount   –BuildUnitCount   –ChangeNotifications   –DeviceChangeNotifications   –DialruleChangeNotifications   –EncryptCount   –GKFoundCount   –GKNotFoundCount   –HeartBeat   –HttpConnectRequests   –HttpRequests   –HttpRequestsAborted   –HttpRequestsNotFound   –HttpRequestsOverflow   –HttpRequestsProcessed   –HttpServedFromDisk   –LDFoundCount   –LDNotFoundCount   –MaxServingCount   –Requests   –RequestsAborted   –RequestsInProgress   –RequestsNotFound   –RequestsOverflow   –RequestsProcessed   –SegmentsAcknowledged   –SegmentsFromDisk   –SegmentsSent   –SEPFoundCount   –SEPNotFoundCount   –SIPFoundCount   –SIPNotFoundCount   –SoftkeyChangeNotifications   –UnitChangeNotifications   •Process Object:   –PID   –STime   –% CPU Time   –Page Fault Count   –Process Status   –VmData   –VmRSS   –VmSize   –Thread Count   •Memory Object:   –Used Kbytes   –Free Kbytes   –Total Kbytes   –Shared Kbytes   –Buffers Kbytes   –Cached Kbytes   –Free Swap Kbytes   –Total Swap Kbytes   –Used Swap Kbytes   –Pages Input   –Pages Output   –Pages   –Used VM Kbytes   –Total VM Kbytes   –% Page Usage   –% VM Used   –% Mem Used   •Processor Object:   –Irq Percentage   –Softirq Percentage   –IOwait Percentage   –User Percentage   –Nice Percentage   –System Percentage   –Idle Percentage   –%CPU Time   •Thread Object—Troubleshooting Perfmon Data Logger only logs CCM threads:   –%CPU Time   •Partition Object:   –Used Mbytes   –Total Mbytes   –%Used   –Await Read Time   –Await Write Time   –Await Time   –% CPU Time   –Read Bytes Per Sec   –Write Bytes Per Sec   –Queue Length   •IP Object:   –In Receives   –InHdrErrors   –In UnknownProtos   –In Discards   –In Delivers   –Out Requests   –Out Discards   –Reasm Reqds   –Reasm Oks   –Reasm Fails   –Frag OKs   –Frag Fails   –Frag Creates   –InOut Requests   •TCP Object:   –Active Opens   –Passive Opens   –Attempt Fails   –Estab Resets   –Curr Estab   –In Segs   –Out Segs   –Retrans Segs   –InOut Segs   •Network Interface Object:   –Rx Bytes   –Rx Packets   –Rx Errors   –Rx Dropped   –Rx Multicast   –Tx Bytes   –Tx Packets   –Tx Errors   –Tx Dropped   –Total Bytes   –Total Packets   –Tx QueueLen   •System Object:   –Allocated FDs   –Freed FDs   –Being Used FDs   –Max FDs   –Total Processes   –Total Threads   –Total CPU Time The following procedure provides the steps for using the troubleshooting perfmon data- logging feature. Procedure Step 1 Configure the Troubleshooting Perfmon Data Logging parameters in the Cisco RIS Data Collector service.   See the "Configuring Troubleshooting Perfmon Data Logging" section   Step 2 Verify that log partition monitoring is enabled.   See the Cisco Unified CallManager Administration Guide.   Step 3 Collect the log files for the Cisco RIS Data Collector service on the server that has troubleshooting perfmon data logging enabled   •If you want to download the log files by using RTMT, refer to Cisco Unified CallManager Serviceability Administration Guide.   •If you want to download the log files by using the CLI, refer to Cisco Unified Communications Operating System Administration Guide.   Step 4 View the log file in graphical format by using the Microsoft Windows performance tool as described in "Viewing the Perfmon Log Files with the Microsoft Performance Tool" section or by using the Real-Time Monitoring Tool as described in the Cisco Unified CallManager Serviceability Administration Guide.   Step 5 When you have collected all the necessary files, disable troubleshooting perfmon data logging by setting the Enable Logging parameter to False.     Configuring Troubleshooting Perfmon Data Logging The following procedure describes how to configure the troubleshooting perfmon data-logging feature. Procedure Step 1 In Cisco Unified CallManager Administration, choose System > Service Parameters.   The Service Parameter Configuration window displays.   Step 2 From the Server drop-down list box, choose the server.   Step 3 From the Service drop-down list box, choose Cisco RIS Data Collector.   Step 4 Enter the appropriate settings as described in Table 2-4.   Step 5 Click Save.     Troubleshooting Perfmon Data-Logging Configuration Settings Table 2-4 describes the available settings to enable and disable troubleshooting perfmon data logging. Table 2-4 Troubleshooting Perfmon Data-Logging Parameters     Viewing the Perfmon Log Files with the Microsoft Performance Tool To view the log files by using the Microsoft Performance tool, follow these steps: Procedure Step 1 Choose Start > Settings > Control Panel > Administrative Tools > Performance.   Step 2 In the application window, click the right mouse button and choose Properties.   Step 3 Click the Source tab in the System Monitor Properties dialog box.   Step 4 Browse to the directory where you downloaded the perfmon log file and choose the perfmon csv file. The log file includes the following naming convention: PerfMon_<node>_<month>_<day>_<year>_<hour>_<minute>.csv; for example, PerfMon_172.19.240.80_06_15_2005_11_25.csv.   Step 5 Click Apply.   Step 6 Click the Time Range button. To specify the time range in the perfmon log file that you want to view, drag the bar to the appropriate starting and ending times.   Step 7 To open the Add Counters dialog box, click the Data tab and click Add.   Step 8 From the Performance Object drop-down box, choose the perfmon object. If an object has multiple instances, you may choose All instances or select only the instances that you are interested in viewing.   Step 9 You can choose All Counters or select only the counters that you are interested in viewing.   Step 10 To add the selected counters, click Add   Step 11 When you finish selecting counters, click Close.     Common Troubleshooting Tasks, Tools, and Commands This section provides a quick reference for commands and utilities to help you troubleshoot a Cisco Unified CallManager server with root access disabled. Table 2-5 provides a summary of the CLI commands and GUI selections that you can use to gather information troubleshoot various system problems. Table 2-5 Summary of CLI Commands and GUI Selections INSERT TABLE Table 2-6 provides a list of common problems and tools to use to troubleshoot them. Table 2-6 Troubleshooting Common Problems with CLI Commands and GUI Selections INSERT TABLE   Troubleshooting Tips The following tips may help you when you are troubleshooting the Cisco Unified CallManager. TIP: Check the release notes for Cisco Unified CallManager for known problems. The release notes provide descriptions and workaround solutions for known problems. TIP: Know where your devices are registered. Each Cisco Unified CallManager log traces files locally. If a phone or gateway is registered to a particular Cisco Unified CallManager, the call processing gets done on that Cisco Unified CallManager if the call is initiated there. You will need to capture traces on that Cisco Unified CallManager to debug a problem. A common mistake involves having devices that are registered on a subscriber server but are capturing traces on the publisher server. These trace files will be nearly empty (and definitely will not have the call in them). Another common problem involves having Device 1 registered to CM1 and Device 2 registered to CM2. If Device 1 calls Device 2, the call trace occurs in CM1, and, if Device 2 calls Device 1, the trace occurs in CM2. If you are troubleshooting a two-way calling issue, you need both traces from both Cisco Unified CallManagers to obtain all the information that is needed to troubleshoot. TIP: Know the approximate time of the problem. Multiple calls may have occurred, so knowing the approximate time of the call helps TAC quickly locate the trouble. You can obtain phone statistics on a Cisco Unified IP Phone 79xx by pressing the i or ? button twice during an active call. When you are running a test to reproduce the issue and produce information, know the following data that is crucial to understanding the issue: •Calling number/called number   •Any other number that is involved in the specific scenario   •Time of the call NOTE: Remember that time synchronization of all equipment is important for troubleshooting. If you are reproducing a problem, make sure to choose the file for the timeframe by looking at the modification date and the time stamps in the file. The best way to collect the right trace means that you reproduce a problem and then quickly locate the most recent file and copy it from the Cisco Unified CallManager server. TIP: Save the log files to prevent them from being overwritten. Files will get overwritten after some time. The only way to know which file is being logged to is to choose View >Refresh on the menu bar and look at the dates and times on the files.   Verify Cisco Unified CallManager Services Are Running Use the following procedure to verify which Cisco CallManager services are active on a server. Procedure Step 1 From Cisco Unified CallManager Administration, choose Navigation > Cisco Unified CallManager Serviceability.   Step 2 Choose Tools > Service Activation.   Step 3 From the Servers column, choose the desired server.   The server that you choose displays next to the Current Server title, and a series of boxes with configured services displays.   Activation Status column displays either Activated or Deactivated in the Cisco CallManager line.   If the Activated status displays, the specified Cisco CallManager service remains active on the chosen server.   If the Deactivated status displays, continue with the following steps.   Step 4 Check the check box for the desired Cisco CallManager service.   Step 5 Click the Update button.   The Activation Status column displays Activated in the specified Cisco CallManager service line.   The specified service now shows active for the chosen server. Perform the following procedure if the Cisco CallManager service has been in activated and you want to verify if the service is currently running. Procedure Step 1 From Cisco Unified CallManager Administration, choose Navigation > Cisco Unified CallManager Serviceability.   The Cisco Unified CallManager Serviceability window displays.   Step 2 Choose Tools > Control Center - Feature Services.   Step 3 From the Servers column, choose the server.   The server that you chose displays next to the Current Server title, and a box with configured services displays.   The Status column displays which services are running for the chosen server.   Cisco Unified CallManager System Issues This section covers solutions for the following most common issues that relates to a Cisco Unified CallManager system.   • Cisco Unified CallManager System Not Responding • Replication Fails Between the Publisher and the Subscriber • Slow Server Response • JTAPI Subsystem Startup Problems • Security Issues     Cisco Unified CallManager System Not Responding This section covers the following issues for a Cisco Unified CallManager system that is not responding:   • Cisco Unified CallManager System Stops Responding • Cisco Unified CallManager Administration Does Not Display • Error When Attempting to Access Cisco Unified CallManager Administration • Error When Attempting to Access Cisco Unified CallManager Administration on a Subsequent Node • You Are Not Authorized to View • Problems Displaying or Adding Users with Cisco Unified CallManager • Name to Address Resolution Failing • Port 80 Blocked Between Your Browser and the Cisco Unified CallManager Server • Improper Network Setting Exists in the Remote Machine • Slow Server Response     Cisco Unified CallManager System Stops Responding Symptom The Cisco Unified CallManager system does not respond.   When the Cisco CallManager service crashes, the following message displays in the System Event log: The Cisco CallManager service terminated unexpectedly.  It has done this 1 time. The following corrective action  will be taken in 60000 ms. Restart the service. Other messages you may see in the event of a crash follow: Timeout 3000 milliseconds waiting for Cisco CallManager service to connect. The Cisco CallManager failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. At this time, when devices such as the Cisco Unified IP Phones and gateways unregister from the Cisco Unified CallManager, users receive delayed dial tone, and/or the Cisco Unified CallManager server freezes due to high CPU usage. For event log messages that are not included here, view the Cisco Unified CallManager Event Logs. Possible Cause The Cisco CallManager service can crash because the service does not have enough resources such as CPU or memory to function. Generally, the CPU utilization in the server is 100 percent at that time.   Recommended Action Depending on what type of crash you experience, you will need to gather different data that will help determine the root cause of the crash. Use the following procedure if a lack of resources crash occurs. Procedure Step 1 Collect Cisco CallManager traces 15 minutes before and after the crash.   Step 2 Collect SDL traces 15 minutes before and after the crash.   Step 3 Collect perfmon traces if available.   Step 4 If the traces are not available, start collecting the perfmon traces and track memory and CPU usage for each process that is running on the server. These will help in the event of another lack of resources crash.     Cisco Unified CallManager Administration Does Not Display Symptom Cisco Unified CallManager Administration does not display.   Possible Cause The Cisco CallManager service stopped.   Recommended Action Verify that the Cisco CallManager service is active and running on the server, as described in "Verify Cisco Unified CallManager Services Are Running" section on page 2-21 or in the Cisco Unified CallManager Serviceability Administration Guide.   Error When Attempting to Access Cisco Unified CallManager Administration Symptom One of the following messages displays when you are trying to access Cisco Unified CallManager Administration. •Internet Explorer—The page cannot be displayed. •Netscape—Warning box displays: There was no response. The server could be down or is not responding.   Possible Cause The services did not start automatically as expected. One of the services stopping represents the most frequent reason for Cisco Unified CallManager Administration not displaying.   Recommended Action Try starting the other services.     Error When Attempting to Access Cisco Unified CallManager Administration on a Subsequent Node Symptom One of the following error messages displays when you are trying to access the Cisco Unified CallManager Administration.   Possible Cause If the IP address of the first Cisco Unified CallManager node gets changed while a subsequent node is offline, you may not be able to log in to Cisco Unified CallManager Administration on the subsequent node.   Recommended Action If this occurs, follow the procedure for changing the IP address on a subsequent Cisco Unified CallManager node in the Cisco Unified Communications Operating System Administration Guide.     You Are Not Authorized to View Symptom When accessing the Cisco Unified CallManager Administration, one of the following messages displays.   •You Are Not Authorized to View This Page   •You do not have permission to view this directory or page using the credentials you supplied.   •Server Application Error. The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detailed information. Please contact the server administrator for assistance.   •Error: Access is Denied.   Possible Cause Unknown   Recommended Action Contact TAC for further assistance.     Problems Displaying or Adding Users with Cisco Unified CallManager Symptom You cannot add a user or conduct a search in Cisco Unified CallManager Administration.   Possible Cause You may encounter the following problems if you are working with Cisco Unified CallManager that is installed on a server that has a special character (such as an underscore) in its hostname or Microsoft Internet Explorer 5.5 with SP2 and a Q313675 patch or above. •When you conduct a basic search and hit submit, the same page redisplays. •When you try to insert a new user, the following message displays. The following error occurred while trying to execute the command. Sorry, your session object has timed out. Click here to Begin a New Search   Recommended Action You may not be able to add a user or do a search on Cisco Unified CallManager Administration, if your Cisco Unified CallManager hostname contains any special characters such as underscore or period (for example, Call_Manager). Domain Name System (DNS)-supported characters include all letters (A-Z, a-z), numbers (0-9), and hyphen (-); any special characters are not allowed. If the Q313675 patch is installed on your browser, make sure that the URL does not contain any non-DNS supported characters. For more information about the Q313675 patch, refer to MS01-058: File Vulnerability Patch for Internet Explorer 5.5 and Internet Explorer 6.   To resolve this problem, you have the following options: •Access Cisco Unified CallManager Administration by using the IP address of the server. •Do not use non-DNS characters in the Server Name. •Use the localhost or IP address in the URL.     Name to Address Resolution Failing Symptom One of the following messages displays when you try to access the following URL:   http://your-cm-server-name/ccmadmin   •Internet Explorer—This page cannot be displayed   •Netscape—Not Found. The requested URL /ccmadmin was not found on this server. If you try to access the same URL by using the Cisco CallManager IP address ( http://10.48.23.2/ccmadmin ) instead of the name, the window displays. Possible Cause The name that you entered as "your-cm-server-name" maps to the wrong IP address in DNS or hosts file.   Recommended Action If you have configured the use of DNS, check in the DNS to see whether the entry for the your-cm-server-name has the correct IP address of the Cisco Unified CallManager server. If it is not correct, change it. If you are not using DNS, your local machine will check in the "hosts" file to see whether an entry exists for the your-cm-server-name and an IP address that is associated to it. Open the file and add the Cisco Unified CallManager server name and the IP address. You can find the "hosts" file at C:\WINNT\system32\drivers\etc\hosts.     Port 80 Blocked Between Your Browser and the Cisco Unified CallManager Server Symptom One of the following messages displays when a firewall blocks the port that is used by the web server or the http traffic:   •Internet Explorer—This page cannot be displayed   •Netscape—There was no response. The server could be down or is not responding   Possible Cause For security reasons, the system blocked the http access from your local network to the server network.   Recommended Action   1. Verify whether other types of traffic to the Cisco Unified CallManager server, such as ping or Telnet, are allowed. If any are successful, it will show that http access to the Cisco Unified CallManager web server has been blocked from your remote network.   2. Check the security policies with your network administrator.   3. Try again from the same network where the server is located.     Improper Network Setting Exists in the Remote Machine Symptom No connectivity exists, or no connectivity exists to other devices in the same network as the Cisco Unified CallManager.   When you attempt the same action from other remote machines, Cisco Unified CallManager Administration displays.   Possible Cause Improper network configuration settings on a station or on the default gateway can cause a web page not to display because partial or no connectivity to that network exists.   Recommended Action   1. Try pinging the IP address of the Cisco Unified CallManager server and other devices to confirm that you cannot connect.   2. If the connectivity to any other device out of your local network is failing, check the network setting on your station, as well as the cable and connector integrity. Refer to the appropriate hardware documentation for detailed information.   If you are using TCP-IP over a LAN to connect, continue with the following steps to verify the network settings on the remote station.   3. Choose Start > Setting > Network and Dial-up connections.   4. Choose Local Area Connection, then Properties.   The list of communication protocols displays as checked.   5. Choose Internet Protocol (TCP-IP) and click Properties again.   6. Depending on your network, choose either Obtain an ip address automatically or set manually your address, mask and default Gateway.   The possibility exists that a browser-specific setting could be improperly configured.   7. Choose the Internet Explorer browser Tools > Internet Options.   8. Choose the Connections tab and then verify the LAN settings or the dial-up settings.   By default, the LAN settings and the dial-up settings do not get configured. The generic network setting from Windows gets used.   9. If the connectivity is failing only to the Cisco Unified CallManager network, a routing issue probably exists in the network. Contact the network administrator to verify the routing that is configured in your default gateway. NOTE: If you cannot browse from the remote server after following this procedure, contact TAC to have the issue investigated in more detail.     Replication Fails Between the Publisher and the Subscriber Replicating the database is a core function of Cisco Communications Manager clusters. The server with the master copy of the database is called the publisher, while the servers replicating the database are called subscribers. Symptom Changes made on the publisher are not reflected on phones that are registered with the subscriber.   Possible Cause Replication fails between the publisher and subscriber.   Recommended Action Complete the following steps to reestablish the relationship between the two systems.   1. Verify the Replication.   a. Open Cisco Unified Communications Manager Real-Time Monitoring Too (RTMT).   b. Choose System > Performance > Open Peformance Monitoring.   c. Double-click the publisher node to expand the performance monitors.   d. Double-click Replication Counters.   e. Double-click Number of Replicates Created.   f. Choose ReplicateCount from the Object Instances dialog box and click Add.   g. Double-click Replication Status.   h. Choose ReplicateCount from the Object Instances dialog box and click Add. NOTE: Right click the counter name and choose Counter Description to view the definition of the counter. 2. Check State of Replication via CLI.   a. Access the platform CLI and use the following command to check repliaction:   utils dbreplication status file view activelog <filename_output_above>   b. Review the Summary information and counts for each node to verify replication.   3. To repair replication, use the following procedure:   a. Access the platform CLI.   b. Repair replication by using the following command: utils dbreplication repair usage:utils dbreplicatoin repair [nodename]|all   Slow Server Response This section addresses a problem that relates to a slow response from the server due to mismatched duplex port settings. Symptom Slow response from the server occurs.   Possible Cause   Slow response could result if the duplex setting of the switch does not match the duplex port setting on the Cisco Unified CallManager server.   Recommended Action   1. For optimal performance, set both switch and server to 100/Full.   Cisco does not recommend using the Auto setting on either the switch or the server.   2. You must restart the Cisco Unified CallManager server for this change to take effect.     JTAPI Subsystem Startup Problems The JTAPI (Java Telephony API) subsystem represents a very important component of the Cisco Customer Response Solutions (CRS) platform. JTAPI communicates with the Cisco Unified CallManager and has responsibility for telephony call control. The CRS platform hosts telephony applications, such as Cisco Unified AutoAttendant, Cisco IP ICD, and Cisco Unified IP-IVR. Although this section is not specific to any of these applications, keep in mind that the JTAPI subsystem is an underlying component that all of them use. Before starting the troubleshooting process, ensure that the software versions that you are using are compatible. To verify compatibility, read the Cisco Unified CallManager Release Notes for the version of Cisco Unified CallManager that you are using. To check the version of CRS, log in to the AppAdmin page by typing http://servername/appadmin , where servername is the name of the server on which CRS is installed. The current version is located in the lower-right corner of the main menu.     JTAPI Subsystem is OUT_OF_SERVICE Symptom The JTAPI subsystem does not start. Possible Cause One of the following exceptions displays in the trace file:   • MIVR-SS_TEL-4-ModuleRunTimeFailure • MIVR-SS_TEL-1-ModuleRunTimeFailure   MIVR-SS_TEL-4-ModuleRunTimeFailure Search for the MIVR-SS_TEL-1-ModuleRunTimeFailure string in the trace file. At the end of the line, an exception reason appears.   The following list gives the most common errors:   • Unable to create provider—bad login or password • Unable to create provider—Connection refused • Unable to create provider—login= • Unable to create provider—hostname • Unable to create provider—Operation timed out • Unable to create provider—null Unable to create provider—bad login or password   Possible Cause Administrator entered an incorrect user name or password in the JTAPI configuration.   Full Text of Error Message   %MIVR-SS_TEL-4-ModuleRunTimeFailure:Real-time failure in JTAPI subsystem: Module=JTAPI Subsystem,Failure Cause=7,Failure Module=JTAPI_PROVIDER_INIT, Exception=com.cisco.jtapi.PlatformExceptionImpl: Unable to create provider -- bad login or password. %MIVR-SS_TEL-7- EXCEPTION:com.cisco.jtapi.PlatformExceptionImpl: Unable to create provider -- bad login or password. Recommended Action Verify that the user name and password are correct. Try logging into the Unified CMuser page ( http://servername/ccmuser ) on the Cisco Unified CallManager to ensure that the Cisco Unified CallManager cannot authenticate correctly.   Unable to create provider—Connection refused   Possible Cause The Cisco Unified CallManager refused the JTAPI connection to the Cisco Unified CallManager.   Full Text of Error Message   %MIVR-SS_TEL-4-ModuleRunTimeFailure:Real-time failure in JTAPI subsystem: Module=JTAPI Subsystem, Failure Cause=7,Failure Module=JTAPI_PROVIDER_INIT, Exception=com.cisco.jtapi.PlatformExceptionImpl: Unable to create provider -- Connection refused %MIVR-SS_TEL-7-EXCEPTION:com.cisco.jtapi.PlatformExceptionImpl: Unable to create provider -- Connection refused Recommended Action Verify that the CTI Manager service is running in the Cisco Unified CallManager Control Center. Unable to create provider—login=  Possible Cause Nothing has been configured in the JTAPI configuration window. Full Text of Error Message %MIVR-SS_TEL-4-ModuleRunTimeFailure:Real-time failure in JTAPI subsystem: Module=JTAPI Subsystem, Failure Cause=7,Failure Module=JTAPI_PROVIDER_INIT, Exception=com.cisco.jtapi.PlatformExceptionImpl: Unable to create provider -- login= %MIVR-SS_TEL-7-EXCEPTION:com.cisco.jtapi.PlatformExceptionImpl: Unable to create provider -- login= Recommended Action Configure a JTAPI provider in the JTAPI configuration window on the CRS server.   Unable to create provider—hostname   Possible Cause The CRS engine cannot resolve the host name of the Cisco Unified CallManager.   Full Text of Error Message %M%MIVR-SS_TEL-4-ModuleRunTimeFailure:Real-time failure in JTAPI subsystem: Module=JTAPI Subsystem, Failure Cause=7,Failure Module=JTAPI_PROVIDER_INIT, Exception=com.cisco.jtapi.PlatformExceptionImpl: Unable to create provider -- dgrant-mcs7835.cisco.com %MIVR-SS_TEL-7-EXCEPTION:com.cisco.jtapi.PlatformExceptionImpl: Unable to create provider -- dgrant-mcs7835.cisco.com Recommended Action Verify that DNS resolution is working correctly from the CRS engine. Try using an IP address instead of the DNS name. Unable to create provider—Operation timed out   Possible Cause The CRS engine does not have IP connectivity with the Cisco Unified CallManager.   Full Text of Error Message 101: Mar 24 11:37:42.153 PST %MIVR-SS_TEL-4-ModuleRunTimeFailure:Real-time failure in JTAPI subsystem: Module=JTAPI Subsystem, Failure Cause=7,Failure Module=JTAPI_PROVIDER_INIT, Exception=com.cisco.jtapi.PlatformExceptionImpl: Unable to create provider -- Operation timed out 102: Mar 24 11:37:42.168 PST %MIVR-SS_TEL-7-EXCEPTION: com.cisco.jtapi.PlatformExceptionImpl: Unable to create provider -- Operation timed out   Recommended Action Check the IP address that is configured for the JTAPI provider on the CRS server. Check the default gateway configuration on the CRS server and the Cisco Unified CallManager. Make sure no IP routing problems exist. Test connectivity by pinging the Cisco Unified CallManager from the CRS server. Unable to create provider—null Possible Cause No JTAPI provider IP address or host name get configured, or the JTAPI client is not using the correct version.   Full Text of Error Message   %MIVR-SS_TEL-4-ModuleRunTimeFailure:Real-time failure in JTAPI subsystem: Module=JTAPI Subsystem, Failure Cause=7,Failure Module=JTAPI_PROVIDER_INIT, Exception=com.cisco.jtapi.PlatformExceptionImpl: Unable to create provider -- null Recommended Action   Verify that a host name or IP address is configured in the JTAPI configuration. If the JTAPI version is incorrect, download the JTAPI client from the Cisco Unified CallManager Plugins window and install it on the CRS server.   MIVR-SS_TEL-1-ModuleRunTime   Failure  Symptom This exception usually occurs when the JTAPI subsystem is unable to initialize any ports. Possible Cause The CRS server can communicate with the Cisco Unified CallManager, but is unable to initialize any CTI ports or CTI route points through JTAPI. This error occurs if the CTI ports and CTI route points are not associated with the JTAPI user.   Full Text of Error Message   255: Mar 23 10:05:35.271 PST %MIVR-SS_TEL-1-ModuleRunTimeFailure: Real-time failure in JTAPI subsystem: Module=JTAPI Subsystem, Failure Cause=7,Failure Module=JTAPI_SS,Exception=null Recommended Action   Check the JTAPI user on the Cisco Unified CallManager and verify that CTI ports and CTI route points that are configured on the CRS server associate with the user.     JTAPI Subsystem is in PARTIAL_SERVICE Symptom The following exception displays in the trace file:   MIVR-SS_TEL-3-UNABLE_REGISTER_CTIPORT   Possible Cause The JTAPI subsystem cannot initialize one or more CTI ports or route points. Full Text of Error Message   1683: Mar 24 11:27:51.716 PST %MIVR-SS_TEL-3-UNABLE_REGISTER_CTIPORT: Unable to register CTI Port: CTI Port=4503, Exception=com.cisco.jtapi.InvalidArgumentExceptionImpl: Address 4503 is not in provider's domain. 1684: Mar 24 11:27:51.716 PST %MIVR-SS_TEL-7-EXCEPTION: com.cisco.jtapi.InvalidArgumentExceptionImpl: Address 4503 is not in provider's domain.   Recommended Action   The message in the trace tells you which CTI port or route point cannot be initialized. Verify that this device exists in the Cisco Unified CallManager configuration and also associates with the JTAPI user on the Cisco Unified CallManager.   Security Issues This section provides information about security-related measurements and general guidelines for troubleshooting security-related problems. This section contains information on the following topics:   • Security Alarms • Security Performance Monitor Counters • Reviewing Security Log and Trace Files • Troubleshooting Certificates • Troubleshooting CTL Security Tokens • Troubleshooting CAPF • Troubleshooting Encryption for Phones and Cisco IOS MGCP Gateways   NOTE: This section does not describe how to reset the Cisco Unified IP Phone if it has been corrupted by bad loads, security bugs, and so on. For information on resetting the phone, refer to the Cisco Unified IP Phone Administration Guide for Cisco Unified CallManager that matches the model of the phone.   For information about how to delete the CTL file from Cisco Unified IP Phone models 7970, 7960, and 7940 only, see the Cisco Unified CallManager Security Guide or the Cisco Unified IP Phone Administration Guide for Cisco Unified CallManager that matches the model of the phone.     Security Alarms Cisco Unified CallManager Serviceability generates security-related alarms for X.509 name mismatches, authentication errors, and encryption errors. The Serviceability GUI provides the alarm definitions.   Alarms may get generated on the phone for TFTP server and CTL file errors. For alarms that get generated on the phone, refer to the Cisco Unified IP Phone Administration Guide for Cisco Unified CallManager for your phone model and type (SCCP or SIP).     Security Performance Monitor Counters Performance monitor counters monitor the number of authenticated phones that register with Cisco Unified CallManager, the number of authenticated calls that are completed, and the number of authenticated calls that are active at any time. Table 3-1 lists the performance counters that apply to security features. Table 3-1 Security Performance Counters ... View more

CA Description Trusted third party that issues digital certificates containing a digital signature that identifies the parties involved and a public key (especially X.509 certificates) and vouches for the validity of the data and identities within the certificate. This is used concerning security and Private Key Infrastructure (PKI) schemes. Complete Definition A complete definition can be found here. ... View more

    Introduction   Cisco Unified CallManager serves as the software-based call-processing component of the Cisco Unified Communications family of products. A wide range of Cisco Media Convergence Servers provides high-availability server platforms for Cisco Unified CallManager call processing, services, and applications.   The Cisco Unified CallManager system extends enterprise telephony features and functions to packet telephony network devices such as IP phones, media processing devices, voice-over-IP (VoIP) gateways, and multimedia applications. Additional data, voice, and video services, such as unified messaging, multimedia conferencing, collaborative contact centers, and interactive multimedia response systems, interact through Cisco Unified CallManager open telephony application programming interface (API).   Cisco Unified CallManager provides signaling and call control services to Cisco integrated telephony applications as well as third-party applications. Cisco Unified CallManager performs the following primary functions: • Call processing   • Signaling and device control   • Dial plan administration   • Phone feature administration   • Directory services   • Operations, administration, maintenance, and provisioning (OAM&P)   • Programming interface to external voice-processing applications such as Cisco IP Communicator, Cisco Unified IP Interactive Voice Response (IP IVR), and Cisco Unified CallManager Attendant Console   Key Features and Benefits The Cisco Unified CallManager system includes a suite of integrated voice applications that perform voice-conferencing and manual attendant console functions. This suite of voice applications means that no need exists for special-purpose voice-processing hardware. Supplementary and enhanced services such as hold, transfer, forward, conference, multiple line appearances, automatic route selection, speed dial, last-number redial, and other features extend to IP phones and gateways. Because Cisco Unified CallManager is a software application, enhancing its capabilities in production environments requires only upgrading software on the server platform, thereby avoiding expensive hardware upgrade costs.   Distribution of Cisco Unified CallManager and all Cisco Unified IP Phones, gateways, and applications across an IP network provides a distributed, virtual telephony network. This architecture improves system availability and scalability. Call admission control ensures that voice quality of service (QoS) is maintained across constricted WAN link and automatically diverts calls to alternate public switched telephone network (PSTN) routes when WAN bandwidth is not available.   A web-browsable interface to the configuration database provides the capability for remote device and system configuration. This interface also provides access to HTML-based online help for users and administrators.   Cisco Unified CallManager release 5.1, designed to work like an appliance, refers to the following functions: •Cisco Unified CallManager servers can get preinstalled with software to ease customer and partner deployment and automatically search for updates and notify administrators when key security fixes and software upgrades are available for their system.This process comprises Electronic Software Upgrade Notification.   • You can upgrade Cisco Unified CallManager servers while they continue to process calls, so upgrades take place with minimal downtime.   • Cisco Unified CallManager supports the Asian and Middle Eastern markets by providing support for Unicode on higher resolution phone displays.   • Cisco Unified CallManager provides Fault, Configuration, Accounting, Performance, and Security (FCAPS).   Browsing to Cisco Unified CallManager Administration You access the Cisco Unified CallManager Administration program from a PC that is not the web server or has Cisco Unified CallManager installed. No browser software exists on the server. See the "Web Browsers" section for more information on browsing to the server.   Web Browsers Cisco Unified CallManager Administration supports the following Microsoft Windows operating system browsers:   • Microsoft Internet Explorer (IE) 6.0   • Netscape 7.1   From any user PC in your network, browse into a server that is running Cisco Unified CallManager Administration and log in with administrative privileges.Note: Simultaneous logon to Cisco Unified CallManager Administration by a large number of users can cause performance to suffer. Try to limit the number of users and administrators that are logged on simultaneously. Note: Cisco Unified CallManager Administration does not support the buttons in your browser. Do not use the browser buttons (for example, the Back button) when you perform configuration tasks. Cisco Unified CallManager Administration Logon Use the following procedure to log on to Cisco Unified CallManager Administration.   Procedure Step 1 Start your preferred operating system browser. Step 2 In the address bar of the web browser, enter the following case-sensitive URL: https://<Unified CM-server-name>:{8443}/ccmadmin/showHome.do where: <Unified CM-server-name> equals the name or IP address of the server Note: You can optionally specify a port number. Step 3 A Security Alert dialog box displays. Click the appropriate button. Step 4 At the Logon window, enter the application user password that you specified during Cisco Unified CallManager installation and click Submit. The Cisco Unified CallManager Administration window displays (see Figure 1-1).   Note: For security purposes, Cisco Unified CallManager Administration logs you out after 30 minutes, and you must log back in.   Cisco Unified CallManager Administration Log Off Use the following procedure to log off Cisco Unified CallManager Administration.   Procedure Step 1 From the main Cisco Unified CallManager Administration window, click the Log Off button that is in the upper, right corner (see Figure 1-1). Step 2 The Logon window displays. Hypertext Transfer Protocol Over Secure Sockets Layer (HTTPS) Hypertext Transfer Protocol over Secure Sockets Layer (SSL), which secures communication between the browser client and the web server (for Microsoft Windows users), uses a certificate and a public key to encrypt the data that is transferred over the internet. HTTPS also ensures that the user login password transports securely via the web. The following Cisco Unified CallManager applications support HTTPS, which ensures the identity of the server: Cisco Unified CallManager Administration, Cisco Unified CallManager Serviceability, the Cisco Unified CallManager User Options, Trace Collection Tool, the Real-Time Monitoring Tool (RTMT), and the XML (AXL) application programming interface. A self-signed certificate gets generated on the web server at installation (the certificate also gets migrated during upgrades). Note: If you access the web application by using the hostname and install the certificate in the trusted folder and then try to access the application by using the localhost or IP address, the Security Alert dialog box displays to indicate that the name of the security certificate does not match the name of the site. If you use the localhost, the IP address, or the hostname in the URL to access the application that supports HTTPS, you must save the certificate in the trusted folder for each of type of URL (with the local host, IP address, and so on); otherwise, the Security Alert dialog box displays for each type. Using Internet Explorer and HTTPS with Cisco Unified CallManager Administration   The following section describes how to save the CA Root certificate in the trusted folder, so the Security Alert dialog box does not display each time that you access the web application. The first time that you (or a user) accesses Cisco Unified CallManager Administration or other Cisco Unified CallManager SSL-enabled virtual directories after the Cisco Unified CallManager 5.1 installation/upgrade from a browser client, a Security Alert dialog box asks whether you trust the server. When the dialog box displays, you must perform one of the following tasks: • By clicking Yes, you choose to trust the certificate for the current web session only. If you trust the certificate for the current session only, the Security Alert dialog box displays each time that you access the application; that is, until you install the certificate in the trusted folder. • By clicking View Certificate > Install Certificate, you indicate that you intend to perform certificate installation tasks, so you always trust the certificate. If you install the certificate in the trusted folder, the Security Alert dialog box does not display each time that you access the web application. • By clicking No, you cancel the action. No authentication occurs, and you cannot access the web application. To access the web application, you must click Yes or install the certificate via the View Certificate > Install Certificate option. For other tasks that you can perform in the Security Alert dialog box, refer to the Cisco Unified CallManager Security Guide. Procedure Step 1 Browse to the application on the web server. Step 2 When the Security Alert dialog box displays, click View Certificate. Step 3 In the Certificate pane, click Install Certificate. Step 4 Click Next. Step 5 Click the "Place all certificates in the following store" radio button; click Browse. Step 6 Browse to Trusted Root Certification Authorities. Step 7 Click Next. Step 8 Click Finish. Step 9 To install the certificate, click Yes. A message states that the import was successful. Click OK. Step 10 In the lower, right corner of the dialog box, click OK. Step 11 To trust the certificate, so you do not receive the dialog box again, click Yes. Note: If you use the localhost, the IP address, or the hostname in the URL to access the application that supports HTTPS, you must save the certificate in the trusted folder for each of type of URL (with the local host, IP address, and so on); otherwise, the Security Alert dialog box displays for each type. Using Netscape and HTTPS with Cisco Unified CallManager Administration When you use HTTPS with Netscape, you can view the certificate credentials, trust the certificate for one session, trust the certificate until it expires, or not trust the certificate at all. Tip: If you trust the certificate for one session only, you must repeat the following procedure each time that you access the HTTPS-supported application. If you do not trust the certificate, you cannot access the application. Perform the following procedure to save the certificate to the trusted folder:   Procedure Step 1 Browse to the application, for example, Cisco Unified CallManager Administration, by using Netscape. The certificate authority dialog box displays. Step 2 Click one of the following radio buttons: • Accept this certificate for this session • Do not accept this certificate and do not connect • Accept this certificate forever (until it expires) Note: If you choose Do not accept, the application does not display. Note: To view the certificate credentials before you continue, click Examine Certificate. Review the credentials, and click Close. Step 3 Click OK. The Security Warning dialog box displays. Step 4 Click OK. Navigating the Cisco Unified CallManager Administration Application After you log on, the main Cisco Unified CallManager Administration window displays. The window includes the drop-down list box in the upper, right corner called Navigation (see Figure 1-1). To access the applications in the drop-down list box, choose the program that you want and click Go. The choices in the drop-down list box include the following Cisco Unified CallManager applications: • Cisco Unified CallManager Administration—Shows the default when you access Cisco Unified CallManager. Use Cisco Unified CallManager Administration to configure system parameters, route plans, devices, and much more. • Cisco Unified CallManager Serviceability—Takes you to the main Cisco Unified CallManager Serviceability window that is used to configure trace files and alarms and to activate and deactivate services. • Disaster Recovery System—Takes you to the Cisco Disaster Recovery System, a program that provides full data backup and restore capabilities for all servers in a Cisco Unified CallManager cluster. • Platform Administration—Takes you to a logon window, so you can configure and administer the Cisco Unified CallManager platform. These applications include additional security, so you must enter a userid and password before you can access these programs. Accessibility Cisco Unified CallManager Administration and Cisco Unified CallManager User Options provide functionality for users that allows them to access buttons on the window without using a mouse. You can perform the following procedures from any point on the window, so the user does not have to scroll or tab through various fields.   Accessing the Icons in the Window Many of the windows in Cisco Unified CallManager and Cisco PCA have icons that display at the top of the window; for example, an icon of a disk for Save, an icon that is a plus sign (+) for Add, and so on. To access these icons, perform the following procedure. 1. Press Alt, press 1, then press Tab. The cursor will highlight the first icon from the left. To move to the next icon, press Tab again. 2. Press Enter. The system performs the function of the icon; for example, Add. Accessing the Buttons in the Window Many of the windows in Cisco Unified CallManager and Cisco PCA have buttons that display at the bottom of the window; for example, a button for Save, a button for Add, and so on. To access these buttons, perform the following procedure. 1. Press Alt, press 2, and then press Tab. The cursor will highlight the first button from the left. To move to the next button, press Tab again. 2. Press Enter. The function of the button gets performed; for example, Save. Where to Find More Information • Cisco Unified CallManager System Guide • Cisco Unified CallManager Features and Services Guide • Cisco Unified CallManager Serviceability System Guide • Cisco Unified CallManager Serviceability Administration Guide • Cisco CDR Analysis and Reporting Administration Guide • Cisco Unified Communications Solution Reference Network Design • Installing Cisco Unified CallManager Release 5.1(3) • Upgrading Cisco Unified CallManager Release 5.1(3) • Cisco Unified CallManager Security Guide • Cisco Unified Communications Operating System Administration Guide • Disaster Recovery System Administration Guide Server Configuration Use the server configuration to specify the address of the server where Cisco Unified CallManager is installed. If your network uses Domain Name System (DNS) services, you can specify the host name of the server. If your network does not use DNS services, you must specify the Internet Protocol (IP) address of the server. Note: You must update the DNS server with the appropriate Cisco Unified CallManager name and address information before using that information to configure the Cisco Unified CallManager server. Finding a Server Because you might have several servers in your network, Cisco Unified CallManager lets you locate specific servers on the basis of specific criteria. Use the following procedure to locate servers. Note: During your work in a browser session, your find/list search preferences are stored in the cookies on the client machine. If you navigate to other menu items and return to this menu item, or if you close the browser and then reopen a new browser window, your Cisco Unified CallManager search preferences are retained until you modify your search. Procedure Step 1 Choose System > Server. The Find and List Servers window displays. Use the two drop-down list boxes to search for a server. Step 2 From the first Find Servers window drop-down list box, choose one of the following criteria:                • Host Name/IP Address • Description               From the second Find Servers window drop-down list box, choose one of the following criteria: • begins with • contains • is exactly • ends with • is empty • is not empty Step 3 Specify the appropriate search text, if applicable, and click Find. Tip To find all servers that are registered in the database, click Find without entering any search text. A list of discovered servers displays by • Host Name/IP Address • Description From the Find and List Servers window, you can also specify how many items per page to display. Note You can delete multiple servers from the Find and List Servers window by checking the check boxes next to the appropriate servers and clicking Delete Selected. You can delete all servers in the window by checking the check box in the Matching records title bar and clicking Delete Selected. Also Before you delete a server, review the considerations in the "Deleting a Server" section. Step 4 From the list of records, click the Server name that matches your search criteria. The window displays the server that you choose. Configuring a Server This section describes how to add or update a server address to the Cisco Unified CallManager database.   Before You Begin The following guideline applies to adding a server: • Make sure that you only add each server once in the Server Configuration window. If you add a server using the host name and add the same server using the IP address, Cisco Unified CallManager cannot accurately determine component versions for the server after a Cisco Unified CallManager upgrade. If you have two entries in Cisco Unified CallManager Administration for the same server, delete one of the entries before you upgrade (see the "Deleting a Server" section). Procedure Step 1 Perform one of the following tasks: • To add a server, choose System > Server and click Add New. • To update a server, find the server by using the procedure in the "Finding a Server" section. The Server Configuration window displays. Step 2 Enter the appropriate settings as described in Table 2-1. Step 3 Click the Save icon that displays in the tool bar in the upper, left corner of the window (or click the Save button that displays at the bottom of the window) to save the data and to add the server to the database. Changes to the server configuration do not take effect until you restart Cisco Unified CallManager. For information about restarting the Cisco Unified CallManager service, refer to the Cisco Unified CallManager Serviceability Administration Guide. Note: When you perform a fresh installation of Cisco Unified CallManager, you must define any subsequent servers (nodes) in the Cisco Unified CallManager Administration Server Configuration window before you can install the Cisco Unified CallManager software on each subsequent server. To define a subsequent node, click Add New, as described in Step 1 above, and configure the server. After you add the subsequent server, you can then install the Cisco Unified CallManager software on that server. Deleting a Server This section describes how to delete a server from the Cisco Unified CallManager database. Before you delete the server, consider the following information: • In Cisco Unified CallManager Administration, you cannot delete the first node of the cluster, but you can delete subsequent nodes. • Cisco recommends that you do not delete any node that has Cisco Unified CallManager running on it, especially if the node has devices, such as phones, registered with it. • Although dependency records exist for the subsequent nodes, the records do not prevent you from deleting the node. To find out which Cisco Unified CallManagers are using the server, choose Dependency Records from the Related Links drop-down list box in the Server Configuration window and click Go. • If any call park numbers are configured for Cisco Unified CallManager on the node that is being deleted, the deletion fails. Before you can delete the node, you must delete the call park numbers in Cisco Unified CallManager Administration. • The system may automatically delete some devices, such as MOH servers, when you delete a server. • Before you delete a node, Cisco recommends that you deactivate the services that are active on the subsequent node. Performing this task ensures that the services work after you delete the node. • To delete a server and add it back to the cluster, see the "Deleting Then Adding Back a Server in Cisco Unified CallManager Administration" section. Procedure Step 1 To delete the server(s) from the Find and List Servers window, find the server by using the procedure in the "Finding a Server" section. The Find and List Servers window displays. Step 2 From the list of matching records, choose the server(s) that you want to delete. Step 3 Click the Delete Selected Item icon that displays in the tool bar in the upper, left corner of the window (or click the Delete Selected button that displays at the bottom of the window) to delete the server. Step 4 Cisco Unified CallManager Administration displays the following message: "You are about to permanently delete one or more servers. This action cannot be undone. Continue?". Click OK; the server gets deleted from the Cisco Unified CallManager database and is not available for use. Tip If the Server Configuration window is displaying for a specific server, you can click Delete to delete the server. Cisco Unified CallManager Administration displays the following message: "You are about to permanently delete this server. This action cannot be undone. Continue?". Click OK; the server gets deleted from the Cisco Unified CallManager database and is not available for use. Step 5 Reboot the servers in the cluster. Tip If you delete a subsequent server and then want to add it back to the cluster, see the "Deleting Then Adding Back a Server in Cisco Unified CallManager Administration" section. Deleting Then Adding Back a Server in Cisco Unified CallManager Administration Procedure Step 1 In Cisco Unified CallManager Administration, add the deleted server, as described in the "Configuring a Server" section. Step 2 After you add the subsequent node to Cisco Unified CallManager Administration, you must install Cisco Unified CallManager on the node by using the 5.X disk that was provided in your software kit. If you have a 5.1(3) disk, perform a 5.1(3) installation on the node. If you have a disk with a previous version of 5.X on it (for example, 5.0(1), 5.0(4), 5.1(1), 5.1(2), and so on), use the 5.X disk to install Cisco Unified CallManager on the subsequent node; during the installation, choose the Upgrade During Install option when the 5.X installation displays the options. Tip Make sure that the version that you install on the subsequent node matches the version that runs on the first node (publisher) in the cluster. For example, if the first node in the cluster runs 5.1(3) and a service release (or engineering special), you must choose the Upgrade During Install option when the 5.X installation displays the installation options; before you choose this option, ensure that you can access the service release (or engineering special) image on DVD or a remote server. For more information on how to perform an installation, refer to the document, Installing Cisco Unified Communications Manager 5.1(3). Step 3 After you install Cisco Unified Communications Manager, configure the subsequent node, as described in Installing Cisco Unified Communications Manager 5.1(3). Cisco Unified CallManager Configuration Use Cisco Unified CallManager configuration to specify the ports and other properties for each Cisco Unified CallManager that is installed in the same cluster. A cluster comprises a set of Cisco Unified CallManagers that enables redundancy.   For the first node in a Cisco Unified CallManager cluster, the server gets automatically added as part of the installation. To add additional Cisco Unified CallManagers to a cluster, the administrator must configure a server (by using Server Configuration) and then add the Cisco Unified CallManager (by using Cisco Unified CallManager Configuration). This procedure is repeated for each Cisco Unified CallManager that is in the cluster.   Use the following topics to find and update a Cisco Unified CallManager configuration or to view system component version information: • Finding a Cisco Unified CallManager • Updating a Cisco Unified CallManager • Cisco Unified CallManager Configuration Settings • Cisco CallManager Service Activation/Deactivation Finding a Cisco Unified CallManager Because you may have several Cisco Unified CallManagers in your network, Cisco Unified CallManager Administration lets you locate specific Cisco Unified CallManagers on the basis of specific criteria. Use the following procedure to locate Cisco Unified CallManagers. Note During your work in a browser session, your find/list search preferences are stored in the cookies on the client machine. If you navigate to other menu items and return to this menu item, or if you close the browser and then reopen a new browser window, the system retains your Cisco Unified CallManager search preferences until you modify your search. Procedure Step 1 Choose System > Cisco Unified CallManager. The Find and List Cisco Unified CallManagers window displays. Use the two drop-down list boxes to search for a Cisco Unified CallManager. Step 2 From the first Find Cisco Unified CallManagers window drop-down list box, choose one of the following criteria: • Name • Description From the second Find Cisco Unified CallManagers window drop-down list box, choose one of the following criteria: • begins with • contains • is exactly • ends with • is empty • is not empty Step 3 Specify the appropriate search text, if applicable, and click Find. Tip To find all Cisco Unified CallManagers that are registered in the database, click Find without entering any search text. A list of discovered Cisco Unified CallManagers displays by •Cisco Unified CallManager name •Description From the Find and List Cisco Unified CallManagers window, you can also specify how many rows per page to display. Step 4 From the list of records, click the Cisco Unified CallManager name that matches your search criteria. The window displays the Cisco Unified CallManager that you chose. Updating a Cisco Unified CallManager This section describes how to update a Cisco Unified CallManager.   Procedure Step 1 Choose System > Cisco Unified CallManager. The Find and List Cisco Unified CallManagers window displays. Step 2 To update a Cisco Unified CallManager, locate the appropriate Cisco Unified CallManager as described in Finding a Cisco Unified CallManager. Click the Cisco Unified CallManager that you want to update and continue with Step 3. Step 3 Enter the appropriate settings as described in Table 3-1. Step 4 Click Save. Cisco Unified CallManager Configuration Settings Table 3-1 describes the Cisco Unified CallManager configuration settings.   Table 3-1 Cisco Unified CallManager Configuration Settings [#wp1056152 Table 3-1] describes the Cisco Unified CallManager configuration settings. For related procedures, see the [#wp1058170 "Related Topics" section].   Table 3-1 Cisco Unified CallManager Configuration Settings   Field Description Server Information Cisco Unified CallManager Server This read-only field displays the server where this Cisco Unified CallManager is installed. Cisco Unified CallManager Name Enter the name that you want to assign to this Cisco Unified CallManager. Description Enter a description of the Cisco Unified CallManager. Auto-registration Information Starting Directory Number Enter the first directory number to use for autoregistration of devices. The starting dn cannot be prefixed by "0"(e.g 0123). Zero gets striped off after clicking on the save button. Ending Directory Number Enter the last directory number to use for autoregistration of devices. Note Specifying a valid range of directory numbers in the Starting Directory Number and Ending Directory Number fields automatically enables autoregistration. Setting the starting and ending directory numbers to the same value disables autoregistration. Partition If you are not using partitions, choose <None>. If you are using partitions, choose the partition to which autoregistered directory numbers belong from the drop-down list box. Tip You must choose a range for autoregistration before you can choose a partition, external phone number mask or voice messaging box mask. If more than 250 partitions exist, the ellipsis (...) button displays next to the drop-down list box. 1.To display the Select Partition window, click the (...)button. 2. In the List items where Name contains field, enter a partial partition name. 3. In the list of partitions that displays in the Select item to use box, click the desired partition name. 4. Click OK. External Phone Number Mask Specify the mask that is used to format caller ID information for external (outbound) calls that are made from the autoregistered devices. •The mask can contain up to 50 characters. •Enter the literal digits that you want to appear in the caller ID information and use Xs to represent the directory number of the autoregistered device. See the following examples: •If you specify a mask of 972813XXXX, an external call from extension 1234 displays a caller ID number of 9728131234 if the Use External Phone Number Mask option is checked on the route pattern that is used to make the external call. •If you specify a mask of all literal digits, such as 9728135000 to represent a main attendant number, that literal number (9728135000) displays as the caller ID for an external call from any autoregistered device. Auto-registration Disabled on this Cisco Unified CallManager Cisco Unified CallManager disables the autoregistration by default to prevent unauthorized connections to the network. You can choose to enable or disable autoregistration by one of the following options: •To enable autoregistration for this Cisco Unified CallManager, uncheck the Auto-registration Disabled check box. •To disable autoregistration for this Cisco Unified CallManager, check the Auto-registration Disabled check box. •When autoregistration is disabled, you must configure the directory numbers manually whenever you add new devices to your network. •Setting the Starting Directory Number and Ending Directory Number to the same value also disables autoregistration. •If starting and ending directory numbers are currently specified when you disable autoregistration by checking this option, Cisco Unified CallManager sets the starting and ending directory numbers to the same value. Cisco Unified CallManager resets the partition and external phone mask information when autoregistration is disabled. Cisco Unified CallManager TCP Port Settings for This Server Ethernet Phone Port Cisco Unified CallManager uses this TCP port to communicate with the Cisco Unified IP Phones (SCCP only) on the network. •Accept the default port value of 2000 unless this port is already in use on your system. Choosing 2000 identifies this port as non-secure. •Ensure all port entries are unique. •Valid port numbers range from 1024 to 49151. •Refer to the Cisco Unified CallManager Security Guide for information about security configurations. MGCP Listen Port Cisco Unified CallManager uses this TCP port to detect messages from its associated MGCP gateway. •Accept the default port of 2427 unless this port is already in use on your system. •Ensure all port entries are unique. •Valid port numbers range from 1024 to 49151. MGCP Keep-alive Port Cisco Unified CallManager uses this TCP port to exchange keepalive messages with its associated MGCP gateway. •Accept the default port of 2428 unless this port is already in use on your system. •Ensure all port entries are unique. •Valid port numbers range from 1024 to 49151. SIP Phone Port This field specifies the port number that Cisco Unified CallManager uses to listen for SIP line registrations over TCP and UDP. SIP Phone Secure Port This field specifies the port number that Cisco Unified CallManager uses to listen for SIP line registrations over TLS. Refer to the Cisco Unified CallManager Security Guide for information about security configurations.   Cisco CallManager Service Activation/Deactivation The following requirements apply to Cisco CallManager service activation and deactivation: • Cisco CallManager Service Activation • Cisco CallManager Service Deactivation   Cisco CallManager Service Activation When you perform a new Cisco Unified CallManager installation, you must follow these steps in sequence:   1. Add the Server. Cisco Unified CallManagers automatically get added when a server gets configured. 2. Activate the Cisco CallManager service, as described in the Cisco Unified CallManager Serviceability Administration Guide. A message displays if you do not follow this sequence.   Cisco CallManager Service Deactivation You can deactivate the Cisco CallManager service in Cisco Unified CallManager Serviceability. When you deactivate the Cisco CallManager service, the Cisco Unified CallManager where you deactivated the service becomes inactive for use. Note From Cisco Unified CallManager Serviceability, you can view the status of the Cisco Unified CallManager by accessing Tools > Service Activation. When the Cisco CallManager service is deactivated, no one can make calls on that Cisco Unified CallManager. You may still be able to perform configuration operations on a deactivated Cisco Unified CallManager if the Cisco CallManager Administration web service is active and the database is up and running.   When you reactivate the Cisco CallManager service on the Cisco Unified CallManager, the database automatically re-creates the Cisco Unified CallManager by retaining the original configuration (server name or IP address). This Cisco Unified CallManager then becomes active; you can verify that the Cisco CallManager service is running by accessing Tools > Control Center - Feature Services in Cisco Unified CallManager Serviceability.   For more information about Service Activation, refer to the Cisco Unified CallManager Serviceability System Guide and the Cisco Unified CallManager Serviceability Administration Guide. Cisco Unified CallManager Group Configuration A Cisco Unified CallManager Group specifies a prioritized list of up to three Cisco Unified CallManagers. The first Cisco Unified CallManager in the list serves as the primary Cisco Unified CallManager for that group, and the other members of the group serve as secondary and tertiary (backup) Cisco Unified CallManagers.   Each device pool has one Cisco Unified CallManager Group assigned to it. When a device registers, it attempts to connect to the primary (first) Cisco Unified CallManager in the group that is assigned to its device pool. If the primary Cisco Unified CallManager is not available, the device tries to connect to the next Cisco Unified CallManager that is listed in the group, and so on.   Cisco Unified CallManager Groups provide important features for your system: •Redundancy—This feature enables you to designate a primary and backup Cisco Unified CallManagers for each group. •Call processing load balancing—This feature enables you to distribute the control of devices across multiple Cisco Unified CallManagers. For most systems, you need to have multiple groups, and you need to assign a single Cisco Unified CallManager to multiple groups to achieve better load distribution and redundancy.   Use the following topics to add, update, or delete a Cisco Unified CallManager group: • Finding a Cisco Unified CallManager Group • Configuring a Cisco Unified CallManager Group • Cisco Unified CallManager Group Configuration Settings • Deleting a Cisco Unified CallManager Group Finding a Cisco Unified CallManager Group Because you might have several Cisco Unified CallManager groups in your network, Cisco Unified CallManager Administration lets you locate specific Cisco Unified CallManager groups on the basis of specific criteria. Use the following procedure to locate Cisco Unified CallManager groups. Note During your work in a browser session, your find/list search preferences are stored in the cookies on the client machine. If you navigate to other menu items and return to this menu item, or if you close the browser and then reopen a new browser window, your Cisco Unified CallManager search preferences are retained until you modify your search. Procedure Step 1 Choose System > Cisco Unified CallManager Group. The Find and List Cisco Unified CallManager Groups window displays. Use the drop-down list box to search for a Cisco Unified CallManager Group. Step 2 From the Find Cisco Unified CallManager Groups window drop-down list box, choose one of the following criteria: • begins with • contains • is exactly • ends with • is empty • is not empty Step 3 Specify the appropriate search text, if applicable, and click Find. Tip To find all Cisco Unified CallManager groups that are registered in the database, click Find without entering any search text. A list of discovered Cisco Unified CallManager groups displays by • Cisco Unified CallManager Group name • Auto-registration Cisco Unified CallManager Group From the Find and List Cisco Unified CallManager Groups window, you can also specify how many items per page to display. Note You can delete multiple Cisco Unified CallManager groups from the Find and List Cisco Unified CallManager Groups window by checking the check boxes next to the appropriate Cisco Unified CallManager groups and clicking Delete Selected. You can delete all Cisco Unified CallManager groups in the window by checking the check box in the Matching records title bar and clicking Delete Selected. Step 4 From the list of records, click the Cisco Unified CallManager Group name that matches your search criteria. The window displays the Cisco Unified CallManager group that you chose. Configuring a Cisco Unified CallManager Group This section describes how to add, copy, or update a Cisco Unified CallManager group. Before You Begin Before configuring a Cisco Unified CallManager group, you must configure the Cisco Unified CallManagers that you want to assign as members of that group. See the "Updating a Cisco Unified CallManager" section for more information. Procedure Step 1 Choose System > Cisco Unified CallManager Group. The Find and List Cisco Unified CallManager Groups displays. Step 2 Perform one of the following tasks: • To copy an existing Cisco Unified CallManager Group, locate the appropriate Cisco Unified CallManager Group as described in the "Finding a Cisco Unified CallManager Group" section, choose the Cisco Unified CallManager Group that you want to copy, click Copy, and continue with Step 3. • To add a new Cisco Unified CallManager Group, click Add New button, and continue with Step 3. • To update an existing Cisco Unified CallManager Group, locate the appropriate Cisco Unified CallManager Group as described in the "Finding a Cisco Unified CallManager Group" section, and continue with Step 3. Step 3 Enter the appropriate settings as described in Table 4-1. Step 4 Click the Save icon that displays in the tool bar in the upper, left corner of the window (or click the Save button that displays at the bottom of the window) to save the Cisco Unified CallManager Group configuration in the database. After you have configured the Cisco Unified CallManager Group, you can use it to configure device pools. Devices obtain their Cisco Unified CallManager Group list setting from the device pool to which they are assigned. Cisco Unified CallManager Group Configuration Settings Table 4-1 describes the configuration settings for Cisco Unified CallManager groups. Table 4-1 Cisco Unified CallManager Group Configuration Settings INSERT TABLE HERE Deleting a Cisco Unified CallManager Group This section describes how to delete a Cisco Unified CallManager Group from the database. Before You Begin Note: You cannot delete a Cisco Unified CallManager group if it is assigned to any device pools or MGCP gateways or if it is the current Auto-registration Cisco Unified CallManager Group for the cluster. To find out which devices are using the Cisco Unified CallManager group, choose Dependency Records from the Related Links drop-down list box on the Cisco Unified CallManager Group Configuration window and click Go.   If the dependency records feature is not enabled for the system, the dependency records summary window displays a message that shows the action that you can take to enable the dependency records; the message also displays information about high CPU consumption that is related to the dependency records feature. For more information about dependency records, see the "Accessing Dependency Records" section.   If you attempt to delete a Cisco Unified CallManager group that is in use, an error message displays. Before deleting a Cisco Unified CallManager group that is currently in use, you must perform some or all of the following tasks:   • Assign a different Cisco Unified CallManager group to the device pools or MGCP gateways that currently use this Cisco Unified CallManager group. See the "Configuring a Device Pool" section. • Create or choose a different Cisco Unified CallManager group to be the Auto-registration Cisco Unified CallManager Group.   Procedure Step 1 Find the Cisco Unified CallManager group by using the procedure in the "Finding a Cisco Unified CallManager Group" section. Step 2 From the list of matching records, choose the group that you want to delete. Step 3 Click the Delete Selected Item icon that displays in the tool bar in the upper, left corner of the window (or click the Delete Selected button that displays at the bottom of the window) to delete the Cisco Unified CallManager group. Step 4 When asked to confirm the delete operation, click either OK to delete or Cancel to cancel the delete operation. Phone NTP Reference Configuration If you want to do so, you can configure phone Network Time Protocol (NTP) references in Cisco Unified CallManager Administration to ensure that a Cisco SIP IP Phone gets its date and time from the NTP server. If all NTP servers do not respond, the SIP phone uses the date header in the 200 OK response to the REGISTER message for the date and time.   After you add the phone NTP reference to Cisco Unified CallManager Administration, you must add it to a date/time group. In the date/time group, you prioritize the phone NTP references, starting with the first server that you want the phone to contact.   The date/time group configuration gets specified in the device pool, and the device pool gets specified on the phone page.   Use the following topics to configure phone NTP references:   • Finding the Phone NTP References • Configuring the Phone NTP References • Phone NTP Reference Configuration Settings • Deleting the Phone NTP Reference Finding the Phone NTP References Because you can configure several phone NTP references in Cisco Unified CallManager Administration, Cisco Unified CallManager Administration allows you to locate specific phone NTP references. Use the following procedure to locate the phone NTP references that exist in Cisco Unified CallManager Administration. Note: During your work in a browser session, the cookies on the client machine store your find/list preferences. If you navigate to other menu items and return to this menu item, or if you close the browser and then reopen a new browser window, the system retains your Cisco Unified CallManager search preferences until you modify your search. Procedure Step 1 Choose System > Phone NTP Reference. The Find and List window displays.   Tip: To find all phone NTP references that exist in the database, click Find without specifying any search criteria.   Step 2 If you want to do so, choose search criteria from the Find drop-down list boxes; enter the appropriate search text, if applicable, and click Find. From the Find and List window, you can also specify how many items per page to display. Step 3 From the list of records, click the phone NTP reference name that matches your search criteria. Configuring the Phone NTP References This section describes how to add a phone NTP reference to the Cisco Unified CallManager database or to update a phone NTP reference that exists in the database.   Procedure Step 1 Choose System > Phone NTP Reference. The Find and List window displays. Step 2 Perform one of the following tasks: • To add the phone NTP reference to the Cisco Unified CallManager database, click the Add New button and continue with Step 3. • To update an existing phone NTP reference, locate the existing phone NTP reference as described in the "Finding the Phone NTP References" section and continue with Step 3. Step 3 Enter the appropriate settings as described in Table 5-1. Step 4 To save the configuration in the database, click the Save icon that displays in the tool bar in the upper, left corner of the window (or click the Save button that displays at the bottom of the window). Next Steps After you add a new phone NTP reference to the Cisco Unified CallManager database, assign it to a date/time group. For more information, refer to the "Configuring a Date/Time Group" section. Phone NTP Reference Configuration Settings Table 5-1 describes the phone NTP reference configuration settings.   Table 5-1 Phone NTP Reference Configuration Settings INSERT TABLE Deleting the Phone NTP Reference This section describes how to delete a phone NTP reference from the Cisco Unified CallManager database.   Before You Begin   Before you can delete the phone NTP reference from Cisco Unified CallManager Administration, you must delete the phone NTP reference from the date/time group. To find which date/time groups use the phone NTP reference, choose Dependency Records from the Related Links drop-down list box in the Phone NTP Reference Configuration window and click Go. When you know which date/time groups use the phone NTP reference, you can then remove that phone NTP reference from that group.   If the dependency records feature is not enabled for the system, the dependency records summary window displays a message that shows the action that you can take to enable the dependency records; the message also displays information about high CPU consumption that is related to the dependency records feature. For more information about dependency records, refer to the "Accessing Dependency Records" section.   Procedure Step 1 By using the procedure in the "Finding the Phone NTP References" section, find the phone NTP reference. Step 2 To delete multiple phone NTP references, check the check boxes next to the appropriate phone NTP references in the Find and List window; then, click the Delete Selected icon or the Delete Selected button. Step 3 To delete a single phone NTP reference, perform one of the following tasks: • In the Find and List window, check the check box next to the appropriate phone NTP reference; then, click the Delete Selected icon or the Delete Selected button. • In the Find and List window, click the Name link for the phone NTP reference. After the Phone NTP Reference Configuration window for that specific phone NTP reference displays, click the Delete Selected icon or the Delete Selected button. Step 4 When prompted to confirm the delete operation, click OK to delete or Cancel to cancel the delete operation. ... View more

  Introduction The Cisco® integrated Cable high-speed WAN interface cards (HWICs) provide lower total cost of ownership, advanced quality-of-service (QoS) enforcement, and advanced monitoring and load-balancing capabilities for customers by optionally integrating a DOCSIS 2.0-based cable modem within a Cisco Integrated Services Router (ISR) or Cisco IAD2430 Series Integrated Access Device. Additionally, the new Cisco Cable HWICs greatly expand the portfolio of managed business-class cable services cable operators can offer to their small and medium sized business (SMB) and enterprise customers. The Cisco ISRs and Cisco IAD2430 Series can be coupled with the cable HWIC to provide a range of services, including security, IP Communications, switching, wireless LAN management and connectivity, WAN optimization, and much more.   Overview The new Cable HWICs (HWIC-CABLE-D-2 and HWIC-CABLE-E/J-2) are designed to comply with DOCSIS 2.0, Euro-DOCSIS 2.0, and J-DOCSIS 2.0 specifications and provide single-port cable modem connectivity for the Cisco modular integrated services routers and the Cisco IAD2430 series routers to the cable operator WAN. These cable HWICs (Figure 1), combined with the Cisco 2800 and 3800 Series Integrated Services Routers; Cisco 1841 Integrated Services Router; and Cisco IAD2430 Series provide high-speed digital data transmission between customer premises equipment (CPE) and a central office. This enables cable service providers and resellers to offer additional services by supporting features for business-class security, voice integration, differentiated classes of service (CoS), and managed network access with Cisco IOS® Software. These value-added features, along with the manageability and reliability of Cisco IOS Software technology, provide the mission-critical networking that businesses require. Figure 1. Single-Port DOCSIS 2.0 and Euro/J-DOCSIS 2.0-Based Cable HWICs (HWIC-CABLE-D-2 and HWIC-CABLE-E/J-2) Both the 1-port DOCSIS-based cable HWIC and the one-port Euro/J-DOCSIS-based cable HWIC cards provide a single F-connector for broadband connectivity. The cable HWICs are supported starting with Cisco IOS Software Release 12.4(11)T. Cable operators can use the Cisco ISRs and Cisco IAD2430 Series when combined with the cable HWICs to provide a vast array of business services, including voice, video, data, security, wireless, switching, and content caching over the DOCSIS network. The cable HWICs embedded in the Cisco IOS Software routers provide an integrated solution for a cost-effective alternative to leased lines, ISDN, or xDSL services for critical primary WAN links or backup solutions. Cable service providers and enterprise customers can also benefit from ease of deployment and management by deploying an integrated cable solution. Additional benefits of an integrated cable solution over a standalone cable modem plus a router include improved QoS enforcement, enhanced WAN failover capabilities, and improved availability.   Applications   Business-Class Cable Broadband Connectivity The Cisco 2800 and 3800 Series ISRs and Cisco 1841 ISR offer multiple WAN slots to support the broadest range of WAN connectivity. These routers can be configured with the Cisco cable HWIC for primary WAN access, offering high-speed cable broadband connection to the Internet or to enterprise offices. The advanced QoS enforcement minimizes latency for high-priority data and voice traffic. The status and quality of the link can be monitored with Cisco IOS Software using advanced management instrumentation. The cable HWIC coupled with the breadth of WAN access technologies available for the ISR offers enterprise and SMB customers the maximum WAN flexibility and choice for branch office connections (Figure 2). Figure 2. Cable Solution for Branch/Retail Office with Security, Voice, Wireless     Secondary WAN Connectivity In addition to being an excellent primary WAN link, the cable HWICs are well suited for used as a secondary WAN link for businesses of all sizes. This secondary link can be used to offload Web traffic directly to the Internet, provide a redundant option for a primary link in case of failure, or provide load balancing with a xDSL or other type of WAN link. Increasingly, Internet connectivity is crucial to a branch or small business employee's productivity. However, as more streaming media and rich content is placed on the Web, the WAN bandwidth requirements to provide this connectivity continue to grow. In the case of a branch office, as shown in Figure 2, using Policy-Based Routing, all HTTP (Port 80) traffic can be diverted from a primary low-bandwidth link to the DOCSIS link to minimize the amount of traffic being routed back to corporate headquarters. The ISRs can optionally provide end-to-end security with advanced firewall, intrusion prevention, and URL filtering capabilities to help ensure security and proper usage of the Internet. As more business applications are centralized, connectivity to the central or regional office becomes crucial to the growing population of workers distributed among branch offices around the world. Cable broadband provides an excellent backup to traditional public switched telephone network (PSTN)-based WAN links because it uses a separate network infrastructure. This separation helps reduce the probability that if the primary PSTN-based WAN link goes down, the backup link, which would often otherwise reside in the same binder as the primary link, will simultaneously go down as well. The ISRs can create IP Security (IPsec) tunnels back to the central site to secure any mission-critical communications until the primary link is restored. Additionally, the high performance capability of the cable HWIC makes it an excellent backup option for newer high-speed technologies such as ADSL2+ and Ethernet WAN services.   Business-Class Security The Cisco ISRs with the cable HWICs can be optimized for Internet security with the Cisco IOS Firewall supporting stateful inspection firewall and intrusion prevention system (IPS) features (Figure 2). With an always-on cable connection, Internet security is vital to protect corporate resources from malicious network attacks. These features can be enabled on the modular routers by deploying the optional Cisco IOS Software with the Advanced Security or higher feature set. These platforms can also be utilized for VPN IPsec and Multiprotocol Label Switching (MPLS) connectivity, which allow secure use of the Internet for communications with the same policies and levels of security and performance as a private network. IPsec-based VPNs provide security through encryption tunneling, and the Cisco ISRs support hardware-based Triple Data Encryption Standard (3DES) IPsec and Advanced Encryption Standard (AES) support. Encryption features can be enabled on the routers by deploying the optional Cisco IOS Software Advanced Security feature set. Using cable HWICs with Cisco ISRs, cable operators can increase their average revenue per subscriber (ARPU) and decrease the potential for subscriber churn by offering business-class security services as a managed service to customers.   Converged Data and Voice over IP Services The Cisco IAD2430, 2800 and 3800 Series ISRs combined with the cable HWIC can meet the IP Communications needs of SMBs and enterprise branch offices while concurrently delivering an industry-leading level of security within a single routing platform. Cisco CallManager Express (CME) is an optional solution embedded in Cisco IOS Software that provides call processing for Cisco IP phones, including wired and wireless LAN phones. Cisco IAD2430, 2800, and 3800 Series platforms together with the cable HWIC provide advanced QoS enforcement to help ensure high levels of quality for IP Communications (Figure 2). The Cisco CallManager Express solution offers a core set of phone features that customers require for their everyday business needs and uses the wide array of voice capabilities embedded in the Cisco modular ISRs running Cisco IOS Software. The Cisco ISRs and Cisco IAD2430 Series with the cable HWIC provide an integrated data and voice services platform for cable service providers to cost-effectively accelerate the migration from traditional time-division multiplexing (TDM) to voice over IP (VoIP) for business customers. In this application, a business customer would connect (or would already have connected) its private branch exchange (PBX) or key system to a VoIP-enabled Cisco ISR. The router would packetize the voice traffic and send the packets over the HFC network. At the headend, the call manager or the H.323 gatekeeper would then decide which packets get sent on to the PSTN and which would stay on the IP network. For a business, the advantages of using VoIP services include toll bypass, remote PBX presence over a WAN, and unified voice/data trunking.   Features and Benefits   Architecture Feature and Benefits The new Cisco cable HWICs help ensure maximum availability, high performance, ease of upgrade, and expandability. The modules have their own processor, firmware, and memory that run independently of the host router resources, helping to ensure maximum performance and upgradability and facilitating ongoing DOCSIS compliance. Table 1 lists some of the features and benefits of this advanced architecture. Table 1. Cisco Cable HWIC Module Architecture Features and Benefits Feature Benefit Standards Based • The Cable HWICs are designed to comply with DOCSIS 2.0 standards and integrate transparently within existing cable operator networks. • HWIC-CABLE-D-2 is designed to comply with DOCSIS 2.0. • HWIC-CABLE-E/J-2 is designed to comply with the J-DOCSIS and Euro-DOCSIS 2.0 standards. (Note: J-DOCSIS downstream center frequency is limited to 90-860MHz.) • The Cable HWIC is designed to work in PacketCable™ Multimedia networks and supports up to 15 secondary service flows. Independent Software Image • The Cisco Cable HWIC runs its own firmware image and can be upgraded independently of the host router's Cisco IOS Software by the cable modem termination system (CMTS). Protected Cable Modem Configuration • The Cisco Cable HWIC configuration can only be changed by the cable operator using a CMTS. Maximum Availability • The Cisco Cable HWIC can be restarted independently of Cisco IOS Software by the CMTS or by the end user. • The Cisco router with the integrated cable modem can monitor the cable modem state and automatically reroute traffic to an alternate interface in the case of a WAN failure. • Replaces the external RJ-45 cable when using an external cable modem with a highly available internal connection. • Integration limits the opportunity/potential for opportunistic theft of the cable modem or accidental disconnection.   Cisco IOS Software Support Cisco IOS Software features integrate the power and flexibility of the infrastructure to provide a complete set of network services. Cisco IOS Software provides a common architecture for the creation of network services, which provides many advantages to Cisco customers. Cisco IOS Software provides business-class networking in important areas such as routing, security, IP Communications, high availability, and manageability, as described in Table 2. Table 2. Cisco IOS Feature Support Feature Benefit Advanced Routing • Provides robust, scalable, and feature-rich internetworking software support using the accepted standard networking software for Internet and private WANs. • Cisco IOS Software feature sets support IP routing and standards such as Network Address Translation (NAT), Open Shortest Path First (OSPF), Routing Information Protocol (RIPv1 and RIPv2), Border Gateway Protocol (BGP), Enhanced Interior Gateway Protocol (EIGRP), Next Hop Resolution Protocol (NHRP), and more. Advanced Security • With the Cisco IOS Software Advanced Security feature set, the Cisco ISRs can provide end-to-end security, adaptive threat defense, and protection for network infrastructure through security features such as a Cisco IOS Firewall, intrusion prevention, IPsec VPN, advanced application inspection and control, Secure Shell (SSH) Protocol Version 2.0, and Simple Network Management Protocol (SNMPv3) in one secure solution set. IP Communications • Cisco CallManager Express is an optional solution that provides call processing for Cisco IP phones and delivers telephony features similar to those that are commonly used by business users to meet the requirements of SMBs. • With Survivable Remote Site Telephony (SRST), branch offices can use centralized call control while cost-effectively providing local branch backup using SRST redundancy for IP telephony. • Conferencing and transcoding across a broad set of Cisco access platforms provide substantial scalability and also enable Cisco customers to reduce network costs. • Designed to meet enterprise and service provider Session Border Controller (SBC) needs, the Cisco Multiservice IP-to-IP Gateway is an integrated application within Cisco IOS software that runs on Cisco 2800 and 3800 Series ISRs for integrated voice, video, and data services. Traffic Monitoring and Advanced Management • Consistent Cisco IOS Software-based interface and instrumentation across portfolio, service-level agreement (SLA) enforcement with IP SLA, role-based access for split control, NetFlow for advanced traffic monitoring, Embedded Event Manager for advanced scripting.   Advanced QoS Support By integrating the cable modem functionality into a Cisco router, advanced functionality such as expanded QoS enforcement (Table 3) can be enabled. In a two-box solution (that is, a standalone cable modem plus a standalone router) the cable modem is usually connected to the router using an Ethernet or USB port. In this scenario, the router has no ability to sense congestion at the cable modem. If the router continues to send packets, the cable modem will be forced to make decisions regarding the processing and dropping of packets without proper knowledge or understanding of the appropriate prioritization of the packets, which can result in poor performance for latency-sensitive traffic such voice, video, and mission-critical data. The Cisco Cable HWIC overcomes this limitation by using its integration within Cisco routers to constantly communicate its status and ability to handle additional packets. Table 3. Advanced QoS Features and Benefits Feature Benefit Cable interface Congestion Management for the Primary Service Flow • Cisco IOS Software can detect upstream congestion on the Cable HWIC primary service flow and prioritize packets to help ensure latency-sensitive and mission-critical traffic receives the highest priority. Dynamic ACLs for Secondary Service Flows • Cisco IOS Software uses a propriety protocol to install dynamic ACLs to bypass the router's normal forwarding queue and pass latency-sensitive packets directly to high-priority secondary service flows. Cisco IOS Software-Based QoS • Cisco IOS Software supports a broad array of QoS features, including Low Latency Queuing (LLQ), Weighted Fair Queuing (WFQ), Class-Based Weighted Fair Queuing (CBWFQ), and Weighted Random Early Detection (WRED), allowing a customer to maximize the control of the WAN interface. Enhanced Failover and Load Balancing • When the cable interface is being used as a secondary or backup interface and the primary link fails, latency-sensitive and mission-critical traffic can be prioritized on the cable interface over Web and lower priority data. Secondary Service Flow Support for up to 15 Flows • Secondary service flows are optionally used by cable operators to provide advanced levels of QoS throughout the cable operator's network to help ensure latency-sensitive and mission-critical traffic is prioritized throughout the cable operator's network.   Ease of Management and Deployment Cisco Cable HWICs are highly manageable devices that offer many ease of management advantages (Table 4). For instance, the cable HWICs can be monitored using the host router command-line interface (CLI), providing one point of monitoring and management for the cable modem and host router. Additionally, the Cisco Cable HWIC can be managed using an advanced Cisco GUI software suite such as the Cisco Router and Security Device Manager (SDM) or CiscoWorks. These easy-to-use Web-based management interfaces can be accessed through a standard Web browser. Table 4. Management Features and Benefits Feature Benefit Single, Static MAC Address • MAC address of the cable HWIC is assigned at the factory and does not change, allowing for ease of management by cable operators. Clear Demarcation Point • The cable HWIC configuration can only be modified using the cable operator's CMTS and cannot be changed using Cisco IOS Software in compliance with the DOCSIS, Euro-DOCSIS, and J-DOCSIS standards. Real-time Status and Statistics Using Cisco IOS Software • The cable HWIC provides Cisco IOS Software with real-time status and statistics updates, which can be monitored remotely or onsite using Cisco IOS Software. Cisco IOS Software IP SLA • End-to-end service-level measurement assures IP service levels, proactively verifies network operation, and accurately measures network performance. Cisco IOS Software Embedded Event Manager (EEM) • EEM harnesses network intelligence through event detectors and takes action according to predefined policies, resulting in increased manageability, control, and resiliency. Ease of deployment • Single box to manage for managed services. New features and services can be enabled using Cisco IOS Software without the introduction of a second device or a truck roll. Cisco Router and Security Device Manager (SDM) • Provides an easy-to-use, Web-based management interface through a standard Web browser to configure the Cisco IOS Software router and control the router's interaction with the cable HWIC. Cisco CNS 2100 Series Intelligence Engine support • Secure networking product supports the activation, upgrading, and configuration of CPE through centralized template-based configuration management. Future CiscoWorks support (planned for 2007) • CiscoWorks network management software provides management capabilities on a per-port and per-switch basis, providing a common management interface for Cisco routers and switches.   Summary/Conclusion Bandwidth requirements continue to rise at businesses of all sizes, and convergence of data, voice, and video on these single pipes requires more intelligent solutions. As companies strive to lower the costs of running their networks and to increase the productivity of their end users with network applications, broadband connectivity is increasingly a core requirement for businesses of every size. The Cisco Cable HWICs enable a higher level of physical and logical security, provide advanced QoS for IP Communications, easy expandability, higher availability, and simplified management for SMBs and enterprise branch offices. By integrating the Cable HWIC into existing or new Cisco IOS Software-based routers, the Cisco Cable HWICs can help businesses of all sizes avoid expensive private circuit upgrades and allow cable operators to reach a broader set of customers and provide increasing levels of advanced managed services in a cost-effective manner.   Software Support The Cable HWICs are supported starting with Cisco IOS Software Release 12.4(11)T. The Cable HWICs and Cisco IOS Software features are supported in the IP Base image and above for the Cisco 1841, the Cisco 2800 and 3800 Series ISRs.   Platform Support The cable HWICs are supported in the onboard HWIC slots of the modular Cisco 1841 ISR and Cisco 2800 and 3800 Series ISRs and in the WIC slot of the Cisco IAD2430 Series. Table 5 provides platform support details. Table 5. Platform Support Details HWIC-CABLE-D-2 and HWIC-CABLE-E/J-2 Maximum Number of HWICs Cisco 1841 ISR 2 Cisco 2801 ISR 2 Cisco 2811, 2821, and 2851 ISR 4 Cisco 3825 and 3845 ISR 4 Cisco IAD2431 and IAD2432 Integrated Access Devices 1   Hardware Specifications Hardware specifications of the cable HWICs are described in Table 6. Table 6. Specifications for the HWIC-CABLE-D-2 and HWIC-CABLE-E/J-2 Specification Data Hardware/Platform Compatibility Cisco 1841, 2800 and 3800 Series, and IAD2430 Series Network Module Support Cable HWICs are supported by the following NM carrier modules: NM-2W, NM-1FE1R2W, NM-1FE2W-V2, NM-2FE2W-V2 Ports Single F-type standard coax interface for HFC network Cabling Required Standard coax cabling LEDs Power, link status indicators, downstream (DS) and upstream (US) activities, and online indicator Cable Certification HWIC-CABLE-D-2 is CableLabs® certified (CW45). Pending certification at T-Com Labs for HWIC-CABLE-E/J-2. DOCSIS Standards Based • HWIC-CABLE-D-2: based on DOCSIS 1.0, 1.1, 2.0 • HWIC-CABLE-E/J-2: based on Euro-DOCSIS 2.0, J-DOCSIS 2.0 Dimensions • Width 3.08 in. (6.93 cm) • Height .75 in. (1.91 cm) • Depth 4.38 in. (9.86 cm) Weight 2.4 oz (68 g)   Product Number and Ordering Information The cable HWIC product numbers are listed in Table 7. Table 7. Cisco Cable HWIC Product Numbers Product Number Description HWIC-CABLE-D-2 1-port DOCSIS 2.0-based cable HWIC (system) HWIC-CABLE-D-2= 1-port DOCSIS 2.0-based cable HWIC (spare) HWIC-CABLE-E/J-2 1-port Euro/J-DOCSIS 2.0-based cable HWIC (system) HWIC-CABLE-E/J-2= 1-port Euro/J-DOCSIS 2.0-based cable HWIC (spare)   Cisco 1800, 2800, and 3800 Series Regulatory Approvals When installed in the Cisco 1800, 2800, and 3800 Series ISRs, the cable HWICs do not change the router standards (regulatory compliance, safety, EMC, telecom). Refer to the platform-specific data sheets for their regulatory compliance, safety, EMC, and telecom standards. • For Cisco 1841 Integrated Services Router: http://www.cisco.com/en/US/products/ps5853/products_data_sheet0900aecd8016a59b.html • For Cisco 2800 Series Integrated Services Routers: http://www.cisco.com/en/US/products/ps5854/products_data_sheet0900aecd8016fa68.html • For Cisco 3800 Series Integrated Services Routers: http://www.cisco.com/en/US/products/ps5855/products_data_sheet0900aecd8016a8e8.html • For Cisco IAD2430 Integrated Access Devices: http://www.cisco.com/en/US/products/hw/gatecont/ps887/products_data_sheet09186a008019aded.html   Country Availability For the latest information regarding per-country approval for the HWIC-CABLE-D-2 and HWIC-CABLE-E/J-2, contact your local Cisco representative.   Environmental Operating Ranges • Operating temperature: 32 to 104ºF (0 to 40ºC) • Nonoperating temperature: 4 to 149ºF (-20 to 65ºC) • Relative humidity: 10 to 85 percent noncondensing operating; 5 to 95 percent noncondensing, nonoperating safety ... View more

  Installing Cisco Unified CallManager Release 5.1(1)   Because the 5.0(x) release of Cisco Unified CallManager has a different installation framework than previous releases of Cisco Unified CallManager, review all installation instructions carefully before you install Cisco Unified CallManager 5.1(1).   This document includes information about installing Cisco Unified CallManager Release 5.1(1) on one server or many servers in a cluster environment. Contents This document contains the following topics:   • Installation Overview   • Important Considerations   • Frequently Asked Questions About the Cisco Unified CallManager Installation   • Browser Requirements   • Configuring the Hardware   • Installing Cisco Unified CallManager   • Gathering Information for an Installation   • Installing the New Operating System and Application   • Post-Installation Tasks   • Examining Log Files   • Obtaining Documentation   • Documentation Feedback   • Obtaining Technical Assistance   • Obtaining Additional Publications and Information     Installation Overview Cisco Unified CallManager 5.0(x) uses a different installation framework than previous releases. The installation process allows you to perform a basic installation, upgrade from Cisco Unified CallManager 4.x to Cisco Unified CallManager 5.1(1), and upgrade to a newer service release during the installation.   For a more detailed description of the different installation types, see Table 1.   Table 1 Installation Options   INSERT TABLE   Important Considerations Before you proceed with the Cisco Unified CallManager installation, consider the following requirements and recommendations:   • Be aware that when you install Cisco Unified CallManager 5.1(1) on an existing server, the hard drive gets formatted, and all existing data on the drive gets overwritten.   • Install the Cisco Unified CallManager software on the first node or publisher server first and then on the subsequent nodes.   • Make sure that the subsequent node servers that you are installing can connect to the first node server during the installation.   • Enter the same security password on all servers in the cluster.   • Install the Cisco Unified CallManager software during off-peak hours or a maintenance window to avoid impact from call-processing interruptions.   • Configure the server by using static IP addressing to ensure that the server obtains a fixed IP address and that the Cisco Unified IP Phones can register with the application when you plug the phones into the network.   • Do not attempt to perform any configuration tasks during the installation.   • Do not install any Cisco-verified applications until you complete installing Cisco Unified CallManager on every server in the cluster.   • Carefully read the instructions that follow before you proceed with the installation   Frequently Asked Questions About the Cisco Unified CallManager Installation The following section contains information about commonly asked questions and responses. Review this section carefully before you complete the Cisco Unified CallManager installation.   How long does it take to perform the Cisco Unified CallManager installation? The entire installation process, excluding pre- and post-installation tasks, takes 45 to 90 minutes per server, depending on your server type. Before you install Cisco Unified CallManager, consider the size of your cluster.   What Passwords do I Need to Specify? During the Cisco Unified CallManager installation, you must specify the following user names and passwords:   • Administrator account   You use the Administrator username and password to log in to the following areas:   – Cisco Unified Communications Operating System Administration   – Disaster Recovery System   – Command Line Interface   The Administrator login must start with an alphabetic character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. You can change the Administrator password or add a new Administrator account by using the command line interface. See the Cisco Unified Communications Operating System Administration Guide for more information.   • Application User password   You use the Application User password for the following default application user names:   – CCMAdministrator   – CCMSysUser   – WDSysUser   – CCMQRTSysUser   – IPMASysUser   – WDSecureSysUser   – CCMQRTSecureSysUser   – IPMASecureSysUser   You can change the application user password for each application through Cisco Unified CallManager Administration. See the Cisco Unified CallManager Administration Guide for more information.   • Database Access Security Password   The system uses this password to authorize communications between nodes, and you must ensure that this password is identical on all nodes in the cluster.   The Database Access Security password must start with an alphanumeric character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores.   Which servers does Cisco support for this installation? For information about the supported servers, refer to the release notes for your version of Cisco Unified CallManager. Click here for Cisco Product Release Notes.   May I install other software besides Cisco Unified CallManager on the server? For Cisco Unified CallManager 5.1(1), you must do all software installations and upgrades by using the Software Upgrades menu options in Cisco Unified Communications Operating System Administration. The system can upload and process only software that Cisco Systems approved. You cannot install or use third-party or Windows-based software applications that you may have been using with a previous version of Cisco Unified CallManager with Cisco Unified CallManager 5.1(1).   What are the Installation Options? • Basic Install This option represents the basic installation and does not use any imported data.   • Upgrade During Install This option allows you to upgrade the preinstall software with the latest service release prior to configuring your system. You can also choose Upgrade During Install followed by a Windows Upgrade and perform both during the installation process.   Note: Ensure that you have the software image available on DVD or on a remote server prior to choosing this option.   • Windows Upgrade This option allows you to import the TAR file that the DMA tool produced while upgrading an existing Cisco Unified CallManager server. Browser Requirements You can access Cisco Unified CallManager Administration, Cisco Unified CallManager Serviceability, and Cisco Unified Communications Administration by using the following browsers:   • Microsoft Internet Explorer version 6.0 or later   • Netscape Navigator version 7.1 or later Note: Cisco does not support or test other browsers, such as Mozilla Firefox.   Configuring the Hardware As a part of software installation, the system installer configures the system BIOS and RAID settings for the new operating system and Cisco Unified CallManager application. See Table 2 for the BIOS settings and Table 3 for the RAID settings that are set up during installation. Note: If the hardware configuration process fails during installation, you can use boot-time utilities that are found on both the IBM and HP servers to manually configure the RAID and BIOS settings, as shown in Table 2 and Table 3. Table 2 BIOS Configuration Settings for HP and IBM Servers   HP Servers IBM Servers OS Selection: Linux (not applicable on newer                           models) OS Selection: Not Applicable Boot Order: CD, C:, Floppy Boot Order: CD, C:,                           Floppy Post F1 prompt: Delayed Post F1 prompt:                           Delayed Hyperthreading: Enabled Hyperthreading:                           Enabled Table 3 RAID Settings   MCS 7825 Servers (HP and                 IBM) MCS 7835 Servers (HP and                 IBM) MCS 7845 Servers (HP and IBM) Software Raid Logical Drives: 1 Logical Drives:                 2 Software Raid Note For the HP 7825H1 and the IBM 7825I1, SATA RAID is enabled, and the RAID type specifies 1(1+0), with one logical drive RAID type: 1(1+0) RAID type: 1(1+0)     Installing Cisco Unified CallManager The next sections contain the procedures for installing the first and subsequent nodes. Review the following sections carefully before you perform the installation:   • Gathering Information for an Installation   • Handling Network Errors During Installation   • Installing the New Operating System and Application   Gathering Information for an Installation Use Table 4 to record the information about your Cisco Unified CallManager server. Gather this information for each Cisco Unified CallManager server that you are installing in the cluster. You may not need to obtain all the information; gather only the information that is pertinent to your system and network configuration. You should make copies of this table and record your entries for each server in a separate table, even if you are planning to use the DMABackupInfo.inf file to configure your system.   Note: Because some of the fields are optional, they may not apply to your configuration. For example, you choose not to set up an SMTP host.   Caution: You cannot change some of the fields after installation without reinstalling the software, so be sure to enter the values that you want.   The last column in the table shows whether a field can be changed after installation, and if so, whether you can change it through Cisco Unified Communications Operating System Administration or through the Command Line Interface (CLI). Table 4 Configuration Data   Configuration Data Your                 Entry Can Entry Be Changed After                 Installation Administrator Password   Yes. CLI>                 set password admin Application User Password   Yes. CLI>                 set password Country   Yes. CLI>set                 web-security DHCP   Yes. CLI> set network                 dhcp DNS Primary   Yes. CLI>set                 network dns DNS Secondary   Yes. CLI>set                 network dns Domain   Yes. CLI>set network                 domain Domain Name Service DNS Enable   NO. Gateway Address   Yes Use OS Adminstration > Settings>IP or CLI > set network gateway Host Name   NO. IP Address   Yes Use OS Adminstration > Settings>IP or CLI > set network IP IP Mask   Yes Use OS Adminstration > Settings>IP or CLI > set network ip eth0 Location   Yes. CLI>set                 web-security Master Administrator ID   NO. NTP Server IP Address Note You can enter up to five NTP servers.   Yes Use OS Administration >                 Settings>NTP Servers Organization   Yes CLI> set                 web-security Security Password   Yes CLI>                 set password security SMTP Location   Yes CLI>                 set smtp State   Yes CLI> set                 web-security Time Zone   Yes CLI> set                 timezone Unit   Yes CLI> set                 web-security   For more detailed descriptions of each installation field, see Table 5.   Table 5 Installation Field Definitions   Field Description Usage Administrator ID This field specifies the name that you                 want to assign to this account. Ensure the name is unique; it can contain lowercase, alphanumeric characters, hyphens, and underscores. It must                 start with a lowercase alphanumeric character. For this mandatory                 field, you should record it for use when logging in to the CLI or into Cisco Unified Communications Operating System Administration. Administrator Password This field specifies the password that you use for logging into the the CLI on the platform and for logging into Cisco Unified Communications Operating System Administration. Ensure the password is at least six characters long; it can contain alphanumeric                 characters, hyphens, and underscore. For this mandatory field, you should                 record it for use when logging in to the CLI or into Cisco Unified Communications Operating System Administration. DHCP Dynamic Host Configuration Protocol Choose Yes if you want to use DHCP to automatically configure the network settings on your server. If you choose No, you must enter a hostname, IP Address, IP Mask, and Gateway. DNS Enabled A DNS server represents a device that resolves a hostname into an IP address or an IP address into a hostname. If you do not have a DNS server, enter No. When DNS is not enabled, you should only enter IP addresses (not hostnames) for all network devices in                 your Cisco Unified Communications network. If you have a DNS server,                 Cisco recommends that you enter Yes to enable DNS. Disabling DNS limits the system ability to resolve some domain names. DNS Primary The server contacts this DNS server                 first when it attempts to resolve host names. Enter the IP address of the DNS server that you want to specify as the primary DNS server. Enter the IP                 address in dotted decimal format as ddd.ddd.ddd.ddd where ddd can have a value                 between 0 and 255 (except 0.0.0.0). Consider this field mandatory if DNS is set to yes. DNS Secondary When a primary DNS server fails, the                 server will attempt to connect to the secondary DNS server. In this optional field, enter the IP address of the secondary DNS. Enter the IP address                 in dotted decimal format as ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0). Domain This field represents the name of the domain                 in which this machine is located. Consider this field mandatory if DNS                 is set to yes. First Cisco Unified Communications Manager                 Node This field specifies the first Cisco Unified Communications Manager node that contains the database. Subsequent nodes connect to                 the first node to access database content. The first node also                 synchronizes with an external NTP server and provides time to the other nodes. Choose Yes if you are configuring the first Cisco Unified Communications Manager node in the cluster. If you are configuring subsequent nodes, see Table 4 for information on the different fields. Gateway Address A gateway represents a network point that acts as an entrance to another network. Outbound packets get sent to the gateway that will forward them to their final destination. Enter the IP address of the gateway in the format ddd.ddd.ddd.ddd where ddd can have                 a value between 0 and 255 (except 0.0.0.0) If you do not have a                 gateway, you must still fill in this field by setting it to 255.255.255.255.                 Not having a gateway may limit you to only being able to communicate with devices on your subnet. Host Name A host name represents an alias that is                 assigned to an IP address to identify it. Enter a host name that is unique to your network. The host name can comprise up to 64 characters                 and can contain alphanumeric characters and hyphens. If DHCP is set to No, consider this field mandatory. IP Address This field specifies the IP address of this machine. It will uniquely identify the server on this network. Ensure another machine in this network does not use this IP address. Enter the IP address in the form ddd.ddd.ddd.ddd where ddd can have a value between 0                 and 255 (except 0.0.0.0). If DHCP is set to No, consider this field mandatory. IP Mask This field specifies the IP subnet mask of this machine. The subnet mask together with the IP address define the network address and the host address. Enter the IP mask in the form ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0).                 A valid mask should have contiguous '1' bits on left side and                 contiguous '0' bits on the right. For example, a valid mask follows:                 255.255.240.0 (11111111.11111111.11110000.00000000) An invalid mask follows: 255.255.240.240 (11111111.11111111.11110000.11110000) NIC Speed This field specifies the speed of the                 server network interface card (NIC) in megabits per second. The                 possible speeds include 10 or 100. NIC Duplex This field specifies the duplex setting                 of the server NIC. The possible settings include half and full. NTP Server This field identifies the NTP servers                 with which you want to synchronize. Enter the hostname or IP address of one or more NTP server(s). Note You can add additional NTP servers or make changes to the NTP server list at a later time NTP Server Enable When enabled, this server will act as a NTP server and provide time updates to the subsequent nodes in the cluster. Choose Yes if you want to enable this machine to be an NTP server. This option is available only on the first node in a cluster. Security Password Servers in the cluster use the security password to communicate with one another. You will be asked to                 enter the same security password for each subsequent node in the cluster. Enter the security password. Enter the same password in the confirm password field. The password must contain at least six                 alphanumeric characters. It can contain hyphens and underscores, but it must start with an alphanumeric character. Caution You must enter the same password for all nodes in the cluster. Set Hardware Clock This field specifies the date                 and local time for the machine. Note If you set the hardware clock manually, the node does not use an external NTP server for time synchronization. Choose Yes if you want to set the date and local time for the time zone that you chose. Enter the hours based on a                 24-hour format. Note If you configure an external NTP server, the hardware clock gets set automatically. SMTP This field specifies the name of the SMTP host                 that is used for outbound e-mail. Enter the hostname or dotted IP address for the SMTP server. For a host, it can contain alphanumeric                 characters, hyphens, or periods. For a host name, it must start with an                 alphanumeric character. You must fill in this field if you plan to use electronic notification. If not, you can leave it blank. Subnet IP Address By entering a subnet address, you can specify a range of IP Addresses that will be granted access to query this NTP server. Enter an IP subnet that will be granted access to the NTP server During installation, you can only enter two subnets. Subnet Mask This field specifies the subnet mask                 for the subnet address. Enter the subnet mask for the IP subnet. Time zone This field specifies the local                 time zone and offset from Greenwich Mean Time (GMT). Choose Yes if you want to change the time zone. Choose the time zone that most closely matches the location of your machine.     Handling Network Errors During Installation During the installation process, the installation program verifies that the server can successfully connect to the network by using the network configuration you enter. If it cannot, a message displays, and you get prompted to select one of the following options:   • RETRY — The installation program tries to validate networking again. If validation fails again, the error dialog box displays again.   • REVIEW (Check Install)— Allows you to review and modify the networking configuration. The installation program returns to the network configuration windows.   • HALT — The installation halts. You can copy the installation log files to a USB disk to aid troubleshooting of your network configuration.   • IGNORE — The installation continues. The networking error gets logged. In some cases, the installation program validates networking multiple times, so this error dialog box might display multiple times. Note: Networking is validated after you complete each networking window, so the message might display multiple times. If the message displays while you are reviewing the network configuration windows, choose IGNORE to move to the next window. If you choose REVIEW, the first network configuration window appears again.   Installing the New Operating System and Application Use this procedure to begin installing the operating system and Cisco Unified CallManager application: Procedure Step 1 Insert the installation DVD into the tray and restart the server, so it boots from the DVD. After the server completes the boot sequence, the Media Check window displays.   Note: If you have a new server with Cisco Unified CallManager preinstalled, you do not need to install from a DVD. Go directly to the "If You Choose Skip" procedure.   Step 2 Verify that the checksum that displays on the Media Check matches the checksum for the release on Cisco.com.   When the media check completes, the Media Check Result window displays.   Step 3 If the Media Check Result displays Pass, choose OK to continue the installation.   If the media fails the Media Check, either download another copy from Cisco.com or obtain another disc directly from Cisco Systems.   After you choose OK, the system installer performs various hardware checks to ensure you system is correctly configured for Cisco Unified CallManager 5.1(1), including the following checks:   – First, the installation process checks for the correct drivers, and you may see the following warning:   Drivers not found, do you want to install manually? To continue the installation, choose Yes.   – The installation next checks to see whether you have a supported hardware platform. If your server does not meet the exact hardware requirements, the installation process fails with a critical error. If you think this is not correct, capture the error and report it Cisco support.   – The installation process next verifies RAID configuration and BIOS settings. If the installation process makes any changes to your hardware configuration settings, you will get prompted to restart your system.   After the hardware checks complete, the Overwrite Hard Drive window displays.   Step 4 The Overwrite Hard Drive window indicates the current software version on your hard drive, if any, and the version on the DVD. Choose Yes to continue with the installation or No to cancel.   Caution If you choose Yes on the Overwrite Hard Drive window, all existing data on your hard drive gets overwritten and destroyed.   The Platform Installation Wizard window displays.   Step 5 To configure the platform now, choose Proceed. If you want to configure the platform later, choose Skip.   – If you want to install and configure the software at this time, choose Proceed and skip to the "If You Choose Proceed" section.   – If you want to install the software now and configure it later, choose Skip and continue with the "If You Choose Skip" section.   If You Choose Skip   Start here if you have a server that has Cisco Unified CallManager preinstalled or if you chose Skip on Platform Installation Wizard window.   Step 6 After the system restarts, the Preexisting Installation Configuration window displays. If you have configuration information on a USB drive or on a diskette, insert it now.   Note If a popup window states that the system detected new hardware, press any key and then choose Install from the next window.   Note If you have a file that the Data Migration Assistant created, see the Data Migration Assistant User Guide for more information.   Step 7 To continue, choose OK.   The Platform Installation Wizard window displays.   Step 8 To continue with the installation, choose Proceed.   The Upgrade During Install window displays. Continue with the "If You Choose Proceed" section.   If You Choose Proceed   Step 9 Choose the type of installation to perform by doing the following steps. See Table 3 for more information on installation options:   a. In the Upgrade During Install window, choose one of the options:   • To upgrade to a later Service Release of the software during installation, choose Yes. Continue with the "Upgrade During Install" section.   • To skip this step, choose No.   • To return to the previous window, choose Back.   b. In the Windows Upgrade window, choose No.   Note To perform a Windows Upgrade, that is, to upgrade from a Windows version of Cisco Unified CallManager to Cisco Unified CallManager 5.1(1), see Upgrading to Cisco Unified CallManager for more information.   c. In the Basic Install window, choose Continue to install the software version on the DVD or configure the preinstalled software. Continue with the "Basic Installation" section.     Upgrade During Install If you choose Yes in the Upgrade During Install window, the installation wizard installs the software version on the DVD first and then restarts the system. You then get prompted to enter certain network configuration parameter values and the location of the upgrade file. Step 10 After the system restarts, the Platform Installation Wizard window displays. To continue the installation, choose Proceed.   The Upgrade During Install window displays.   Note If the installer pops up a window that states that it detected new hardware, press any key and then choose Install from the next window.   Step 11 Choose Yes.   The Install Upgrade Retrieval Mechanism Configuration window displays.   Step 12 Choose the upgrade retrieval mechanism to use to retrieve the upgrade file:   – SFTP — Retrieves the upgrade file from a remote server by using the Secure File Transfer Protocol (SFTP). Skip to the "Upgrade From a Remote Server" section.   – FTP — Retrieves the upgrade file from a remote server by using File Transfer Protocol (FTP). Skip to the "Upgrade From a Remote Server" section.   – LOCAL — Retrieves the upgrade file from a local CD or DVD. Continue with the "Upgrade From a Local Disc" section.     Upgrade From a Local Disc Before you can upgrade from a local drive, you must download the appropriate patch file from Cisco.com and copy the file to a CD or DVD. Because of the size of the patch files, you will need to copy it to a DVD in most cases. The patch-file name has the following format:   cisco-ipt-k9-patchX.X.X.X-X.tar.gz.sgn Where X.X.X.X-X represents the release and build number   Note Do not rename the patch file before you install it because the system will not recognize it as a valid file.   Step 13 When the Local Patch Configuration window displays, enter the patch directory and patch name, if required, and choose OK.   Note You only need to enter the patch directory when the patch is not stored in the root directory of the CD or DVD.   The Install Upgrade Patch Selection Validation window displays.   Step 14 The window displays the patch file that is available on the CD or DVD. To update the system with this patch, choose Continue.     Upgrade From a Remote Server If you chose to upgrade through an FTP or SFTP connection to a remote server, you must first configure the network settings. The Auto Negotiation Configuration window displays.   Step 15 The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) by using automatic negotiation. You can change this setting after installation.   – To enable automatic negotiation, choose Yes. The DHCP Configuration window displays.   Note: To use this option, your hub or Ethernet switch must support automatic negotiation.   – To disable automatic negotiation, choose No. The NIC Speed and Duplex Configuration window displays.   Step 16 If you chose to disable automatic negotiation, manually choose the appropriate NIC speed and duplex settings now and choose OK to continue.   The DHCP Configuration window displays.   Step 17 For network configuration, you can choose to either set up static network IP addresses for the node and gateway or to use Dynamic Host Configuration Protocol (DHCP).   – If you have a DHCP server that is configured in your network and want to use DHCP, choose Yes. The system restarts and checks for network connectivity. Skip to the "Retrieving the Remote Patch" section.   – If you want to configure static IP addresses for the node, choose No. The Static Network Configuration window displays.   Step 18 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 7 for field descriptions.   The DNS Client Configuration window displays.   Step 19 To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 7 for field descriptions.   After the system configures the network and checks for connectivity, the Remote Patch Configuration window displays.     Retrieving the Remote Patch Step 20 Enter the location and login information for the remote file server. See Table 7 for field descriptions. After the network restarts, the system connects to the remote server and retrieves a list of available upgrade patches.   If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path. For example, if the upgrade file is in the patches directory, you must enter /patches. If the upgrade file is located on a Windows server, check with your system administrator for the correct directory path.   The Install Upgrade Patch Selection window displays.   Step 21 Choose the upgrade patch to install. The system downloads, unpacks, and installs the patch and then restarts the system running the upgraded software version.   After the system restarts, the Preexisting Configuration Information window displays.     Using Preexisting Configuration Information Step 22 If you have preexisting configuration information that is stored on a floppy disc or a USB key, insert the disc or the USB key now and choose Continue. The installation wizard will read the configuration information during the installation process.   The Platform Installation Wizard window displays.   Step 23 To continue with the Platform Installation Wizard, choose Proceed.   The Product Installation Configuration window displays.   Step 24 To configure the platform now, choose Proceed.   Step 25 In the Upgrade During Install window, choose No.   Step 26 In the Windows Upgrade window, choose No.   Step 27 In the Basic Install window, choose Continue. Continue with the "Basic Installation" section.     Basic Installation Step 28 When the Timezone Configuration displays, choose the appropriate time zone for the server and then choose OK.   The Auto Negotiation Configuration window displays.   Step 29 The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) by using automatic negotiation. You can change this setting after installation.   – To enable automatic negotiation, choose Yes. The DHCP Configuration window displays.   Note To use this option, your hub or Ethernet switch must support automatic negotiation.   – To disable automatic negotiation, choose No. The NIC Speed and Duplex Configuration window displays.   Step 30 If you chose to disable automatic negotiation, manually choose the appropriate NIC speed and duplex settings now and choose OK to continue.   The DHCP Configuration window displays.   Step 31 For network configuration, you can choose to either set up static network IP address for the node or to use Dynamic Host Configuration Protocol (DHCP).   – If you have a DHCP server that is configured in your network and want to use DHCP, choose Yes. The network restarts, and the Administrator Login Configuration window displays.   – If you want to configure static IP address for the node, choose No. The Static Network Configuration window displays.   Step 32 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 7 for field descriptions.   The DNS Client Configuration window displays.   Step 33 To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 7 for field descriptions.   The network restarts by using the new configuration information, and the Administrator Login Configuration window displays.   Step 34 Enter your Administrator login and password from Table 6.   Note The Administrator login must start with an alphabetic character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. You will need the Administrator login to log in to Cisco Unified Communications Operating System Administration, the command line interface, and the Disaster Recovery System.   The Certificate Signing Request Information window displays.   Step 35 Enter your certificate signing request information from Table 6 and choose OK.   The First Node Configuration window displays.   Step 36 You can configure this server as either the first node in a Cisco Unified CallManager cluster or as a subsequent node.   – To configure this server as the first Cisco Unified CallManager node, choose Yes and continue with the "Configure the First Node" section.   – To configure this server as a subsequent node in the cluster, choose No and continue with the "Configure a Subsequent Node" section.     Configure the First Node If you chose to configure the server as the first node in the cluster, the Network Time Protocol Client Configuration window displays. Cisco recommends that you use an external NTP server to ensure accurate system time on the first node. Ensure the external NTP server is stratum 9 or higher (meaning stratums 1-9). Subsequent nodes in the cluster will get their time from the first node. Step 37 Choose whether you want to configure an external NTP server or manually configure the system time.   – To set up an external NTP server, choose Yes and enter the IP address, NTP server name, or NTP server pool name for at least one NTP server. You can configure up to five NTP servers, and Cisco recommends that you use at least three. Choose Proceed to continue with the installation.   The system contacts an NTP server and automatically sets the time on the hardware clock.   Note If the Test button displays, you can choose Test to check whether the NTP servers are accessible.   – To manually configure the system time, choose No and enter the appropriate date and time to set the hardware clock. Choose OK to continue with the installation.   The Database Access Security Configuration window displays.   Step 38 Enter the Database Access Security password from Table 6.   Note The Database Access Security password must start with an alphanumeric character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. The system uses this password to authorize communications between nodes, and you must ensure this password is identical on all nodes in the cluster.   The SMTP Host Configuration window displays.   Step 39 If you want to configure an SMTP server, choose Yes and enter the SMTP server name.   Note You must configure an SMTP server to use certain platform features; however, you can also configure an SMTP server later by using the platform GUI or the command line interface.   The Platform Configuration Confirmation window displays.   Step 40 To continue with the installation, choose OK; or to modify the platform configuration, choose Back.   When you choose OK, the Application User Password Configuration window displays.   Step 41 Enter the Application User Password from Table 6 and confirm the password by entering it again.   Step 42 Choose OK.   The Cryptographic Export Warning window displays, and the systems installs and configures the software.   Step 43 When the installation process completes, you get prompted to log in by using the Administrator account and password.   Step 44 Complete the post-upgrade tasks that are listed in the "Post-Installation Tasks" section.     Configure a Subsequent Node To configure a subsequent node in the cluster, follow these steps.   Caution You must configure a subsequent node on the first node before you install it. From Cisco Unified CallManager Administration on the first node, choose System>Server.   The First Node Access Configuration window displays.   Step 45 Enter the First Node Access Configuration information from Table 5.   The SMTP Host Configuration window displays.   Step 46 If you want to configure an SMTP server, choose Yes and enter the SMTP server name.   NOTE: You must configure an SMTP server to use certain platform features. However, you can also configure an SMTP server later by using the platform GUI or the command line interface.   The Platform Configuration Confirmation window displays.   Step 47 To start installing the software, choose OK, or, if you want to change the configuration, choose Back.   Step 48 When the installation process completes, you get prompted to log in by using the Administrator account and password.   Step 49 Complete the post-upgrade tasks that are listed in the "Post-Installation Tasks" section.     Post-Installation Tasks After installing Cisco Unified CallManager on your server, you must set some configuration parameters for Cisco Unified CallManager and perform other post-installation tasks before you can begin using it. Perform these tasks for the server that you install and complete the tasks before other servers in the cluster are installed. For post-installation tasks that you must complete after the installation, see Table 6. INSERT TABLE     Changing the Default Cisco Unified CallManager Application User Passwords Cisco Unified CallManager installation sets all Application User passwords to the same Application User password that you entered during installation. Cisco recommends that you log in to Cisco Unified CallManager Administration and change these passwords. Refer to Cisco Unified CallManager System Guide for the procedure for changing a password.   Accessing Cisco Unified CallManager Serviceability To access Cisco Unified CallManager Administration or Cisco Unified CallManager Serviceability, you will need to use a web browser from a PC with network access to the Cisco Unified CallManager server.   Even though all Cisco Unified CallManager services are installed on each server in the cluster, you must manually activate the services that you want to run on each server in the cluster through Cisco Unified CallManager Serviceability. For service recommendations and more information, refer to Cisco Unified CallManager Serviceability Administration Guide and Cisco Unified CallManager Serviceability System Guide.   To activate services through Cisco Unified CallManager Serviceability, follow this procedure:   Procedure Step 1 Open a web browser on a computer with network access to the Cisco Unified CallManager server.   Step 2 Enter the following url:   http://ccm_server:8080/ccmadmin   where ccm_server specifies the IP address or hostname of the Cisco Unified CallManager server.   Step 3 Enter the Cisco Unified CallManager Application user name and password.   Step 4 From the Navigation menu, choose Cisco Unified CallManager Serviceability and click Go.   Step 5 From the menu bar, click Tools > Service Activation.   Step 6 Choose a server from the drop-down menu.   Step 7 Check the Service Names check boxes for the services to activate.   Step 8 Click Save.     Configuring the Database After installing Cisco Unified CallManager, you use Cisco Unified CallManager Administration to begin configuring the database. The Cisco Unified CallManager database contains information and parameters that relate to the system as a whole, to connected devices, and to individual users. The following list describes a few tasks that you must perform in Cisco Unified CallManager Administration or Cisco Unified CallManager Serviceability: 1. In Cisco Unified CallManager Serviceability, activate the services that you want to run on each server in the cluster.   2. Configure system-level settings, such as Cisco Unified CallManager Groups.   3. Design and configure your dialing plan.   4. Configure media resources for conferences, music on hold, and so on.   5. Configure systemwide features, Cisco Unified IP Phone services, Cisco Unified CallManager Extension Mobility, Cisco Unified CallManager Attendant Console, and Cisco Unified CallManager Assistant.   6. Install and configure the gateways.   7. Enable computer telephony integration (CTI) application support; then, install and configure the desired CTI applications.   8. Configure the users.   9. Configure and install the phones; then, associate users with the phones. For more information about configuring the Cisco Unified CallManager database, refer to the Cisco Unified CallManager Administration Guide, the Cisco Unified CallManager System Guide, or online help in the Cisco Unified CallManager application.   Examining Log Files If you encounter problems with the installation, you can obtain and examine the install log files by entering the following commands in Command Line Interface. To obtain a list of install log files from the command line, enter   CLI>file list install   To view the log file from the command line, enter   CLI>file view install log_file   where log_file is the log file name. You can also view logs by using the Cisco Unified CallManager Real-Time Monitoring Tool (RTMT). For more information on using and installing the Cisco Unified CallManager RTMT, refer to the Cisco Unified CallManager Serviceability Administration Guide .   Obtaining Documentation Cisco documentation and additional literature are available on Cisco.com. This section explains the product documentation resources that Cisco offers.   Cisco.com You can access the most current Cisco documentation at this URL: http://www.cisco.com/techsupport You can access the Cisco website at this URL: http://www.cisco.com You can access international Cisco websites at this URL: http://www.cisco.com/public/countries_languages.shtml   Product Documentation DVD The Product Documentation DVD is a library of technical product documentation on a portable medium. The DVD enables you to access installation, configuration, and command guides for Cisco hardware and software products.   The Product Documentation DVD is created and released regularly. DVDs are available singly or by subscription. Registered Cisco.com users can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at the Product Documentation Store at this URL: http://www.cisco.com/go/marketplace/docstore   Ordering Documentation You must be a registered Cisco.com user to access Cisco Marketplace. Registered users may order Cisco documentation at the Product Documentation Store at this URL: http://www.cisco.com/go/marketplace/docstore If you do not have a user ID or password, you can register at this URL: http://tools.cisco.com/RPF/register/register.do   Cisco Product Security Overview   Cisco provides a free online Security Vulnerability Policy portal at this URL: http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html From this site, you will find information about how to do the following: • Report security vulnerabilities in Cisco products   • Obtain assistance with security incidents that involve Cisco products   • Register to receive security information from Cisco A current list of security advisories, security notices, and security responses for Cisco products is available at this URL: http://www.cisco.com/go/psirt To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL: http://www.cisco.com/en/US/products/products_psirt_rss_feed.html   Reporting Security Problems in Cisco Products   Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT: • For emergencies only —  security-alert@cisco.com An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies. • For nonemergencies —  psirt@cisco.com In an emergency, you can also reach PSIRT by telephone: • 1 877 228-7302   • 1 408 525-6532 Tip - We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x. - Never use a revoked encryption key or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL: http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html The link on this page has the current PGP key ID in use. - If you do not have or use PGP, contact PSIRT to find other means of encrypting the data before sending any sensitive material. Product Alerts and Field Notices   Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field Notices. You can receive Cisco Product Alerts and Cisco Field Notices by using the Product Alert Tool on Cisco.com. This tool enables you to create a profile and choose those products for which you want to receive information. To access the Product Alert Tool, you must be a registered Cisco.com user. (To register as a Cisco.com user, go to this URL: http://tools.cisco.com/RPF/register/register.do) Registered users can access the tool at this URL: http://tools.cisco.com/Support/PAT/do/ViewMyProfiles.do?local=en ... View more

Installing Cisco Unified CallManager Release 5.1(1) Because the 5.0(x) release of Cisco Unified CallManager has a different installation framework than previous releases of Cisco Unified CallManager, review all installation instructions carefully before you install Cisco Unified CallManager 5.1(1). This document includes information about installing Cisco Unified CallManager Release 5.1(1) on one server or many servers in a cluster environment. Contents This document contains the following topics: • Installation Overview • Important Considerations • Frequently Asked Questions About the Cisco Unified CallManager Installation • Browser Requirements • Configuring the Hardware • Installing Cisco Unified CallManager • Gathering Information for an Installation • Installing the New Operating System and Application • Post-Installation Tasks • Examining Log Files • Obtaining Documentation • Documentation Feedback • Obtaining Technical Assistance • Obtaining Additional Publications and Information Installation Overview Cisco Unified CallManager 5.0(x) uses a different installation framework than previous releases. The installation process allows you to perform a basic installation, upgrade from Cisco Unified CallManager 4.x to Cisco Unified CallManager 5.1(1), and upgrade to a newer service release during the installation. For a more detailed description of the different installation types, see Table 1. Table 1 Installation Options INSERT TABLE HERE Note: This document describes only the first two installation types: Basic Install and Upgrade During Install. For information on performing a Windows Upgrade, refer to Upgrading Cisco Unified CallManager. Important Considerations Before you proceed with the Cisco Unified CallManager installation, consider the following requirements and recommendations: • Be aware that when you install Cisco Unified CallManager 5.1(1) on an existing server, the hard drive gets formatted, and all existing data on the drive gets overwritten. • Install the Cisco Unified CallManager software on the first node or publisher server first and then on the subsequent nodes. • Make sure that the subsequent node servers that you are installing can connect to the first node server during the installation. • Enter the same security password on all servers in the cluster. • Install the Cisco Unified CallManager software during off-peak hours or a maintenance window to avoid impact from call-processing interruptions. • Configure the server by using static IP addressing to ensure that the server obtains a fixed IP address and that the Cisco Unified IP Phones can register with the application when you plug the phones into the network. • Do not attempt to perform any configuration tasks during the installation. • Do not install any Cisco-verified applications until you complete installing Cisco Unified CallManager on every server in the cluster. • Carefully read the instructions that follow before you proceed with the installation Frequently Asked Questions About the Cisco Unified CallManager Installation The following section contains information about commonly asked questions and responses. Review this section carefully before you complete the Cisco Unified CallManager installation. How long does it take to perform the Cisco Unified CallManager installation? The entire installation process, excluding pre- and post-installation tasks, takes 45 to 90 minutes per server, depending on your server type. Before you install Cisco Unified CallManager, consider the size of your cluster. What Passwords do I Need to Specify? During the Cisco Unified CallManager installation, you must specify the following user names and passowords: • Administrator account You use the Administrator username and password to log in to the following areas: – Cisco Unified Communications Operating System Administration – Disaster Recovery System – Command Line Interface The Administrator login must start with an alphabetic character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. You can change the Administrator password or add a new Administrator account by using the command line interface. See the Cisco Unified Communications Operating System Administration Guide for more information. • Application User password You use the Application User password for the following default application user names: – CCMAdministrator – CCMSysUser – WDSysUser – CCMQRTSysUser – IPMASysUser – WDSecureSysUser – CCMQRTSecureSysUser – IPMASecureSysUser You can change the application user password for each application through Cisco Unified CallManager Administration. See the Cisco Unified CallManager Administration Guide for more information. • Database Access Security Password The system uses this password to authorize communications between nodes, and you must ensure that this password is identical on all nodes in the cluster. The Database Access Security password must start with an alphanumeric character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. Which servers does Cisco support for this installation? For information about the supported servers, refer to the release notes for your version of Cisco Unified CallManager. Click here for Cisco Product Release Notes May I install other software besides Cisco Unified CallManager on the server? For Cisco Unified CallManager 5.1(1), you must do all software installations and upgrades by using the Software Upgrades menu options in Cisco Unified Communications Operating System Administration. The system can upload and process only software that Cisco Systems approved. You cannot install or use third-party or Windows-based software applications that you may have been using with a previous version of Cisco Unified CallManager with Cisco Unified CallManager 5.1(1). What are the Installation Options? • Basic Install This option represents the basic installation and does not use any imported data. • Upgrade During Install This option allows you to upgrade the preinstall software with the latest service release prior to configuring your system. You can also choose Upgrade During Install followed by a Windows Upgrade and perform both during the installation process. Note: Ensure that you have the software image available on DVD or on a remote server prior to choosing this option. • Windows Upgrade This option allows you to import the TAR file that the DMA tool produced while upgrading an existing Cisco Unified CallManager server. Note: 'For more information on performing a Windows Upgrade, see' Upgrading Cisco Unified CallManager. Browser Requirements You can access Cisco Unified CallManager Administration, Cisco Unified CallManager Serviceability, and Cisco Unified Communications Administration by using the following browsers: • Microsoft Internet Explorer version 6.0 or later • Netscape Navigator version 7.1 or later Note: Cisco does not support or test other browsers, such as Mozilla Firefox. Configuring the Hardware As a part of software installation, the system installer configures the system BIOS and RAID settings for the new operating system and Cisco Unified CallManager application. See Table 2 for the BIOS settings and Table 3 for the RAID settings that are set up during installation. Note: If the hardware configuration process fails during installation, you can use boot-time utilities that are found on both the IBM and HP servers to manually configure the RAID and BIOS settings, as shown in Table 2 and Table 3. Table 2 BIOS Configuration Settings for HP and IBM Servers HP Servers IBM Servers OS Selection: Linux (not applicable on newer                           models) OS Selection: Not Applicable Boot Order: CD, C:, Floppy Boot Order: CD, C:,                           Floppy Post F1 prompt: Delayed Post F1 prompt:                           Delayed Hyperthreading: Enabled Hyperthreading:                           Enabled Table 3 RAID Settings MCS 7825 Servers (HP and                 IBM) MCS 7835 Servers (HP and                 IBM) MCS 7845 Servers (HP and IBM) Software Raid Logical Drives: 1 Logical Drives:                 2 Software Raid Note For the HP 7825H1 and the IBM 7825I1, SATA RAID is enabled, and the RAID type specifies 1(1+0), with one logical drive RAID type: 1(1+0) RAID type: 1(1+0) Installing Cisco Unified CallManager The next sections contain the procedures for installing the first and subsequent nodes. Review the following sections carefully before you perform the installation: • Gathering Information for an Installation • Handling Network Errors During Installation • Installing the New Operating System and Application Gathering Information for an Installation Use Table 4 to record the information about your Cisco Unified CallManager server. Gather this information for each Cisco Unified CallManager server that you are installing in the cluster. You may not need to obtain all the information; gather only the information that is pertinent to your system and network configuration. You should make copies of this table and record your entries for each server in a separate table, even if you are planning to use the DMABackupInfo.inf file to configure your system. Note: Because some of the fields are optional, they may not apply to your configuration. For example, you choose not to set up an SMTP host. Caution: You cannot change some of the fields after installation without reinstalling the software, so be sure to enter the values that you want. The last column in the table shows whether a field can be changed after installation, and if so, whether you can change it through Cisco Unified Communications Operating System Administration or through the Command Line Interface (CLI). Table 4 Configuration Data Configuration Data Your                 Entry Can Entry Be Changed After                 Installation Administrator Password Yes. CLI>                 set password admin Application User Password Yes. CLI>                 set password Country Yes. CLI> set                 web-security DHCP Yes. CLI> set network                 dhcp DNS Primary Yes. CLI> set                 network dns DNS Secondary Yes. CLI> set                 network dns Domain Yes. CLI> set network                 domain Domain Name Service DNS Enable NO. Gateway Address Yes Use OS Adminstration > Settings>IP or CLI > set network gateway Host Name NO. IP Address Yes Use OS Adminstration > Settings>IP or CLI > set network IP IP Mask Yes Use OS Adminstration > Settings>IP or CLI > set network ip eth0 Location Yes. CLI> set                 web-security Master Administrator ID NO. NTP Server IP Address Note You can enter up to five NTP servers. Yes Use OS Administration >                 Settings>NTP Servers Organization Yes CLI> set                 web-security Security Password Yes CLI>                 set password security SMTP Location Yes CLI>                 set smtp State Yes CLI> set                 web-security Time Zone Yes CLI> set                 timezone Unit Yes CLI> set                 web-security For more detailed descriptions of each installation field, see Table 5. Table 5 Installation Field Definitions Field Description Usage Administrator ID This field specifies the name that you                 want to assign to this account. Ensure the name is unique; it can contain lowercase, alphanumeric characters, hyphens, and underscores. It must                 start with a lowercase alphanumeric character. For this mandatory                 field, you should record it for use when logging in to the CLI or into Cisco Unified Communications Operating System Administration. Administrator Password This field specifies the password that you use for logging into the the CLI on the platform and for logging into Cisco Unified Communications Operating System Administration. Ensure the password is at least six characters long; it can contain alphanumeric                 characters, hyphens, and underscore. For this mandatory field, you should                 record it for use when logging in to the CLI or into Cisco Unified Communications Operating System Administration. DHCP Dynamic Host Configuration Protocol Choose Yes if you want to use DHCP to automatically configure the network settings on your server. If you choose No, you must enter a hostname, IP Address, IP Mask, and Gateway. DNS Enabled A DNS server represents a device that resolves a hostname into an IP address or an IP address into a hostname. If you do not have a DNS server, enter No. When DNS is not enabled, you should only enter IP addresses (not hostnames) for all network devices in                 your Cisco Unified Communications network. If you have a DNS server,                 Cisco recommends that you enter Yes to enable DNS. Disabling DNS limits the system ability to resolve some domain names. DNS Primary The server contacts this DNS server                 first when it attempts to resolve host names. Enter the IP address of the DNS server that you want to specify as the primary DNS server. Enter the IP                 address in dotted decimal format as ddd.ddd.ddd.ddd where ddd can have a value                 between 0 and 255 (except 0.0.0.0). Consider this field mandatory if DNS is set to yes. DNS Secondary When a primary DNS server fails, the                 server will attempt to connect to the secondary DNS server. In this optional field, enter the IP address of the secondary DNS. Enter the IP address                 in dotted decimal format as ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0). Domain This field represents the name of the domain                 in which this machine is located. Consider this field mandatory if DNS                 is set to yes. First Cisco Unified Communications Manager                 Node This field specifies the first Cisco Unified Communications Manager node that contains the database. Subsequent nodes connect to                 the first node to access database content. The first node also                 synchronizes with an external NTP server and provides time to the other nodes. Choose Yes if you are configuring the first Cisco Unified Communications Manager node in the cluster. If you are configuring subsequent nodes, see Table 4 for information on the different fields. Gateway Address A gateway represents a network point that acts as an entrance to another network. Outbound packets get sent to the gateway that will forward them to their final destination. Enter the IP address of the gateway in the format ddd.ddd.ddd.ddd where ddd can have                 a value between 0 and 255 (except 0.0.0.0) If you do not have a                 gateway, you must still fill in this field by setting it to 255.255.255.255.                 Not having a gateway may limit you to only being able to communicate with devices on your subnet. Host Name A host name represents an alias that is                 assigned to an IP address to identify it. Enter a host name that is unique to your network. The host name can comprise up to 64 characters                 and can contain alphanumeric characters and hyphens. If DHCP is set to No, consider this field mandatory. IP Address This field specifies the IP address of this machine. It will uniquely identify the server on this network. Ensure another machine in this network does not use this IP address. Enter the IP address in the form ddd.ddd.ddd.ddd where ddd can have a value between 0                 and 255 (except 0.0.0.0). If DHCP is set to No, consider this field mandatory. IP Mask This field specifies the IP subnet mask of this machine. The subnet mask together with the IP address define the network address and the host address. Enter the IP mask in the form ddd.ddd.ddd.ddd where ddd can have a value between 0 and 255 (except 0.0.0.0).                 A valid mask should have contiguous '1' bits on left side and                 contiguous '0' bits on the right. For example, a valid mask follows:                 255.255.240.0 (11111111.11111111.11110000.00000000) An invalid mask follows: 255.255.240.240 (11111111.11111111.11110000.11110000) NIC Speed This field specifies the speed of the                 server network interface card (NIC) in megabits per second. The                 possible speeds include 10 or 100. NIC Duplex This field specifies the duplex setting                 of the server NIC. The possible settings include half and full. NTP Server This field identifies the NTP servers                 with which you want to synchronize. Enter the hostname or IP address of one or more NTP server(s). Note You can add additional NTP servers or make changes to the NTP server list at a later time NTP Server Enable When enabled, this server will act as a NTP server and provide time updates to the subsequent nodes in the cluster. Choose Yes if you want to enable this machine to be an NTP server. This option is available only on the first node in a cluster. Security Password Servers in the cluster use the security password to communicate with one another. You will be asked to                 enter the same security password for each subsequent node in the cluster. Enter the security password. Enter the same password in the confirm password field. The password must contain at least six                 alphanumeric characters. It can contain hyphens and underscores, but it must start with an alphanumeric character. Caution You must enter the same password for all nodes in the cluster. Set Hardware Clock This field specifies the date                 and local time for the machine. Note If you set the hardware clock manually, the node does not use an external NTP server for time synchronization. Choose Yes if you want to set the date and local time for the time zone that you chose. Enter the hours based on a                 24-hour format. Note If you configure an external NTP server, the hardware clock gets set automatically. SMTP This field specifies the name of the SMTP host                 that is used for outbound e-mail. Enter the hostname or dotted IP address for the SMTP server. For a host, it can contain alphanumeric                 characters, hyphens, or periods. For a host name, it must start with an                 alphanumeric character. You must fill in this field if you plan to use electronic notification. If not, you can leave it blank. Subnet IP Address By entering a subnet address, you can specify a range of IP Addresses that will be granted access to query this NTP server. Enter an IP subnet that will be granted access to the NTP server During installation, you can only enter two subnets. Subnet Mask This field specifies the subnet mask                 for the subnet address. Enter the subnet mask for the IP subnet. Time zone This field specifies the local                 time zone and offset from Greenwich Mean Time (GMT). Choose Yes if you want to change the time zone. Choose the time zone that most closely matches the location of your machine. Handling Network Errors During Installation During the installation process, the installation program verifies that the server can successfully connect to the network by using the network configuration you enter. If it cannot, a message displays, and you get prompted to select one of the following options: • RETRY — The installation program tries to validate networking again. If validation fails again, the error dialog box displays again. • REVIEW (Check Install)— Allows you to review and modify the networking configuration. The installation program returns to the network configuration windows. • HALT — The installation halts. You can copy the installation log files to a USB disk to aid troubleshooting of your network configuration. • IGNORE — The installation continues. The networking error gets logged. In some cases, the installation program validates networking multiple times, so this error dialog box might display multiple times. Note: Networking is validated after you complete each networking window, so the message might display multiple times. If the message displays while you are reviewing the network configuration windows, choose IGNORE to move to the next window. If you choose REVIEW, the first network configuration window appears again. Installing the New Operating System and Application Use this procedure to begin installing the operating system and Cisco Unified CallManager application: Procedure Step 1 Insert the installation DVD into the tray and restart the server, so it boots from the DVD. After the server completes the boot sequence, the Media Check window displays. Note: If you have a new server with Cisco Unified CallManager preinstalled, you do not need to install from a DVD. Go directly to the "If You Choose Skip" procedure. Step 2 Verify that the checksum that displays on the Media Check matches the checksum for the release on Cisco.com. When the media check completes, the Media Check Result window displays. Step 3 If the Media Check Result displays Pass, choose OK to continue the installation. If the media fails the Media Check, either download another copy from Cisco.com or obtain another disc directly from Cisco Systems. After you choose OK, the system installer performs various hardware checks to ensure you system is correctly configured for Cisco Unified CallManager 5.1(1), including the following checks: – First, the installation process checks for the correct drivers, and you may see the following warning: Drivers not found, do you want to install manually? To continue the installation, choose Yes. – The installation next checks to see whether you have a supported hardware platform. If your server does not meet the exact hardware requirements, the installation process fails with a critical error. If you think this is not correct, capture the error and report it Cisco support. – The installation process next verifies RAID configuration and BIOS settings. If the installation process makes any changes to your hardware configuration settings, you will get prompted to restart your system. After the hardware checks complete, the Overwrite Hard Drive window displays. Step 4 The Overwrite Hard Drive window indicates the current software version on your hard drive, if any, and the version on the DVD. Choose Yes to continue with the installation or No to cancel. Caution If you choose Yes on the Overwrite Hard Drive window, all existing data on your hard drive gets overwritten and destroyed. The Platform Installation Wizard window displays. Step 5 To configure the platform now, choose Proceed. If you want to configure the platform later, choose Skip. – If you want to install and configure the software at this time, choose Proceed and skip to the "If You Choose Proceed" section. – If you want to install the software now and configure it later, choose Skip and continue with the "If You Choose Skip" section. If You Choose Skip Start here if you have a server that has Cisco Unified CallManager preinstalled or if you chose Skip on Platform Installation Wizard window. Step 6 After the system restarts, the Preexisting Installation Configuration window displays. If you have configuration information on a USB drive or on a diskette, insert it now. Note If a popup window states that the system detected new hardware, press any key and then choose Install from the next window.   Note If you have a file that the Data Migration Assistant created, see the Data Migration Assistant User Guide for more information. Step 7 To continue, choose OK. The Platform Installation Wizard window displays. Step 8 To continue with the installation, choose Proceed. The Upgrade During Install window displays. Continue with the "If You Choose Proceed" section. If You Choose Proceed Step 9 Choose the type of installation to perform by doing the following steps. See Table 3 for more information on installation options: a. In the Upgrade During Install window, choose one of the options: • To upgrade to a later Service Release of the software during installation, choose Yes. Continue with the "Upgrade During Install" section. • To skip this step, choose No. • To return to the previous window, choose Back. b. In the Windows Upgrade window, choose No. Note To perform a Windows Upgrade, that is, to upgrade from a Windows version of Cisco Unified CallManager to Cisco Unified CallManager 5.1(1), see Upgrading to Cisco Unified CallManager for more information. c. In the Basic Install window, choose Continue to install the software version on the DVD or configure the preinstalled software. Continue with the "Basic Installation" section. Upgrade During Install If you choose Yes in the Upgrade During Install window, the installation wizard installs the software version on the DVD first and then restarts the system. You then get prompted to enter certain network configuration parameter values and the location of the upgrade file. Step 10 After the system restarts, the Platform Installation Wizard window displays. To continue the installation, choose Proceed. The Upgrade During Install window displays. Note If the installer pops up a window that states that it detected new hardware, press any key and then choose Install from the next window. Step 11 Choose Yes. The Install Upgrade Retrieval Mechanism Configuration window displays. Step 12 Choose the upgrade retrieval mechanism to use to retrieve the upgrade file: – SFTP — Retrieves the upgrade file from a remote server by using the Secure File Transfer Protocol (SFTP). Skip to the "Upgrade From a Remote Server" section. – FTP — Retrieves the upgrade file from a remote server by using File Transfer Protocol (FTP). Skip to the "Upgrade From a Remote Server" section. – LOCAL — Retrieves the upgrade file from a local CD or DVD. Continue with the "Upgrade From a Local Disc" section. Upgrade From a Local Disc Before you can upgrade from a local drive, you must download the appropriate patch file from Cisco.com and copy the file to a CD or DVD. Because of the size of the patch files, you will need to copy it to a DVD in most cases. The patch-file name has the following format: cisco-ipt-k9-patchX.X.X.X-X.tar.gz.sgn Where X.X.X.X-X represents the release and build number Note Do not rename the patch file before you install it because the system will not recognize it as a valid file. Step 13 When the Local Patch Configuration window displays, enter the patch directory and patch name, if required, and choose OK. Note You only need to enter the patch directory when the patch is not stored in the root directory of the CD or DVD. The Install Upgrade Patch Selection Validation window displays. Step 14 The window displays the patch file that is available on the CD or DVD. To update the system with this patch, choose Continue. Upgrade From a Remote Server If you chose to upgrade through an FTP or SFTP connection to a remote server, you must first configure the network settings. The Auto Negotiation Configuration window displays. Step 15 The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) by using automatic negotiation. You can change this setting after installation. – To enable automatic negotiation, choose Yes. The DHCP Configuration window displays. Note: To use this option, your hub or Ethernet switch must support automatic negotiation. – To disable automatic negotiation, choose No. The NIC Speed and Duplex Configuration window displays. Step 16 If you chose to disable automatic negotiation, manually choose the appropriate NIC speed and duplex settings now and choose OK to continue. The DHCP Configuration window displays. Step 17 For network configuration, you can choose to either set up static network IP addresses for the node and gateway or to use Dynamic Host Configuration Protocol (DHCP). – If you have a DHCP server that is configured in your network and want to use DHCP, choose Yes. The system restarts and checks for network connectivity. Skip to the "Retrieving the Remote Patch" section. – If you want to configure static IP addresses for the node, choose No. The Static Network Configuration window displays. Step 18 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 7 for field descriptions. The DNS Client Configuration window displays. Step 19 To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 7 for field descriptions. After the system configures the network and checks for connectivity, the Remote Patch Configuration window displays. Retrieving the Remote Patch Step 20 Enter the location and login information for the remote file server. See Table 7 for field descriptions. After the network restarts, the system connects to the remote server and retrieves a list of available upgrade patches. If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path. For example, if the upgrade file is in the patches directory, you must enter /patches. If the upgrade file is located on a Windows server, check with your system administrator for the correct directory path. The Install Upgrade Patch Selection window displays. Step 21 Choose the upgrade patch to install. The system downloads, unpacks, and installs the patch and then restarts the system running the upgraded software version. After the system restarts, the Preexisting Configuration Information window displays. Using Preexisting Configuration Information Step 22 If you have preexisting configuration information that is stored on a floppy disc or a USB key, insert the disc or the USB key now and choose Continue. The installation wizard will read the configuration information during the installation process. The Platform Installation Wizard window displays. Step 23 To continue with the Platform Installation Wizard, choose Proceed. The Product Installation Configuration window displays. Step 24 To configure the platform now, choose Proceed. Step 25 In the Upgrade During Install window, choose No. Step 26 In the Windows Upgrade window, choose No. Step 27 In the Basic Install window, choose Continue. Continue with the "Basic Installation" section. Basic Installation Step 28 When the Timezone Configuration displays, choose the appropriate time zone for the server and then choose OK. The Auto Negotiation Configuration window displays. Step 29 The installation process allows you to automatically set the speed and duplex settings of the Ethernet network interface card (NIC) by using automatic negotiation. You can change this setting after installation. – To enable automatic negotiation, choose Yes. The DHCP Configuration window displays. Note To use this option, your hub or Ethernet switch must support automatic negotiation. – To disable automatic negotiation, choose No. The NIC Speed and Duplex Configuration window displays. Step 30 If you chose to disable automatic negotiation, manually choose the appropriate NIC speed and duplex settings now and choose OK to continue. The DHCP Configuration window displays. Step 31 For network configuration, you can choose to either set up static network IP address for the node or to use Dynamic Host Configuration Protocol (DHCP). – If you have a DHCP server that is configured in your network and want to use DHCP, choose Yes. The network restarts, and the Administrator Login Configuration window displays. – If you want to configure static IP address for the node, choose No. The Static Network Configuration window displays. Step 32 If you chose not to use DHCP, enter your static network configuration values and choose OK. See Table 7 for field descriptions. The DNS Client Configuration window displays. Step 33 To enable DNS, choose Yes, enter your DNS client information, and choose OK. See Table 7 for field descriptions. The network restarts by using the new configuration information, and the Administrator Login Configuration window displays. Step 34 Enter your Administrator login and password from Table 6. Note The Administrator login must start with an alphabetic character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. You will need the Administrator login to log in to Cisco Unified Communications Operating System Administration, the command line interface, and the Disaster Recovery System. The Certificate Signing Request Information window displays. Step 35 Enter your certificate signing request information from Table 6 and choose OK. The First Node Configuration window displays. Step 36 You can configure this server as either the first node in a Cisco Unified CallManager cluster or as a subsequent node. – To configure this server as the first Cisco Unified CallManager node, choose Yes and continue with the "Configure the First Node" section. – To configure this server as a subsequent node in the cluster, choose No and continue with the "Configure a Subsequent Node" section. Configure the First Node If you chose to configure the server as the first node in the cluster, the Network Time Protocol Client Configuration window displays. Cisco recommends that you use an external NTP server to ensure accurate system time on the first node. Ensure the external NTP server is stratum 9 or higher (meaning stratums 1-9). Subsequent nodes in the cluster will get their time from the first node. Step 37 Choose whether you want to configure an external NTP server or manually configure the system time. – To set up an external NTP server, choose Yes and enter the IP address, NTP server name, or NTP server pool name for at least one NTP server. You can configure up to five NTP servers, and Cisco recommends that you use at least three. Choose Proceed to continue with the installation. The system contacts an NTP server and automatically sets the time on the hardware clock. Note If the Test button displays, you can choose Test to check whether the NTP servers are accessible. – To manually configure the system time, choose No and enter the appropriate date and time to set the hardware clock. Choose OK to continue with the installation. The Database Access Security Configuration window displays. Step 38 Enter the Database Access Security password from Table 6. Note The Database Access Security password must start with an alphanumeric character, be at least six characters long, and can contain alphanumeric characters, hyphens, and underscores. The system uses this password to authorize communications between nodes, and you must ensure this password is identical on all nodes in the cluster. The SMTP Host Configuration window displays. Step 39 If you want to configure an SMTP server, choose Yes and enter the SMTP server name. Note You must configure an SMTP server to use certain platform features; however, you can also configure an SMTP server later by using the platform GUI or the command line interface. The Platform Configuration Confirmation window displays. Step 40 To continue with the installation, choose OK; or to modify the platform configuration, choose Back. When you choose OK, the Application User Password Configuration window displays. Step 41 Enter the Application User Password from Table 6 and confirm the password by entering it again. Step 42 Choose OK. The Cryptographic Export Warning window displays, and the systems installs and configures the software. Step 43 When the installation process completes, you get prompted to log in by using the Administrator account and password. Step 44 Complete the post-upgrade tasks that are listed in the "Post-Installation Tasks" section. Configure a Subsequent Node To configure a subsequent node in the cluster, follow these steps. Caution You must configure a subsequent node on the first node before you install it. From Cisco Unified CallManager Administration on the first node, choose System>Server. For more information, see the Cisco Unified CallManager Administration Guide''. The First Node Access Configuration window displays. Step 45 Enter the First Node Access Configuration information from Table 5. The SMTP Host Configuration window displays. Step 46 If you want to configure an SMTP server, choose Yes and enter the SMTP server name. NOTE: You must configure an SMTP server to use certain platform features. However, you can also configure an SMTP server later by using the platform GUI or the command line interface. The Platform Configuration Confirmation window displays. Step 47 To start installing the software, choose OK, or, if you want to change the configuration, choose Back. Step 48 When the installation process completes, you get prompted to log in by using the Administrator account and password. Step 49 Complete the post-upgrade tasks that are listed in the "Post-Installation Tasks" section. Post-Installation Tasks After installing Cisco Unified CallManager on your server, you must set some configuration parameters for Cisco Unified CallManager and perform other post-installation tasks before you can begin using it. Perform these tasks for the server that you install and complete the tasks before other servers in the cluster are installed. For post-installation tasks that you must complete after the installation, see Table 6. INSERT TABLE Changing the Default Cisco Unified CallManager Application User Passwords Cisco Unified CallManager installation sets all Application User passwords to the same Application User password that you entered during installation. Cisco recommends that you log in to Cisco Unified CallManager Administration and change these passwords. Refer to Cisco Unified CallManager System Guide for the procedure for changing a password. Accessing Cisco Unified CallManager Serviceability To access Cisco Unified CallManager Administration or Cisco Unified CallManager Serviceability, you will need to use a web browser from a PC with network access to the Cisco Unified CallManager server. Even though all Cisco Unified CallManager services are installed on each server in the cluster, you must manually activate the services that you want to run on each server in the cluster through Cisco Unified CallManager Serviceability. For service recommendations and more information, refer to Cisco Unified CallManager Serviceability Administration Guide and Cisco Unified CallManager Serviceability System Guide. To activate services through Cisco Unified CallManager Serviceability, follow this procedure: Procedure Step 1 Open a web browser on a computer with network access to the Cisco Unified CallManager server. Step 2 Enter the following url: http://ccm_server:8080/ccmadmin where ccm_server specifies the IP address or hostname of the Cisco Unified CallManager server. Step 3 Enter the Cisco Unified CallManager Application user name and password. Step 4 From the Navigation menu, choose Cisco Unified CallManager Serviceability and click Go. Step 5 From the menu bar, click Tools > Service Activation. Step 6 Choose a server from the drop-down menu. Step 7 Check the Service Names check boxes for the services to activate. Step 8 Click Save. Configuring the Database After installing Cisco Unified CallManager, you use Cisco Unified CallManager Administration to begin configuring the database. The Cisco Unified CallManager database contains information and parameters that relate to the system as a whole, to connected devices, and to individual users. The following list describes a few tasks that you must perform in Cisco Unified CallManager Administration or Cisco Unified CallManager Serviceability: 1. In Cisco Unified CallManager Serviceability, activate the services that you want to run on each server in the cluster. 2. Configure system-level settings, such as Cisco Unified CallManager Groups. 3. Design and configure your dialing plan. 4. Configure media resources for conferences, music on hold, and so on. 5. Configure systemwide features, Cisco Unified IP Phone services, Cisco Unified CallManager Extension Mobility, Cisco Unified CallManager Attendant Console, and Cisco Unified CallManager Assistant. 6. Install and configure the gateways. 7. Enable computer telephony integration (CTI) application support; then, install and configure the desired CTI applications. 8. Configure the users. 9. Configure and install the phones; then, associate users with the phones. For more information about configuring the Cisco Unified CallManager database, refer to the Cisco Unified CallManager Administration Guide, the Cisco Unified CallManager System Guide, or online help in the Cisco Unified CallManager application. Examining Log Files If you encounter problems with the installation, you can obtain and examine the install log files by entering the following commands in Command Line Interface. To obtain a list of install log files from the command line, enter CLI>file list install To view the log file from the command line, enter CLI>file view install log_file where log_file is the log file name. You can also view logs by using the Cisco Unified CallManager Real-Time Monitoring Tool (RTMT). For more information on using and installing the Cisco Unified CallManager RTMT, refer to the Cisco Unified CallManager Serviceability Administration Guide. Obtaining Documentation Cisco documentation and additional literature are available on Cisco.com. This section explains the product documentation resources that Cisco offers. Cisco.com You can access the most current Cisco documentation at this URL: http://www.cisco.com/techsupport You can access the Cisco website at this URL: http://www.cisco.com You can access international Cisco websites at this URL: http://www.cisco.com/public/countries_languages.shtml Product Documentation DVD The Product Documentation DVD is a library of technical product documentation on a portable medium. The DVD enables you to access installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the HTML documentation and some of the PDF files found on the Cisco website at this URL: http://www.cisco.com/univercd/home/home.htm The Product Documentation DVD is created and released regularly. DVDs are available singly or by subscription. Registered Cisco.com users can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at the Product Documentation Store at this URL: http://www.cisco.com/go/marketplace/docstore Ordering Documentation You must be a registered Cisco.com user to access Cisco Marketplace. Registered users may order Cisco documentation at the Product Documentation Store at this URL: http://www.cisco.com/go/marketplace/docstore If you do not have a user ID or password, you can register at this URL: http://tools.cisco.com/RPF/register/register.do Cisco Product Security Overview Cisco provides a free online Security Vulnerability Policy portal at this URL: http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html From this site, you will find information about how to do the following: C• Report security vulnerabilities in Cisco products • Obtain assistance with security incidents that involve Cisco products • Register to receive security information from Cisco A current list of security advisories, security notices, and security responses for Cisco products is available at this URL: http://www.cisco.com/go/psirt To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL: http://www.cisco.com/en/US/products/products_psirt_rss_feed.html Reporting Security Problems in Cisco Products Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT: • For emergencies only —  security-alert@cisco.com An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies. • For nonemergencies —  psirt@cisco.com In an emergency, you can also reach PSIRT by telephone: • 1 877 228-7302 • 1 408 525-6532 Tip - We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x. - Never use a revoked encryption key or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL: http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html The link on this page has the current PGP key ID in use. - If you do not have or use PGP, contact PSIRT to find other means of encrypting the data before sending any sensitive material. [edit] Product Alerts and Field Notices Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field Notices. You can receive Cisco Product Alerts and Cisco Field Notices by using the Product Alert Tool on Cisco.com. This tool enables you to create a profile and choose those products for which you want to receive information. To access the Product Alert Tool, you must be a registered Cisco.com user. (To register as a Cisco.com user, go to this URL: http://tools.cisco.com/RPF/register/register.do) Registered users can access the tool at this URL: http://tools.cisco.com/Support/PAT/do/ViewMyProfiles.do?local=en [edit] Obtaining Technical Assistance [edit] Obtaining Additional Publications and Information ... View more