You can access Cisco IPICS software on Cisco Connection Online (CCO) by going to the following URL and, under “Select a Product,” choosing Products > IP Interoperability and Collaboration System, then clicking the link for your Cisco IPICS release:
Cisco IPICS is an IP standards-based solution that provides voice interoperability among disparate systems. It dissolves communication barriers between land mobile radio systems and devices including mobile devices, landline phones, IP phones, and PCs, wherever they are located. It also provides powerful and flexible management of personnel and media resources. Cisco IPICS streamlines radio dispatch operations and improves response to incidents, emergencies, and facility events. 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
New and updated features in Cisco Instant Connect for Android Devices include the following:
Quick-launch—Lets you use the Yellow button on a Sonim device to start another app such as Cisco Jabber while Cisco Instant Connect is running.
Channel scan—The scan feature locks onto a channel to allow dialog between users. The lock is released after 5 seconds of silence and then the scan continues for channels in the list.
Participants lists—Shows the Cisco IPICS users who are participants in a talkline.
PTT button—Updated appearances and new low profile appearance option.
Adding or removing radios, channel, or users—Updated functionality for adding or removing radios or channels from a VTG or incident, and adding or removing users to or from a VTG, radio, channel, or incident.
New settings options—The Settings screen includes options for configuring unlatched PTT timeout, displaying low profile PTT buttons, disabling touch screen PTT, configuring bluetooth settings, filtering contacts on the Contacts screen, and configuring the Yellow button on a Sonim device.
Diagnostics screen—Provides information and options that apply to VPN connections.
Feature updates—Various updates to screen layouts and feature operation
Bluetooth support—Cisco Instant Connect for Android mobile clients can now pair Bluetooth accessories, which allows for hands-free audio operations. Standard Bluetooth headsets are supported in addition to Savox push to talk Bluetooth accessories.
Device support—Support has been added for the Cisco DX650, Panasonic X1, Samsung S5, and Samsung S6
New and updated features in Cisco IPICS include the following:
Information in About window—The About window now provides links to third-party licensing information and additional legal notices.
Fixed connections—A fixed connection is generated on a UMS and allows a user to connect to the channel by using a third-party SIP device. You can manage fixed connections from the Configuration > Fixed Connections window, and from the Fixed Connections tab for a channel, VTG, or Radio.
Client tab options—The Client tab in the Administration > Options window includes new IDC Location Configuration and Sonim Yellow Button Configuration options.
Reporting—The reporting feature prepares and lets you obtain a variety of reports regarding system operations. You manage reporting from the Configuration Reporting window and from the Reporter pane in the General tab in the Administration > Options window.
New and updated features in Cisco IPICS Dispatch Console include the following:
Powered on resource appearance—In the display for a powered on resource, the power button has been moved to the left. In addition, a flashing green border indicates that a channel is receiving traffic.
Tear away feature enhancement—The state of the Regions list is maintained when this list is torn away.
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:
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 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:
Step 1Use 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 (such as /idspri/backup/cron/IDSB_2014-10-20_23-59-03/) 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:
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 log them out from Cisco IPICS before they can log in to the new Cisco IPICS version. To manually log out Cisco Instant Connect MIDlet users, go to the Administration > Active Users window in the Cisco IPICS Administration Console.
Cisco IPICS Dispatch Console User Guide, Release 4.9(1) applies to this 4.9(2) release. The updates in release 4.9(2) for the display for a powered on resource (power button has moved to the left and a flashing green border for a channel is receiving traffic) are not reflected in that document.
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.
Channel attenuation on the IDC dialer is not supported in this release. For channel attenuation options that use third-party audio hardware, contact your Cisco representative.
The following sections provide information about caveats in this Cisco IPICS release:
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. (Bug Search Tool is the successor to the Bug Toolkit.)
Table 1 describes known caveats in this Cisco IPICS release.
Table 1 Known Caveats
VLC 2.0.6 and above is not supported to play media in IDC
Remote IDC cannot disconnect unit calls, then unit calls will not connect
IDC with dialer and P25 gets error of same user logged already
IP Phone text notification fails—Unknown axis fault (missing SSL cert)
IDC through VPN: Network settings not set on IDC but seen on IPICS
Android: Robotic pots and pans noise in WiFi/4G/LTE when network drops
Users cannot power on Native channels due to cluttered hosts file
IDC 2nd Dialer call drops post IDC start
IDC version on admin console does not change to recommended post upgrade
Remote IDC user could not CLEAR or ACK an Emergency Alert @Native ISSI Channel
X-mute not functioning for P25 ISSI channels powered in native mode
Occasionally common channel across multi VTGs does not restream in multi UMS
Poor VQ scores when PTT from Sonim to Sonim using iLBC codec
Scan VTG does not switch to P25 Native channels in VTG Scan List on Cisco Instant Connect
P2P call: Audio loss on callee as caller can talk before callee is ready
UMS Reporter: No listen records generated for P25 native channel
Split brain is the default behavior during a network outage on reporter HA
Missing PTT records when shutting down (HA enabled) active reporter engine
No PTT or Listen records generated when those events span over two IREs
Receiving audio after stopping PTT and UMS in split brain mode
No listen report for incident
dfsig disable attempt in Admin Console fails
Text notification does not work with CUCM 10.5
CIC is not reconnecting to previous talkline in ICE license after re-login
Post restore, need to save Max Report Log... setting to update Reporter
No PTT CSV records generated for PTT on P25 Native mode channel from IDC
Reporter/IPICS HA could fail if there is not sufficient disk space for DB
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:
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)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.