Release Notes
IR Prognosis 10.2 UCF Important Notices Copyright Copyright 2014 - Integrated Research Limited (ABN 76 003 588 449). All rights reserved. This guide is protected by copyright law and international treaties. No part of this document may be reproduced in any form or distributed, and no derivative works such as translations may be made, without prior written permission from Integrated Research. Unauthorized reproduction or distribution of this document or of the computer software, or any portion of it, may result in severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under the law. Date of Issue: 19 November 2014 Product Version: Prognosis 10.2 Trademarks Prognosis and IR are registered trademarks of Integrated Research Limited. Other product names mentioned in this manual may be trademarks, registered trademarks and/or service marks of their respective owners and may not be used for commercial purposes without express permission from their respective owners. Third Party Software License Notices Please refer to the Third Party Software License Guide on the Prognosis installation CD or in the Documentation folder of the Prognosis Installation path for details of third party software license notices. Disclaimer The information in this guide is published as is and without warranties of any kind, expressed or implied, including those regarding the accuracy or completeness of the information, warranties of merchantability and fitness for a particular purpose, or those arising from a course of dealing, usage or trade practice. In no event will Integrated Research be liable for any damages whatsoever (including, without limitation, those resulting from lost profits, lost data or business interruption) arising out of the use, inability to use, or the results of this guide. Page 2
Release Notes Introduction Prognosis for Unified Communications Foundation Edition is an abridged version of the full Prognosis unified communications management product. It is specifically designed as a monitoring tool for smaller environments. It provides a range of metrics including: QoS information such as MOS, latency, packet loss and jitter; component availability and device utilization. A browser-based interface provides access for easy configuration and data monitoring. This Release Notes document contains very important information that must be read carefully before attempting to install this new Prognosis version. Please also read the Readme.txt file on the installation CD for any late-breaking information. ***** I M P O R T A N T 10.2 UPGRADE ****** Prognosis will be shut down for the upgrade. Therefore, users that are using the Prognosis Web Application will be logged out during this time. Users will need to re-login to the Web Application upon completion of the upgrade. When upgrading from Prognosis VoIP Monitor (PVM) version or from Prognosis version 10.0, the previously collected data will not be preserved. Data is preserved for users who are upgrading from Prognosis version 10.1.5 onwards. Page 3
IR Prognosis 10.2 UCF Contents Important Notices... 2 Introduction... 3 New and Changed Features... 5 Common... 5 Prognosis for Unified Communications... 6 AudioCodes... 6 Avaya... 6 Cisco Unified Communications... 7 Microsoft Lync... 8 Sonus... 9 Issues Resolved...10 Prognosis User Interface...10 Prognosis for Unified Communications...10 Limitations...12 Common...12 Prognosis for Unified Communications...13 Avaya Aura Communications...13 Avaya Communication Server 1000...13 Cisco Unified Communications...14 Microsoft Lync...16 Prognosis UC Reporter...17 Known Issues...18 Common...18 Prognosis User Interface...19 Prognosis for Unified Communications...19 Page 4
Release Notes New and Changed Features Common URLs in Alerts Alerts can be set to include URLs to the most relevant web dashboard that relates to the alert condition. While some URLs will be added for some parts of Prognosis 10.2, most of the actual URLs will be added over time and made available in future releases. Alert Blueprints Alert Blueprints can enrich alert output sent via email or SNMP trap with a wide range of extra information related to the system being managed and other relevant systems. While some alert blueprints will be added for some parts of Prognosis 10.2, most of the content will be added over time and made available in future releases. The Prognosis SNMP MIB has been extended to accommodate this extra information. Page 5
IR Prognosis 10.2 UCF Prognosis for Unified Communications AudioCodes AudioCodes Session Border Controller (SBC) Voice Quality Prognosis 10.2 provides voice quality information for AudioCodes SBC Mediant series. The Voice quality information gathered from an AudioCodes SBC is correlated with voice quality information received from other devices in order to provide an end-to-end view. Prognosis presents this information in a Voice Quality 360 diagram which allows easy troubleshooting as media traffic traverses across multi-vendor environments. Prognosis also provides call statistics information including Concurrent calls, Inbound Attempts and Outbound attempts. AudioCodes Session Border Controller (SBC) Mediant Series Health Prognosis 10.2 supports monitoring for AudioCodes Session Border Controller (SBC) Mediant series. This includes the following AudioCodes Mediant versions: - 500-800 - 1000-2000 - 2600-3000 - 4000-9000. Prognosis provides SBC health statistics information. This includes; the status of each SBC, the status of the Signaling Group, CPU and Memory utilization and the firmware version. Foundation Edition users can view the Voice Quality and Health information provided they have the correct module. The Voice Quality 360 feature is not available to Foundation Edition users. Avaya Identifying Routers That May Strip Quality of Service (QoS) Tags Prognosis can identify routers that may have been stripping QoS tags from voice streams in an Avaya environment. Prognosis provides a Display that shows the routers based on the number of streams that traverse through each one and have QoS tags missing. Users can also view historical information and drilldown to the actual calls that have been impacted by this. Better Indication for Network Hops Data Availability Network hops data is not necessarily available for all Avaya calls. In previous versions of Prognosis, there was a blue color indicator to show that hop data was available. However, this indicator was not very noticeable so in this latest version of Prognosis, a specific link, Details + Hops, is used to indicate that hop data is available. When no hop data is available the link will be shown as just Details. Page 6
Release Notes Cisco Unified Communications Physical Gateway Running with Multiple Protocols Previous versions of Prognosis did not support physical gateways having multiple interfaces where some interfaces were H323 while others might be MGCP and SCCP, even though there were multiple logical gateway entries under the Cisco Unified Communication Manager Configuration Database with different names. Prognosis 10.2 has been enhanced to ensure that information from a single physical gateway can be supplied to multiple logical gateways. Standalone IOS Router, H323 and SIP Gateway Monitoring Previous versions of Prognosis could only monitor H323, MGCP and SCCP gateways that were added to the Cisco Unified Communications Manager as a gateway device. If the Cisco gateways were standalone (i.e. not used in conjunction with Cisco Unified Communications Manager or the gateways are added as SIP trunks), it was not possible to monitor them. With Prognosis 10.2, users can set up monitoring for these standalone gateways separately including the status of the various PSTN interfaces and SIP traffic statistics. In addition, Prognosis can be set up to provide basic CPU, memory and hardware environment statistics on various Cisco IOS devices in 10.2. Voice Quality by Location Support for Cisco Unified Communications Manager Prognosis 10.2 has been enhanced to provide voice quality summary information for calls based on the location pair of the devices involved in the call. There is a new window counting the number of calls with Good, Fair, Poor or Unacceptable MOS for each location pair. Customers who wish to utilize this feature will have to stop and restart the call database for each existing cluster after upgrade. Any new cluster added after upgrade will pick up this feature up automatically. Voice Quality Support for Cisco Unified Border Element via RADIUS Prognosis 10.2 now supports retrieving CDR information from CUBE using the RADIUS protocol. This includes voice quality information that can be correlated with voice quality information received from other devices to provide an end-to-end Voice Quality 360 diagram. Foundation Edition users can view the Voice Quality and Health information provided they have the correct module. The Voice Quality 360 feature is not available to Foundation Edition users. Page 7
IR Prognosis 10.2 UCF Microsoft Lync Call Network Path Prognosis can now provide a network path for calls and conference calls that occur in a Lync 2013 environment. Any media traffic that originates from a Lync 2013 client will provide network path information. Prognosis visualizes the media path in a diagram as it travels through the network. The hop-by-hop visualization allows users to potentially identify any problem areas in the network that may be causing voice quality degradation. Call Network Hop Aggregation Utilizing Lync SDN API 2.1, Network Path information for every Lync call, provided that it has originated from a Lync 2013 client, is aggregated to provide a high level view of the router/switches that are most likely to be involved whenever voice quality degradation occurs. This allows for the easy identification of any potential problem areas in the network that may be causing voice quality degradation. Drill-downs are available to view detailed information for each call. This can assist in troubleshooting in order to find the root cause of any voice quality degradation. Lync in a Network Address Translation (NAT) Environment Prognosis can now provide visibility for Lync Server Roles that are behind a secure NAT environment. Prognosis 10.2 provides support to request server health information using Windows Remote Management (WinRM) protocol. Therefore, Service Provider customers that manage Lync environments using NAT can see the full visibility of Lync Servers statistics data through Prognosis. The previous option to use Windows Management Instrument (WMI) to retrieve server health information is still available and is the default option. Lync SQL Monitoring Server Using Mirroring for High Availability Prognosis 10.2 supports the ability to continuously retrieve Lync QoE metrics when failover occurs on a Lync SQL Monitoring server which has Mirroring configured. In these cases Prognosis will automatically switch to the backup server and continue to retrieve information when it detects that it can no longer retrieve data from the Lync SQL Monitoring Server database. When Prognosis detects that a failover has occurred it will automatically switch its queries to the backup server. It will also raise an alert to notify that a failover has occurred. SQL Connection Minimization Prognosis 10.2 minimizes the number of login and log out requests that are used to request SQL information. Prognosis will now maintain a fixed number of connections (10 by default) to query the Quality of Experience (QoE) information from Lync SQL Monitoring Server. If required, the number of connections used by Prognosis can be reconfigured. Monitoring Polling Profile Modification Prognosis 10.2 will query information from Lync Monitoring SQL Servers and Lync Servers at 30 second intervals. Previously this polling was at 10 second intervals. The reduction in polling rates will assist in scalability improvements when Prognosis is used to monitor large Lync environments. However, a number of live (on-demand) Displays will continue to be polled at 10 second intervals in order to assist in troubleshooting problem areas. Search for a Lync Conference Call An upgrade to the Search facility in the Prognosis Web Application now allows searches for Lync conference calls by entering the alphanumeric conference ID. Prognosis will search through its databases and return the Conference call information along with the organizer and participants of the conference. Page 8
Release Notes Additional Lync Alerts Additional alerts have been added to provide notifications whenever anomalies occur in a Lync environment. The additional alerts cover various anomalies for each of the Lync Server Roles, which include: - Front End - AV Conferencing - Mediation - Monitoring - Edge - Director User Calls Classification In Prognosis 10.2 extra filters have been added which allow for the identification of Enterprise, Federated, Anonymous, and Public IM Connection users in a Lync environment. This will assist in troubleshooting any voice quality degradation issues experienced by a specific Lync user type. SQL Query Optimization A number of Prognosis SQL queries to the Lync Monitoring SQL Server have been optimized. This allows Prognosis 10.2 to populate live or on-demand Displays faster than previous versions. Sonus Sonus Session Border Controller (SBC) 1000 and 2000 Voice Quality. Prognosis 10.2 provides voice quality information for Sonus SBC 1000 and 2000 series via RADIUS. The voice quality information gathered from a Sonus SBC is correlated with voice quality information received from other devices to provide an end-to-end view. Prognosis presents this information in a Voice Quality 360 diagram which allows easy troubleshooting as media traffic traverses across multi-vendor environments. Note that the RADIUS information from Sonus about each call does not include the codec used. Therefore codec is assumed to be G.711 when calculating MOS value. Prognosis also provides call statistics information including Busy Hour Call Attempt (BHCA) and Busy Hour Call Completed (BHCC) to provide additional information in regards to the load that the SBC is experiencing for each of the Signaling Groups configured. Note that Prognosis will not respond to ping messages from Sonus 1000/2000 SBC if no online display and/or database collection is started to collect Sonus SBC voice quality information. It may be marked as Down on the Sonus SBC and an error raised regarding CDR delivery. These error messages can be safely ignored. To avoid such messages please ensure that the SBC-Reporting database is started once Sonus SBC via RADIUS has been configured. Foundation Edition users can view the Voice Quality and Health information provided they have the correct module. The Voice Quality 360 feature is not available to Foundation Edition users. Sonus Session Border Controller 1000 and 2000 Health Prognosis 10.2 supports Sonus Session Border Controller (SBC) 1000, and Sonus SBC 2000 server health information. This includes; the status of each SBC, the status of the Signaling Group, CPU and Memory utilization and the firmware version. Page 9
IR Prognosis 10.2 UCF Issues Resolved The following items are issues that were raised, both internally and from customer feedback, from the previous Prognosis release that have now been resolved. Prognosis User Interface Web Application Item No. SF-8642 SF-9503 Description Column-Line charts show unnecessary decimal places on the left axis. The Web Application needs to cater for SBC names with embedded dots. Prognosis for Unified Communications Common Item No. PRNX-4728 SF-9002 SF-9054 Description Duplicate SBCs in navigation and report list on the Prognosis Web Application. UCF license enforcement feature taking LSP and ESS into account. Some call legs are missing from VQ360 data when the Web Application times out before data is retrieved. Avaya Item No. PBXII-23 PBXII-205 PRNX-4577 PRNX-4743 SF9150 SF-9227 Description Implement the estimate of the number of trunks required in the AvayaTrunkGroupSummaryReport record. In Avaya Voice Streams and Avaya Voice Streams Finished Displays, the indicator in the Type column that signals the presence of hops in the Voice Stream Details display is not working. Blue should mean that there are hops, black should mean that there are no hops, but neither of them is always true. Avaya Network Hops indicator is not obvious to the user. AvayaTrunkGroupUsageHourlyReport record is not populated for AOS. Session Manager Status does not update after initial UP status. No data displayed in AV-Media Gateway DSP Resources Last 24 Hours display. Page 10
Release Notes Cisco Item No. PRNX-4752 PRNX-4962 PRNX-5000 SF-8230 SF-8665 Description CUBE reporting is using the wrong database for periods; This Week, Last Week, This Month and Last Month. Some conditions in the cmahardwarealerts do not have SNMP trap as default destination. cmaserveralerts is picking up extra availability entries which it should not have. No CPU statistic for UCS-C. CUBE does not go offline when connectivity is lost. Microsoft Lync Item No. Description PRNX-4742 Lync conference display has invalid where clause. Prognosis UC Reporter Item No. SF-8357 Description Supporting large number of devices in IPTRDEV record over 32K limit. Page 11
IR Prognosis 10.2 UCF Limitations Prognosis 10.2 has certain limitations in what it can do due to the method and technology it uses to collect information. The following limitations are known. Common LDAP support The Prognosis Web Application does not support login using Open LDAP credentials. Active Directory Groups and Individuals and Windows credentials are supported. Automatic upgrades Currently Prognosis 10.2 only upgrades from the following earlier Prognosis versions: Prognosis 9.1 service pack 3 and 4 Prognosis IP Telephony Manager Version 9.6.1 updates 6 and 7. Prognosis 10.0 Prognosis 10.0 Service Pack 1 Prognosis 10.1 Prognosis 10.1.5 Prognosis IP Telephony Management Reporter version 9.6.1 update 3 is not fully automatic and some manual steps are involved to backup, uninstall and restore. Please refer to the Upgrading from Prognosis IP Telephony Management Reporter page under the UC Reporter section in the Installation Guide. Prognosis UC Reporter version 10.0 is not fully automatic. After running the Prognosis 10.1 upgrade process, an extra step is required to run the set up UC Reporter command which is the same as step 3 in upgrade from IP Telephony Management Reporter version 9.6.1 update 3. In addition, the installation directory cannot be preserved if it is under Program Files or Program Files (x86). The default directory on upgrade is Prognosis directly under the original drive. The default directory for UC Reporter is Prognosis\Reporter under the original drive. Upgrade limitations Upgrading to Prognosis 10.2 from earlier version of Prognosis may fail due to the lack of necessary permissions. The resolution is to run or execute Prognosis 10.2 msi with the Run as administrator option. No upgrade support for Lync from Prognosis 10.0 Foundation Edition to Prognosis 10.2, users are advised to run auto discovery again to re-discover their Lync environment. Parallel Installation Prognosis for UC Foundation Edition, including Prognosis VoIP Monitor, must be installed on its own server. Therefore, no two Prognosis installations can be installed on the same server. Page 12
Release Notes Web Application Drill-downs via legends in charts does not support the Open in new tab browser option. Change in column width is not retained if the Display is closed or refreshed. There is no left/right axis indicator shown for dual axis charts in the Web Application. Generic SNMP Traps In vs. Alcatel monitoring vs. AvayaCS1000 monitoring The generic SNMP traps in collector, Avaya CS1000 collector and Alcatel collector must be run on separate Prognosis Monitoring Servers. Prognosis for Unified Communications Avaya Aura Communications Avaya ESS mode activation cannot be monitored. Unable to monitor server status in an S87xx pair. Aura Configuration XML files (SIPEntities.XML and EntityLinks.XML) do not get removed. That is: - When removing System Manager or Session Manager from Prognosis, the SipEntities.XML and EntityLinks.XML remain behind. - When re-adding a System Manager or Session Manager, user can upload a new SipEntities.XML and EntityLinks.XML files and it will replace the existing XML files. - When importing System Manager Configuration to Web Administration, the web form will contain error messages until the XML files are uploaded using Web Administration display. - When Upgrading from earlier version of Prognosis 10, the SipEntities.XML and EntityLinks.XML files are preserved in under <Prognosis_Home>/Server/Configuration/IPTM/Avaya. However, the Web Administration does not import them into the model, so the Configuration page on the Web Administration shows the red warning: "System Manager Configuration incomplete, please upload SIP Entity and SIP Entity link XML files". - Uploading incorrect XML files may remove existing Session Managers from Prognosis Configuration. Avaya Communication Server 1000 Voice Quality Only data for degraded voice streams is available. Voice quality data is only present as streams, not Erlangs. Entities not supported There is no data presented for: Route Patterns, Call Failure Ratios, Disconnect Cause Codes Calls Rejected Page 13
IR Prognosis 10.2 UCF Incorrect port in the configuration setup When an incorrect CS1000 PBX port has been setup using the Web Administration page or Windows Client, modifying the port through either interface may not fix the issue. If this occurs, it is recommended to restart the irnortel_pbx.exe by: - Going to the Windows Client, - Open the PROGNOSIS Configuration document - Enter the value SET RUN (irnortel.exe N), and click start - Change the value to SET RUN (irnortel.exe, Y), and click start. The collector now should be requesting data using the new port. Cisco Unified Communications Upgrade from Cisco Unified Communications 9 to Cisco Collaboration System Release 10 When Cisco Unified Communications Manager and Cisco Unified Presence Server are upgraded from version 9 to10, the two clusters configured in Prognosis will have to be removed and then re-added as one. Searching Cisco MGCP gateway interface A new field ProtocolEnum has been added to the CallManagerDevSum (CMGWDEVS) record in Prognosis 10 to distinguish MGCP, SCCP and H323 interfaces. This field is not available in any previous versions of Prognosis, such as IP Telephony Manager version 9.6.1. Therefore, a search of gateway devices will always return the Other link which points to the Gateway Details instead of the Call Last Hour if the gateway is being monitored by IP Telephony Manager version 9.6.1. Instant data on new web application Instant data in the new Web Application is supported for the top level screens of Cisco Unified Communications Manager (CUCM), Cisco Unity Connection (CUC), Cisco Unified Presence (CUP), Cisco Unified Contact Center Express (UCCX), Cisco Unified Border Element (CUBE), Cisco Unified Computing System (UCS) B and C-series with the following exceptions: All Displays for Cisco Call Manager version 3.x and 4.x All Displays for Cisco Unity CMA All Clusters Central CMA All Server Central CMA TelePresence Central CUC Cluster Overview CUC Ports CUC Server Sessions CUP SIP Proxy Statistics Cisco UBE Details UCS C-Series System Central Page 14
Release Notes Gateways/Trunks CPU, memory, DSP resources and environmental statistics are only available on for H323 and SCCP gateways where the associated MIBs are supported and Prognosis has SNMP connectivity directly to the gateway. H.323 and Voice Gateways that do not support the IF-MIB (i.e. the IfTable SNMP table) will not have accurate status information and the status of the gateway will default to Down. If accurate information is required, it will be necessary to enable the IF-MIB. H.323 gateways that stop responding to SNMP requests will be displayed in Prognosis with the last retrieved status for each interface. In addition, if there has never been a response from SNMP, no count or device details regarding the type of interface available on the H.323 gateway will be provided. A Voice Gateway (VG) configured as part of a CUCM 5+ cluster that does not respond to SNMP requests will report the correct number of configured devices on the Gateway Central page, but no devices will be listed when drilling-down to the Gateway Details page. The Gateway Details page lists devices that only contain data retrieved via SNMP requests from the Voice Gateway. No performance data is provided by CUCM 5+ for any MGCP gateway configured on a CUCM 5+ cluster that has never been registered to any CUCM server since the servers started up. The detailed device information will not be available due to lack of performance data from the CUCM servers. Status of SIP trunks and non-gatekeeper controlled inter-cluster trunk will be set to Unknown. Route patterns with all destinations set to these types of trunk will be Unknown. Status of route patterns which include other types of destinations will be based only on the destinations with known status. For physical gateways that have multiple interfaces where some interfaces are H323 while others might be MGCP and SCCP, the logical H323 gateways will show all interfaces on the physical gateway including those which might be actually running another protocol. In addition, Prognosis will only support physical gateways using multiple protocols when the logical gateways entries under the Cisco Unified Communication Manager Configuration Database have different names. Calls and Voice Quality Voice quality data for calls rely on Cisco Call Management Records (CMRs), also referred to as Call Detailed Diagnostics Records (CDDRs), being available from the devices involved in a call. However, some devices such as H.323 gateways and SIP trunks do not provide CMRs on the CUCM. Voice quality for a call will be available as long as one of the devices involved in the call provides CMRs. Calls involving only devices with no CMRs will not have voice quality data provided by Prognosis. CUCM 5+ calls will be put into the Unknown call category if they involve devices currently not being reported individually by Prognosis such as conference bridges. The Call by Category windows in the Cisco Calls Display and the Voice Quality Distribution graph in the Cisco Voice Quality Display for CUCM 5+ plots the CDRs processed by Prognosis per interval. If Prognosis is set up to use SOAP requests rather than the Billing Application Server for CDR retrieval, there will be a time overhead in the delivery of the CDRs to Prognosis. This is due to the CUCM server having to respond to individual SOAP requests. Occasionally the CUCM server can take longer than one time interval to reply to a SOAP request resulting in a delay in the processing of CDRs from one interval into the next. Therefore, the Displays may occasionally have an interval showing no data followed by another interval which has twice the normal amount of data. To prevent this from occurring, it is recommended that a Billing Application Server be selected for CDR retrieval. This eliminates unnecessary SOAP requests/responses between the CUCM server and the Prognosis Monitoring Server. Any files present in the CDR directory will be processed on Prognosis startup. If there are a large number of files in this directory it may result in spikes in the Calls and Voice Quality records. This is particularly important when the Billing Application Server mechanism is used and there has been extended downtime for the Prognosis service. Page 15
IR Prognosis 10.2 UCF Phones and extensions Currently, Prognosis will only be able to obtain CallManagerIpPhoneInformation (RTDEVINF) configuration information and CallManagerIpPhoneQos (RTDEVQOS) real-time call quality information for the various 69xx, 79xx, 89xx, and 99xx series IP phones. These information are obtained through the IP phone web pages including http://<phone ip address>/deviceinformationx, http://<phone ip address>/portinformationx http://<phone ip address>/streamingstatisticsx Hence population of fields in these two records is only available for IP phones which support and have the web page function enabled. These records are not supported for soft phones such as IP communicator or Cisco Jabber. No SNMP data is provided by CUCM 5+ for phones configured on a CUCM 5+ cluster that have never been registered to any CUCM server since the servers started up. The status of these phones will remain Unknown due to lack of SNMP data from the CUCM servers. Prognosis currently only refreshes the device-extension mapping once a day, the dynamics introduced by Extension Mobility will affect the CallManagerApplianceExtensions (CMAEXTN) and CallManagerDeviceExtension (CMDEVEXT) records where extension details are missing or the associated device listed against the extension is not the most up to date. The CallManagerDevice (CMDEV) record will also be affected where the LineInUse (LNSINUSE) field is representing activities on an extension that is no longer associated with the particular device. Calls information as given in Calls Details and Call Details Diagnostic Records will still accurately reflect the device and the extension number used during the call at the time. Cisco Alerts Cisco Alerts data will only be available when Prognosis can contact and retrieve data from the publisher. There will be no Cisco alerts update when the publisher is down. Cisco Unified Communication Server version 5.x does not put alerts into subcategories. Therefore the group field in the Cisco Alerts record will be empty. Microsoft Lync MOS values are provided directly by Microsoft and are not calculated using the standard Prognosis MOS formula. There is no data presented for PSTN trunks and Route Patterns. There is no active call information in Microsoft Lync 2013 monitoring as the data is no longer available in the Monitoring SQL Server. There is no Network Hop information available in Microsoft Lync 2010. Therefore, network hop information will not be populated on the Lync Call Details and Lync Conference Session Details dashboards for calls made in Lync 2010 environment. Page 16
Release Notes Prognosis UC Reporter Calls Some call records received by Prognosis UC Reporter may have missing device names if the names are not contained in the original CDR flat files received from the Cisco Cluster. These calls will not be accounted for in the report if the call count is based on the device involved. Show charts as tables On the Report Creation Wizard dialog box an option to Show charts as tables is provided. This is used to show chart data in table format so that it can be used for further processing by other applications. However, when this option is selected there is a limitation with charts that include Busy hour times. UC Reporter shows time data in charts by converting it into an equivalent decimal number between 0 and 24. For example, if the Busy hour time is 12:10 it will be converted to 12.16666 then rounded to 12.17. In the same way, a Busy hour time of 12:30 will be converted to 12.5. When printing the tabular format of these charts, UC Reporter can only use these decimal values instead of being able to provide the Busy hour in the hour:minute format. Bear in mind that this is a decimal value and not an actual time. A Busy hour time of 12.17, does not mean 12:17 but actually means 12:10. Remote SQL requires SQL authentication Prognosis UC Reporter requires SQL authentication, MS Windows authentication is not supported. Page 17
IR Prognosis 10.2 UCF Known Issues The following issues are known at the time of product release and, where available, workarounds have been provided. Common Item No. PRNX-229 PRNX-731 PRNX-1121 PRNX-1808 PRNX-1825 PRNX-2465 PRNX-2910 PRNX-2924 PRNX-2966 PRNX-3285 PRNX-3319 PRNX-4769 Description The time remaining shown during an uninstall of Prognosis can be inaccurate where the time reported is greater than the time actually required. Navigation for the Web Application cannot be updated by multiple users simultaneously. The SET MEM-SIZE statement in the PROGNOSIS Configuration can only be set with an executable name instead of symbolic process id. Bookmarking a URL for the Web Application using IE9 may not work. Generating reports via the Web Application around interval boundary may result in the last interval being missed. Administration of Thresholds and Databases via the Web Application may not take into account any specified Node to Run On. Table heading tooltips position is incorrect when the navigation panel is unpinned. Using the back button on the browser will not keep the database replay position on the Web Application. Prognosis 10 cannot show double byte characters. The position of an item in the Web Application navigation tree is not preserved if open new tab or open in new window is used. The Prognosis Node Connection may not work when class C address is of x.x.x.255 while there is another class B address set up with the right subnet mask. Deleting a Prognosis SQL database that resides on a remote SQL Server can receive Failed to connect to the server errors. Page 18
Release Notes Prognosis User Interface Item No. Description PRNX-3909 When Web Application Server is down, which could be due to license exceeded after 14 days, the error message provided on Prognosis login refer to failed socket connection. PRNX-4255 Database replay scroll indicator on chart is not very clear when using Charcoal Skin on Web Application. Prognosis for Unified Communications Item No. PRNX-353 PRNX-1552 PRNX-1755 PRNX-3057 PRNX-3269 PRNX-3986 PRNX-4244 Description After adding a new UC system, it may not show up in the Web Application navigation tree until the browser is refreshed. Cisco Alerts with descriptions longer than 508 characters will not be displayed properly. Incorrect alerts may be raised for any Avaya ESS being monitored. Removing a UC monitoring item may not always remove it from the middle panel on the Web Application Administration page. Cisco UBE does not pick up CLI password change until the collector is restarted. CUC process needs a restart after update of password configuration. Lync Voice Quality Details display does not show the From and To device identifier properly Page 19