ASTRO 25 7.15 Release Notes - semnrrb.comsemnrrb.com/Documents/MOTOROLA/7.15 release notes 12-8-2014.pdf · repeaters. The 10Base-T Ethernet Epic IV and Epic VI QUANTAR base stations

ASTRO 25 7.15 Release Notes

. . . . . . . . . .

ASTRO® 25 7.15 Release Notes

27-Oct-14

© Copyright 2013 Motorola Solutions, Inc. US

1


Contents System Level Information ................................................................................................................. 3 Centralized System Logging ............................................................................................................. 8 Configuration Manager ...................................................................................................................... 9 Configuration / Service Software (CSS) ........................................................................................... 9 FSA4000 Fire Station Alerting ......................................................................................................... 10 GCM 8000 Comparator .................................................................................................................... 10 GCP 8000 Site Controller (SC) ........................................................................................................ 11 GTR 8000 Base Radio (BR) ............................................................................................................. 12 Key Management Facility (KMF) ..................................................................................................... 13 License Manager .............................................................................................................................. 13 MCC 7100 IP Console ...................................................................................................................... 13 MCC 7500 IP Digital Logging Recorder .......................................................................................... 14 MCC 7500 Dispatch Position Software .......................................................................................... 15 MKM 7000 Console Alias Manager (CAM) ...................................................................................... 18 MLC 8000 Comparator ..................................................................................................................... 19 MZC 5000 Zone Controller (ZC) ...................................................................................................... 19 Network Security Firewalls ............................................................................................................. 20 Packet Data Gateway (PDG) ............................................................................................................ 20 Routers and Gateways .................................................................................................................... 21 SmartX Site Converter ..................................................................................................................... 22 System Traffic Monitor Applications .............................................................................................. 22 Unified Event Manager (UEM) ......................................................................................................... 25 Unified Network Configurator (UNC) .............................................................................................. 27 Virtual Management Server ............................................................................................................. 28

2


System Level Information

New Features RN_CCMPD-00002736 Abstract: Automatic Inter-System Data Roaming with Connectivity System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature applies to M-core trunking configurations with Integrated Data and/or Enhanced Data, GTR 8000 base stations in site configurations, and inter-RF subsystem interface (ISSI) 8000 functionality. This feature works on APX series mobile and portable subscriber radios. Description: This feature allows mobile subscribers to use data applications when roaming outside their home system. With this feature, using ISSI 8000 for voice service, a mobile subscriber from any customer enterprise network (CEN) can roam to another ASTRO 25 system and maintain connectivity to their home CEN and its data applications, such as: location, text messaging, over-the-air programming (OTAP), over-the-air rekeying (OTAR), and programming over Project 25 (POP25).

RN_CCMPD-00002737 Abstract: Headset Jack Sense Through Application Programming Interface (API) System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A Description: With the implementation of this feature, when an operator headset is connected to or disconnected from a headset jack on an MCC 7100 or MCC 7500 dispatch console, a status indicator for the headset is now included as part of the console API. As a result, application vendors now have the option to include this feature in software applications developed for interface with an MCC 7500 console.

RN_CCMPD-00002738 Abstract: Conventional Talkgroups System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature applies to L-core and M-core systems where zone cores include conventional dynamic system resilience (DSR), or sub-core conventional system architectures using MCC 7500 or MCC 7100 dispatch consoles, G-Series devices (GTR 800 expandable site subsystem, GCM 8000 comparator, GPW receiver, GCP 8000 site controller), and GGM 8000 conventional channel gateways (CCGWs). This feature is compatible with XTS/XTL series and APX series subscriber radios. APX radios are recommended when this feature is used in combination with the radio "scan" feature. Description: This feature provides separation of voice communications on digital conventional channels. Subscribers and console operators using the same talkgroup can communicate with each other without being heard by users of other talkgroups. In addition, emergency alarms can be separated by talkgroup. This feature introduces the functionality of talkgroup channels (already implemented in trunking systems) to conventional systems. An IP or V.24 digital conventional channel that is configured for conventional talkgroup operation is identified as a talkgroup channel. An IP or V.24 digital conventional channel that is not configured for conventional talkgroup operation is identified as a classic channel. When a talkgroup is assigned to a channel, it cannot be assigned to another channel, and it cannot be used for trunking. The console operator receives a new cross busy indication to identify any conflict with another talkgroup using the same channel. On each talkgroup channel, consoles can affiliate to the talkgroup for which they want to receive audio and can associate to talkgroups for which they want to be notified of call activity but do not want to receive audio.

RN_CCMPD-00002739 Abstract: Conventional Data Redundancy for High Availability (HA) and Dynamic System Resilience (DSR) System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature applies to ASTRO 25 conventional data systems. Description: This feature provides full conventional data redundancy, completing the ASTRO 25 Data Solution portfolio. Conventional Data Redundancy ensures reliable data delivery by preventing single points of hardware failure at a master site from causing loss of data functionality within a single-zone or multi-zone conventional data system. Optional DSR support is also available to provide geographic redundancy.

3

ASTRO 25 7.15 Release Notes Conventional Data Redundancy also implements a mobile IP protocol that enables HA conventional data to function properly when a subscriber roams to a different zone and loses communication with the originating packet data gateway (PDG), or when a subscriber switches master sites due to a DSR failover.

RN_CCMPD-00002740 Abstract: Simultaneous Call Capacity Increased for Sites with Time Division Multiple Access (TDMA) Capability System Platforms Affected: ASTRO 25 7.15 Special Configurations: The increased call capacity is supported in ASTRO 25 systems with L-core and M-core configurations, ASTRO 25 Express single site standalone trunking configurations, and simulcast and non-simulcast configurations using RF sites with GTR 8000 base radios with TDMA capability. To support this feature, sites must be equipped with GTR 8000 BRs or with a combination of QUANTAR and GTR 8000 base stations. The increased call capacity is not supported for SmartX, High Performance Data (HPD), Individual Short Subscriber Identity (ISSI.1), Motorola Push to Talk (MPTT, formerly known as PTT Over Cellular), or QUANTAR trunked RF sites. Description: Subscriber radio users (and console operators in wide trunking operation) can now place and receive a combined total of up to 36 simultaneous voice or voice and data calls at TDMA-capable trunked RF sites. This is an increase from the 30 simultaneous calls previously permitted. The total number of simultaneous calls can include a mix of TDMA and Frequency Division Multiple Access (FDMA) calls, but no more than 36 in total can be active at one time. For example, if 10 FDMA calls are in progress using 10 of the total possible base radios (BRs), only 26 additional calls are possible, even though 26 TDMA calls do not use all of the remaining available BRs at the site. Aside from the increase in simultaneous call capability, radio users and console operators do not notice any change in call operations when this functionality is implemented. The current limit on the number of physical stations that can reside at a radio site is not impacted by this change in capacity. Sites still cannot exceed 30 BRs at simulcast sites or 28 BRs at non-simulcast sites. FDMA-only trunked RF sites are still limited to 29 voice calls for simulcast sites and 27 voice calls for non-simulcast sites), and trunked RF sites with explicitly assigned channels still have the same limits on call capacity, zone-level channels, and the zone-level call rate.

RN_CCMPD-00002741 Abstract: Management of QUATAR Repeaters by GCP 8000 Site Controllers (SCs) System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature applies to L-core and M-core configurations that include trunking digital site repeaters. The 10Base-T Ethernet Epic IV and Epic VI QUANTAR base stations at ASTRO 25 repeater sites can now be used with GCP 8000 SCs. Coexistence of PSC 9600 SCs and GCP 8000 SCs is not supported. Coexistence of GTR 8000 expandable site subsystems (ESS) and standalone GTR 8000 base radios (BRs) is not supported. Description: GCP 8000 SCs can now control QUANTAR repeaters that use a 9600 bps control channel, so that operators can use PSC 9600 SCs to migrate gradually to the "G-series" platform (GCP 8000 SCs, GTR 8000 BRs, and GCM 8000 comparators). Users may employ: • Standalone GCP 8000 SCs controlling a mix of QUANTAR and standalone GTR 8000 BRs • Standalone GCP 8000 SCs controlling standalone GTR 8000 BRs • GCP 8000 SCs in an ESS controlling external QUANTAR base stations • Standalone GCP 8000 SCs controlling a mix of standalone QUANTAR and GTR 8000 BRs in an ESS package with Expansion Hubs (xHubs)

RN_CCMPD-00002742 Abstract: Software Development Kit (SDK) for MKM 7000 Console Alias Manager (CAM) System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature applies to L-core and M-core configurations and distributed conventional core (K-core) configurations. Description: This feature provides documentation, tools, examples, tutorials, software test tools and engineering assistance to enable development of third-party products, using the CAM application programming interface (API) introduced in ASTRO 25 7.12. The CAM API allows third-party applications to manage subscriber unit aliases for MCC 7500 and MCC 7100 dispatch consoles.

4

ASTRO 25 7.15 Release Notes RN_CCMPD-00002743 Abstract: Software License Manager System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature applies to L-core and M-core configurations. Description: The Software License Manager replaces the current license manager with a Flexera platform that enhances users’ ability to manage zone-level and system-level network management licenses. Prior to implementation of this feature, users managed licenses through the Motorola License Manager at the master site of each zone. In order to view system-level licenses, users had to log in to the User Configuration Server (UCS) or the Air Traffic Router (ATR) server. This feature allows users to view zone-level and system-level network management license information from a single application. Users can now view counts of how many licenses have been used and how many licenses have been purchased (and determine whether they have exceeded the allowed number of licenses). In addition, users can: • View which users are using floating licenses (and release users if necessary). • Manage northbound interface (NBI) client sessions on the Unified Event Manager (UEM) server. • View the number of subscribers with radio authentication. • View license non-compliance reports in the UEM.

