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:
Support for quick connect numbers, which allow a user who is running Cisco Instant Connect for Android Devices on a supported Sonim device that has a physical keypad to quickly connect or reconnect to a talkline or point-to-point call and disconnect from a point-to-point call.
Support for PTT operation by using the side button on the Sonim XP7 phone with the Sonim K50696 headset
A user can now place a point-to-point call to an IDC user in addition to the existing ability to place a point-to-point call to another contact.
New behavior for on Sonim Devices to when Tap and Join Talkgroup is configured for a short press of the Yellow key: If you press this key once, you now connects to the last talkline that is listed in the Talklines screen. If you press this key twice, you now connect to the second-to-last talkline that is listed, and so on
New and updated features in Cisco IPICS include the following:
Support for up to 2,500 active mobile users on the same system
Support up to 1,300 active users in a single talk group.
New CLI IDC Profile Copy command, ipics_idc_profile_mgmt, which lets you export or replace IDC profiles
New behavior for talk priority: When a higher priority user talks while a lower priority user is talking, the system stops streaming (preempts) the lower priority call. When a higher priority user is talking and a lower or equal priority user attempts to PTT, the system denies PTT access to the user who started talking last. When two talkers with the same priority talk, the system transmits the stream from the user who started talking first.
New and updated features in Cisco IPICS Dispatch Console include the following:
Support for private calls to other users and to Android mobile clients.
Added Talk Priority icon at the lower right corner of the Main window. This icon shows the talk priority of the user.
Cisco Instant Connect for mobile devices now runs on Microsoft Windows 7 and Windows 8 devices.
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 the following 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:
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.)
Both Reporters go to standalone/active status once the admin unpairs HA
UMS core dumps in RTCP packet handler area under stream load for Reporter
UMS core dumps intermittently for bulk VTG activation/deactivation
Communication failure post VPN disconnect/reconnect
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.