Guest

Cisco IP Interoperability and Collaboration System

Release Notes for Cisco IPICS Release 4.8(1)

  • Viewing Options

  • PDF (224.1 KB)
  • Feedback

Table of Contents

Release Notes for Cisco IPICS Release 4.8(1)

Contents

Overview

What’s New in Cisco IPICS

System Requirements

Related Documentation

Important Notes

Node Manager Configuration Files

Trust Certificates

Cisco Instant Connect MIDlet Upgrade Consideration

Feature Notes

Caveats

Using the Bug Search Tool

Known Caveats

Obtaining Documentation, Obtaining Support, and Security Guidelines

Release Notes for Cisco IPICS Release 4.8(1)

Revised May, 2014

These release notes describe the new features and caveats for the Cisco IP Interoperability and Collaboration System (Cisco IPICS) release 4.8(1).

To access the documentation suite for Cisco IPICS, go to the following URL:

http://www.cisco.com/en/US/products/ps7026/tsd_products_support_series_home.html

You can access Cisco IPICS software on Cisco Connection Online (CCO) by going to the following URL and, under “Make a selection to continue,” clicking Products > Cisco IP Interoperability and Collaboration System , then clicking the link for your Cisco IPICS release:

http://www.cisco.com/cisco/software/navigator.html?mdfid=280723930&flowid=7120

Contents

These release notes contain the following topics:

Overview

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.

What’s New in Cisco IPICS

Cisco IPICS 4.8(1) includes these major new features:

  • New unified media engine
  • Call assurance feature for Cisco Instant Connect for Android Devices, which automatically reconnects Cisco Instant Connect users to talklines if data connectivity is lost
  • Optimized multi-threading media processing for improved audio processing
  • Faster channel activation
  • Standards-based RTCP talker ID
  • Session refresh, which maximizes resources
  • Various updates to the Cisco IPICS Dispatch Console (IDC), including:

New media engine, which provides faster activation and clearer audio

Simplified patching, which prevents VTGs and incidents from being patched together, avoiding unwanted patches and feedback

Updates to various features and functionality that are accessible through the IDC user interface

System Requirements

The Cisco IPICS server requires 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,

In addition, 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:

http://www.cisco.com/en/US/products/ps7026/products_device_support_tables_list.html

Related Documentation

For more information about Cisco IPICS, refer to the following documentation.

  • Cisco IPICS Server Administration Guide, Release 4.8— Provides information about configuring, operating, and managing the Cisco IPICS server, including how to use the Management Console user interface.
  • Cisco IPICS Installation Guide and Upgrade, Release 4.8(1) — Describes how to instal or upgrade Cisco IPICS and perform related tasks
  • Cisco Instant Connect for Android Devices User Guide, Cisco IPICS, Release 4.8 —Provides detailed information about Cisco Instant Connect for Android devices
  • Cisco Instant Connect MIDlet Reference Guide, Cisco IPICS release 4.7 —Describes how to configure and use the Cisco Instant Connect MIDlet (the 4.7 version of this document applies to release 4.8)
  • Cisco IPICS Compatibility Matrix —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:

http://www.cisco.com/en/US/products/ps7026/tsd_products_support_series_home.html

Important Notes

The following sections describe important issues that apply to this release:

Node Manager Configuration Files

The system stores these node manager configuration files:

  • nodemanager.pri. ip_address .tar—Tape-archive format (tar) file that contains a snapshot of the node manager installation directory (/opt/cisco/nodemanager) from the primary Cisco IPICS server. In this file name, ip_address is the IP address of the primary Cisco IPICS server.
  • nodemanager.sec. ip_address .tar—Applies to a high availability deployment only. Tar file that contains a snapshot of the node manager installation directory (/opt/cisco/nodemanager) from the the secondary Cisco IPICS server. In this file name, ip_address is the IP address of the secondary Cisco IPICS server.

Situations in which you might need to manually restore these files include the following:

  • An error or unexpected interruption occurs during the configuration of the high availability server causes the server no longer allows log in Cisco IPICS Administration Console
  • The /opt/cisco/nodemanager directory on the currently active server is corrupted or deleted