RN_CCMPD-00002745 Abstract: Import/Export User-Computer Interface (UCI) for Configuration Manager (CM) System Platforms Affected: ASTRO 25 7.15 Special Configurations: The UCI is supported only in K-core configurations. The Provisioning Manager (PM) application performs this function for L-core and M-core systems. Description: This feature reduces time spent doing manual data entry in K-core configurations by allowing users to import and export system configuration data into the CM application. This tool supports the following file formats for import and export: • Comma separated variable (CSV) – This option is comparable to the import/export operation implemented in the ASTRO 25 7.13 release of the Provisioning Manager (PM) application. • Excel workbook (XLS) – With this new option, users enter system configuration data in a separate tool, and the output from that tool is loaded into the CM in a single step.

RN_CCMPD-00002746 Abstract: System Upgrade to ASTRO 25 7.15 System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A Description: The ASTRO 25 7.15 system release supports the following upgrade paths. For upgrades from ASTRO 25 7.13 to ASTRO 25 7.15: • M1 core configuration with conventional subsystem architecture (CSA) to M1 with CSA • M2 core configuration non-CSA to M2 CSA • M2 CSA to M2 CSA • M3 core configuration non-CSA to M3 CSA • M3 CSA to M3 CSA • M3 non-CSA with dynamic system resilience (DSR) to M3 CSA with DSR • M3 CSA with DSR to M3 CSA with DSR • L1 core configuration to L1 • L2 core configuration to L2 • K1 core configuration to K1 • K2 core configuration to K2 • ASTRO 25 Express to ASTRO 25 Express For upgrades from ASTRO 25 7.14 to ASTRO 25 7.15: • M1 CSA to M1 with CSA • M1 with DSR to M1 with DSR

5

ASTRO 25 7.15 Release Notes • M2 CSA to M2 CSA • M3 CSA to M3 CSA • M3 CSA with DSR to M3 CSA with DSR • L1 core configuration to L1 • L2 core configuration to L2 • K1 core configuration to K1 • K2 core configuration to K2 • ASTRO 25 Express to ASTRO 25 Express

RN_CCMPD-00002747 Abstract: Enhanced Telephone Interconnect (ETI) Software Upgrade System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature is not backward compatible. ASTRO 25 7.9 through ASTRO 25 7.14 systems must use the existing version of software and cannot upgrade to the latest version. Description: This feature updates the NEC software for internet protocol private branch exchange (IP PBX) systems to version 8.5. It provides improved voice prompts, and other enhancements and defect fixes. The upgrade requires no hardware changes.

RN_CCMPD-00002748 Abstract: High Capacity Unified Network Configurator (UNC) System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature applies to M3 configurations and can be used in systems with full Information Assurance options. This feature is not supported in systems where the dynamic system resilience (DSR) feature is implemented. Description: The UNC can now manage up to 15,000 devices in each system with an M3 core configuration. The previous limit was 5,000 devices per system.

RN_CCMPD-00002749 Abstract: Console Repeat System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature applies to systems that include analog conventional and MDC 1200 conventional channels. Description: This feature enables MCC 7500 dispatch consoles to force a set of scanners to detect audio on a particular channel and to remain on that channel as long as audio is being received on the channel. Console Repeat allows dispatchers who are near a scanner to hear all the activity on that channel without interruption caused by scanning other channels. To accomplish this, a dispatcher activates Console Repeat feature on the desired analog or MDC 1200 channel from the console’s graphical user interface (GUI), causing the transmitter on the channel to key up continuously. When the incident is over, the dispatcher deactivates Console Repeat from the console GUI, causing the transmitter on the channel to dekey. When the audio is no longer being received on the channel, the scanners resume their normal scanning. Console Repeat also includes a timer that automatically deactivates the feature after it has been active for a configurable amount of time. This functionality was supported on CENTRACOM Gold Elite consoles in previous releases. The ASTRO 25 7.15 release adds this capability to MCC 7500 consoles. This feature also allows a conventional channel gateway (CCGW) to repeat received audio in a non-latched mode similar to the functionality provided in the past by the CENTRACOM Base Interface Module (BIM).

RN_CCMPD-00002751 Abstract: Duplex Patch on MCC 7100 and MCC 7500 Dispatch Consoles System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A Description: This feature enables MCC 7100 and MCC 7500 dispatch consoles to support the duplex patch functionality supported on existing CENTRACOM Gold series consoles. When two analog conventional or MDC 1200 conventional channels or telephone resources are in a duplex patch, audio received on one channel is repeated on that channel at the conventional channel gateway (CCGW) and is mixed and sent over the air with audio from the patched channel. As a result, the non-transmitting users on both channels hear the sum of the audio from the transmitting user on their channel as well as the transmitting user on the other channel.

6

ASTRO 25 7.15 Release Notes When more than two channels are involved in the patch, operation is identical to the existing "simplex" patch operation.

RN_CCMPD-00002752 Abstract: Juniper Firewall Replacement System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A Description: Beginning in ASTRO 25 7.15, the Juniper Networks Systems Solutions Group / Information Systems Group (SSG/ISG) firewall portfolio is being replaced with Fortinet firewalls in all new ASTRO 25 systems. The Juniper firewalls deployed in existing systems will be supported through the ASTRO 25 7.17 system release. A new firewall manager (FortiManager) accompanies the firewall replacement equipment. The Fortigate firewall supports software and configuration distribution from the Unified Network Configurator (UNC). The feature adds fault management using simple network management protocol version 3 (SNMPv3) between Fortinet firewalls and the Unified Event Manager (UEM). The feature also maintains remote interfaces for installations and upgrades to the firewall equipment and reinstates centralized backup and restore (BAR) services for firewall manager log files.

RN_CCMPD-00002756 Abstract: GGM 8000 Certification in Configurations Without Cooperative Wide Area Network Routing (CWR) System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A Description: Certification of the GGM 8000 gateway in non-CWR configurations allows users to replace Motorola Network Router (MNR) S6000 routers with GGM 8000 gateways in the following network positions for new ASTRO 25 systems: • Gateway General Packet Radio Service (GPRS) Support Node (GGSN) in K-core, L-core, and M-core systems • Core and gateway router (supporting Ethernet site links in M-core systems) Users are not required to replace MNR S6000 routers with GGM 8000 gateways in these positions in existing systems. An MNR S6000 router is still required in the following network positions/configurations: • Peripheral network router with more than two T1/E1 connections • Core routers, exit routers, and access routers in T1/E1 CWR configurations • Simulcast Prime sites and network management (NM) sites or dispatch console sites that require a multilink frame relay (MFR) bundle of three T1/E1 links

RN_CCMPD-00002757 Abstract: Geographic Talkgroup Select Assist System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature requires a Computer Aided Dispatch Interface (CADI). Description: This feature enables system administrators to configure assignment of subscribers within geographic areas to defined talkgroups so that dispatchers can activate the configured assignments when needed. Functions include automatic regrouping within defined geographic areas, dynamic defining of areas and talkgroups, audible and visible indicators on radio for loss of Global Positioning System (GPS) location signal, and subscriber ability to override a regrouped talkgroup when needed.

RN_CCMPD-00002758 Abstract: High Availability (HA) Performance Management and Radio Control Services System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature applies to redundant L-core and M-core configurations with air traffic information access (ATIA) or computer aided dispatch interface (CADI). For dynamic system resilience (DSR) configurations, both the primary zone core and the backup zone core must have this capability enabled. Description: This feature provides redundancy for Air Traffic Router (ATR) applications. This prevents a single point of failure from causing a loss of the reporting, management, and monitoring services provided by the ATR, such as ATIA Log Viewer, CADI, Historic Reports, Dynamic Reports, Radio Control Manager (RCM), Affiliation Display, and ZoneWatch.

RN_CCMPD-00002759 Abstract: Fault Trap Overload System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A

7

ASTRO 25 7.15 Release Notes Description: This feature improves the functionality of the Unified Event Manager (UEM) by supporting higher incoming traffic rates, detecting overload conditions, and preventing application failure as a result of excessive traffic. With the implementation of this feature, color-coded visual indicators on the interface display the operational state of the UEM: • Green: The UEM is displaying fault traffic in real time (normal state). • Yellow: The UEM is buffering fault traffic. Higher-priority alarms are displayed first in the queue. • Orange: The UEM is buffering fault traffic, and the buffer is approaching a critical level. When the UEM reaches this state, user intervention is recommended. Users can manually purge the oldest traps to free buffer space. The purged traps remain in the events archives • Red: The UEM is buffering fault traffic, and the buffer has reached a critical level. When the UEM reaches this state, it automatically purges the oldest traps to prevent UEM failure. The purged traps remain in the events archives. Users can configure the UEM to send notifications regarding UEM status via page, email or north bound interface (NBI). The UEM also returns a list of the devices that are reporting the most events.

