OneSight Release Notes

Empirix OneSight 8.1 SR1 

Release Notes 

Revision A 

June 2012

OneSight Release Notes 

Version 8.1 SR1 

Empirix Inc. 

Copyright Notice 

Copyright © 1997-2012 Empirix Inc. All rights reserved. The 

contents of this document and the associated OneSight suite 

software are the property of Empirix Inc. and are copyrighted. No 

part of this document may be copied or distributed, transmitted, 

transcribed, stored in a retrieval system, or translated into any 

human or computer language, in any form, or by any means, 

electronic, mechanical, magnetic, manual, or otherwise, or disclosed 

to third parties without the express written permission of Empirix 

Inc. 

This Empirix software product also includes copyrighted third party 

software. See the OneSight online help for complete information 

about third party copyrights. 

Printed in the United States of America 

Trademarks 

Empirix logos are either registered trademarks or trademarks of 

Empirix Inc. in the United States and/or other countries. All other 

names are used for identification purposes only and may be either 

registered trademarks or trademarks of their respective owners. 

Empirix Inc. 

20 Crosby Drive 

Bedford, MA 01730 

Ph: 781-266-3200 

Fax: 781-266-3201 

Web: http://www.empirix.com 

Email: onesight-sales@empirix.com 

USA, Japan, Singapore, UK/Europe 

To contact a local Empirix office, visit our Web site at 

www.empirix.com

Table of Contents 

New Features 1 

Upgrades and Compatibility 2 

Supported Platforms ............................................................................... 2 

Supported Upgrade Paths to OneSight 8.1 ............................................. 2 

Troubleshooting ..................................................................................... 2 

Known Issues 3 

Installation.............................................................................................. 3 

Upgrade .................................................................................................. 4 

General ................................................................................................... 5 

Submitting New Issues .......................................................................... 9 

Fixed Issues SR0 9 

Fixed Issues SR1 11

New Features 

Below is a list of the new features and enhancements that you will find in 

OneSight 8.1. 

Voice Quality Basic Profile Monitors – Support has been added for 

collecting reference and received DTMF. Note if you are upgrading, you 

will need to re-import the OneSight Voice Quality – Basic profile to see 

this feature. 

Probe Call Summary Report – This new report has been added that 

shows a summary of successful and failed calls and DTMF by VQ Probe. 

Reports – Reports have been redesigned. 

VQ Probe – Support has been added for Cisco SCCP v7 and enhanced 

support has been added for Avaya 323. 

Empirix IDMC (Intelligent Data Mediation and Correlation) Profile 

Monitor – A new profile has been added that monitors Key Performance 

Indicators (KPIs) that are received from Empirix IDMC. Monitors are 

automatically created and can then be edited in Empirix OneSight. 

Empirix E-XMS Integration – You can configure OneSight so that you 

can view Call Data Records (CDRs) using the Hammer E-XMS 

diagnostics, voice reports, and analysis tool directly from OneSight. 

When one or more E-XMS systems are configured, OneSight displays the 

Diagnostics tab, which allows you to connect to the selected E-XMS 

system. 

Cisco Call Manager Profile Monitor – The Cisco Call Manager Profile 

monitor has been added to passively monitor call activity to create a 

metric data set for each completed call handled by the Cisco Call 

Manager. 

Voice Quality – Voice Quality has been enhanced to provide better drill 

down capability. 

OneSight Release Notes 1 

1

Upgrades and Compatibility 

Supported Platforms 

Refer to the "Hammer Test Solution and OneSight Platform Compatibility 

Matrices" document for information on supported platforms. This document 

can be downloaded from the downloads/OneSight folder on 

https://eSupport.empirix.com. 

Supported Upgrade Paths to OneSight 8.1 

Troubleshooting 

OneSight 7.1 SR3 to OneSight 8.0 SR0 







If you selected, "Backup the database before upgrading," during the 

installation process, and your system does NOT have a backup device, the 

backup will fail and the database will not be upgraded. When the setup 

program has finished running, you will need to upgrade your database 

before using OneSight. To upgrade the database, run Initdb.exe located in 

the C:\Empirix\Onesight\Setup directory. 

2 

2 OneSight Release Notes

Known Issues 

Installation 

The following section describes known issues that a OneSight user and/or 

administrator may encounter when using OneSight 8.1. When possible, a 

workaround has been described. 

If you are using Hammer Call Analyzer (HCA) with VQ Probe on a 64 bit 

system, you must manually install WinPCap version 4.2.1 before you 

install HCA. WinPCap can be downloaded from www.winpcap.org. 