To restore the node manager configuration files, follow these steps:

Procedure


Step 1 Use an SSH client to access the server on which the Cisco IPICS backup is located, log in as the root user, and enter these commands to extract the node manager backup file to a /tmp directory:

a. # cd /tmp

b. To extract the file for the primary Cisco IPICS server, enter this command, where path is the full backup directory path and ip_address is the IP address of the primary Cisco IPICS server:

# tar xvf path /nodemanager.pri. ip_address .tar nodemanager/conf/ipicsNode.properties

To extract the file for the secondary Cisco IPICS server, (in a high availability deployment only), where path is the full backup directory path and ip_address is the IP address of the secondary Cisco IPICS server:

# tar xvf path /nodemanager.sec. ip_address .tar nodemanager.sec. ip_address
.informix/conf/ipicsNode.properties

Step 2 Log in as the root user to the Cisco IPICS server on which the node manager property file is to be manually restored and enter these commands to back up the current node manager properties file:

# cd /opt/cisco/nodemanager/conf

# /bin/cp -p ipicsNode.properties ipicsNode.properties.save

Step 3 Enter this command to replace the current node manager configuration file with the file that you extracted in Step 1:

# /bin/cp -p /tmp/ipicsNode.properties

Step 4 Enter these commands to restart Cisco IPICS:

# service ipics stop-all

# service ipics start-all


 

Trust Certificates

The system stores these trust certificate files:

  • security.pri. ip_address .tar—Tar file that contains a snapshot of the Cisco IPICS security directory (/opt/cisco/ipics/security) from the primary Cisco IPICS server. This directory contains all self-signed certificates and third-party certificates for Cisco IPICS. In this file name, ip_address is the IP address of the primary Cisco IPICS server.
  • nodemanager.sec. ip_address .tar—Applies to a high availability deployment only. Tar file that contains a snapshot of the Cisco IPICS security directory (/opt/cisco/ipics/security) from the secondary Cisco IPICS server. This directory contains all self-signed certificates and third-party certificates for Cisco IPICS. In this file name, ip_address is the IP address of the secondary Cisco IPICS server.

Situations in which you might need to manually restore these files include the following:

  • The /opt/cisco/ipics/security directory on the active Cisco IPICS server is corrupted or deleted
  • The server trust setup is accidentally reinitialized

To restore the certificate files, follow these steps:

Procedure


Step 1 Use an SSH client to access the server on which the Cisco IPICS backup is located, log in as the root user, and enter these commands to extract the security tar file to a /tmp directory:

a. # cd /tmp

b. To extract the files for the primary Cisco IPICS server, where path is the full backup directory path and ip_address is the IP address of the primary Cisco IPICS server:

# tar xvf path /security.pri. ip_address .tar

To extract the files for the secondary Cisco IPICS server, (in a high availability deployment only), where path is the full backup directory path and ip_address is the IP address of the primary Cisco IPICS server:

# tar xvf path /security.sec. ip_address .tar

Step 2 Log in as the root user to the Cisco IPICS server on which the security directory is to be manually restored and enter these commands to back up the current security directory:

# cd /opt/cisco/ipics

# tar cvf security.tar.save security

Step 3 Enter this command to replace the trust certificate files with the files that you extracted in Step 1:

# /bin/cp -rp /tmp/security/* /opt/cisco/security

Step 4 Enter this command to restart Cisco IPICS:

# service ipics restart


 

Cisco Instant Connect MIDlet Upgrade Consideration

Cisco Instant Connect MIDlet users should log out of Cisco IPICS before you upgrade the Cisco Instant Connect MIDlet by unsubscribing and subscribing to the service from Cisco Unified Communications Manager. If any users are not logged out, you must manually disconnect them from Cisco IPICS before they can log in to the new Cisco IPICS version. To manually disconnect Cisco Instant Connect MIDlet users, go to the Administration > Active Users window in the Cisco IPICS Administration Console.