RN_CCMPD-00002760 Abstract: Console Subsystem Interface (CSSI) 8000 Support for Multiple Interfaces for Individual Calls System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A Description: The CSSI 8000 now supports up to 24 CSSI interfaces that can support individual calls to an ASTRO 25 system. Previous releases supported only one a single CSSI interface with individual call support. Increasing the number of supported interfaces with individual call support to 24 does not increase the limit of CSSI 8000 and inter-RF subsystem interface (ISSI) 8000 connections per system. The limit remains at 24.

RN_CCMPD-00002761 Abstract: Mixed Mode Conventional Simulcast System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature applies to conventional simulcast configurations using “GEN 2” GTR 8000 base radios (BR), MLC 8000 comparators or site link converters, and GCM 8000 comparators. Description: This feature supports the use of both MLC 8000 comparators and GCM 8000 comparators for mixed mode conventional simulcast operation and enables gradual migration to G-Series devices: GTR 8000 BRs, GTR 800 expandable site subsystem (ESS), GCM 8000 comparator, GPW 8000 receivers, and GCP 8000 site controllers. The use of dual comparators enables both analog and digital audio to be provided in a conventional simulcast environment. This solution enables operators to reuse existing subscriber radios during gradual migration.

RN_CCMPD-00002762 Abstract: Status Updates for Third Party-Consoles through Console Subsystem Interface (CSSI) 8000 System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature applies to M-core system configurations with CSSI 8000 functionality. Description: Trunking subscribers on an ASTRO 25 system can now send status update requests to third-party consoles using the CSSI 8000 functionality.

RN_CCMPD-00002763 Abstract: Increased Channel Capacity on K-Core Systems System Platforms Affected: ASTRO 25 7.15 Special Configurations: This feature applies to K-core system configurations. Description: The number of channels supported in ASTRO 25 K core systems has been increased from 50 to 75. There is no change to the number of channels supported at a conventional site (40 analog channels, 20 V.24 digital channels, and (not or) 30 IP digital channels).

Centralized System Logging

Issue Update RN_CCMPD-00002579 Abstract: Extraneous words are interspersed between valid syslog client host names in Syslog Client list on Centralized Event Logging Server. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14

8

ASTRO 25 7.15 Release Notes Special Configurations: N/A User Symptoms: When a user requests a list of syslog clients from the Centralized Event Logging Server, using the “Application Administration->Application Specific Management and Operations->View Syslog Clients” menu path, the resulting list contains the host names from which syslog messages are successfully received. However, the list also contains extra words that are not host names. Functionality is not impaired, but the presence of the extra words in the list may be confusing to the user. Description: When a user requests a list of syslog clients from the Centralized Event Logging Server, the resulting list no longer contains extra words that are not host names.

Configuration Manager

Issue Update RN_CCMPD-00002901 Abstract: Elite Dispatch application becomes unresponsive after restore or upgrade operation on Zone Database Server (ZDS). System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user performs a restore or upgrade operation on the ZDS after the ZDS is enabled, the Elite Dispatch application receives an "Invalid Login" error message from the ZDS. When this issue occurs, Elite Dispatch becomes unresponsive to user inputs until the Provisioning Manager (PM) application triggers a force initialization of the ZDS. In addition, the following message appears: "Authentication failed. User login name and user password combination is not recognized." Description: When a user performs a restore or upgrade operation on the ZDS after the ZDS is enabled, the Elite Dispatch application now operates normally, and the error messages listed in the User Symptoms no longer appear.

Configuration / Service Software (CSS)

Issue Updates RN_CCMPD-00002586 Abstract: Rarely, CSS may freeze during exit. System Platforms Affected: ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: Rarely, during an exit operation, the CSS application may become unresponsive while creating a zip archive of its internal log file. When this occurs, no data is lost, but the unresponsiveness of the application may be confusing to the user. Description: During an exit operation, the CSS application no longer becomes unresponsive, and the exit operation now completes successfully.

RN_CCMPD-00002587 Abstract: Software Download (SWDL) installation may fail. System Platforms Affected: ASTRO 25 7.14 Special Configurations: This issue affects multisite system configurations that contain more than 150 base radios. User Symptoms: When a user attempts a multi-channel installation for more than 150 devices at the same time, the SWDL installation may fail. When this issue occurs, the SWDL application stops performing operations on the sites where the devices reside for an extended period of time, and the following message appears in the Message Box: "Transaction failed. Vlan API failed". Description: When a user initiates a multi-channel installation for more than 150 devices at the same time, the SWDL installation now completes successfully.

RN_CCMPD-00002977 Abstract: CSS may report Repeater Activity State as "VOICE" while all subsite states are "IDLE". System Platforms Affected: ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14

9

ASTRO 25 7.15 Release Notes Special Configurations: N/A User Symptoms: When a user selects the Local Status Screen in CSS while no voice call is in progress, all subsites correctly appear in "IDLE" state, but the Repeater Activity State field may erroneously continue to display a "VOICE" value, instead of displaying "IDLE" as expected. When any inbound activity occurs, CSS updates the Repeater Activity State field to the correct value. Functionality is not impaired, but the erroneous display may be confusing to the user. Description: When a user selects the Local Status Screen in CSS while no voice call is in progress, the Repeater Activity State field now correctly displays "IDLE" as expected.

Known Problem RN_CCMPD-00002986 Abstract: CSS erroneously saves unintended changes to "Site/Comparator State" settings. System Platforms Affected: ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14, ASTRO 25 7.15 Special Configurations: This issue affects the GCP 8000 Site Controller (SC) and GCM 8000 Comparator. User Symptoms: When a user starts to enter a change in the setting for "Site/Comparator State" and then clicks the red “X" button to close the window or selects "cancel" followed by selecting the red "X" box, CSS saves the change and applies the new setting to the affected device, instead of canceling the change as expected. Work Around: None. To recover, users should manually restore the intended settings for any affected devices.

FSA4000 Fire Station Alerting

Issue Update RN_CCMPD-00001849 Abstract: FSA4000 Dispatch Application may send some alerts to location not intended by user. System Platforms Affected: ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: This issue affects systems configured with eight (8) possible sequences for dispatching alerts to fire stations. User Symptoms: When a user selects eight sequences for dispatching alerts to fire stations, the FSA Dispatch Application may display both sequence 8 and the previously selected default sequence as being selected for dispatching. When this occurs, alerts are sent to the selected station on the default sequence, rather than to sequence 8. Description: The FSA4000 product is no longer available in ASTRO 25 7.15, and as a result, the issue described in this note no longer occurs.

GCM 8000 Comparator

Issue Update RN_CCMPD-00002493 Abstract: Subscribers may not hear console audio after comparator reset during V.52 test. System Platforms Affected: ASTRO 25 7.14 Special Configurations: This issue affects conventional IP simulcast systems. User Symptoms: When a user starts a V.52 test on a given channel but does not properly stop the test (because the comparator resets and interrupts the test), subscribers may not hear audio originated by dispatch consoles on that channel. When this occurs, the Unified Event Manager (UEM) and other network management (NM) servers report the state of the comparator as "Enabled", as if the comparator were fully operational, when in fact the comparator is inactive. When the user verifies the state of the comparator using Configuration/Service Software (CSS), the "Local Status Screen" in CSS displays the state of the comparator correctly. Description: When a user starts a V.52 test on a given channel but does not properly stop the test (because the comparator resets and interrupts the test), subscribers now hear audio originated by dispatch consoles on that channel.

10


GCP 8000 Site Controller (SC)

Issue Updates RN_CCMPD-00002567 Abstract: Site enters failsoft during field replacement of SC. System Platforms Affected: ASTRO 25 7.5, ASTRO 25 7.6, ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user performs the Field Replaceable Unit (FRU) procedure for an SC, the site where the SC is located enters site failsoft for approximately seven (7) minutes during the procedure. Description: When a user performs the FRU procedure for an SC, the site where the SC is located no longer enters site failsoft during the procedure.

RN_CCMPD-00002568 Abstract: Status Panel screen in Configuration/Service Software (CSS) may not refresh display when SC goes to standby status. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When an SC changes its status from active to standby, the SC resets as expected. However, if the Status Panel screen in CSS is open during the reset, the screen may continue to display field values that were retrieved when the SC was active, instead of replacing those values with "N/A" as expected when an SC is on standby. The screen correctly displays the standby status of the SC, but the display of values in other fields that are not applicable to a standby SC may be confusing to the user. Description: When an SC changes its status from active to standby and the Status Panel screen in CSS is open during the expected reset, the screen now replaces all field values with "N/A" as expected.

RN_CCMPD-00002570 Abstract: Channel faults may be reported inconsistently during reset of active SC. System Platforms Affected: ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a channel fault occurs during a reset of an active SC, the fault may be reported inconsistently between devices in the ASTRO 25 system. For example: • The ZoneWatch (ZW) application may report the state of the channel as "Enabled" (displayed in green in ZW). • The Unified Event Manager (UEM) may report the state of the same channel as "Entity has been removed". • The Zone Controller (ZC) and Configuration/Service Software (CSS) may report the same channel as present and in some non-enabled state (for example, "Faulted" or "User Disabled"). In addition, a channel that ZW reports as "Enabled" may not be assigned to any calls. When this issue occurs, users can determine the actual state of a channel element by doing any of the following: • Viewing the fault state reported directly by the channel in the UEM. • Viewing the fault state reported for the channel by the ZC in the UEM. • Connecting to the active SC using CSS. Description: When a channel fault occurs during a reset of an active SC, the fault is now reported correctly by devices in the ASTRO 25 system.

