Table Of Contents
Release Notes for Cisco IPICS Release 2.1(1)
Contents
Introduction
Overview
Cisco IPICS Components
User Roles
System User Roles and Groups
Cisco IPICS Support Team Communications
System Requirements
Server Requirements
PMC Requirements
Determining the Software Version
Compatibility Matrix
Related Documentation
New and Changed Information
Server Installation Guidelines
Server Upgrade Guidelines
Backup and Restore Guidelines
Guidelines for Choosing a Destination for Database Backups
PMC Installation and Upgrade Guidelines
Cisco IPICS Security Enhancements
Cisco IPICS Server Enhancements
Support for Tone-Controlled Radios
Cisco IPICS Policy Engine Notification Enhancements
Serviceability and Usability Enhancements
Logging Updates
PMC Management Enhancement
Cisco Unified IP Phone Enhancements
Support for Network Time Protocol
Cisco IPICS PMC Enhancements
Overview
Introducing the 36-Channel Radio Console Skin
Support for Channel Selector Buttons
Support for RFC 2198 and RFC 2833 Packets
Support for Anchored Channels
Logging Updates
Upgrading to Cisco IPICS Release 2.1(1)
Support for Additional Hardware Platforms
Support for Additional Cisco Unified IP Phone
Update to the Cisco IPICS RMS Configuration
Important Notes
Using Cisco Security Agent with the PMC
Establishing PMC Connectivity with the RMS for SIP-Based Remote Connections
Cisco IPICS Usage and Licensing Guidelines
Browser Guidelines
Server Usage Guidelines
PMC Usage Guidelines
License Guidelines
Cisco IPICS Voice Quality Tips
Resolved Caveats for Cisco IPICS - Release 2.1(1)
Using Bug Toolkit
Saving Bug Toolkit Queries
Open Caveats for Cisco IPICS - Release 2.1(1)
Documentation Updates
Errors
Correction to the Channel Status Information in the Cisco IPICS Server Administration Guide and the Server Online Help
Changes
Omissions
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco IPICS Release 2.1(1)
September 28, 2007
These release notes describe the new features and caveats for the Cisco IP Interoperability and Collaboration System (hereafter referred to as Cisco IPICS) and the Push-to-Talk Management Center (hereafter referred to as PMC) release 2.1(1).
Note 
To view all of the release notes for Cisco IPICS, go to: http://www.cisco.com/en/US/products/ps7026/
tsd_products_support_series_home.html
Before you install Cisco IPICS, Cisco recommends that you review the "Important Notes" section for information about issues that may affect your system.
For a list of the open and resolved caveats for Cisco IPICS release 2.1(1), see the "Resolved Caveats for Cisco IPICS - Release 2.1(1)" section and the "Open Caveats for Cisco IPICS - Release 2.1(1)" section. Updates for these release notes occur with every maintenance release and major release.
To access the documentation suite for interoperability systems products, refer to the following URL:
http://www.cisco.com/en/US/products/ps7026/
tsd_products_support_series_home.html
You can access some of the Cisco IPICS software upgrades on Cisco Connection Online (CCO) at the following URL:
http://www.cisco.com/cgi-bin/tablebuild.pl/ipics
Contents
These release notes contain the following topics:
•Introduction
•System Requirements
•Compatibility Matrix
•Related Documentation
•New and Changed Information
•Important Notes
•Resolved Caveats for Cisco IPICS - Release 2.1(1)
•Open Caveats for Cisco IPICS - Release 2.1(1)
•Documentation Updates
•Obtaining Documentation, Obtaining Support, and Security Guidelines
Introduction
This section provides an introduction to the Cisco IPICS product. It includes the following topics:
•Overview
•Cisco IPICS Components
•User Roles
•System User Roles and Groups
•Cisco IPICS Support Team Communications
Overview
The Cisco IPICS solution provides a cost-effective and highly-efficient IP standards-based solution to enable voice interoperability among disparate systems. By interconnecting voice channels, talk groups, and virtual talk groups (VTGs), Cisco IPICS bridges communications from radio networks to the Cisco IPICS Push-to-Talk Management Center (PMC) PC application and supported models of Cisco Unified IP Phones.
Cisco IPICS release 2.1(1) includes enhancements to provide support for Tone Remote Control (TRC) functionality. Tone Remote Control (also known as Tone Control) refers to the use of a sequence of audible tones (inband tone sequences) to control a radio that is connected to a Land Mobile Radio (LMR) gateway (typically a base station). This control can be used, for example, to tune the radio to a different frequency (change the channel).
Note Be aware that the version of Cisco IOS software that is required to support the tone remote control functionality may not be available when Cisco IPICS release 2.1(1) becomes available. For updated availability information, refer to the Cisco IPICS Compatibility Matrix.
In this release, Cisco IPICS provides support for tone-controlled radios by enabling the definition of radio channels in the Cisco IPICS server configuration and implementing a 36-channel radio console skin in the PMC.
Each radio channel that you define in the server represents a physical radio that can be configured with one or more operational tones, including high level guard tones (HLGT), function tones (such as channel select and channel scan), and low level guard tones (LLGT). The high level guard tone is usually the first tone in a preamble, or the sequence of tones that precedes a transmission. The high level guard tone is set at high volume to alert the radio that a function tone will follow. The function tone follows the high level guard tone and causes the radio to perform a specific function, such as selecting a new transmit frequency. The low level guard tone is used as a hold tone or keying tone.
This radio-specific enhancement enables the PMC to send RFC 2198 and RFC 2833 packets to control tone sequences on a per-channel basis. RFC 2833 dual-tone multifrequency (DTMF) is supported for the generation of DTMF signals when these signals have been previously configured in the server via the tone descriptors and associated to Cisco IPICS channels.) RFC 2198 and RFC 2833 improve reliability by guaranteeing that tones play out in the proper sequence and by making the system more resilient to packet loss conditions.
Although the Cisco IPICS server manages the resources and notifies the PMC and other components about defined radio channels and radio control tones, only the PMC can interoperate with and control these radios. When the PMC transmits on a defined radio channel, it generates defined radio control tones via RFC 2833 packets that flow to the LMR gateway. In the LMR gateway, these encoded packets are converted into audible tones and output via the configured E&M interface to the physical radio.
With these enhancements, Cisco IPICS release 2.1(1) extends the Cisco IPICS solution by allowing customers to more completely use their radios with Cisco IPICS.
Note You can find information about RFC 2198 and RFC 2833, along with various Requests for Comment (RFCs), by accessing the RFC repository that is maintained by the Internet Engineering Task Force (IETF) at the following URL: http://www.ietf.org/rfc.html.
Where to Find More Information
•Cisco IPICS Server Administration Guide, Release 2.1(1)
•Cisco IPICS PMC Installation and User Guide, Release 2.1(1)
Cisco IPICS Components
The Cisco IPICS solution comprises the following major components, as described in Table 1:
Table 1 Cisco IPICS System Components
Component
|
Description
|
Cisco IPICS Server
|
This component provides the core functionality of the Cisco IPICS system. The Cisco IPICS server software runs on the Cisco Linux operating system on selected Cisco Media Convergence Server (MCS) platforms. (Refer to the Cisco IPICS Compatibility Matrix for information about the servers that Cisco IPICS supports.)
The Cisco IPICS server software includes the Cisco IPICS Administration Console, which is an incident management framework graphical user interface (GUI) that enables dynamic resource management for users, channels, and VTGs. (In Cisco IPICS, VTGs combine one or more channels and/or users.) By using this GUI, authorized Cisco IPICS users can manage the system configuration and authentication and security services, policies and privileges, and database information.
The server also enables control of the configuration of the media resources that are installed in the router and which are used for audio mixing capabilities.
In addition, the server hosts the Cisco IPICS policy engine, which enables telephony dial functionality and maintains responsibility for the management and execution of policies and user notifications.
The Cisco IPICS server supports several different user roles. For more information, see the "User Roles" section. The server also supports several different system user roles and groups. For more information, see the "System User Roles and Groups" section.
|
Push-to-Talk Management Center (PMC)
|
The PMC is a PC-based audio application that simulates a handheld radio to enable PTT functionality for PC users. It connects Cisco IPICS users via an IP network to enable participation in and monitor of one or more talk groups or VTGs at the same time. The PMC is supported for use only with the Windows XP operating system.
The PMC includes several skins that allow PMC users to change the appearance of the PMC user interface. These skins may include Cisco-provided skins or a custom skin.
|
Gateways
|
This component includes LMR gateways, which functionality is usually installed as an additional feature in a supported Cisco router. LMR gateways provide voice interoperability between radio and non-radio networks by bridging radio frequencies to IP multicast streams. They also provide keying signals to key radio transmissions.
Cisco IPICS leverages the Cisco Hoot 'n' Holler feature, which is enabled in specific Cisco IOS versions, to provide radio integration into the Cisco IPICS solution. LMR is integrated by providing an ear and mouth (E&M) interface to a radio or other PTT devices, such as Nextel phones. Configured as a voice port, this interface provides the appropriate electrical interface to the radio. You configure this voice port with a connection trunk entry that corresponds to a voip dial peer, which in turn associates the connection to a multicast address. This configuration allows you to configure a corresponding channel in Cisco IPICS, using the same multicast address, which enables Cisco IPICS to provide communication paths between the desired endpoints.
|
Router Media Service
|
The Router Media Service (RMS) component enables the PMC to remotely attach to a VTG. This component also provides support, through its loopback functionality, for remotely attaching (combining) two or more VTGs. The RMS provides support for mixing multicast channels in support of VTGs and for mixing remote PMC SIP-based (unicast) connections to a multicast channel or VTG. In addition, the RMS component provides support for unicast M1:U12:M2 connection trunks. The RMS can be installed as a stand-alone component (RMS router) or as an additional feature that is installed in the LMR gateway.
For a list of Cisco IOS versions that Cisco IPICS supports for use as an RMS, refer to the Cisco IPICS Compatibility Matrix. (Each supported Cisco IOS version includes the Cisco Hoot `n' Holler feature.)
|
Networking Components
|
The Cisco IPICS solution may include some or all of the following network components, depending on the functionality that you require: routers, gateways, switches, firewalls, mobile access routers, wireless access points, and bridges.
|
Cisco Unified Communications Manager and VoIP Services
|
Cisco IPICS provides support for SIP-based interoperability with supported versions of Cisco Unified Communications Manager (formerly known as Cisco CallManager) and a Cisco router that is running a supported version of Cisco IOS with Cisco Unified Communications Manager Express (formerly known as Cisco Unified CallManager Express) to enable selected Cisco Unified IP Phone models to participate in channels and VTGs.
These applications help extend the reach of PTT technology to the IP network by enabling these phones to work with Cisco IPICS as IP phone multicast client devices. They also serve as the SIP provider for the Cisco IPICS policy engine to provide SIP telephony support for calls to and from the dial engine.
|
Note For the most updated information about supported hardware and software that is compatible for use with Cisco IPICS, refer to the Cisco IPICS Compatibility Matrix.
Where to Find More Information
•Cisco IPICS Server Administration Guide, Release 2.1(1)
•Cisco IPICS PMC Installation and User Guide, Release 2.1(1)
User Roles
Every Cisco IPICS user is assigned one or more roles. The Cisco IPICS solution authorizes access to different features based on the role that is assigned to each user. In this way, roles help to provide system security.
Table 2 describes the user roles that Cisco IPICS supports.
Table 2 Cisco IPICS User Roles
User Role
|
Description
|
System Administrator
|
The system administrator is responsible for installing and setting up Cisco IPICS resources, such as servers, routers, multicast addresses, locations, and PTT channels. The system administrator also creates ops views, manages the Cisco IPICS licenses and PMC versions, and monitors the status of the system and its users via the activity log files. The system administrator has the ability to administer all resources in the Cisco IPICS system.
|
Ops View Administrator
|
The ops view administrator capabilities include managing and monitoring the activity logs that are filtered by ops views and accessible in the Administration Console (Administration > Activity Log Management) window.
|
Operator
|
The operator is responsible for setting up and managing users and policies, configuring access privileges, and assigning user roles, and ops views. Policy management activities include create/modify/delete policies, view policies, execute policies, and activate privileges.
|
Dispatcher
|
The dispatcher is responsible for setting up inactive VTGs, activating the VTGs to begin groups or conferences, and adding and/or removing participants in VTGs. The dispatcher also monitors the active VTGs and events, can mute and unmute PMC users, as necessary, and manages policies, which activate and/or deactivate VTGs based on specific criteria and designated intervals. Policy management activities include create/modify/delete policies, view policies, execute policies, and activate privileges.
|
User
|
The Cisco IPICS user may set up personal login information, download the PMC application, configure the PMC skin, and specify communication preferences that are used to configure audio devices. By using a predefined user ID and profile, the user can participate in PTT channels and VTGs by using the PMC, supported models of Cisco Unified IP Phones, and the Public Switched Telephone Network (PSTN) via the telephony dial functionality of the policy engine.
|
All
|
This role is equivalent to being assigned each of the above Cisco IPICS roles.
|
Where to Find More Information
•Cisco IPICS Server Administration Guide, Release 2.1(1)
•Cisco IPICS Server Installation and Upgrade Guide, Release 2.1(1)
•Cisco IPICS PMC Installation and User Guide, Release 2.1(1)
System User Roles and Groups
This release of Cisco IPICS supports the system user roles and system groups, as described in Table 3.
Table 3 Cisco IPICS System User Roles and System Groups
System User Roles and System Groups
|
Description
|
ipics linux group
|
Members of this group have full permission to Cisco IPICS server folders, files, and scripts that are related to the Cisco IPICS application and database backup and restore operations. Members of this group include the ipicsadmin, ipicsdba, and informix users.
|
informix linux group
|
Members of this group have full permission to Cisco IPICS server folders, files, and scripts that are related to the Informix database application. Members of this group include the informix and ipicsdba users.
|
root user
|
The Cisco IPICS Linux user that has access to all files in the Cisco IPICS server. Strong passwords are enforced and Linux operating system password expiration rules apply to this user ID.
|
ipics user
|
The Cisco IPICS application-level user ID that can perform all administration-related tasks via the Cisco IPICS Administration Console. Cisco IPICS creates this web-based user ID during the software installation process.
|
ipicsadmin user
|
The Cisco IPICS Linux user that, as part of the ipics linux group, has full permission to the Cisco IPICS server folders, files, and scripts that are related to the Cisco IPICS application and database backup and restore operations. In addition, the ipicsadmin user has permission to read and write data from and/or to the Informix database. Cisco IPICS creates this Linux system user ID during the software installation process. The password for this user ID never expires.
|
ipicsdba user
|
The Cisco IPICS Linux user that belongs to both the informix linux group, which includes full permission to the Cisco IPICS database server folders, files, and scripts, and the ipics linux group, which includes permission to Cisco IPICS application-related folders, files, and scripts. In addition, the ipicsdba user has permission to read data, write data, create tables, and create databases in the Informix database instance. Cisco IPICS creates this Linux system user ID and generates the password during the software installation process. The password for this user ID never expires. To access the ipicsdba user, log in to the Cisco IPICS server by using the root user ID; then, enter su - ipicsdba (substitute user from root).
|
informix user
|
The Cisco IPICS Linux user that belongs to both the informix linux group, which includes full permission to the Cisco IPICS database server folders, files, and scripts, and the ipics linux group, which includes permission to Cisco IPICS application-related folders, files, and scripts. In addition, this user has full administrative permission to the Informix database instance. Cisco IPICS creates this Linux system user ID and generates the password during the software installation process. The password for this user ID never expires. To access the informix user, log in to the Cisco IPICS server by using the root user ID; then, enter su - informix (substitute user from root).
|
Where to Find More Information
•Cisco IPICS Server Installation and Upgrade Guide, Release 2.1(1)
•Cisco IPICS Server Administration Guide, Release 2.1(1)
•Cisco IPICS PMC Installation and User Guide, Release 2.1(1)
Cisco IPICS Support Team Communications
The Cisco IPICS Support Team provides an external mailing list that you can use to obtain additional support directly from the Cisco IPICS engineering team. To subscribe to this mailing list, create an email that includes "subscribe" in the subject line; then, send the email to the following address:
ask-ipics-support@external.cisco.com
Whenever you need additional support, or if you have questions about Cisco IPICS, send your request to ask-ipics-support@external.cisco.com.
A Cisco IPICS engineer will respond to your email to provide you with the assistance that you need.
System Requirements
The Cisco IPICS server and the PMC require specific versions of hardware and software. This section contains information about systems requirements for the Cisco IPICS server and PMC components; it includes the following sections:
•Server Requirements
•PMC Requirements
Server Requirements
Hardware
For a list of supported hardware platforms, including Cisco Media Convergence Servers (MCS), Cisco IPICS-Mobile Platforms, and Cisco routers and gateways that you can use with Cisco IPICS, refer to the Cisco IPICS Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/products/ps7026/
tsd_products_support_series_home.html
Note Make sure that you install and configure Cisco IPICS release 2.1(1) only on a supported Cisco platform.
Software
For a list of the software that is supported for use with Cisco IPICS, refer to the Cisco IPICS Compatibility Matrix.
Note You must use only the Cisco-supported operating system for use with Cisco IPICS. No other operating system versions are supported.
PMC Requirements
Hardware
The PMC supports minimum hardware requirements that depend on the number of active PME channels that you use. For information about the PMC minimum hardware requirements that Cisco IPICS supports, refer to the Cisco IPICS Compatibility Matrix.
Note•The Cisco IPICS system allows you to turn on or turn off logging for individual PMC log files and set the debug log levels.
•To use the logging functionality, Cisco IPICS requires sufficient free disk space on the PMC client machine; that is, when the PMC detects that only 100 MB of disk space is available on the PMC client machine, it displays a warning message to alert you, and when the PMC detects only 50 MB of free disk space, it stops logging data to the log files.
Caution Because of the large amount of information that the system collects and generates when you set all of the debug options, Cisco recommends that you use debug logging only to isolate specific problems. When your debugging tasks have been completed, be sure to turn off debug logging by clearing the debug log. For more information, refer to the "Using the PMC Application Logs" chapter in the
Cisco IPICS PMC Installation and User Guide, Release 2.1(1).
Software
In this release, Cisco IPICS supports the use of only Windows XP Professional SP2 on the PMC client machine.
Note Make sure that you install the PMC application on a PC that has the required Windows operating system installed.
Where to Find More Information
•Cisco IPICS Compatibility Matrix
•Cisco IPICS PMC Installation and User Guide, Release 2.1(1)
Determining the Software Version
The current version of the Cisco IPICS server software displays in the upper left corner of the Administration Console. You can also locate the server version information by clicking the About link that is located in the upper right corner of the Administration Console.
To see the version information for the PMC application, click the Menu button or right-click in the PMC interface to see a list of options; then, click About. The version information for your PMC application displays. Alternatively, you can access the Settings > Status menu to see version information for the PMC.
Compatibility Matrix
You can find the list of the hardware and software versions that are compatible with this release of Cisco IPICS by referring to the Cisco IPICS Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/products/ps7026/
tsd_products_support_series_home.html
Note Make sure that you check the Cisco IPICS Compatibility Matrix for the most current versions of compatible hardware components and software versions for use with Cisco IPICS. Be sure to upgrade your RMS components and SIP and LMR gateways to the latest, supported releases before you install this release of Cisco IPICS.
Related Documentation
For more information about this release of Cisco IPICS, refer to the following documentation:
•Cisco IPICS PMC Quick Start Reference Card, Release 2.1(1)—This document provides tips and quick references for the most frequently used procedures that a user can perform on the Cisco IPICS PMC.
•Cisco IPICS PMC Debug Reference Quick Start Card, Release 2.1(1)—This document provides a quick reference for troubleshooting and debugging the Cisco IPICS PMC.
•Cisco IPICS PMC Command Line Interface, Release 2.1(1)—This document describes the commands that you can use from the command line interface (CLI) to obtain information or to change settings for the Cisco IPICS PMC.
•Cisco IPICS Server Administration Guide, Release 2.1(1)—This document contains information about the key configuration, operation, and management tasks for the Cisco IPICS server.
•Cisco IPICS Server Quick Start Guide, Release 2.1(1)—This document is a condensed version of the Cisco IPICS Server Administration Guide to help the administrator to quickly get started with Cisco IPICS.
•Cisco IPICS Server Quick Start Reference Card, Release 2.1(1)—This document provides tips, quick references, and usage guidelines for the Cisco IPICS server.
•Using Cisco IPICS on Your IP Phone Quick Start Reference Card, Release 2.1(1)—This document contains information about accessing Cisco IPICS from your IP phone and tips and guidelines for using this service.
•Using the Cisco IPICS TUI Quick Start Reference Card, Release 2.1(1)—This document describes the steps that you follow to dial in to, or receive a call from, the policy engine telephony user interface (TUI) and guidelines for using the system.
•Cisco IPICS Radio and Tone Descriptor File Examples Reference Card, Release 2.1(1)—This document contains examples of valid and invalid radio control and signaling descriptor file entries and guidelines for creating these entries.
•Cisco IPICS Server Installation and Upgrade Guide, Release 2.1(1)—This document describes how to install, configure, and upgrade the Cisco IPICS server software and Cisco IPICS operating system.
•Cisco IPICS Server Quick Start Installation Reference Card, Release 2.1(1)—This document provides tips and quick references for installing and upgrading the Cisco IPICS server.
•Cisco IPICS Troubleshooting Guide, Release 2.1(1)—This document contains reference material about how to maintain and troubleshoot the Cisco IPICS system.
•Release Notes for Cisco IPICS Release 2.1(1)—This document contains a description of the new and changed features, important notes, caveats, and documentation updates for this release of Cisco IPICS.
•Cisco IPICS 2.1(1) Resources Card (Documentation Locator)—This document provides a summary of the documentation that is available for this release of Cisco IPICS.
•Solution Reference Network Design (SRND) for Cisco IPICS Release 2.1(1)— This document provides information about design considerations and guidelines for deploying the Cisco IPICS solution.
•Cisco IPICS Compatibility Matrix—This document contains information about compatible hardware and software that is supported for use with Cisco IPICS.
To access the documentation suite for Cisco IPICS, refer to the following URL:
http://www.cisco.com/en/US/products/ps7026/
tsd_products_support_series_home.html
New and Changed Information
The following sections describe the new features that are available and pertinent to this release of Cisco IPICS. These sections may include configuration tips for the administrator, information about users, and where to find more information.
•Server Installation Guidelines
•Server Upgrade Guidelines
•Backup and Restore Guidelines
•PMC Installation and Upgrade Guidelines
•Cisco IPICS Security Enhancements
•Cisco IPICS Server Enhancements
•Cisco IPICS PMC Enhancements
•Upgrading to Cisco IPICS Release 2.1(1)
•Support for Additional Hardware Platforms
•Support for Additional Cisco Unified IP Phone
•Update to the Cisco IPICS RMS Configuration
Server Installation Guidelines
This section contains information about the guidelines that apply to Cisco IPICS release 2.1(1) server installation procedures.
As a best practice, make sure that you adhere to the following guidelines when you perform Cisco IPICS server installation procedures:
•If your server includes more than one network interface card (NIC), make sure that you configure the eth0 network interface, as documented in the Cisco IPICS Server Installation and Upgrade Guide, Release 2.1(1). Cisco IPICS requires that you configure the eth0 interface, even if it is disabled, because the Cisco IPICS licensing mechanism performs its validation by using this NIC. Therefore, to ensure proper system operation, always configure the eth0 interface.
•Use the MAC address of the eth0 interface to obtain your license. To obtain the MAC address of the eth0 interface, enter the following command:
[root]# ifconfig eth0
•To obtain a license for your server, navigate to the following URL: http://www.cisco.com/go/license. (You need the Product Authorization Key (PAK) that shipped with your Cisco IPICS product package.)
–You may use valid Cisco IPICS release 2.0(x) license(s) for use with release 2.1(1).
•Always log in to the Cisco IPICS server with root user privileges before you begin the server installation or uninstallation process.
•Make sure that you do not press the SysRq key when you are about to start the Cisco IPICS operating system installation or at any time during the installation process. If you press the SysRq key while you are installing the operating system, a kernel panic error occurs. To resolve this problem, you must restart the system with a hard reboot.
•Cisco recommends that you perform server installation tasks during a maintenance window or other off-peak hours to minimize service interruptions to users.
•The server installation process requires that you use the applicable Cisco IPICS operating system that is compatible with the version of server software that you are installing.
Note You must use only the Cisco-supported operating system for use with Cisco IPICS. No other operating system versions are supported.
•The Cisco IPICS installation requires a minimum of 2 GB of memory on the Cisco IPICS server and Cisco IPICS-Mobile Platform. You can check the amount of memory that is installed on your hardware platform by entering the following command from the root user account:
[root] #top
The amount of memory that is installed displays as shown in the example below:
Mem: 2055448k av, 1490160k used, 565288k free, 0k shrd, 142344k
buff
To exit, press Ctrl-C.
•Cisco IPICS does not support a Redundant Array of Disks (RAID) on Cisco MCS 7825 servers. When you install the Cisco IPICS operating system on Cisco MCS 7825 servers, you must disable both the Serial ATA (SATA) controller option and the virtual install disk option to disable RAID before you install the operating system.
•The Cisco IPICS operating system software installation is GUI-based and must be run from a directly-connected console terminal.
–During this installation, the installer prompts you for the root user password.
–Cisco IPICS enforces password aging for the root user (180-day password expiration) and the enforcement of password complexity, or strong passwords, that must adhere to the following rules for password creation.
Strong passwords must be at least eight characters long and include the following elements:
At least one lower case letter
At least one upper case letter
At least one number
At least one of the following special characters:
@ [ ] ^ _ ` ! " # $ % & ' ( ) * + , - . / : ; { < | = } > ~ ?
•The Cisco IPICS server software installation program uses a text-based interface; you can install this software from a directly-connected console terminal or by remotely accessing the system via SSH Secure Shell client software (or similar software).
–During this installation, the installer prompts you for the ipics and ipicsadmin user passwords.
–Cisco IPICS enforces strong passwords that must adhere to the following rules:
Strong passwords must be at least eight characters long and include the following elements:
At least one lower case letter
At least one upper case letter
At least one number
At least one of the following special characters:
@ [ ] ^ _ ` ! " # $ % & ' ( ) * + , - . / : ; { < | = } > ~ ?
•Make sure that you follow the exact instructions in the Cisco IPICS Server Installation and Upgrade Guide, Release 2.1(1) to mount and copy the contents of the Cisco IPICS server software CD on to the server.
•To start the server software installation, enter the following command:
[root]# bash <installerfilename>.run
where:
<installerfilename>.run specifies the name of the installer file.
•To complete the server software installation, log in by using the ipics user ID and password. Then, upload and apply the license file(s) to the server by navigating to the Administration > License Management window. (You must upload the license file to use the Administration Console features.)
•In this release, the default run level has been changed from run level 5 (GUI mode) to run level 3 (console mode).
•The Cisco IPICS server supports the following installation and/or upgrade options. (The options that the installer displays may differ depending on the current software version that is running on your system.)
–Install—This option installs the Cisco IPICS server software and the Cisco Security Agent (CSA) software.
–Upgrade—This option allows you to upgrade your server software.
•After you install the server software, make sure that you generate the PMC installer so that the installation file is associated with the correct server IP address. To generate the PMC installer, log in to the Administration Console. and navigate to PMC Management > PMC Installer. From this window, you can generate a new PMC installation file.
Note The Cisco IPICS server software includes the PMC application. You need to generate the PMC installer after the first time that you install the server software and after subsequent PMC application updates that include software fixes.
Where to Find More Information
•Cisco IPICS Server Installation and Upgrade Guide, Release 2.1(1)
•Cisco IPICS Server Administration Guide, Release 2.1(1)
Server Upgrade Guidelines
This section contains information about the guidelines that apply to Cisco IPICS release 2.1(1) server upgrade procedures.
As a best practice, make sure that you adhere to the following guidelines when you perform Cisco IPICS server installation and upgrade procedures:
•Verify the versions of Cisco IPICS that are compatible for upgrade before you upgrade your system. For the most recent version information, refer to the Cisco IPICS Compatibility Matrix.
•Make sure that you have the installation CDs that pertain to both the Cisco IPICS release 2.1(1) server software and the Cisco IPICS release 2.0(1) operating system software.
•Before you upgrade your system, make sure that you have available another Linux-based server or a Windows-based PC or server to back up your data.
–To back up your data files to a remote Linux-based server that supports the Linux Secure Copy (scp) command, use the remote host option.
–To back up your data files to a remote host that does not support scp, such as a Windows-based PC or server, use the local directory option; then, use the SSH Secure Shell Client software, or similar software, to perform a secure copy (scp) to the Windows-based machine.
•Follow the sequence of steps to upgrade the operating system (if necessary) and server software, as documented in the Cisco IPICS Server Installation and Upgrade Guide, Release 2.1(1).
•Make sure that you have valid license(s) for this release. This release supports the use of valid Cisco IPICS release 2.0(x) license(s).
When you upgrade your system, be aware that the options that the installer displays may differ depending on the current software version that is running on your system:
•When you run the Cisco IPICS installer and it does not detect an existing installation of the Cisco IPICS server software, the installer does not display any installation and/or upgrade options (Install/Upgrade/Quit). In this situation, the installer automatically invokes the install option and installs the Cisco IPICS server software on your system.
•When you run the Cisco IPICS installer and it detects an existing version of the Cisco IPICS server software that is part of the supported upgrade path, the installer displays the full installation menu; that is, Install/Upgrade/Quit.
–If you choose the Install option in this situation, the installer removes the existing version of the Cisco IPICS server software and installs the new version of software.
Note Be aware that your data is not preserved during this process. Therefore, make sure that you first back up your data before you perform a new installation.
–If you choose the Upgrade option, your data is preserved and your system is upgraded to the latest version.
•When you run the Cisco IPICS installer and it detects an existing version of the Cisco IPICS server software that is not part of the supported upgrade path, a warning message displays to inform you that your data will be lost if you proceed.
–If you choose to proceed, the installer invokes the install option and installs the Cisco IPICS server software on your system.
Note Be aware that your data is not preserved during this process. Therefore, make sure that you first back up your data before you perform a new installation.
Where to Find More Information
•Cisco IPICS Server Installation and Upgrade Guide, Release 2.1(1)
•Cisco IPICS Compatibility Matrix
Backup and Restore Guidelines
This section contains information about the guidelines that apply to Cisco IPICS release 2.1(1) backup and restore procedures. It also includes information about guidelines to follow for choosing the database backup destination in the "Guidelines for Choosing a Destination for Database Backups" section.
Cisco IPICS includes the following options for database backups:
•Manual backups—At any time, you can perform a manual database backup to capture the current state of the Cisco IPICS database. To perform a manual backup, navigate to the Administration > Database Management > Database Backup window and click the Backup Now button.
•Scheduled backups—By default, Cisco IPICS backs up the database daily. This backup runs at a predefined time and Cisco IPICS stores the backup in a predefined location. You can change the time, frequency, and/or location of the scheduled backup.
As a best practice, make sure that you adhere to the following guidelines when you perform Cisco IPICS backup and restore procedures:
•To ensure data integrity in the event of system failure, Cisco recommends that you back up your files to a remote host location.
•For optimum performance, Cisco recommends that you back up your database during periods of low activity or other off-peak hours. If you perform a backup during periods of high activity, the length of time that it takes to complete this operation may be significantly increased.
•Cisco recommends that you regularly check the database logs for status messages and/or error information that may be pertinent to recent backup and recovery activity.
–To view the backup log, navigate to the Administration > Database Management > Database Backup window. Log entries display in the Backup Log pane.
–To view and/or download the database logs, navigate to the Administration > Database Management > Log window.
•To help ensure the security of your data, Cisco IPICS does not support the use of different user IDs for remote backup and restore operations that you perform on the same data set. Therefore, when you restore your data, make sure that you specify the same user ID as the one that you used to back up your data. If you specify a different user ID, the restore procedure does not succeed because of file accessibility issues; in this situation, Cisco IPICS displays "permission denied" error messages in the db-maintenance.log. As a best practice, Cisco recommends that you designate a specific user ID that you can use for all of your remote backup and restore activities.
Guidelines for Choosing a Destination for Database Backups
Be aware of the following guidelines when you choose a destination for your Cisco IPICS backups:
•Cisco recommends that you choose the remote host option when you back up your database. Using the remote host option ensures that you have a location for your database backups that will not be affected by Cisco IPICS server hardware or software failures.
•As an extra safeguard, you can also copy or move a database backup from one remote host to another for redundancy purposes.
•Manually perform a database backup to a remote host destination before you uninstall, reinstall, or upgrade the Cisco IPICS server software to preserve your most recent data.
•When you reinstall the Cisco IPICS operating system software on your server, the installation process formats the hard drive and removes all data from your server. To prevent the loss of your backup data, make sure that you have available another Linux-based server or a Windows-based PC or server to back up your database.
–Choose the remote host option only if the remote host supports the Linux Secure Copy (scp) command, such as a Linux server. To back up your data to a remote host that does not support scp, such as a Windows-based PC or server, choose the local directory option; then, use the SSH Secure Shell Client software, or similar software, to perform a secure copy (scp) to the Windows-based machine.
Where to Find More Information
•Cisco IPICS Server Administration Guide, Release 2.1(1)
PMC Installation and Upgrade Guidelines
Be aware of the following PMC version guidelines:
•Cisco IPICS does not support the use of previous PMC releases with a Cisco IPICS release 2.1(1) server. That is, you must use PMC release 2.1(1) with a Cisco IPICS server that also has release 2.1(1) installed.
•When a PMC that is running version 2.0(2) or earlier logs in to a 2.1(1) server, Cisco IPICS forces the PMC to upgrade to the 2.1(1) supported version.
•If you try to use a pre-2.1(1) version of the PMC with a server that has release 2.1(1) installed, the PMC pops up a message to alert you of the version mismatch. In this situation, you must access the Cisco IPICS server via your browser to download and then install the 2.1(1) version of the PMC.
•Support for full PMC upgrades (including PMC online help and skin files) between major releases, such as 2.0 and 2.1, requires that you uninstall the 2.0 PMC and then install the 2.1 PMC by accessing the server via your browser. This action allows for the installation of the latest PMC online help and skin files.
This section includes information about the guidelines that apply to Cisco IPICS release 2.1(1) PMC installation and upgrade procedures:
•Be sure to install the PMC application on a client machine on which the required Windows operating system is already installed and be aware of the hardware requirements for your PMC client machine. For more information about software and hardware requirements, see the "PMC Requirements" section.
•To obtain the PMC application for installation on your client machine, access the Cisco IPICS server and download the software from the Home > Download PMC window.
•The PMC installation involves downloading the self-extracting PMC installation program, which includes the PMC installation and configuration files along with the PMC skins. If you are authorized to use alert tones, the PMC installation program may also include alert tones (or they may be downloaded separately).
•When you install the PMC application, the installation automatically adds an entry to the Windows Start menu for "Cisco IPICS PMC" along with a desktop shortcut. You can access the Start menu shortcut by navigating to Start > Programs > Cisco IPICS > PMC.
•You do not need to be connected to the server to install the PMC application software.
•If you have an existing version of the PMC on your client machine, make sure that you close the PMC application before you install a new version.
•Upon login, the Cisco IPICS server provides information to the PMC about available versions; the PMC then performs a check for version compatibility and determines whether the PMC must be upgraded.
•You do not need the fully executable file to completely update the PMC. The PMC automatic upgrade process may install only the PMC.dll file or it may install other components as well, depending on the contents of the package. The contents of the update package determine whether the PMC skins, alert tones, and online help are also updated as part of the automatic update process.
•Cisco IPICS provides the capability for the PMC to log in to the primary or alternate server if the primary becomes unavailable. To log in to the PMC, enter or choose the server IP address or host name, followed by your user ID and password.
Note Be aware that login user names and server host names are case-insensitive; that is, you can enter either upper case or lower case characters for these names. However, passwords are case-sensitive.
•The PMC retrieves your configuration data from the Cisco IPICS server, which maintains the most current information.
•The PMC can maintain multiple versions, current and previous, of the PMC application to enable quick reversion to an earlier compatible version, if necessary.
•When you have Cisco Security Agent (CSA) installed on the PMC client machine, be aware that you may be prompted with CSA access permission dialog boxes for various operations that you are trying to perform. Whenever CSA prompts you for permission, while you are performing any operation on the PMC, be sure to always click Yes to grant permission and continue with that operation. For more information about using CSA, refer to the Cisco Security Agent documentation at the following URL: http://www.cisco.com/en/US/products/sw/secursw/ps5057
/tsd_products_support_series_home.html
Where to Find More Information
•Cisco IPICS PMC Installation and User Guide, Release 2.1(1)
Cisco IPICS Security Enhancements
This release of Cisco IPICS includes the following server security enhancements:
•Cisco IPICS now supports password encryption when you perform a remote host backup operation.
•For additional security, this release now accepts the establishment of only Secure Shell (SSH) version 2 connections to the Cisco IPICS server and has removed support for SSH version 1.
•Reconfiguration that sets the ForwardX11 parameter to "no" to prevent the SSH client from automatically sending X-Windows system information across the network.
•Requirement to use medium or strong encryption ciphers (128 bits or greater) within Transport Layer Security (TLS) sessions and discontinuance of support for weak and null encryption ciphers (less than 128 bits).
•Modification of the server debug log file to no longer display dial-in user ID and password values.
•To protect data integrity, all Cisco IPICS server components now use the restricted ipicsadmin account to access the Informix database.
Cisco IPICS Server Enhancements
This section describes the new features and enhancements that this release implements and includes information about the following topics:
•Support for Tone-Controlled Radios
•Cisco IPICS Policy Engine Notification Enhancements
•Serviceability and Usability Enhancements
•Logging Updates
•PMC Management Enhancement
•Cisco Unified IP Phone Enhancements
•Support for Network Time Protocol
Support for Tone-Controlled Radios
The Cisco IPICS server has been enhanced to include the following new features in support of tone-controlled radios:
•Support for a new radio channel connection type in the Cisco IPICS Administration Console.
•Capability to define a tone-controlled radio in the Cisco IPICS server and enable assignment of a radio channel connection type to an end-user.
–Each radio channel that the administrator defines in the server represents a physical radio that can be configured with one or more tone sequences.
–These tone sequences are used to control various tones and functionality on the radio.
–Each tone sequence includes parameters, such as the frequency or frequencies, volume (RF power), and duration, that are necessary to generate a specific tone and invoke an action on the radio.
•Ability to associate and disassociate a tone-controlled radio with user(s).
•Enhancement to channel and user associations to include radio configuration and enable system administrator management of the following entities via the Cisco IPICS server Administration Console:
–Radio Profile Management—To manage radio profiles, navigate to the Configuration > Radios window. This functionality includes the ability to define multiple radio profiles for a single channel so that the same channel can reside on multiple radio profiles. This window includes support for list pagination.
–Tone/Signal Management—To manage tones and signals, navigate to the Configuration > Channels > <channel name> Associations > Signals window.
–Channel Association with Radio Profile—To associate channels with radio profiles, navigate to the Configuration > Channels > <channel name> Associations window.
–User Association with Radio Profile—To associate users with radio profiles, navigate to the User Management > Users > <user name> > Associations > Radios window.
•Capability to add, update, or delete a radio descriptor file or a tone descriptor file via the Cisco IPICS server Administration Console:
–Radio/Tone Descriptor Management—To manage radio and tone descriptor files, navigate to the Configuration > Descriptors window. The Cisco IPICS server includes sample radio and tone descriptor files that you can use as a guide if you need to create additional descriptor files for your specific radio hardware. This window includes support for list pagination.
–Radio descriptors are .xml files that contain commands that control radio functionality. For each radio capability, the radio descriptor defines the tones that are sent to the radio to enable or disable that capability. The radio descriptor files include channel selectors, which are used to change the frequency on a radio, and control functions, which may be stateful (such as power settings and encryption on/off) or simple/momentary controls, such as monitor and scan.
–Tone descriptors are .xml files that define a sequence of momentary controls and signals that transmit over-the-air. These tones and signals can be associated with one or more Cisco IPICS channels. Unlike momentary controls, signals do not cause the radio to change configuration; instead, signals are treated like voice and transmitted over the currently-tuned radio channel frequency.
–Cisco IPICS supports only RFC 2833 for tone control sequences and a maximum of six tones per control sequence.
–Cisco IPICS supports a maximum of six consecutive RFC 2833 tones for signaling tone sequences. However, you can enter additional tones by separating them with a pause (such as 1 millisecond (ms) or a DTMF entry (such as digit 1 for 200 ms). There is no limit to the number of DTMF entries that are allowed in a signaling tone sequence, and these entries can co-exist with RFC 2833 tone entries.
–When you send DTMF digits, be sure to configure a delay between the digits as required by local specifications. Most US specifications require an interdigit delay of at least 40 ms.
–Pauses are defined by a tone with a frequency of zero; for example, <Rfc2833Tone db="0" frequency="0" duration="40" />
•Enable the configuration of specific user radio permissions:
–The system administrator can select the level of permission that pertains to each individual radio channel selector button.
–Because channel permissions are configured separately from radio channel selector button permissions, PMC users who have access to a radio may be able to use all, or only some, of the channel selector buttons.
–The server configuration determines the order in which the PMC displays the radio channel selector buttons on the PMC.
–If the system administrator does not configure any radio channel selector buttons for a user, the user is able to listen to the channel but is not able to change the channels or control the radio.
Cisco IPICS Policy Engine Notification Enhancements
The Cisco IPICS policy engine implements the following new features and enhancements in this release:
•The Cisco IPICS policy engine includes a new notification action, which sends notifications to designated recipients who are not configured as Cisco IPICS users and provides them with information that you specify.
Note This feature is not configurable via the Cisco IPICS Administration Console. Instead, you must configure one or more dedicated dial servers, which are Cisco IPICS servers that perform the dial-out functionality to the external recipients.
The external notification action performs the following actions:
–Simultaneously calls many external users at telephone numbers that Cisco IPICS obtains from a file that you specify.
To designate a recipient list, you create an .xml file that contains the telephone numbers of all users who you want to contact.
–Plays a designated message to each user who answers the call.
To designate a message file, you create a .wav file that contains the message that you want to play to the recipients.
To invoke the external notification, you send an HTTP request or a Common Alerting Protocol (CAP) .xml file to the appropriate dedicated dial server.
–Captures results of each call in a log file that you can review at any time.
•In this release, the Cisco IPICS policy notification feature includes the following new action types:
–IP Phone Notification—This type of notification displays a designated message on supported Cisco Unified IP Phones.
–Dial Notification—This notification calls out to designated users and plays the selected prompt or sends a message to the Cisco Unified IP Phones of the designated users and plays automatically on the speaker of the phone.
–Talk Group Notification—This type of notification plays out the selected prompt to all users in the VTG.
•When you configure a new policy notification action, the Message notification types now include the following options: Email, IP Phone Text, Dial, Talk Group, and Dial Engine Script.
•Cisco IPICS now includes the capability for the dispatcher to enter specific notification subject and body text when sending a notification to participants from the VTG Management > Virtual Talk Groups window.
•This release includes the ability to export executing and executed policy history to a Microsoft Excel format. To download the execution status history, navigate to the Policy Management > Execution Status window and click the Download Execution Status button. You can either open the file or save the file to a location of your choice and then open it by using Microsoft Excel to view the report.
Serviceability and Usability Enhancements
This release includes the following serviceability and usability enhancements:
•The addition of server software installation history information in the Serviceability > Diagnostics window that includes the date and time that the current version of server software was installed along with a history of installation and uninstallation activity.
•Ability to specify a timeout period for the Cisco IPICS Administration Console browser session in the Administration > Options window.
The default setting specifies 30 minutes.
•Improved system startup performance by decreasing the Cisco IPICS application installer Kudzu utility default timeout period from 3600 seconds to 30 seconds.
•The addition of Quality of Service (QoS) markings to voice packets to reduce latency and improve voice quality.
•Support for up to 50,000 users defined in the database.
Logging Updates
Cisco IPICS implements enhanced capabilities and flexibility for the Cisco IPICS activity logs by enabling the following updates:
•Updated logging capability to track the creation, removal, and update of radios and their related associations.
•Ability to parse new activity log messages from the PMC.
PMC Management Enhancement
Cisco IPICS provides support for the following PMC management enhancement in this release:
•Ability to facilitate the prestaging of PMC downloads so that users can upgrade their PMC versions before you upgrade the server software.
–This process enhances PMC download management and alleviates the burden of long PMC downloads to all users at one time.
–Before you upgrade the Cisco IPICS server software, you can set up a new version of the latest, supported PMC so that the PMC download process is staged.
–When the PMC users log in and connect to the server, the latest PMC version is automatically downloaded.
–After users have downloaded the latest PMC version, you perform the procedure to upgrade the server software. The upgrade program changes the state of the PMC from staged to recommended and makes the PMC available for use.
Cisco Unified IP Phone Enhancements
The following Cisco Unified IP Phone enhancements are included in this release:
•Capability to specify whether an IP phone times out after a configured period of inactivity, forcing the user to log in again. To configure this timeout period, navigate to the Administration > Options window.
The default setting specifies 45 minutes.
–Ability to configure whether the Cisco IPICS service requires users to log in before they access the service from a Cisco Unified IP Phone.
You can configure the Cisco IPICS service so that it does not prompt for user login credentials on the Cisco Unified IP Phone and automatically activates a channel or VTG if only one channel or VTG is assigned.
If the Cisco IPICS service is configured to bypass the user login and if there is only one channel or VTG that is assigned, Cisco IPICS automatically activates that channel or VTG.
If the Cisco IPICS service is configured to bypass the user login and if there are more than one channel or VTG that is assigned, Cisco IPICS displays the list of these channels and VTGs on the IP phone.
–On some model IP phones, the administrator may add a special parameter to the Cisco IPICS server URL configuration to enable the display of the Logout softkey while IP phone users are connected to a channel or VTG. This enhancement simplifies user operation by allowing users to access the Logout softkey from the main display screen.
Support for Network Time Protocol
In this release, Cisco IPICS provides support for Network Time Protocol (NTP) in the following situations:
•Permanent (purchased) licenses—This release of Cisco IPICS supports NTP when NTP is used with Cisco IPICS permanent licenses.
•Time-bound (evaluation or demonstration) licenses—Time-bound licenses also support the use of NTP, however, be aware that updates that alter the system date may cause the Cisco IPICS license to become invalidated if the installed license has an explicitly defined start date.
Where to Find More Information
•Cisco IPICS Server Installation and Upgrade Guide, Release 2.1(1)
•Cisco IPICS Server Administration Guide, Release 2.1(1)
Cisco IPICS PMC Enhancements
The Cisco IPICS PMC has been enhanced to include support for tone-controlled radios. This support includes enhanced functionality in the LMR gateway that enables support for RFC 2198 and RFC 2833 standard messages.
This section includes the following topics:
•Overview
•Introdu