Feature Notes

  • The call assurance functionality for Cisco Instant Connect for Android Devices release 4.8 is supported with the UMS only.
  • To simplify deployment and avoid audio loop scenarios, the nested VTG feature has been deprecated. The IDC prevents including VTGs and incidents in a patch.
  • High availability for the DFSI is not part of the 4.8 general release. If you require this functionality, contact your Cisco representative.
  • P25 Supplementary services such as unit call, call alert, and message are not supported in the 4.8 general release. If you require this functionality, contact your Cisco representative.
  • Channel attenuation on the IDC dialer is not supported in the 4.8 release. For channel attenuation options that use third-party audio hardware, contact your Cisco representative.

Caveats

The following sections provide information about caveats in this Cisco IPICS release:

Using the Bug Search Tool

You can use the Bug Search Tool to find information about caveats (bugs) for this release, including a description of the problems and available workarounds. The Bug Search Tool lists both open and resolved caveats.


Note Bug Search Tool is the successor to the Bug Toolkit.


To use the Bug Search Tool, follow these steps:

Procedure


Step 1 Go to https://tools.cisco.com/bugsearch/ .

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 field, then press Enter .

Step 4 To look for information if you do not know the bug ID number, enter keywords which search for text matches in the following sections of a bug:

  • headline/title
  • release note text
  • product
  • known affected releases/ known fixed releases


 

For more information about the Bug Search Tool, click Help on the main Bug Search Tool page:

https://tools.cisco.com/bugsearch/

Known Caveats

Table 1 describes known caveats in this Cisco IPICS release.

 

Table 1 Known Caveats

Headline
Description

CSCum13312

Some remote channels in VTG may not get audio; transmit is OK

CSCun37992

Remote IDC and multicast IDC crashed after EMG alert received from a radio on an ISSI channel

CSCun38117

Remote IDC cannot disconnect unit calls then unit calls will not connect

CSCun49099

Resource leak on UMS, IPICS/UMS resources are not cleaned

CSCun53456

Android: Disable user audio get update issues when user is in PTT screen

CSCun64223

Rx (no media) stuck with VTG across RMS and UMS after restarting UMS

CSCun77570

Android: Cannot get new SIP connection after IPICS failover

CSCun95654

Audio level never change when drag up/down IDC master volume slide

CSCun98734

After UMS restart, P25 gateway mode channel cannot be latched intermittently

CSCuo00875

Switching from WiFi to cellular and vice versa causes bad noise

CSCuo05422

IncidentMediaViewer hang (remote IDC after videos playing post IPICS failover)

CSCuo09893

After UMS restart, RIDC channels end up with multiple SIP connections

CSCuo10333

Remote IDC channels may not power-up again after disable/enable LAN

CSCuo12564

IDC “Related Incidents” in channel do not show correct incident name

CSCuo12680

MIDC media service failure, communication stopped unexpectedly

CSCuo15386

Splash screen installed: primary IPICS VM off ; IDC cannot log in

CSCuo20546

Shows incorrect concurrent mobile endpoint users under Licence Management

CSCuo20635

IDC detail view does not show participants if they are group members

CSCuo22797

RIDC cannot power on VTG/channel stuck in gold ring

CSCuo22820

All Talk progress bar is not shown if it is configured in complex keys

CSCuo23203

Joystick all talk: Audio does not start on all channels until key release

CSCuo24598

IDC does not relearn reprovisioned P25 channel

CSCuo25318

Remote IDC crashes reported

CSCuo27840

Power off active UMS causing channels reconnection on/off with no ending

CSCuo28049

IDC caches old RX talkerId values even after logout/login

CSCuo30706

Cannot power up P25 native mode if user with unit ID but without supplementary service CALL

CSCuo30730

Loud static noise on 8941/8945/6945 when IDC dialer put the call on hold

CSCuo30997

Region1 loading delay after IDC login or after closing and opening Region1

CSCuo32660

Failed to stop PTT and failed to start PTT on P25 channel on remote IDC

CSCuo34880

Sometimes UMS does not remove hosted resources after call ends

CSCuo36458

Android: CIC shows empty talk lines intermittently

CSCuo37436

Garbled audio transmit on Dial Engine dial into a VTG channel

CSCuo39644

User gets stuck with white PTT button intermittently

CSCuo46885

IP phone text notification not working; unknown axis fault

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:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html