RN_CCMPD-00002588 Abstract: SC reports confusing event to Unified Event Manager (UEM) during wide trunking recovery. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: During recovery of the primary prime site or a switch upgrade on the primary prime site, the UEM displays the state of a repeater SC or simulcast SC as "Site Trunking" with "No Voice channel". After approximately one second, the SC returns to wide trunking without user intervention. When this occurs, the UEM reports the state of the SC correctly, but the earlier state displays are recorded in the UEM event log. Functionality is not impaired, but the brief status display and the log entries may be confusing to the user.

11

ASTRO 25 7.15 Release Notes Description: During recovery of the primary prime site or a switch upgrade on the primary prime site, the UEM now correctly displays the state of a repeater SC or simulcast SC as "Site Trunking" with "No site link". After approximately one second, the SC returns to wide trunking as expected, and the correct entries are now recorded in the UEM event log.

GTR 8000 Base Radio (BR)

Issue Updates RN_CCMPD-00002101 Abstract: Rarely, BR may experience second reset during initialization. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: Rarely, during BR initialization, users may observe an extended startup time, and the BR may reset a second time before becoming operational. When fully initialized, the BR operates normally. When this issue occurs, no additional failures are reported to the Unified Event Manager (UEM). Description: During BR initialization, the BR now starts up within approximately 1 minute, and the BR no longer resets a second time before becoming operational. When fully initialized, the BR operates normally.

RN_CCMPD-00002450 Abstract: Rarely, BR may experience second reset during initialization. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: N/A Description: During BR initialization, users no longer observe an extended startup time, and the BR no longer resets a second time before becoming operational. When fully initialized, the BR operates normally.

Known Problems RN_CCMPD-00002896 Abstract: Bit error rate (BER) is measured incorrectly. System Platforms Affected: ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14, ASTRO 25 7.15 Special Configurations: This issue affects a BR configured for Frequency Division Multiple Access (FDMA) redundancy and/or Time Division Multiple Access (TDMA) diversity operation. User Symptoms: When a BR has diversity or redundant path receive systems, a user cannot measure the 5% BER for branch B as expected. Instead, the user receives the BER measurement for branch A and branch B combined. As a result, when operating conditions cause branch B to be completely faulty, the user still receives a BER measurement based on branch A influences. Work Around: Option A: To conduct a BER test on Branch B, the user must terminate branch A with a 50 Ohm terminator and then apply an appropriate FDMA or TDMA test signal to branch B. The user must wait for the length of time configured for the “Dual Branch Receive Operations - time to failure” setting in CSS (the default value is 120 seconds). When this time expires, the branch B BER can be read via CSS. Option B: To verify the sanity of Branch B, the user should disable diversity via CSS and measure receiver sensitivity at 5% BER on branch A, then decrement receiver power level by 2 dB and enable diversity, then measure BER again. If BER is less than 5 %, branch B is working properly.

RN_CCMPD-00002978 Abstract: Working Unit ID (WUID) embedded in System Events may be not correct. System Platforms Affected: ASTRO 25 7.15 Special Configurations: This issue affects BRs configured as a Multisite Base Radio (MsBR) in systems equipped for Frequency Multiple Division Access (FDMA) audio traffic. User Symptoms: System Events triggered by an MsBR related to FDMA calls may contains incorrect WUID values. Work Around: Users should compare System Events logs with call activity records, such as Air Traffic Information Access (ATIA) logs, to determine the correct WUID values.

12


Key Management Facility (KMF)

Issue Update RN_CCMPD-00002576 Abstract: Rarely, KMF Client window may freeze. System Platforms Affected: ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: In rare instances, the KMF Client application window may become unresponsive until the user minimizes and then restores the window. KMF functionality is not impaired, but the freezing of the application window may be confusing to the user. Description: The KMF Client application window no longer becomes unresponsive.

License Manager

Known Problem RN_CCMPD-00002999 Abstract: License requests from applications may be erroneously rejected after reset of License Manager virtual machine (VM). System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A User Symptoms: When an application, such as the Unified Event Manager (UEM) or ZoneWatch (ZW), requests a software license from the License Manager application after a reset of the License Manager VM, the request may be rejected when licenses are in fact available, and the requesting application may display the message "No license available". When this issue occurs, the License Manager correctly indicates that licenses are available, but the "Device ID" field in the lower right corner of the License Manager window indicates "ETHERNET" instead of "VM_UUID". Work Around: After a reset of the License Manager VM, users should perform the following actions: 1. Log into the License Manager VM. 2. Type "admin_menu" at the command prompt. 3. Select "Application Administration" from the menu. 4. Select "Manage Application Status" from the menu. 5. Select "Disable Application" from the menu. 6. Enter "Y" when asked to confirm the disable. 7. Select "Display Application Status" from the menu to verify that the application has been disabled. 8. Select "Enable Application" from the menu. 9. Enter "Y" when asked to confirm the enable.

MCC 7100 IP Console

Issue Updates RN_CCMPD-00002555 Abstract: Elite Dispatch transmissions may fail, and receive audio may be missing in headsets. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: After initial installation of an MCC 7100 IP Console, the Universal Serial Bus (USB) Archiving Interface Module (AIM) may not initialize completely. When this occurs, transmissions in the Elite Dispatch application may fail, and the user may see the following error message: "Insufficient Audio Peripherals". In addition, receive audio may not be present in headsets connected to the USB AIM. Description: After initial installation of an MCC 7100 IP Console, the USB AIM now initializes completely.

13

ASTRO 25 7.15 Release Notes As a result, transmissions from the Elite Dispatch application now complete successfully, and receive audio is now present in headsets connected to the USB AIM.

RN_CCMPD-00002556 Abstract: Extra “Audio Only” call records appear in Instant Recall Recorder (IRR) call list. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When recording a call on an MCC 7100 IP console that is located outside the ASTRO 25 Radio Network Interface (RNI), the IRR application may create an “Audio Only” call record in addition to the expected call record for each call being recorded. These extra call records are more likely to appear when the IRR is recording a parallel console call, especially if that parallel console is also located outside the RNI. Console and IRR functionality are not impaired, but the extra call records may be confusing to the user. Description: When recording a call on an MCC 7100 IP console outside the RNI, the IRR application now creates only the expected call record for each call being recorded, and the extra “Audio Only” call records no longer appear.

RN_CCMPD-00002563 Abstract: Peripheral Configuration Tool may become unresponsive. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user upgrades firmware on the universal serial bus (USB) Archiving Interface Module (AIM) using the Peripheral Configuration Tool (PCT) in the MCC 7100 IP console, the PCT may become unresponsive, and the user may be unable to close the PCT window. This condition is more likely to occur while the Elite Dispatch application is running. Description: When a user upgrades firmware on the USB AIM using the PCT, the PCT now functions normally.

RN_CCMPD-00002564 Abstract: Instant Recall Recorder (IRR) may become stuck in initializing state. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user opens the IRR application while the Elite Dispatch application is closing, the IRR may become stuck in initializing state and may remain stuck after Elite Dispatch is fully closed. Description: When a user opens the IRR application while the Elite Dispatch application is closing, the IRR now opens successfully and functions normally.

Known Problem RN_CCMPD-00002463 Abstract: Elite Dispatch application restarts when Message Monitoring is enabled in Debug Viewer. System Platforms Affected: ASTRO 25 7.14, ASTRO 25 7.15 Special Configurations: N/A User Symptoms: When a user enables Message Monitoring in the WinQuicc query (under embedded queries in the Debug Viewer), the Elite Dispatch application may restart spontaneously. Enablement of Message Monitoring is not necessary to the operation of the Elite Dispatch application. Work Around: Users should not enable Message Monitoring in the WinQuicc query in the Debug Viewer. To recover, users should disable Message Monitoring in the WinQuicc query in the Debug Viewer.

MCC 7500 IP Digital Logging Recorder

Known Problem RN_CCMPD-00002427 Abstract: Scroll bar in Archiving Interface Server (AIS) Administrator application may not move smoothly. System Platforms Affected: ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14, ASTRO 25 7.15 Special Configurations: N/A

14

ASTRO 25 7.15 Release Notes User Symptoms: On the Resources tab of the AIS Administrator application, the vertical scroll bar used for browsing through the records listed may not move up and down smoothly when the AIS database contains a large number of records. Access to the records listed on the Resources tab is not impaired, but the movement of the scroll bar may be inconvenient to the user. Work Around: To avoid this issue, users who wish to browse the records on the Resources tab should use the up or down arrow (marked by a thumbtack icon) instead of the scroll bar.

RN_CCMPD-00002915 Abstract: Audio logging playback workstation may not display "Channel Marker Enabled" event after trunking transition. System Platforms Affected: ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14, ASTRO 25 7.15 Special Configurations: This issue affects systems where the channel marker feature is configured for a channel, conventional site mode is configured for a dispatch console site, and the IP logging vendor has decided to implement user notifications for the “channel marker” feature on the audio logging playback workstation. User Symptoms: When a channel marker is enabled, and then a transition from wide trunking to site trunking or from site trunking to wide trunking occurs, the audio logging playback workstation displays the channel marker as disabled. After the transition is complete, the channel marker is enabled as expected, but the audio logging playback workstation may not display the "Channel Marker Enabled" event as expected. The channel marker tones are still recorded and can be replayed on the associated playback equipment, but absence of the event may be confusing to the user. Work Around: None