By default, SQL 2008 is installed with TCP/IP disabled. TCP/IP must be 

enabled so that OneSight can communicate with the database. To enable 

TCP/IP: 

Start the SQL Server Configuration Manager. 

Select SQL Server Network Configuration Protocols. 

Double-click on TCP/IP in the right pane. 

Set the Enabled field to Yes. 

Restart SQL Server. 

If you are using Windows 2003 with SQL Server 2005, Action Plan 

History reports may not display all data when attributes are used. 

Download and install the latest version of SQL Server 2005, service pack 

3. 

If the OneSight Server and OneSight Database Server are installed on 

separate machines, SQL Server 2005 Express must be installed on the 

OneSight Server so that they can communicate. SQL Server 2005 Express 

will not be the actual database. It will be used for communicating only. 

SQL Server 2005 Express can be downloaded free from the Microsoft 

web site. This is true if the database being used is SQL 2005 or SQL 

2008. 

If the PasswordAuthentication setting in the sshd_config file is set to no 

on the Unix server, some OneSight monitors will fail. See 

http://www.ganymed.ethz.ch/ssh2/FAQ.html#passwordauth for more 

information. 

If installing on SQL 2005/2008 you must run the following query to 

properly configure the sql server: 


3

Upgrade 

EXECUTE sp_configure 'show advanced options', 1 RECONFIGURE 

WITH OVERRIDE 

EXECUTE sp_configure 'xp_cmdshell', '1' RECONFIGURE WITH 

OVERRIDE 

EXECUTE sp_configure 'show advanced options', 0 RECONFIGURE 

WITH OVERRIDE 

In addition, you must enable Mixed Mode on the Authentication Mode 

dialog box when installing SQL. 

Services panel MUST be closed during installation of a Data Collector or 

Remote Agent so that service can be properly registered and installed. 

If you are installing to a remote SQL 2005/2008 server, SQL 2005 client 

tools must be installed on the OneSight server. The tools can be installed 

by selecting to install client tools only from the SQL 2005 installation. 

Mapping a network drive does not work. 

If you are installing onto a Windows 2008 machine, you must create an 

inbound rule on the Windows firewall to allow port 8080 so that OneSight 

can be accessed from an outside machine. See Onesight Default Ports in 

the online help for information about the default ports used by OneSight. 

Custom reports are deleted during the uninstall process when upgrading to 

OneSight 8.1 SR1. If you have created any custom reports, you should 

back up the custom .jsp files in the 

…\empirix\onesight\webapps\ROOT\CustomReports folder before you start the 

upgrade. 

If you are splitting your database, it must be split before upgrading to 

OneSight 8.1. 

When you are upgrading a Data Collector or VQ Probe, you may get false 

alarms if the monitors using that Data Collector or VQ Probe are trying to 

sample during the upgrade period. After applying the configuration is 

complete, the alarms will not occur. 

If you have used a custom port for the OneSight Data Collector or NT 

Remote Agent, the custom port number is not retained during an upgrade. 

Change the #Comm.ServerPort setting in the OSDC.Properties file from 

the default port of 5007 to your custom port setting. 

4 


General 

Data Collector and Remote Agent Update/Upgrade - Remotely updating 

or upgrading Data Collectors or Remote Agents may take a significant 

amount of time. This is expected. A new Java Runtime Environment may 

need to be transferred to the remote machine. Please allow for this when 

planning updates or upgrades. 

Remotely updating Agents - The remote upgrade may not be available 

depending on your configuration. The work around is to manually 

upgrade your data collector. 

OneSight Voice Quality Basic Monitors – When using G.723.1, do 

NOT choose "In Band" when selecting the dtmf type, otherwise, an error 

may occur when decoding the DTMF. 

Restoring the OneSight Database from a Backup – Before restoring 

the OneSight database from a backup, the sysadmin right must be enabled 

for the OneSight administrator user in the SQL Studio application. If the 

sysadmin right is not enabled, OneSight does not finish initializing. 

Linux Remote Agent upgrade – Linux Remote Agents cannot be 

automatically updated from the Agent Update page. They must be 

manually upgraded. 

VQ Call Debug – VQ call debug information is not available for VQ 

Probes installed on G5 or FX-TDM machines. 

OneSight Voice Engine monitors – Monitors do not start immediately 

when they are created. Instead, they wait for a "random" amount of time 

(up to the length of the sample period) before running the transaction. 

OneSight Voice Quality Probes – 

Zero-padded IP-based phone names do not always increment 

