Table Of Contents
Release Notes for Cisco IPICS Release 4.0(2)
These release notes describe the new features and caveats for the Cisco IP Interoperability and Collaboration System (Cisco IPICS) release 4.0(2).
For information about caveats that apply to Cisco IPICS release 4.0(2), see the "Caveats" section.
To access the documentation suite for Cisco IPICS, go to the following URL:
You can access Cisco IPICS software upgrades on Cisco Connection Online (CCO) by going to the following URL and, under "Make a selection to continue," clicking Products > Interoperability Systems > Cisco IP Interoperability and Collaboration System, then clicking the link for your Cisco IPICS release:
These release notes contain the following topics:
The Cisco IPICS solution streamlines radio dispatch operations and improves response to incidents, emergencies, and facility events. Cisco IPICS dissolves communication barriers between land mobile radio systems and devices including mobile phones, landline phones, IP phones, and PC users, helping enable communications among users of all devices, wherever they are located. When time is critical, Cisco IPICS delivers information into the hands of the right people, at the right time and in the right format. By providing flexible, scalable communication interoperability, Cisco IPICS enhances the value of existing and new radio, telephony, and IP communications networks.
The Cisco IPICS server and the IDC require specific versions of hardware and software. Cisco IPICS Compatibility Matrix, lists the hardware and software versions that are compatible with this release of Cisco IPICS. Make sure that you check that document for the most current versions of compatible hardware components and software versions for use with Cisco IPICS, and make sure to upgrade your RMS components and SIP and LMR gateways to the latest supported releases before you install this release of Cisco IPICS.
Also make sure to use only the Cisco-supported operating system for use with Cisco IPICS. No other operating system versions are supported
Cisco IPICS Compatibility Matrix is available at the following URL:
For more information about Cisco IPICS, refer to the following documentation.
•Cisco IPICS Server Administration Guide, Release 4.0(2)—Provides information about configuring, operating, and managing the Cisco IPICS server, including how to use the Management Console user interface.
•Cisco IPICS Server Installation and Upgrade Guide, Release 4.0(1)— Describes how to install, configure, and upgrade the Cisco IPICS server software and Cisco IPICS operating system
•Cisco IPICS Dispatch Console User Guide, Release 4.0(2)—Provides information about understanding, installing, operating, and performing other IDC activities
•Cisco IPICS Mobile Client for Apple iPhone Reference Guide—Provides detailed information about the Cisco IPICS Dispatch Console application for the Apple iPhone
•Release Notes for Cisco IPICS Release 4.0(2)—Provides important information about this release of Cisco IPICS Cisco IPICS and its components
•Cisco IPICS Compatibility Matrix—This document contains information about hardware and software that is supported for use with Cisco IPICS
To access the documentation suite for Cisco IPICS, go to the following URL:
What's New in Cisco IPICS
The following sections provide information about new features and functions in Cisco IPICS 4.0(x):
What's New in Cisco IPICS 4.0(2)
New features and functions in Cisco IPICS 4.0(2) include the following:
•ISR G2 LMR gateway
•Text-to-speech in the policy engine
•Ops view functionality—Incidents can now be associated with the ops view that the incident creator is associated with
•IPICS Dispatch Console enhancements:
–Microsoft Windows 7 support
–Increased number of regions
–Increased channel name length
–Configurable video clip size
What's New in Cisco IPICS 4.0(1)
New features and functions in Cisco IPICS 4.0(1) include the following:
•Cisco IPICS Dispatch Console (IDC)—A radio dispatching solution that is designed for critical radio communications. The IDC runs on a standard PC platform and extends push-to-talk (PTT) radio channels so that users with a variety of communication devices can participate in an event. It provides control of radio resources and allows users to monitor and coordinate emergency response across incompatible radio systems and between multiple agencies, jurisdictions, and departments. Key features include the following:
–An intuitive graphical user interface
–Integrated telephony client for incoming and outgoing calls
–Radio to telephone patching
–Receive and transmit on-screen indicators for channel activity
–Handset, headset, or desktop microphone operation
–Individual channel mute/All mute
–Instant recall recording per channel
–Last call transmit
–Confirmation tones for trunked systems
–Unit ID/talker ID
•Cisco IPICS Mobile Client—Standalone application that runs on an Apple iPhone, provides access to an incident VTG and supporting media, and allows users to add journals, videos and pictures to an incident.
•High Availability—Cisco IPICS 4.0 supports an optional hot standby server to provide high availability with no single point of failure. If a primary server fails, the secondary server automatically takes over service.
•Loop Prevention— Cisco IPICS automatically identifies potential audio loops and resolves them before they become an issue.
•Radio Pooling—Enables grouping Cisco IPICS radio assets into logical radio pools.
•Enhanced API—A web service API enables integration of Cisco IPICS with third-party applications, such as command and control physical security information management (PSIM) and computer aided dispatch (CAD) applications.
Installing Certificates on an IDC Client PC
By default, IDC client PCs authenticate the Cisco IPICS server by using a self-signed certificate that is generated when the Cisco IPICS server software is installed. If you replace the self-signed certificate on the server with a third-part party certificate, perform the following steps on each IDC client PC that access the Cisco IPICS server. This procedure is not needed of you are using the default self-signed certificate.
Before you begin
Make sure that certificates are installed on the Cisco IPICS server as explained in the "Managing Server Certificates" section in Cisco IPICS Server Installation and Upgrade Guide.
Step 1 Copy the following files from the Cisco IPICS server to the client PC:
Step 2 On the client PC, take these actions:
a. Rename root_ca.cert.pem to root_ca.crt.
b. Rename intermediate_ca.cert.pem to intermediate_ca.crt.
c. Rename signed_server.cert.pem to hostname.crt, where hostname is the hostname of the Cisco IPICS server.
Step 3 On the client PC, take these actions for each .crt file that you renamed in the previous step:
a. Double-click the file name.
b. Click Install Certificate to launch the Windows Certificate Import Wizard.
c. Click Next.
d. Click Place all certificates in the following trust store.
e. Choose Trusted Root Certification Authorities.
f. Click Next.
g. Click Finish.
Step 4 Restart the IDC if it is running.
Changing the Password for a Trusted Certificate
This section describes how to change the default keystore password for trusted certificates.
Before you begin
Make a backup copy of the truststore or keystore that you will modify.
Step 1 On the Cisco IPICS server, enter these commands to stop all Cisco IPICS services:
a. [root]# ssh root@ipics-server, where ipics-server is the host name or IP address of the Cisco IPICS server.
b. [root]# cd /opt/cisco/ipics/security/security.properties
c. [root]# service ipics stop-all
Step 2 Use the following command to change the password:
[root]# cp server.keystore.p12 server.keystore.p12.bkup
[root]# keytool -storepasswd -keystore server.keystore.p12
Enter keystore password: Old password
New keystore password: New password
Re-enter new keystore password: New password
Step 3 Update the security.properties file with the password that you changed.
For example, if you edited the keystore, you might update this file as follows:## Cisco IPICS - Advanced Security Configuration## You may customize the x500 settings, passwords, and/or key# strength, and re-run './security-manager' to regenerate your# local self-signed certificates. Be aware that the keystore# password must match the private key password!#Note: If you change the keystore and/or truststore passwords, be# sure to also fix server.xml in tomcat/conf otherwise tomcat# cannot start-up.##Wed Aug 04 00:41:34 GMT 2010certValidity=1095x500OrginizationName=Cisco Systems, Inc.providerName=x500OrginizationalUnit=PSBUproviderClass=keyAlgorithm=RSAprotectedFlag=falsetruststorePassword=changeitx500LocalityName=San Josex500Country=USsigAlgorithm=privateKeyPassword=changeitsshPort=22x500Emailfirstname.lastname@example.orgOption=keystoreType=PKCS12enableSynchronizeTrust=falsekeystorePassword=changeittruststoreType=JKSproviderArg=x500StateName=CaliforniakeySize=2048
Step 4 Take these actions to update the server.xml file with the password that you changed.
a. Enter this command:
[root]# cd /opt/cisco/ipics/tomcat/current/conf
Step 5 Update the line with the truststore or keystore you changed. For example, if you edited the truststore, you might update this file as follows:<Connector port="8443"maxHttpHeaderSize="4096"ciphers="SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_RC4_128_SHA,SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DH_DSS_WITH_3DES_EDE_CBC_SHA,SSL_DH_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA,SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA,TLS_KRB5_WITH_3DES_EDE_CBC_MD5, TLS_KRB5_WITH_3DES_EDE_CBC_SHA,TLS_KRB5_WITH_RC4_128_MD5, TLS_KRB5_WITH_RC4_128_SHA,TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA"maxThreads="500" minSpareThreads="25" maxSpareThreads="75"enableLookups="false" disableUploadTimeout="true"acceptCount="100" scheme="https" secure="true"clientAuth="false" sslProtocol="TLS"keystoreFile="/opt/cisco/ipics/security/server.keystore.p12"keystoreType="PKCS12"keystorePass="changeit"truststoreFile="/opt/cisco/ipics/security/server.truststore.jks"truststoreType="JKS"truststorePass="changeit"connectionTimeout="60000" />
Step 6 On the Cisco IPICS server, enter this command to start all Cisco IPICS services:
[root]# service ipics start-all
Using Cisco IOS Release 15.0(1)M4
In your Cisco IPICS deployment, use Cisco IOS release 15.0(1)M4 on routers that function as LMRG and RMS components. This release addresses the following issues:
•Allows the "Go Ahead" tone to be heard when making a transmission on a secure digital channel
•Eliminates audio clipping that occurred when multiple channel or talk group resources were included in a VTG
•Enables DTMF key transmission from IDC remote users to relay properly from the RMS to all other participants in the same or associated talk groups.
Table 1 describes caveats in this release of Cisco IPICS.
You can use the Bug Toolkit to find information about caveats for the this release, including a description of the problems and available workarounds. The Bug Toolkit lists both open and resolved caveats.
To access Bug Toolkit, you need the following items:
•Cisco.com user ID and password
To use the Bug Toolkit, follow these steps:
Step 1 To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Step 2 Log in with your Cisco.com user ID and password.
Step 3 To look for information about a specific problem, enter the bug ID number in the Search for bug ID field, then click Go.
Step 4 To look for information if you do not know the bug ID number:
a. Choose Security from the Select Product Category menu.
b. Choose the desired product from the Select Product menu.
c. Choose the version number from the Software Version menu.
d. Under Advanced Options, choose Use default settings or Use custom settings. The default settings search for severity 1, 2 and 3 bugs, open and fixed bugs, and only bugs containing bug details. Use the custom settings to change the severity and status parameters, or to search for keywords within the bug headline and description.
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information about obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Copyright © 2011 Cisco Systems, Inc. All rights reserved.