MCC 7500 Dispatch Position Software

Issue Updates RN_CCMPD-00002557 Abstract: Dispatch consoles may lose audio from some subscriber calls after takeover. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: Dispatch consoles may lose audio from some subscriber calls after a takeover. This may occur in the following scenario: 1. One operator position (Console 1) has Talkgroups 1 and 2 in a patch group. 2. A parallel operator position (Console 2) has the same Talkgroups 1 and 2 in an open Multi-Select (MSEL) group. 3. When Talkgroup 1 receives an incoming subscriber call, the Console 1 audio patch is transmitted on Talkgroup 2. 4. When Console 2 receives two audio streams from the same source (one directly from the subscriber and another from the Console 1 audio patch transmitting on Talkgroup 2), Console 2 stops transmitting subscriber audio on Talkgroup 1. 5. When Console 1 performs a takeover of the audio patch call by keying Talkgroup 2 with "General Transmit", Console 1 cannot hear the subscriber call during and after the takeover on Talkgroup 1. Description: Dispatch consoles no longer lose audio from subscriber calls after a takeover in the scenario described in the User Symptoms.

RN_CCMPD-00002558 Abstract: Archiving Interface Server (AIS) logs duration of secure Voice Selective Call (VSC) recordings incorrectly. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a secure VSC is made on a system where the MCC 7500 IP Logging is registered for "control ONLY" messages (no encryption), the AIS logs the duration of the VSC as 15 seconds, regardless of the actual duration of the VSC. No audio loss occurs, but the erroneous duration records may be confusing to the user. Description: When a secure VSC is made on a system where the MCC 7500 IP Logging is registered for "control ONLY" messages, the AIS now logs the actual duration of the VSC.

15

ASTRO 25 7.15 Release Notes RN_CCMPD-00002559 Abstract: “Broken Link” Icon is not displayed for telephony resource in Multi-Select (MSEL) linked patch group. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a telephony resource is added to an MSEL linked patch group, no "Broken Link" icon is displayed to notify the user that the resource is not added to the MSEL group. The resource should not be added to the MSEL group, but the lack of notification may be confusing to the user. Description: When a telephony resource is added to an MSEL linked patch group, a "Broken Link" icon is now displayed, as expected, to notify the user that the resource is not added to the MSEL group.

RN_CCMPD-00002560 Abstract: Audio for general transmit may be routed incorrectly during "alert tone talk extend". System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user performs a general transmit on a channel in a Multi-Select (MSEL) group while the "alert tone talk extend" option is active, the audio for parallel consoles with that channel selected may be routed to all speakers and headsets, instead of being routed only to select speakers or headsets as expected. This issue occurs when an MSEL group, set up with Channel 1 as its first member, is opened; an alert tone is transmitted then released using Channel 1; and a general transmit on Channel 1 is performed during the configured "talk extend" time of the alert tone. This issue is less likely to occur when the user reduces the "talk extend time" of the alert tone. Description: When a user performs a general transmit on a channel in an MSEL group while the "alert tone talk extend" option is active, the audio for parallel consoles with that channel selected is now routed only to the select speakers or headsets, as expected.

RN_CCMPD-00002561 Abstract: Dispatch console may display acknowledgements of emergency calls inconsistently. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user sets the folder resource size in the Elite Dispatch application to a value greater than the default value of 1, the dispatch console may display acknowledgments of emergency calls inconsistently. For example, when an emergency call is received and acknowledged, and then another emergency call is received an acknowledged, the call stack in the dispatch console may display the green check mark symbol (indicating acknowledgment) for only the first of the two calls. When the folder resource size in Elite Dispatch is set to 1, this issue does not occur. Emergency call functionality is not impaired, but the inconsistent display of acknowledgments may be confusing to the user. Description: When a user sets the "Resource Size" to a value greater than 1, the dispatch console now displays acknowledgments of emergency calls correctly.

RN_CCMPD-00002562 Abstract: After takeover of Multi-Select (MSEL) group or patch group, channel may transmit at wrong priority. System Platforms Affected: ASTRO 25 7.14 Special Configurations: This issue affects patch channels in an open MSEL group on a patching console. User Symptoms: When the dispatcher at a patching console performs a "general transmit" operation on an open MSEL or patch group, and later one of the transmitting channels is taken over by an "instant transmit" operation on a different console and then dekeyed, the affected channel is rekeyed at "patch transmit" priority rather than at "general transmit" priority as expected. When this occurs, the affected channel is subject to takeover by a "general transmit" operation on a parallel console until the patching console finishes its transmissions on that channel. Description: When the dispatcher at a patching console performs a "general transmit" operation on an open MSEL or patch group, and later one of the transmitting channels is taken over by an "instant transmit" operation on a different console and then dekeyed, the affected channel is now rekeyed at "general transmit" priority as expected and is not subject to takeover by a "general transmit" operation on a parallel console.

16

ASTRO 25 7.15 Release Notes RN_CCMPD-00002565 Abstract: Changes to push-to-talk (PTT) configuration for speakers may not take effect after first restart of Elite Dispatch. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user changes the "Mute on PTT" setting for a speaker on the dispatch console, using the Provisioning Manager (PM) application, the changes may not take effect after the user restarts the Elite Dispatch application. However, when the user restarts Elite Dispatch again, the changes take effect as expected. Description: When a user changes the "Mute on PTT" settings in the PM application for a speaker on the dispatch console, the changes now take effect after the first Elite Dispatch restart.

RN_CCMPD-00002566 Abstract: Private call audio from subscriber to console operator is routed to unselect speaker. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a subscriber initiates a private call to a console operator on an unselected resource, private call audio from that subscriber is routed to the unselect speaker under the following conditions: • The operator responds to the call before selecting the resource. • The operator subsequently selects the resource and then keys again. All subsequent private call audio from the subscriber is routed to the select speaker as expected. Description: When a subscriber initiates a private call to a console operator on an unselected resource, private call audio from that subscriber is now routed to the select speaker as expected.

Known Problems RN_CCMPD-00002888 Abstract: Console may send erroneous warning events about Voice Processor Module (VPM) links or Console Alias Manager (CAM) links. System Platforms Affected: ASTRO 25 7.15 Special Configurations: This issue affects systems in which third-party software development kit (SDK) software is running in peer mode (registered as DUI_TYPE) with the Elite Dispatch Console software. User Symptoms: When a user closes either the Elite Dispatch application or third-party SDK software while those applications are operating simultaneously, the dispatch console may send one of the following warning events to the Unified Event Manager (UEM): “VPM Link Down/User Requested” or “CAM Link Unconfigured/User Logout”. When this issue occurs, the VPM and CAM links remain operational until both applications are closed, and neither warning event requires the user to take any action. Console functionality is not impaired, but the erroneous warning events may be confusing to the user. Work Around: Users should close the Elite Dispatch and third-party SDK applications at the same time To recover, users should restart both applications, because the restart clears the warning events.

RN_CCMPD-00002898 Abstract: Console may not receive push-to-talk (PTT) callback after busied conventional talkgroup call. System Platforms Affected: ASTRO 25 7.15 Special Configurations: This issue affects an MCC 7500 Dispatch Console or MCC 7100 IP Console equipped for the Conventional Talkgroups feature. User Symptoms: When a console user attempts to initiate a call on a conventional talkgroup and that request is busied, the console user receives a notification that the call request is queued, as expected. However, when a channel becomes available for the requested call, the user may not receive a PTT callback as expected. Work Around: None. To recover, the user must manually reinitiate a console PTT request.

RN_CCMPD-00002899 Abstract: Console PC sends fault to Unified Event Manager (UEM) upon reboot. System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A

17

ASTRO 25 7.15 Release Notes User Symptoms: When a user reboots a PC that is configured as an MCC 7500 Dispatch Console or MCC 7100 IP Console, full synchronization with the UEM fails. When this issue occurs, the UEM displays a "Communication Failure" fault for the affected console. When the user starts the Elite Dispatch application, the UEM fault is cleared. Work Around: Users should start Elite Dispatch at least once after rebooting a console PC.

RN_CCMPD-00002967 Abstract: Outbound patch transmit fails on conventional Consolette channels with talk-permit tone. System Platforms Affected: ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14, ASTRO 25 7.15 Special Configurations: This issue affects patched calls using conventional channels connected to a conventional channel gateway (CCGW) operating on either GGM 8000 or S2500 hardware, using Tone Remote Control (TRC) or E&M keying, to a Consolette used as a control station on a trunking system with talk-permit tones enabled on the Consolette for that talkgroup. User Symptoms: When the system is configured as noted in “Special Configurations” and inbound activity received on another console patch member causes a push-to-talk (PTT) on the CCGW channel, the console receives a trunking talk-permit tone from the Consolette as “inbound user audio”, and the console de-asserts the PTT on that CCGW channel. When the talk-permit tone finishes, the console re-asserts the PTT on the CCGW channel, causing the talk-permit tone to be generated again and the PTT to be de-asserted again (and re-asserted again when the tone finishes), and so on. When this issue occurs, outbound transmit audio from the console to the trunked Consolette is lost. Work Around: Using the appropriate version of Customer Programming Software (CPS), users should configure the Consolette trunking personalities to disable talk-permit tones for talkgroups that could be included in a console patch. An alternative work-around is to reconfigure the Consolette so that it uses ASTRO Console Interface Module (ACIM) keying rather than E&M or TRC keying. ACIM Consolettes are not affected by this issue when used with MCC 7500 or MCC 7100 software version 7.13.02.34 or later. A list of Consolettes updated with this work around and copies of unmodified Consolette codeplugs should be maintained to facilitate easy return of the “talk permit tone enabled” configuration when a long-term fix is available.