correctly. For example, if the name is 0000101612719 (for IP 

address 10.16.127.9) the next address becomes 000010161280 (for 

IP address 10.16.127.10) instead of 000101612710. 

If the HTServer is restarted, B side channels do not run the B side 

script. You must manually restart the Data Collector on the probes, 

or apply the configuration from OneSight to make the channels 

alive. To apply the configuration from OneSight, open the 

configuration and click OK. 


5

When using the VQ Probe with G5 1.6 with more than one protocol, 

Skinny must be configured ahead of H323. If it is not, 

HTIPSigserver cannot be started. 

DTMF may not be sent correctly when the DTMF Type is set to In 

Band for highly compressed codecs. 

OneSight Voice Engine and OneSight Voice Quality – Advanced 

Monitors - There is a limit to the number of monitors that can be 

configured on a Data Collector. To avoid overloading a Data Collector, it 

is recommended that no more than thirty-five OSVE scripts with less than 

ten steps be configured on a Data Collector. An indication that a Data 

Collector is overloaded can be found by checking for stale samples from 

the Support and Diagnostics page in OneSight. 

OneSight Voice Quality – Advanced Monitors Location Tab - When 

setting up a OneSight Voice Quality Advanced monitor, you must select 

only the default location on the locations tab during monitor creation. 

Multiple locations are not supported. 

Metric Performance Report for Voice Quality Basic monitors – The 

Metric Performance Report for Voice Quality Basic monitors cannot be 

modified when drilled down to a one hour time frame. The Modify button 

is displayed; however, it disappears when you click on it. 

VQ Probe - Restarting the HT Server – If you manually restart the HT 

Server, only the A side scripts are restarted for the VQ Probe. Restart the 

OneSight Data Collector to start the B side scripts. 

VQ Probe Command Not Completed in Time Error – This error 

occurs due to a known FX/TDM issue that causes the HT Server process 

to stop. You can avoid this problem either by connecting all of the D- 

channels or by stopping the D-channels that are not in use. 

VQ Probe - UNIStim – When using the UNIStim protocol, the VQ Probe 

always uses the G.711 U-Law protocol to make calls regardless of the 

codec selected in the VQ Probe Configuration dialog box. 

Data Collectors for WebLogic 9.2 – New Data Collector installations 

for WebLogic 9.2 require an update for the OSDC.properties file to 

prevent discovery from failing. Add the following line to the 

[Agents.JMX] section: 

Agents.JMX.MAPPING.weblogic92 = weblogic9.2 

Modified Default Alert Message Templates After Upgrade – If you 

have modified a default alert message template, changes may not be 

6 


maintained after an upgrade. If you need to customize a default alert 

message template it is recommended that you clone the default template, 

rename it, and then customize it. 

Downtime Configuration – If you configure downtime to start in the last 

hour of DST, the downtime will start an hour later at the first hour of 

standard time. 

If you configure downtime to start in the hour when DST begins, the 

downtime will not start until the next scheduled time. For example, if a 

monitor is scheduled to go into downtime daily at 2:10 am, it will not go 

into downtime on the day DST occurs because DST time starts at 2:00 am, 

so there will not be a 2:10 am. It will go into downtime at 2:10 am on the 

day following DST. 

Popup Blockers – Popup Blockers must be turned off for OneSight to 

operate. Please see the help file for instructions on turning them off in 

popular browsers. 

URL Monitor – HTTPS through a NTLM proxy server is not supported. 

Oracle Test for Web Applications Monitor 

When running e-TEST version 9 scripts, proxy logs are not created 

when OneSight and e-TEST are installed on different machines. 

When using Java agent as the browser type, scripts fail if there are 

too many images on the playback side. Uncheck the download 

image checkbox and the script runs without error. 

Using Thin Client or Java Agent browsers with JHTTP in e-TEST 

suite 8.30 higher (including OATS 9.0) does not work. 

When playing back a script that uses the Java Agent as the browser 

type, the proxy settings in the Data Collector will not be used. This 

is a known Oracle issue, not a OneSight issue. 

e-TEST Transaction monitors must not contain a slash character in 

the monitor name, either "/" or "\". If present they will cause 

exceptions in the log. 

When configuring an e-TEST Transaction monitor, if the html page 

in the e-TEST script is large (greater than 1M) the thick client may 

not work properly. To correct this issue please follow the steps 

below. 

1. Stop the Data Collector service. 


7

2. Open the dc_services.properties file in a text editor. 

3. Uncomment the line: JHP.commandline = - 

DentityExpansionLimit=64000. 

4. Edit the line, change the value to a larger number. i.e. 

JHP.commandline = -DentityExpansionLimit=200000. 

