Installing This Application
NetIQ Performance Endpoints
NetIQ Vivinet Diagnostics diagnoses problems with the routing, connections, and performance of Voice over IP (VoIP) calls on your network. With the data you receive from a diagnosis, you can quickly resolve problems with VoIP hardware, software, and performance.
Vivinet Diagnostics is designed to perform two primary functions:
- Diagnose and locate the source of problems detected on your network, such as poor-quality voice transmissions, dropped calls, and cutouts.
- Analyze the path a particular call actually takes through your network, including routers, switches, or voice gateways that intervene between the calling and called parties.
This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure our products meet all your needs. You can post feedback in the AppManager forum or the Vivinet Diagnostics forum on Qmunity, our community Web site that also includes product notifications, blogs, and product user groups.
For more information about this release and for the latest documentation, see the Vivinet Diagnostics Documentation page. To download this release of Vivinet Diagnostics, see the Vivinet Diagnostics Upgrade page.
This release of Vivinet Diagnostics adds the following support:
- Support for Windows Server 2012 and Windows 8. With this release, you can use Vivinet Diagnostics on computers running Windows Server 2012 or Windows 8. For more information, see the System Requirements.
This release of Vivinet Diagnostics also resolves the following issues:
- VDiag failing to detect phone registration to signaling server. (ENG322213)
- Configuring SNMP version 3 for use with Vivinet Diagnostics . This release resolves an issue in which . With this release, . (ENG320268)
This release of Vivinet Diagnostics replaces all Previous Releases.
Return to Top
For the most recently updated list of supported application versions, see the
AppManager Supported Products Web site. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.
Vivinet Diagnostics has the following system requirements:
- One of the following Microsoft operating systems on the computer running Vivinet Diagnostics. You must have administrator privileges to install and run Vivinet Diagnostics.
- Windows Server 2012
Note Support for Quality of Service (QoS) Quality of Service settings on Windows Server 2012, Windows 8, Windows Server 2008 R2, and Windows 7 endpoints requires the NetIQ Performance Endpoints version 5.1.15368.0 or later. You can download the Performance Endpoints for your operating system at the Performance Endpoints page.
- Windows 8 (32-bit or 64-bit)
- Windows Server 2008 R2
- Windows Server 2008 (32-bit and 64-bit)
- Windows 7 (32-bit and 64-bit)
- Windows Vista (32-bit and 64-bit)
Note Windows Vista does not support Quality of Service (QoS) settings based on the Differentiated Services Code Point (DSCP) field in the IP header.
- Windows Server 2003 (32-bit and 64-bit)
Vivinet Diagnostics requires WinHTTP 5.1, a component of Windows Server 2003, to retrieve Cisco Communications Manager data through the Secure Sockets Layer (SSL).
- Windows XP (32-bit and 64-bit)
NetIQ Corporation recommends Service Pack 1 if you enabled SSL on your Cisco Communications Manager computer. Vivinet Diagnostics requires WinHTTP 5.1, a component of Service Pack 1, to retrieve Cisco data through the SSL.
- One or both of the following NetIQ applications, to enable diagnoses of SNMP v3-enabled devices:
- Vivinet Assessor version 3.3
- AppManager version 7.x or later
- NetIQ Performance Endpoints on every computer you want to diagnose; for more information, see the topic about NetIQ Performance Endpoints
- One of the following third-party applications running in the environment you are diagnosing:
- Avaya Communication Manager, version 6.0, 5.x, or 4.x
- Avaya (Heritage-Nortel) Communication Server 1000, version 7.5, 7.0, 6.0, 5.5, 5.0, 4.50, or 4.0. Versions 6.0 and earlier of Nortel CS1000 require firmware version D98 (required) or D9C (recommended), and several patches on the Signaling Server:
- For Signaling Server versions 4.00.31 and 4.00.55, install the following patches: MPLR19592, MPLR19581, MPLR20987, and MPLR21070.
- For Signaling Server version 4.50.25, install two patches: MPLR20987 and MPLR21297.
- Obtain the patches from your Nortel support and maintenance provider. MPLR19592 updates the
isetInfoShow commands. MPLR19581 updates RTCP-XR for the R-value metric. MPLR20987 fixes BERR705 and BERR504. MPLR21070 fixes a memory leak from
telnet/rlogin command line interface commands. MPLR21297 enables simultaneous traceroutes between the same two phones.
- Avaya (Heritage-Nortel) Communication Server 2100, version SN11 or SE11 using Phase 2 phones
- Cisco Unified Communications Manager, version 8.6, 8.5, 8.0, 7.1(2), 7.0, 6.1, or 5.0
- Cisco Unified CallManager, version 4.x or 3.x
For more information, see the User Guide for Vivinet Diagnostics, included in the download package.
Return to Top
Installing This Application
For information about installing this application, see the User Guide for Vivinet Diagnostics, included in the download package.
Return to Top
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
- No difference for endpoints installed on Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2. For endpoints installed on a computer running Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2, Vivinet Diagnostic identities the endpoints as simply "Windows." (ENG252765)
- Endpoint-to-Endpoint diagnoses not supported on Microsoft Windows Vista. The security for Windows Vista prevents Vivinet Diagnostics from completing a diagnosis between endpoints installed on that operating system. For more information, see the "Troubleshooting" chapter of the User Guide for Vivinet Diagnostics. (ENG230478)
- Unknown Layer 3 port information for hybrid devices. The SONMP device discovery process assumes that all neighbor devices are switches, not routers or hybrid devices. When a Layer 2 path is completed between a series of neighbor devices that were discovered by SONMP, an error occurs if the final device in the path is a hybrid device. Although the Layer 2 path information is complete, the Layer 3 ingress port information is returned as "unknown" even though the final device information was correctly identified by the Layer 2 trace. (ENG254060)
- CDRs for CallManager 5.0 not supported. Vivinet Diagnostics does not support the collection of call detail records (CDRs) for Cisco CallManager versions 5.0 and later. CDRs provide the call details for a phone. (ENG234873)
- L3 switches may not show up in L2 trace. Layer 3 switches that support both Layer 2 and Layer 3 services and have
ipForwarding enabled may not show up in the Layer 2 traceroute path. (ENG237188)
- SQL Server 2000 may require SQL Server Native Client driver. If the NetIQ AppManager repository is running Microsoft SQL Server 2000 and you want to import SNMPv3 profile information from the repository, install the SQL Server Native Client driver on the repository computer. The SQL Server Native Client driver allows Vivinet Diagnostics to connect to the repository at runtime to collect SNMPv3 profile information. (ENG237892)
- Blank dial patterns match any POTS phone number. Voice gateway POTS dial peers that have a blank dial pattern (typically associated with an MGCP gateway) will match any POTS phone number. All active and recent calls associated with that dial peer are displayed in the Properties dialog box for the POTS phone icon in the traceroute.
- DIAL-CONTROL-MIB may contain invalid dial peer ID. In the DIAL-CONTROL-MIB, the dial peer ID associated with an active or recent call may be zero or invalid. In this case, the call will not display as expected in the Properties dialog box for the POTS phone icon in the traceroute. However, all active and recent calls for the voice gateway can be viewed in the Properties dialog box for the voice gateway icon.
- CISCO-DIAL-CONTROL-MIB may contain invalid dial peer ID and peer ifIndex. In the CISCO-DIAL-CONTROL-MIB, the dial peer ID and ifIndex associated with a recent call may be zero or invalid. In this case, the VoIP call leg will display a zero or an invalid peer ID, as well as "n/a" for the interface name and type in the Raw Data File or in the Recent Call Legs dialog box for the POTS phone or voice gateway icon in the traceroute.
- Digit transformations affect call display. Vivinet Diagnostics does not handle digit transformations that may be performed on a POTS phone number by Cisco CallManager or a voice gateway. For example, if a user is required to dial "9" in order to reach an outside line, CallManager may strip off the "9" before sending the dialed number to the voice gateway. Therefore, the POTS phone number supplied to Vivinet Diagnostics (as dialed by the user) may not match any dial peer in the voice gateway, and the call will not display in the Properties dialog box for the POTS phone icon in the traceroute. However, the call will display in the Properties dialog box for the voice gateway icon.
- CDRs unavailable for CallManager Express. Call detail records (CDRs) are not available for phones registered to a CallManager Express device.
- CallManager required for POTS phone diagnosis. Vivinet Diagnostics does not support a diagnosis with a POTS phone where the only CallManager is a CallManager Express. At least one full CallManager must be available to query for dial plans.
- Diagnoses may incorrectly state that QoS is not enabled. Vivinet Diagnostics recognizes only certain traffic class definitions on Cisco devices. Some traffic class configurations may result in a false diagnosis stating that QoS is not enabled. (ENG214330)
- IIS 6.0 does not recognize .dgv file type. Because IIS 6.0 does not serve "unknown MIME types," you may encounter a broken link in the reports generated when AppManager launches Vivinet Diagnostics to diagnose a VoIP problem. The AppManager event raised by a VoIP diagnosis contains a Web-server-qualified link to default.htm, which in turn contains a link to a Web-server-qualified .dgv file. Clicking on that link results in a "404 not found" error. For more information, see http://support.microsoft.com/kb/326965. (ENG217919)
- L3 switch limitations: (ENG113502)
- Some L3 switches not discovered as routers unless routing turned on. Some Layer 3 switches can be configured to perform traditional Layer 2 functions, as well as traditional Layer 3 routing functions. However, Vivinet Diagnostics will not discover Layer 3 switches that have their routing functions disabled. If you want Vivinet Diagnostics to discover your Layer 3 switches, you must enable the routing function.
- Some L3 switches not discovered as L2 devices. The BRIDGE-MIB in some Layer 3 switches is not populated with the information that Vivinet Diagnostics needs to discover Layer 3 switches as Layer 2 devices. Although you may have the routing feature enabled, the lack of BRIDGE-MIB data will prevent the switch from being discovered.
- Passport routers require SONMP for L3 trace. The Rapid City-based Passport router and its adjacent routers must have SONMP enabled. Vivinet Diagnostics uses the SONMP network topology information to discover ingress and egress interface details. Without the topology information for the Passport router, Vivinet Diagnostics provides support only for device discovery and CPU and memory polling.
- L2 trace does not run automatically for bridge group virtual interfaces. The SNMP interface index for a bridge group interface does not match the SNMP index stored in the CDP (Cisco Discovery Protocol) MIB. Therefore, when Vivinet Diagnostics attempts to run a Layer 2 trace, it cannot determine the correct SNMP port number to use. Layer 2 traces for a bridge group interface work only when at least one switch in the trace path is manually configured (using the Options > Layer 2 Switch menu) AND all switches in the trace path can contact each other using CDP. (ENG178822, ENG109548)
- Frame relay MIB not supported in Nortel router. The BayRS router running version 14.20 does not support the frame relay MIB. BayRS version 18.104.22.168 does support the frame relay MIB.
- Confirmed bugs in IOS software. Cisco has confirmed a bug (affecting almost all of the 12.3 IOS versions) in its IOS software that can adversely affect diagnoses. With this bug, you may notice that the path trace is missing one or more hops. Messages in the Error Log Viewer will indicate the failure of a request for an egress interface address or the failure of an SNMP request. To obtain a fix for the bug, contact Cisco and reference ID number CSCsa92212. According to Cisco, the bug is fixed in versions 12.4(2.2) and 12.3(15.4), which were not available at the time of this release. (ENG179747)
Another bug (affecting IOS version 12.3(14)T1) prevents Vivinet Diagnostics from retrieving the device configuration information it needs for diagnosing problems with QoS settings. Messages in the Error Log Viewer will indicate the failure of an SNMP request or the failure of a request for device configuration. To obtain a fix for the bug, contact Cisco and reference ID number CSCsa53739.
- Missing Cisco switches in L2 trace and incorrect VLAN numbers. In order to discover the Layer 2 trace, Vivinet Diagnostics uses the Cisco Community String Indexing function to access the BRIDGE-MIB and CISCO-VTP-MIB tables. Most Catalyst switches support the function, but at least one version, 12.0(5.0)XP, does not. Without such support, Vivinet Diagnostics cannot find all of the Layer 2 switches and may report an incorrect VLAN number for a Layer 2 link. NetIQ is pursuing this matter with Cisco. It is possible that version 12.0(5.1)XP simply does not support the function.
- Nortel firmware limitations. Nortel reports four instances of incorrect metrics occasionally being returned by the QoS0028 trap and/or RTPStatShow. These errors will be fixed in subsequent firmware updates.
- Incorrect Local Round Trip Time Avg. The QoS0028 trap always reports the Local Round Trip Time Avg as "0." This value appears on the Quality Stats tab of the Results table.
- Incorrect codec. In firmware version D98, the QoS0028 trap and RTPStatShow occasionally report an incorrect codec of 4608. This value appears in the Quality Stats of the Results table and in the Quality Stats of the Phone Details (if you are using Nortel CS1000 4.5). For more information, contact Nortel and reference CR number Q01153910.
- Incorrect Local Average Burst Length. RTPStatShow may report an incorrect value for Local Average Burst Length. This value appears in the Quality Stats of the Results table and in the Quality Stats of the Phone Details (if you are using Nortel CS1000 4.5). For more information, contact Nortel and reference CR number Q01193665.
- Incorrect Average Discard Rate. The Average Discard Rate returned from Nortel firmware version D98 may not be correct. This value appears in the Jitter Buffer Loss field of the Results table and in the Quality Stats tab of the Phone Details (if you are using Nortel CS1000 4.5). For more information, contact Nortel and reference CR number Q01145270.
- Password case changes in Nortel upgrade. The process of upgrading from Nortel CS1000 4.0 to CS1000 4.5 changes the passwords on the Call Server and Signaling Server to all uppercase. Any lowercase password that you configured in Vivinet Diagnostics to work with version 4.0 will not work with version 4.5 because the Call and Signaling Servers expect an uppercase password. Any diagnosis you run will fail with the following error message: "CHR0421: Could not retrieve details for phone [extension] from Call Server [name]." You can either change the Call and Signaling Server passwords back to lowercase, or reconfigure the passwords in Vivinet Diagnostics to match the new uppercase format.
- Vivinet Diagnostics console on a Windows XP or Windows Vista computer. With Windows XP and Vista, Microsoft changed the TCP/IP stack for security purposes. Briefly, the stack imposes rate limiting on the number of incomplete outbound TCP connection attempts. Once the limit of 10 is reached, subsequent attempts are queued up until the first set of attempts are resolved. While this helps limit a virus from spreading to uninfected computers, it also affects benign applications that scan a subnet for network discovery purposes. Vivinet Diagnostics is one such application -- it scans for the NetIQ Performance Endpoint listening on port 10115. Diagnostics tries to discover an endpoint in order to run VoIP Quality performance tests and RTP traceroute. The TCP/IP change causes problems for Diagnostics. The endpoint discovery will not finish in a timely manner and other Diagnostics actions will also fail to run, resulting in an incomplete diagnosis.
There is a workaround, however. If you run the console on Windows XP and Vista and do not use endpoints, add the following two lines to the
ThresholdConfig.txt file located in
C:\Documents and Settings\All Users\Application Data\NetIQ\Vivinet Diagnostics\:
After saving the change, restart Diagnostics. This configuration circumvents the endpoint discovery so that only a single computer is scanned, rather than an entire subnet, thereby avoiding the rate limit issue.
Note Modifying any threshold value (by selecting Threshold on the Options menu) overwrites the changes to
ThresholdConfig.txt. In this case, you need to add the two lines again and restart Vivinet Diagnostics to have the workaround take effect. (ENG196658)
Return to Top
NetIQ Performance Endpoints
Vivinet Diagnostics ships with NetIQ Performance Endpoint version 5.1. Performance Endpoints are software agents used in diagnostic testing. They are not a requirement for running Vivinet Diagnostics, but they are recommended.
- Install an endpoint on each subnet in the network.
- Earlier versions of the endpoint software may work with Vivinet Diagnostics, but they lack some necessary functionality and may not yield the most accurate results.
You can download endpoints free of charge from the Performance Endpoints page and install them in a matter of minutes. Endpoint documentation, including complete installation instructions, is provided at the same Web page.
NetIQ periodically updates the endpoint software to include more functionality. The latest endpoint software is available at the Performance Endpoints page.
Return to Top
This release of Vivinet Diagnostics includes enhancements added in previous releases.
Hotfix 73003, November 2011
This release provided the following enhancements:
- Support for Cisco Unified Communications Manager 8.5 and 8.6. With this release, Vivinet Diagnostics can diagnose VoIP problems in environments running Cisco Unified Communications Manager 8.5 or 8.6.
- Support for Avaya Communication Manager 6.0. With this release, Vivinet Diagnostics can diagnose VoIP problems in environments running Avaya Communication Manager 6.0.
Hotfix 72900, May 2011
This release resolved the following issues:
- Vivinet Diagnostics stops unexpectedly due to missing LLDP information. This release resolves an issue in which Vivinet Diagnostics crashes when incomplete information is available from Link Layer Discovery Protocol (LLDP) queries. With this release, Vivinet Diagnostics does not crash because of missing LLDP information from switches and routers in the path. (ENG266624)
- Vivinet Diagnostics fails to get phone information for some localized Cisco phones. This release resolves an issue in which Vivinet Diagnostics fails to contact Cisco phones with HTTP to request phone information from the call server such as the default router. With this release, a change to the HTTP response parsing allows Vivinet Diagnostics to successfully get phone information from localized Cisco phones. (ENG298783)
This release provided the following enhancement:
- Support for Avaya (Heritage-Nortel) Nortel Communication Server 1000 7.0 and 7.5. With this release, Vivinet Diagnostics can diagnose VoIP problems in environments running Nortel CS1000 versions 7.0 and 7.5.
Hotfix 72505, August 2010
This release resolved the following issue:
- SNMP queries to Publishers fail. This release resolves an issue involving the failure of SNMP queries to Cisco Unified Communications Manager Publishers. Queries for lists of subscribers time out when the response time exceeds the threshold in the Vivinet Diagnostics Knowledge Engine. This release increases the response time value in the Knowledge Engine, and allows you to manually extend the 3-second default SNMP timeout period. (ENG287005).
To extend the SNMP timeout period:
- Configure your Communication Manager for SNMP v1 or v2 authentication with a unique community string. The unique community string ensures that not all SNMP requests use the extended timeout value.
- Rename or backup the file
SNMPConfig.txt file in the Vivinet Diagnostics configuration directory. By default this directory is
C:\Documents and Settings\All Users\Application Data\NetIQ\Vivinet Diagnostics.
- Start Vivinet Diagnostics, which creates a default
SNMPConfig.txt file in the configuration directory.
- On the Options menu, click SNMP, and then click Add on the SNMPv1v2 tab.
- Configure the community string from step 1 as the only SNMP community string in the Vivinet Diagnostics SNMP configuration. By entering this community string as the only SNMP community string, you can positively identify the correct line to edit in the
- Stop Vivinet Diagnostics.
- Edit the
SNMPConfig.txt file in the Vivinet Diagnostics configuration directory.
- Locate a line that has 5 space-separated fields ending in the number 3000. The line should look something like the following:
345D5B19583E 1 161 3 3000.
- The 3000 in this line is the number of milliseconds to wait for an SNMP request to timeout for an SNMP session associated with the unique community string.
- Change the 3000 value to
60000 to increase the timeout to 60 seconds.
- Save the
- Start Vivinet Diagnostics.
- Repeat steps 4 and 5 to enter the other community strings in use in your environment.
- Stop and re-start Vivinet Diagnostics. Vivinet Diagnostics will now use the extended timeout value you configured.
Hotfix 72259, June 2010
This release provided the following enhancement:
- Support for Nortel Communication Server 1000 version 6.0. In conjunction with the release of version 7.4 of the AppManager for Nortel Communication Server 1000 (CS1000) module, Vivinet Diagnostics now supports diagnosing VoIP problems for Nortel CS1000 version 6.0 environments.
Version 2.3 (re-release), September 2009
This release provided the following enhancement:
- Support for Nortel Communication Server 2100. Vivinet Diagnostics now supports the AppManager for Nortel Communication Server 2100 module. Vivinet Diagnostics can diagnose end-of-call quality problems identified by the NortelCS2x_CallQuality Knowledge Script and mid-call quality problems identified by the NortelCS2x_PhoneQuality Knowledge Script.
Version 2.3, October 2008
This release offered the following features:
- Support for Avaya Communication Manager. Vivinet Diagnostics can diagnose VoIP problems in environments running Avaya Communication Manager version 4.0 or 5.0.
- Support for Nortel Communication Server 1000 5.5. Vivinet Diagnostics can diagnose VoIP problems in environments running Nortel CS1000 version 5.5.
- Support for Cisco CallManager version 7.0. Vivinet Diagnostics can diagnose VoIP problems in environments running Cisco Unified CallManager version 7.0.
- Support for IPv6. Vivinet Diagnostics recognizes and displays Internet Protocol version 6 (IPv6) addresses in the Console and in reports.
- Support for a blank context in SNMP v3. Vivinet Diagnostics supports the use of a blank, or empty, context in SNMP version 3.
- Support for Layer 2 data from Rapid City and Synoptic routers. In environments with Nortel/Rapid City 86xx routers and Synoptic Baystack routers, Vivinet Diagnostics can completely identify the Layer 2 path. With this release of Vivinet Diagnostics, you do not need to manually identify the neighboring devices for Rapid City and Synoptic routers. (ENG204598)
Version 2.2, April 2008
This release provided support for the following:
- Cisco Unified CallManager versions 6.0 and 6.1. Support for diagnosing VoIP problems in environments running Cisco Unified CallManager versions 3.1 through 6.1.
- Layer 3 switches in the Layer 2 path. Better support for diagnoses involving Layer 3 switches that are placed in the Layer 2 path.
Version 2.2, November 2007
This release provided support for the following:
- SNMP version 3. Support for diagnosing devices running SNMP v3; Vivinet Diagnostics can use the SNMP v3 permissions you may have already configured for NetIQ Vivinet Assessor or NetIQ AppManager.
- Virtual Router Redundancy Protocol. Support for diagnosing VRRP-enabled devices by allowing you to configure the IP addresses of all Master and backup routers.
- Link Layer Discovery Protocol. Support for using LLDP, in addition to CDP and SONMP, to gather diagnostic information from a device’s management information base (MIB).
This release added support for diagnosing call quality and performance on the Cisco POTS (Plain Old Telephone Service) legs of calls. A POTS leg is defined as the point at which voice traffic enters or exits the PSTN (Public Switched Telephone Network) into the data network. Support for Cisco POTS call legs includes the following:
- Discovery of Cisco routers acting as voice gateways.
- Discovery of dial peers and their associated interface in a voice gateway device.
- Discovery and polling of active POTS/VoIP call legs in a voice gateway:
- Active POTS call legs are polled for Signal In, Signal Out, ERL, and ACOM. For each, Vivinet Diagnostics calculates the average, minimum, maximum, and standard deviation. Diagnoses identify the voice interface associated with each active POTS call leg.
- Active VoIP call legs are polled for round-trip delay, received delay, lost packets, early packets, and late packets. From these metrics, Vivinet Diagnostics calculates MOS, R-value, lost data, delay, and jitter buffer loss.
- Support for the following voice interfaces: Analog FXO/FXS ports and digital voice trunks such as ISDN/T1 PRI, for which diagnoses identify the bearer channel that handles the call.
- Polling of ISDN/T1 PRI bearer channel utilization for the digital voice interface that handles the active call legs for the PSTN phone number.
- Discovery of recent call legs (call history) and the final ACOM value for POTS legs.
- Discovery of the route pattern and associated CallManager used to locate the voice gateway for a PSTN phone number.
- Support for traffic classes on Cisco devices. Vivinet Diagnostics can determine whether traffic classes have been defined and can diagnose problems (utilization, queue discard rate, and queue depth) based on various statistics associated with each traffic class. Vivinet Diagnostics can provide diagnoses only for traffic classes for which priority queuing is enabled.
- Limited support for Cisco CallManager Express. Vivinet Diagnostics presents phone properties (such as IP address, extension number, and registration status) for CallManager Express routers that appear in a traceroute path. These properties are displayed in the Properties dialog box of the router's icon in the Path Trace of the Diagnose view.
- Support for Cisco IPT H.323 voice gateways.
- Changes to the Vivinet Diagnostics Console:
- Two new detail tabs appear after a left-click on the PSTN phone icon in a diagnosis: Active Call Legs and Recent Call Legs. Recent and active call legs are displayed only for traversing dial peers for which the PSTN phone number matches the destination pattern associated with the dial peer.
- Four new detail tabs appear after a left-click on the voice gateway icon in a diagnosis: VoIP Dial Peer, POTS Dial Peer, Active Call Legs, and Recent Call Legs. The dial peer tabs highlight all peers defined in the voice gateway relevant to the direction of voice calls to the proper voice interface. The call legs tabs highlight all active/recent calls on the voice gateway, regardless of the PSTN phone number.
- New detail tab appears after a left-click on the link between the voice gateway and the PSTN phone icons in a diagnosis: POTS Interface. This new tab highlights the media properties of the voice interface that should be handling the calls for the PSTN phone number: the properties of the FXO/FXS port for an analog interface, or the properties of the T1/DS1 group or DS1 signaling channel for a digital interface.
This release added the following new features:
- Support for Nortel products. Support for devices manufactured by Nortel and for Nortel CS1000 versions 4.0 and 4.5.
- Identification of the “Probable Cause” of VoIP problems between Nortel devices. A diagnosis identifies the what, where, when, and severity of a network condition. The Probable Cause tells you why the diagnosis occurred and where you should look to fix the problem. Probable Cause results are triggered only by RTCP-XR metrics.
- Expanded support for CallManager. Support for Cisco CallManager version 4.x.
- More complete diagnosis reports. For example, if phones are used as Target Devices, reports contain information gathered from Nortel RTPStatShow.
- The ability to select the vendor (Cisco or Nortel) whose Target Devices you use to run diagnostic tests. By selecting a vendor, you customize the Define, Diagnose, and Report views, and the Options menu.
- Packet loss concealment enabled. To better reflect the current usage in the field, version 2.0 enables packet loss concealment (PLC) for the G.711a and G.711u codecs. PLC was disabled in previous versions. If you open a G.711a or G.711u diagnosis saved in a previous version, PLC is disabled until you explicitly change the call script to G.711a or G.711u.
Return to Top
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information page.
For general corporate and product information, see the NetIQ Corporate Web site.
For interactive conversations with your peers and NetIQ Corporation experts, become an active member of Qmunity, our community Web site that offers product forums, product notifications, blogs, and product user groups.
Return to Top
THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.
For purposes of clarity, any module, adapter or other similar material ("Module") is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.
This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.
This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.
U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.
© 2012 NetIQ Corporation and its affiliates. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.
Return to Top