RN_CCMPD-00002982 Abstract: Console cross busy indication for conventional talkgroup stays on continuously. System Platforms Affected: ASTRO 25 7.15 Special Configurations: This issue affects systems equipped for conventional talkgroups, which are introduced in the ASTRO 25 7.15 release. User Symptoms: Rarely, the console cross busy indicator for a conventional talkgroup remains active after the end of a talkgroup call, instead of deactivating as expected. When this occurs, the dispatch console reports the outbound channel as active when in fact it is idle. Any transmission by a subscriber or console that is a patch member of the talkgroup restores the cross busy indicator to the correct state. Work Around: None.

MKM 7000 Console Alias Manager (CAM)

Issue Update RN_CCMPD-00002575 Abstract: CAM Server service startup fails. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user attempts to launch the CAM Server service using the Control Panel in the CAM Configuration Utility, the startup fails. When this occurs, one of the following warning messages may appear: ”The MKM 7000 Console Alias Manager failed to start, please contact Motorola Solution Support Center for further assistance.” “Operation failed to complete due to a timeout.” Description: When a user launches the CAM Server service using the Control Panel in the CAM Configuration Utility, the startup now completes successfully.

18

ASTRO 25 7.15 Release Notes Known Problem RN_CCMPD-00002891 Abstract: Underscore ("_") character is treated as wild card in database searches. System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A User Symptoms: When user attempts to locate a record in the CAM database and includes the underscore character in the search string, the CAM erroneously treats the underscore as a wild card character, and resulting volume of search results may impede the user's efforts to locate the desired record. For example: • When the search option selection is "Contains" and the search string contains only the underscore character, the search produces a list all records of the selected type (for example, Alias) in the database. • When the search option selection is "Starts with" and the search string is "Johns_Radio", the search produces results that include any records with names that start with "Johns" followed by any single character followed by "Radio" and any characters found at the end. Work Around: Users should search using keywords that produce a small enough set of results to enable the user to locate the desired record.

MLC 8000 Comparator

New Feature RN_CCMPD-00002868 Abstract: MLC 8000 Comparator can now process RF traffic for up to 64 subsites on each channel. System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A Description: To make the MLC 8000 Comparator more equivalent to its ASTRO-TAC and DIGITAC predecessors, the traffic capacity limit was increased from 16 to 64 subsites per channel.

Known Problem RN_CCMPD-00002892 Abstract: MLC 8000 Configuration Tool (CT) window may not maximize. System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A User Symptoms: When a user minimizes the CT application window while a channel cluster that includes multiple ASTRO Gateway Units (AGUs) is open, the user may be unable to maximize the window as expected. Functionality is not impaired, but when users cannot maximize the CT window, they may erroneously believe that the CT has become unresponsive and may attempt to manually abort a configuration process while it is in progress. Work Around: After minimizing the CT window, wait to maximize it until the progress bar in the Establish Device TCP Connections dialog box indicates that the operation is complete.

MZC 5000 Zone Controller (ZC)

Issue Update RN_CCMPD-00002877 Abstract: Group calls are rejected after ZC reset. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a ZC resets, or when a channel group configuration covering more than one site with multiple groups per channel is submitted, the group calls are not partitioned as configured. When this issue occurs, the affected group calls are rejected, and the ATIA (Air Traffic Information Access) Log Viewer application displays the message “Subscriber Reject Reason = No Partition Resources”.

19

ASTRO 25 7.15 Release Notes Description: When a ZC resets, or when a channel group configuration covering more than one site with multiple groups per channel is submitted, the group calls are now partitioned as configured, and the message listed in the User Symptoms no longer appears.

Known Problem RN_CCMPD-00002913 Abstract: "Controlling Zone Update" and "Call Activity Update" messages in ZoneWatch (ZW) display incorrect values. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14, ASTRO 25 7.15 Special Configurations: N/A User Symptoms: When a subscriber keys up on a regrouped SmartX talkgroup, the "Controlling Zone Update" and the "Call Activity Update" messages in the ZW application display the secondary ID as the supergroup ID, instead of displaying the supergroup ID as expected. In addition, both messages display the target talkgroup's fixed group ID as the affiliated talkgroup ID, instead of displaying the supergroup ID as the affiliated talkgroup ID. When this issue occurs, the same incorrect values appear in Air Traffic Information Access (ATIA) output collected by the Air Traffic Router (ATR). Work Around: None.

Network Security Firewalls

Known Problem RN_CCMPD-00002890 Abstract: FortiGate web configuration utility may display empty screen. System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A User Symptoms: When a user attempts to operate the FortiGate web configuration utility for Internet Protocol version 4 (IPv4) policy using the Internet Explorer version 9 (IE 9) web browser, the utility may display an empty interface screen. Work Around: Use the Command Line Identifier (CLI) widget within the browser (this widget is enabled by default) In the System > Dashboard > Status window pane of the browser, scroll down to the CLI widget, then click in the widget window to activate the CLI of the firewall. To view IPv4 policies, execute the following commands: "config firewall policy" and "show". To view IP version 6 (IPv6) policies, execute the following commands:"config firewall policy6" and "show". For Zone Core Protection (ZCP) firewalls only: Before executing the above commands, select the appropriate Virtual Domains (VDOM) by executing the following commands: "config vdom" and "edit vdom_name". The ZCP Fortinet firewall is currently configured with 2 VDOMs; "root" and "zcpvdom". Type the name of the VDOM for the desired policies, then execute the commands to view the firewall policies for the selected VDOM.

Packet Data Gateway (PDG)

Known Problem RN_CCMPD-00002968 Abstract: Synchronization link between PDGs may reset. System Platforms Affected: ASTRO 25 7.15 Special Configurations: This issue affects systems equipped for both High Performance Data (HPD) and Dynamic System Resilience (DSR). User Symptoms: Rarely, under steady state load conditions, the Secure Socket Layer (SSL) synchronization link between redundant PDGs may reset. When this issue occurs, the Unified Event Manager (UEM) may display the following error messages: “PDR synchronization link Down” (followed after five seconds by “PDR synchronization link Up”) “error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac.”

20

ASTRO 25 7.15 Release Notes No data loss occurs with this issue, and the system recovers without user intervention. Work Around: None.

Routers and Gateways

Issue Update RN_CCMPD-00002597 Abstract: Conventional Channel Gateway (CCGW) does not apply conventional channel reconfigurations from the Provisioning Manager (PM) successfully. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: This issue affects GGM 8000 CCGWs equipped with an Enhanced Conventional Gateway module only. GGM 8000 CCGWs equipped with an analog/V.24 interface kit and MNR S2500 CCGWs are not affected. User Symptoms: When the user creates and configures a conventional channel on the CCGW from the PM, then performs a reconfiguration using the PM (for example, by reassigning the channel to a different port or by creating a second channel with an identical configuration on a different port), the CCGW does not apply the configuration changes. For example, if a channel is reassigned to a different port, the CCGW keeps the channel on the original port, and if a second channel with an identical configuration is created on a different port, the CCGW makes the first channel unavailable (that is, missing in the CCGW configuration or assigned to an unknown port with a “??”label). Description: When the user creates and configures a conventional channel on the CCGW from the PM, then performs a reconfiguration using the PM (for example, by reassigning the channel to a different port or by creating a second channel with an identical configuration on a different port), the CCGW now successfully applies the configuration changes.

Known Problem RN_CCMPD-00002912 Abstract: Rarely, audio may be truncated at start of digital conventional calls. System Platforms Affected: ASTRO 25 7.5, ASTRO 25 7.6, ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14, ASTRO 25 7.15 Special Configurations: This specific audio truncation problem is possible only on digital conventional channels. This issue occurs only when the dispatch console and the Conventional Channel Gateway (CCGW) are both located at sites connected to the zone master site using links with latencies greater than 30 milliseconds (ms). User Symptoms: Users may miss at least 180 ms of audio at the start of a digital conventional call. In systems using encrypted audio, as much as 540 ms of audio may be missing at the start of a digital conventional call. The audio truncation occurs in only one direction: • If subscribers miss audio at the start of a call initiated by a dispatcher, the dispatcher does not miss audio at the start of calls initiated by subscribers. • If the dispatcher misses audio at the start of a call initiated by a subscriber, subscribers do not miss audio at the start of calls initiated by a dispatcher. When this issue occurs, typically only one dispatch console is monitoring the digital conventional channel resource. No other dispatch console or Archive Interface Server (AIS) is monitoring the affected channel. Work Around: Two workarounds are available. The first workaround is preferred because it does not increase the audio throughput delay. (1) Monitor the conventional channel with an additional dispatch console (parallel operator position) or AIS with low latency to the Rendezvous Point Router (Gateway Router). For example, start logging the digital conventional channel traffic using an AIS at the master site. As long as the latency between the additional dispatch console or AIS is less than the latency to the original console site or the conventional channel site, the audio truncation is eliminated. (2) If the audio truncation occurs on calls initiated by subscribers, increase the audio hold off time in the CCGW by 30 ms. If the audio truncation occurs on calls initiated by dispatchers, increase the audio hold off time by 30 ms for the dispatch console. The Motorola Gold Elite Gateway (MGEG) is unaffected by this problem. If audio truncation is still intermittent after increasing the appropriate audio holdoff timer, site link jitter could still be exposing the problem; increase the holdoff timer another 10 ms (for a total 40 ms increase).