5. Start the Data Collector service 

Although very rare, this may fail to correct the issue. Should this 

occur please choose the thin client option. 

If the user creates an e-Test Suite script that uses client certificates 

the script will play in e-Test Thin Client without JHTTP, but not 

play in Onesight. This issue occurs because the certificate is 

associated with the logged in user. As a result the OneSight Data 

Collector service must also be associated with the user. To correct 

this issue please follow the steps below. 

1. Go to Windows Services panel. 

2. Open the OneSight Data Collector service. 

3. Go to the Logon tab. 

4. In the 'Log on as:' section select 'This account' and provide 

the username and password of the user associated with the 

certificate. 

5. Click 'Ok' to save the changes. 

6. Restart the OneSight Data Collector service. 

When playing back a script that uses the Java Agent as the browser 

type, the proxy settings in the Data Collector will not be used. This 

is a known Oracle issue, not a OneSight issue. 

JMX WebSphere Monitor – Entering wrong information in any of the 

Mbean Server Authentication fields in the Advanced tab and then 

executing discovery or saving the configuration necessitates a Data 

Collector restart after correcting the information. This problem is caused 

by the WebSphere application server caching the authentication data. 

NT Event Log Monitor – When monitoring a remote server with the NT 

Event Log Monitor and using the "Time Since Last Modified" metric you 

will see inconsistencies if the time is not synchronized between the 

remote server and the OneSight server. If the remote server has the 

8 


OneSight Remote Agent or a uniquely named Data Collector installed 

time synchronization is not required. 

Voice Transaction Monitor – If the Hammer is located in a different 

time zone than the OneSight server OneSight may report incorrect 

timestamps. This is because the Hammer's local time is used for sampling. 

Status Icons for Status Views – File name specifications for status icons 

are case sensitive on the Status Icon - Modify dialog box. 

JMX Websphere 6.0 Monitors – Operation metrics do not work for 

Websphere 6.0 monitors. 

Submitting New Issues 

Issues with OneSight should be forwarded to Empirix Technical Support. 

Visit our customer support portal at https://esupport.empirix.com. 

Fixed Issues SR0 

Issue(s) 

Comments 

15681 A duplicate alert is created when an alert is created 

using the override profile method, and when the 

description field is changed before the monitor is 

saved. 

16497 Unistim Channels are not added to a VQ Probe if 

"Register with PBX" = NO. 

16773 Special characters cannot be used in attributes. 

16870 Home tab is missing. 

16895 In Unistim, the Username field is fixed to seven digits 

and leading zeros are truncated. 

16899 Vertical bar graphs do not render properly when there 

are too many bars and the legend has long names. 


9

16892 VQ Probe does not allow a plus sign in the extension 

field. 

16904 VQ Probe Unistim channels fail to register. 

16911 Server unavailable when drilling down into monitors. 

16912 Cannot use xp_cmdshell. 

16914 Drill down in Voice Transaction Summary Report 

resets to all Monitor Groups. 

16916 URL monitors fail. 

16918 Initdb cannot initialize the database on an instanced 

SQL s erver if the default port is changed. 

16921 The installer does not recognize sqlcmd.exe. 

16931 Saved reports do not open in Internet Explorer. 

16950 The Hammer_IM page is not password protected. 

16967 The Drill Down URL field in Custom Status View 

configuration is too short for some saved reports. 

17091 The version and licensing page shows incorrect 

information for location licenses. 

17127 Error when creating monitors. 

17163 VQ Inspection CDR field mismatch. 

17273 The Monitor Health Statistics report does not sort 

correctly. 

17279 Linux remote agent does not install. 

10 


Fixed Issues SR1 

Issue(s) 

Comments 

17272 Compound monitor not calculating correctly. 

17329 VQ Inspector fails with unknown payload type. 

17357 Log File monitors will not report the number of 

matching records when an agent has many log file 

metrics assigned. 

17358 The Log File metric is counting the number of 

matching records that already existed in log file prior 

to when the monitor was enabled. 

17408 The login timeout value does not work. 

17416 Upgrading to OneSight 8.1 fails with a thread dump. 

17417 Monitor keeps the original alert after disabling then 

enabling the monitor. 

17419 The Calls by Extension Summary report is broken. 

17421 The VQ Probe Avaya H.323 state machine requires a 

KeepAlive mechanism. 

17424 System attributes are missing after upgrade. 

17425, 

17426 

Custom dashboard is missing after upgrade. 

17427 Ad-hoc reports cannot be edited without saving them 

first. 


11

OneSight Release Notes

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?