21


SmartX Site Converter

Known Problem RN_CCMPD-00002969 Abstract: SmartX site enters failsoft when all control channels are malfunctioned during RF interference. System Platforms Affected: ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.13, ASTRO 25 7.14, ASTRO 25 7.15 Special Configurations: This issue affects systems that include SmartX RF sites. User Symptoms: As long as an RF site has one usable control channel and one usable voice channel (and the user has requested wide trunking operation), the site operates in wide trunking. Normally, when an RF channel detects interference, the system malfunctions the channel until the interference subsides. However, when channel malfunctions at an RF site are so prevalent that the site no longer has an operational voice channel and an operational control channel, the site normally enters "Illegal Carrier Override" (ICOR) mode for one (1) hour. In ICOR mode, the site ignores interference as a reason to malfunction RF channels, and the site can remain in wide trunking (with potential RF capture issues) rather than reverting to failsoft operation. Because of a software defect in the infrastructure, the system does not enter ICOR immediately as expected, and the affected RF site goes into failsoft for approximately 10 seconds, then enters ICOR, then returns to wide trunking (but remains in ICOR for at least 1 hour afterward). Work Around: None.

System Traffic Monitor Applications

Issue Updates RN_CCMPD-00002581 Abstract: "System Voice and Data Detail" report displays less detail than requested in "Counts" and "Duration" graphs. System Platforms Affected: ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user requests a "System Voice and Data Detail" report from the Historical Reports application with 15-minute intervals in the "Counts" and "Duration" graphs, the application generates reports with one-hour intervals in both graphs. The information displayed in the graphs is accurate, but the inability to retrieve the requested level of detail may be confusing to the user. Description: When a user requests a "System Voice and Data Detail" report from the Historical Reports application with 15-minute intervals in the "Counts" and "Duration" graphs, the application now generates reports with the requested intervals in both graphs.

RN_CCMPD-00002582 Abstract: Time Division Multiple Access (TDMA) calls involving more than 32 sites may not appear in grid window in ZoneWatch (ZW) application. System Platforms Affected: ASTRO 25 7.6, ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a TDMA group call is performed on more than 32 sites, the call is not displayed in the grid window in ZW as expected. The call is displayed in the raw ZW window and in the Air Traffic Information Access (ATIA) Log Viewer, but neither of those windows displays the additional information about channel slots that is displayed in the grid window. When this issue occurs, the Zone Controller (ZC) sends the correct information through ATIA to third-party applications. However, the inability to view the expected details in the grid window may be confusing to the user. Description: When a TDMA group call is performed on more than 32 sites, the call is now displayed in the grid window in ZW as expected.

22

ASTRO 25 7.15 Release Notes RN_CCMPD-00002583 Abstract: ZoneWatch (ZW) application may not fully refresh display in channel grid. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user adjusts the width of the channel grid in the ZW window, ZW may apply the change only to the first visible site row, rather than applying the change to the entire grid as expected. When the user presses the F5 key to refresh the ZW display, the width of the channel grid is adjusted for all sites displayed. Description: When a user adjusts the width of the channel grid in the ZW window, ZW now applies the change to the entire grid as expected.

RN_CCMPD-00002584 Abstract: Reports exported to Excel from Historical Reports application may contain misaligned headers or data. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user exports a report from the Historical Reports application to the Excel file format, some columns in the exported file may contain headers or data that are not aligned correctly. The incorrect alignment should have only minor impact on the readability of the report but may be inconvenient to the user. Description: When a user exports a report from the Historical Reports application to the Excel file format, the columns in the exported file now contain headers and data that are aligned correctly.

RN_CCMPD-00002939 Abstract: Unified Event Manager (UEM) erroneously displays critical alarm for Air Traffic Router (ATR). System Platforms Affected: ASTRO 25 7.14 Special Configurations: This issue affects multiple system operator (MSO) systems where an ATR server is installed in a zone that is enabled for the Dynamic System Resilience (DSR) feature. User Symptoms: Approximately six weeks after an ATR server is installed in a zone enabled for DSR, the UEM in an MSO system with a standby zone controller (ZC) erroneously displays the critical alarm “ATR-ZC link connection down” (instead of displaying the event “ATR-ZC link connection standby”). The erroneous alarm display persists until the user performs a process restart on the ATR. Description: The UEM in an MSO system with a standby ZC no longer reports the critical alarm “ATR-ZC link connection down” unless the reported condition actually exists.

RN_CCMPD-00002940 Abstract: Process controlling connections between Air Traffic Router (ATR) and Zone Controller (ZC) may restart. System Platforms Affected: ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: Under heavy call loading and unfavorable network conditions, when a user opens or closes the ZoneWatch (ZW) application, the process controlling connections between the ATR and ZC may restart. When this issue occurs: • All connections between ZW applications and the ATR restart. • Logging of Air Traffic Information Access (ATIA) data stops for several seconds. • Logging of historical data (statistics) stops for several seconds. • The Unified Event Manager (UEM) displays the critical alarm "ATR-ZC link connection down" for several seconds. • Reporting of information to the ATIA interface and the Computer Aided Dispatch Interface (CADI) stops for several seconds. Description: Under heavy call loading and unfavorable network conditions, when a user opens or closes the ZW application, the process controlling connections between the ATR and ZC now continues to function normally.

RN_CCMPD-00002942 Abstract: Historical Reports application displays incorrect value for Level of Service (LOS) alias. System Platforms Affected: ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A

23

ASTRO 25 7.15 Release Notes User Symptoms: When a user requests the "Shared Service Site Detail" report from the Historical Reports application, the report contains an LOS alias consisting of random digits, instead of the actual alias value as defined in the Provisioning Manager (PM) application. Description: When a user requests the "Shared Service Site Detail" report from the Historical Reports application, the report now contains an LOS alias consisting of the actual alias value as defined in the PM application.

RN_CCMPD-00002946 Abstract: Historical Reports may display incorrect values for some statistics. System Platforms Affected: ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: The Historical Reports application may display incorrect values for the “Data Channel Request” statistic in the "Site Data Detail" and "Site Voice and Data Detail" reports. The application may also display incorrect values for the “data_channel_time_util” statistic, which does not appear in any predefined report but may appear in some custom reports defined by users. Description: The Historical Reports application now displays correct values for the “Data Channel Request” statistic in the "Site Data Detail" and "Site Voice and Data Detail" reports, as well as for the “data_channel_time_util” statistic.

RN_CCMPD-00002947 Abstract: Affiliation Display (AD) application may report subscriber affiliation incorrectly. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a subscriber that was affiliated to a talkgroup is later affiliated to a different talkgroup that is not configured in the Radio Network Interface (RNI), the “Radio Viewer” panel in the AD application may indicate that the subscriber is still affiliated to the prior talkgroup, instead of indicating that the subscriber is no longer affiliated in the system. Description: When a subscriber that was affiliated to a talkgroup is later affiliated to a different talkgroup that is not configured in the RNI, the “Radio Viewer” panel in the AD application now correctly indicates that the subscriber is no longer affiliated in the system.

RN_CCMPD-00002948 SR ID: CCMPD01902864 SR Severity: C-Minor Abstract: Affiliation Display (AD) application may display blank fields or incorrect subscriber count. System Platforms Affected: ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: This issue affects systems with a Computer Aided Dispatch Interface (CADI) where the CADI command CADCMD__AFF_DOWNLOAD_REQ is implemented. User Symptoms: When a user opens the "Site Viewer", "Talkgroup Viewer" or "Radio Viewer" screen in the AD, the "Talkgroup Alias" and "Radio Alias" fields may be blank, instead of displaying the talkgroup alias and subscriber alias, respectively. Also, in releases prior to ASTRO 25 7.13, when a user opens the "Site Viewer" or "Talkgroup Viewer" screen in the AD, the "Radios" field may display an incorrect value for the number of subscribers, and the discrepancy between the incorrect value displayed and the actual number of subscribers may be significant. Description: When a user opens the "Site Viewer", "Talkgroup Viewer" or "Radio Viewer" screen in the AD, the "Talkgroup Alias" and "Radio Alias" fields now display the talkgroup alias and subscriber alias, respectively. In releases prior to ASTRO 25 7.13, when a user opens the "Site Viewer" or "Talkgroup Viewer" screen in the AD, the "Radios" field now displays the correct value for the number of subscribers.

RN_CCMPD-00002960 Abstract: Zone Historical Reports application displays incorrect values for "Percent Usage" in "Channel" reports. System Platforms Affected: ASTRO 25 7.11, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user generates "Channel" reports using the Zone Historical Reports application, the "Percent Usage" statistic contains incorrect values. Description: When a user generates "Channel" reports using the Zone Historical Reports application, the "Percent Usage" statistic now contains correct values.

24

ASTRO 25 7.15 Release Notes Known Problems RN_CCMPD-00002958 Abstract: Rarely, ZoneWatch (ZW) does not refresh call data after recovering from broken inter-zone connection. System Platforms Affected: ASTRO 25 7.5, ASTRO 25 7.6, ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14, ASTRO 25 7.15 Special Configurations: This issue affects systems where ZW is connected to an Air Traffic Router (ATR) in a different zone, using an inter-zone link. User Symptoms: Rarely, after r from a broken inter-zone connection, the ZW application does not refresh call data or other packets. As a result, ZW erroneously appears to be connected to the ATR to which it was previously connected. When this issue occurs: • Calls that were started before the connection was broken erroneously appear on the ZW grid as ongoing. • Calls that were started after the recovery of the inter-zone connection do not appear on the ZW grid. • The user observes no call activity on the ZW grid unless and until the ZW application is restarted. • Updates about channel status and site status from the Unified Event Manager (UEM) continue to be displayed as colors on the ZW grid. Work Around: None. To recover, restart the ZW application.

RN_CCMPD-00002972 Abstract: Rarely, Affiliation Display (AD) may become unresponsive. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14, ASTRO 25 7.15 Special Configurations: N/A User Symptoms: Rarely, users may observe that the AD application stops refreshing data and stops responding to user inputs. When the user minimizes and then restores the AD application window, the display is black. Work Around: None. To recover, users should close and restart the application.

RN_CCMPD-00002973 Abstract: ZoneWatch (ZW) online help contains incorrect information. System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A User Symptoms: The “Channel Grid Watch Window” section in the online help for the ZW application incorrectly states that the corresponding window in the application can monitor call information only for trunking channels and not for conventional talkgroup channels. ZW functionality is not impaired, but the incorrect information in the online help may be confusing to the user. Work Around: None. For more current information, users should consult the “Channel Grid Watch Window” section in the “ZoneWatch” manual provided with the ASTRO 25 system.

Unified Event Manager (UEM)

Issue Updates RN_CCMPD-00002925 Abstract: Event archive files downloaded from UEM cannot be opened. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user downloads an event archive file in Comma Separated Values (CSV) format from the UEM, the archive file is unpacked on the server with the extension .gz, and the user cannot open the file. Description: When a user downloads an event archive file in CSV format from the UEM, the user can now open the file.

RN_CCMPD-00002963 Abstract: Restore of UEM database may fail. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: After multiple backup and restore operations, a restore of the UEM database from backup may fail.

25

ASTRO 25 7.15 Release Notes Description: After multiple backup and restore operations, a restore of the UEM database from backup now completes successfully.

RN_CCMPD-00002964 Abstract: UEM may not display requested information in "Current Statistics Graph" window. System Platforms Affected: ASTRO 25 7.14 Special Configurations: This issue affects systems where 50 or more interfaces are configured on a Motorola Network Router (MNR) device. User Symptoms: When a UEM user opens the "Current Statistics Graph" window for an MNR device for which 50 or more interfaces are configured, the window displays only messages saying, "Fetching Data...", instead of displaying the requested information. Description: When a UEM user opens the "Current Statistics Graph" window for an MNR device for which 50 or more interfaces are configured, the window now displays the requested information.

RN_CCMPD-00002965 Abstract: UEM erroneously allows creation of custom view using excessively long text string. System Platforms Affected: ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user creates a new custom view, using a long text string in a criteria field, the view is created, but the following conditions occur: • A generic Postgres error appears, but the message contains no diagnostic information to help the user correct the problem. • The mouse icon displays a "busy" indication. • The user cannot remove the newly created custom view without first clocking on another object in the Navigation view. Description: When a user creates a new custom view, using a long text string in a criteria field, the user now sees an error message indicating which text string exceeded the size limit of the applicable field, and the custom view is not created until the user corrects the problem.

Known Problems RN_CCMPD-00002900 Abstract: Device count in custom view under Network Database View is not updated after device discovery. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14, ASTRO 25 7.15 Special Configurations: N/A User Symptoms: When a user performs a discovery operation for one or more devices while a custom view under the Network Database View is open in the UEM, the device counter in the observed custom view is not updated to reflect the newly discovered devices. Work Around: None. To get the correct device count, click the "Refresh" button on the toolbar menu.

RN_CCMPD-00002989 Abstract: Unified Event Manager (UEM) reports erroneous alarm for Licensing Service. System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A User Symptoms: The UEM reports a "Link is down" alarm for the managed resource "Licensing Service at UCS<xx>.UCS" (where "<xx>" can be either 01 or 02) when in fact the link is operational. Functionality is not impaired, but the erroneous alarm may be confusing to the user. Work Around: None. To recover, users should perform the following actions: 1. Log on to the UEM client. 2. Select the User Configuration Server (UCS) as the network element and select “Synchronize” from the context menu. 3. In the Job View, verify that the synchronization job completes.

26


Unified Network Configurator (UNC)

Issue Updates RN_CCMPD-00002571 Abstract: Users cannot roll Simple Network Management Protocol version 3 (SNMPv3) passphrase using UNC. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When users attempt to roll the SNMPv3 passphrase using the UNC, the operation is marked as failed, and an error message appears. Description: Users can now roll the SNMPv3 passphrase using the UNC.

RN_CCMPD-00002572 Abstract: UNC displays confusing message for login errors. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user attempts to log into the UNC application and enters an invalid user name or an invalid password, the user sees the following message in a popup window: "An unexpected problem has occurred." When the user clicks "OK" in the popup window and enters a valid user name and password, the login completes successfully. Login should be blocked when incorrect credentials are entered, but the message displayed provides no guidance about corrective action and may be confusing to the user. Description: When a user attempts to log into the UNC application and enters an invalid user name or an invalid password, the user now sees an error message indicating that incorrect credentials were entered.

RN_CCMPD-00002573 Abstract: User may be unable to log in to UNC server. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: User may be unable to log in to the UNC server. When this occurs, the Unified Event Manager (UEM) may display a malfunction event for the UNC server and may instruct users to re-enable the server. In addition, the Voyence service may restart without the user instructing it to do so. Disabling and then re-enabling the UNC server clears the stall connections. Description: Users can now log in to the UNC server as expected. The UEM no longer displays a malfunction event for the UNC server (and no longer instructs users to re-enable the UNC server) unless an actual malfunction exists, and the Voyence service no longer restarts without the user instructing it to do so.

RN_CCMPD-00002574 Abstract: Report Advisor in UNC may not generate reports. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user requests a report from the Report Advisor application in the UNC, the report may not be generated as expected. When this occurs, the "in-progress" icon in the application spins continuously and persistently, instead of stopping as expected, and no report appears. Description: When a user requests a report from the Report Advisor, the application now generates the report successfully, and the "in-progress" icon now stops spinning when the report appears.

RN_CCMPD-00002580 Abstract: UNC fails to distribute update for "Subsite Alias" field. System Platforms Affected: ASTRO 25 7.14 Special Configurations: This issue affects systems with simulcast or multisite configurations. User Symptoms: When a user attempts to distribute an update for the "Subsite Alias" field from the UNC, the distribution fails, and the user is notified that the "Subsite Alias" string exceeds the maximum allowed number of characters.

27

ASTRO 25 7.15 Release Notes This issue occurs because the UNC erroneously allows users to enter up to 20 characters in the "Subsite Alias" field, but this field actually accepts no more than 16 characters. Description: The UNC no longer allows users to enter more than the maximum allowed 16 characters in the "Subsite Alias" field. As a result, when a user attempts to distribute an update for the "Subsite Alias" field, the distribution now completes successfully.

Known Problem RN_CCMPD-00002889 Abstract: UNC client may become unresponsive. System Platforms Affected: ASTRO 25 7.15 Special Configurations: N/A User Symptoms: The UNC client window may become unresponsive to user inputs. This issue is most likely to occur when the user selects all of the following debugging options in the Java Control Panel: • Enable Tracing • Enable Logging • Show Applet Lifecycle Exceptions When this issue occurs, data on the UNC server is not affected. Work Around: None. To recover, close and reopen the client.

Virtual Management Server

Issue Updates RN_CCMPD-00002577 Abstract: Unified Event Manager (UEM) or Unified Network Configuration (UNC) may display erroneous error message. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: This issue may occur on a VMS using Hewlett Packard (HP) DL380 server hardware. User Symptoms: The UEM or UNC console may report a lockup of the central processing unit (CPU) when no actual lockup behavior has been observed. When this occurs, an error message similar to the following example appears: "08:59:15 DUMP [UCS1] kernel:BUG: soft lockup - CPU#2 stuck for 64s! [vmmemctl:703]" Functionality is not impaired, but the erroneous error message may be confusing to the user. Description: The UEM and UNC consoles now report a CPU lockup only when actual lockup behavior has been observed.

RN_CCMPD-00002578 Abstract: Zip archive created during "getlogs" operation contains incorrect timestamp in filename. System Platforms Affected: ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: This issue may occur on a VMS using Hewlett Packard (HP) DL380 server hardware. User Symptoms: When a user initiates a "getlogs" operation, the operation archives the desired logs to a zip file, with a timestamp embedded in the zip file name as expected, but the month value in the timestamp is one less than expected. For example, a log file collected in October includes 09 instead of 10 as the month value in the timestamp. The user can see the actual creation date of the zip file by performing the "ls -l" command in the log file directory. Logging functionality is not impaired, but the incorrect timestamp may be confusing to the user. Description: When a user initiates a "getlogs" operation and the operation archives the desired logs to a zip file, the timestamp embedded in the zip file name now contains the correct value for the month.

28