HP Network Node Manager iSPI for IP Telephony Software System and Device Support Matrix

For the Windows® operating system

Software Version: 9.20

This document provides an overview of the system requirements and supported devices for HP Network Node Manager iSPI for IP Telephony Software (NNM iSPI for IP Telephony) version 9.20.

To check for recent updates and to see the Release Notes and Support Matrix for the NNM iSPI for IP Telephony 9.20 on HP-UX, Linux, or Solaris, visit this URL: HP Software Product Manuals

This document is intended to augment the Release Notes. You can find both the Support Matrix (IPT_SupportMatrix_en.html) and the Release Notes (IPT_ReleaseNotes_en.html) at the root directory of the installation media.

Hardware and Software Requirements
   Hardware
       CPU, RAM, and Disk Space Requirements / Maximum Supported Managed Environment
       Disk Space Requirements on the NNM iSPI Performance for Metrics/NPS System for Retention of Reporting Data Generated by the NNM iSPI for IP Telephony
      Memory, CPU Requirements on the NNM iSPI Performance for Metrics/NPS System for Processing of the Reporting Data Generated by the NNM iSPI for IP Telephony
      System sizing NNM iSPI Performance for Metrics/NPS System for Processing of the Reporting Data Generated by the NNM iSPI for IP Telephony
   Operating System
        Virtual Memory/Swap Space
   Database
   Web Browser
Internationalization and Localization Support
Supported Devices
Support
Legal Notices

Hardware and Software Requirements

Pre-installation requirements, as well as instructions for installing NNM iSPI for IP Telephony, are documented in the installation guide provided in Adobe Acrobat (.pdf) format. The document file is included in the root directory on the product's installation media as: IPT_InstallGuide_en.pdf.

Before installing the NNM iSPI for IP Telephony, make sure that your system meets the following minimum requirements:

Hardware

• Intel 64-bit (x86-64) or AMD 64-bit (AMD64)
  • Only supported for the Windows operating system.
  • For Intel 64-bit (x86-64), the following Xeon processor families are recommended: Penryn, Nehalem, Westmere, and Sandy Bridge.
  • For AMD 64-bit (AMD64), the following Opteron processor families are recommended: Istanbul, Lisbon, and Valencia.
• Hypervisor Virtualization
  •  VMware ESX Server 3.5, ESX Server 4.0 or later minor version, ESXi 4.1 or later minor version, ESXi 5.0 or later minor version.
    • Virtual environment must meet the x86-64 or AMD64 hardware requirements listed here.
    • Bridged network environment required. NAT'ed network environments are supported.

CPU, RAM, and Disk Space Requirements / Maximum Supported Managed Environment

Below are the three tiers of managed network environments and the hardware required by the NNM iSPI for IP Telephony for supporting these environments. Managed environments bigger than the Large tier are not supported without additional HP approval. Make sure to check the NNMi Support Matrix.

The NNM iSPI for IP Telephony hardware requirements mentioned in the following tables are in addition to NNMi hardware requirements mentioned in the NNMi Support Matrix.

Before installing the NNM iSPI for IP Telephony, make sure that your system meets the following minimum requirements:.

• The RAM Requirement mentioned in the tables below is an approximate number to help you get started with the sizing of the system. However, if you are planning to install the iSPI Performance for Metrics on the same system, you must ensure that the physical RAM is greater than two times that of the combined Xmx values of NNMi, the NNM iSPI for IP Telephony, other content iSPI s (if installed on the system), the iSPI Performance for Traffic Master Collector (if installed on the system), the iSPI Performance for Traffic Leaf Collector (if installed on the system), and the iSPI Performance for Quality Assurance (if installed on the system). You must also consider the consumption of memory in segments apart from the memory consumption by various heap segments. In addition, you must also consider consumption of memory by the operating system, applications from HP that are not listed in this document, and applications from other vendors.

• If you are planning to install the iSPI Performance for Metrics on a separate system, you must ensure that the physical RAM is greater than that of the combined Xmx values of NNMi, the NNM iSPI for IP Telephony, other content iSPI s (if installed on the system), the iSPI Performance for Traffic Master Collector (if installed on the system), the iSPI Performance for Traffic Leaf Collector (if installed on the system) and the iSPI Performance for Quality Assurance (if installed on the system). You must also consider the consumption of memory in segments instead of considering various heap segments. In addition, you must also consider consumption of memory by the operating system, applications from HP that are not listed in this document, and applications from other vendors.

• It is recommended that you provision 4 GB or more of RAM for the operating system and the other applications on the system.

Table 1: Standalone Instance of the NNM iSPI for IP Telephony for Monitoring the Cisco, Avaya, or Nortel IP Telephony

Managed Environment Size						IP Telephony Minimum Hardware System Requirements
Approximate managed environment tier	Number of discovered IP Phones	Number of discovered NNMi nodes that are not hosting IP Phones	Number of discovered NNMi Interface objects	Number of polled NNMi Interfaces	Number of concurrent NNMi users	CPU (64-bit) x86-64 AMD641	RAM	**Java heap size the NNM iSPI for IP Telephony	Java heap size for NNMi	Disk space for NNM iSPI for IP Telephony installation with an Incremental Demand on (<NnmInstallDir>)	Total Disk Space for Database and Data During Execution (<NnmDataDir>) Note: This does not include the disk space to retain the data for reporting.
Entry	Up to 500	Up to 100	7K	2500	5	2 CPU Cores	10 GB	4 GB (-Xmx4g)	3 GB (-Xmx3g)	1 GB	20 GB
Small	Up to 3K	Up to 500	40K	2500	10	4 CPU Cores	12 GB	6 GB (-Xmx6g)	4 GB (-Xmx4g)	1 GB	40 GB
Medium*	Up to 10K	Up to 1.5K	90K	5K	20	4 CPU Cores	16 GB	6 GB (-Xmx6g)	8 GB (-Xmx8g)	1 GB	80 GB
Large*	Up to 30K	Up to 3K	250K	50K	30	8 CPU Cores	32 GB	16 GB (-Xmx16g)	12 GB (-Xmx12g)	1 GB	160 GB
Very Large*	Up to 50K	Up to 4K	550K	70K	40	8 CPU Cores	48 GB	24 GB (-Xmx24g)	16 GB (-Xmx16g)	1 GB	320 GB

Table 2: Standalone Instance of the NNM iSPI for IP Telephony for Monitoring the Microsoft IP Telephony

Managed Environment Size						IP Telephony Minimum Hardware System Requirements
Approximate managed environment tier	Number of discovered Lync End Users	Number of discovered Gateways	Number of discovered Lync Servers	Number of discovered Lync Sites	Number of concurrent NNMi users	CPU (64-bit) x86-64 AMD641	RAM	*Java heap size for IP Telephony	Java heap size for NNMi	Disk space for NNM iSPI for IP Telephony installation with an Incremental Demand on (<NnmInstallDir>)	Total Disk Space for Database and Data During Execution (<NnmDataDir>) Note: This does not include the disk space to retain the data for reporting.
Entry	Up to 200	1	10	1 Central Site	5	2 CPU Cores	8 GB	2 GB (-Xmx2g)	2 GB (-Xmx2g)	1 GB	20 GB
Small	Up to 1K	Up to 11	Up to 50	1 Central Site and 10 Branches	10	4 CPU cores	12 GB	3 GB (-Xmx3g)	4 GB (-Xmx4g)	1 GB	60 GB
Medium*	Up to 5K	Up to 110	Up to 500	1 Central Site and 100 Branches	20	4 CPU cores	16 GB	4 GB (-Xmx4g)	6 GB (-Xmx6g)	1 GB	80 GB
Large*	Up to 10K	Up to 550	Up to 1K	5 Central Sites and 500 Branches	30	8 CPU cores	24 GB	6 GB (-Xmx6g)	8 GB (-Xmx8g)	1 GB	120 GB
Very Large*	Up to 50K	Up to 1100	Up to 3K	10 Central Sites and 1000 Branches	40	8 CPU cores	32 GB	8 GB (-Xmx8g)	10 GB (-Xmx10g)	1 GB	160 GB

*Note: Also assumes up to 30 K, 75K, and 100K CDR records per hour collected and processed by the NNM iSPI for IP Telephony for the medium tier, large tier, and very large tier respectively.

¹See above for processor recommendations.

**To tune Java heap size, see the Tuning the jboss Memory for the NNM iSPI for IP Telephony.

*Note: Also assumes a total of 375K and 500K CDR records per hour collected across regional manager instances of the NNM iSPI for IP Telephony and forwarded to a single global manager instance of the NNM iSPI for IP Telephony for the medium tier and large tier respectively.

²See above for processor recommendations.

Note: See the NNMi 9.20 Support Matrix for requirements in a Global Network Management (GNM) environment.

**To tune Java heap size, see the Tuning the jboss Memory for the NNM iSPI for IP Telephony.

Disk Space Requirements on the NNM iSPI Performance for Metrics System for Retention of Reporting Data Generated by the NNM iSPI for IP Telephony

If you decide to enable various reporting in the NNM iSPI for IP Telephony, you must provision for incremental disk space usage on the system for long term storage of the reporting data created by the NNM iSPI for IP Telephony and stored in the NPS database. You must make such a provision for the following scenarios:

• The NNM iSPI Performance for Metrics/NPS is installed on the same machine where NNMi and the NNM iSPI for IP Telephony are installed
• The NNM iSPI Performance for Metrics/NPS is installed on a separate system

See the NNM iSPI Performance for Metrics/NPS Support Matrix document for more information about minimum system requirements (including those for disk space) for appropriately evaluating the disk space requirements.

As a sample estimate, consider the following for a global manager instance of the NPS, which is supplied with the reporting data by a global manager instance of the NNM iSPI for IP Telephony for monitoring the Cisco, Avaya, or Nortel IP telephony:

• For the medium tier: The NPS database must be able to accommodate 16 TB of the reporting data generated by the NNM iSPI for IP Telephony after 400 days of operation.
• For the large tier: The NPS database must be able to accommodate 24 TB of the reporting data generated by the NNM iSPI for IP Telephony after 400 days of operation.

Consider the following for a regional manager instances or single system standalone instance of the NPS, which is supplied with the reporting data by a regional manager instance or single system standalone instance of the NNM iSPI for IP Telephony for monitoring the Cisco, Avaya, or Nortel IP telephony:

• For the large tier: The NPS database must be able to accommodate 4 TB of the reporting data generated by the NNM iSPI for IP Telephony after 400 days of operation.
• For the very large tier: The NPS database must be able to accommodate 8 TB of the reporting data generated by the NNM iSPI for IP Telephony after 400 days of operation.

Additional Information

• The NPS database table spaces planning during the deployment is extremely important. For the medium and large tiers, it is recommended that you allocate approximately 100 GB for the TEMP space and an appropriate amount of disk space for the USER space that is your primary container of data. Make sure you refer to the NPS Support Matrix document and other NPS documents for database sizing. Plan and execute these sizing tasks before starting to use the product, or in some cases, before installing and configuring the NPS.
• Specifically for the USER space in the NPS database, periodic checks on the disk utilization is extremely important. This will help you proactively plan and execute database and disk sizing tasks in a way to prevent the loss of your valuable reporting data or to prevent permanent instability of the system. You can again perform these periodic checks by using various database sizing utilities provided by the NPS. See the NPS Support Matrix document and other NPS documents for database sizing.
• You might like to disable the performance polling of a large number of NNMi interfaces and component objects in your environment if you are not interested in reports on interface and component health. Alternatively, you might like to tune the retention of aggregated interface and component health metrics in reporting packages to a value that is smaller than the default 400 (days). You can also apply both the measures at the same time to use your disk space optimally. Refer to the NNM iSPI Performance for Metrics/NPS documentation for reference information on how to accomplish these tasks.

You can use this information along with the iSPI Performance for Metrics/NPS Support Matrix document for appropriate sizing of the systems involved.

Memory, CPU Requirements on the NNM iSPI Performance for Metrics/NPS System for Processing of the Reporting Data Generated by the NNM iSPI for IP Telephony

If you decide to enable various reporting options for the NNM iSPI for IP Telephony, you must provision for incremental memory and CPU usage on the system for the NNM iSPI Performance for Metrics/NPS, which is supplied with the reporting data created by the NNM iSPI for IP Telephony. You must make such a provision for the following scenarios:

• The NNM iSPI Performance for Metrics/NPS is installed on the same machine where NNMi and the iSPI for IP Telephony are installed
• The NNM iSPI Performance for Metrics/NPS is installed on a separate system

See the NNM iSPI Performance for Metrics/NPS Support Matrix document for more information on minimum system requirements (including those for the CPU and memory) for appropriately evaluating the CPU and memory requirements and taking adequate measures before deploying the NNM iSPI Performance for Metrics/NPS.

• As a general rule, for co-located installations (where the NPS and NNMi are installed on the same system), the physical RAM size of the system must be at least twice as much as the total Heap Size requirements from the NNM iSPI for IP Telephony, NNMi, other iSPI product (or product components), and other applications installed on the system (leaving aside around 4 GB for the operating system).
• For the other type of installation (where the NPS is not installed on the NNMi management server), the physical RAM size of the NPS system must be at least twice as much as the total Heap Size requirements from the other iSPI products or product components and other applications installed on the system (leaving aside around 4 GB for the operating system).
• For large and very large tier deployments of the standalone instance of the NNM iSPI for IP Telephony, and for medium and large tier deployments of all global manager instances of the NNM iSPI for IP Telephony, install the NPS on system other than the NNMi management server.

Also, make sure that the various parameters related to the NPS database and BI server are appropriately tuned for your scale. Default settings created by the NPS installation for these parameters might not be appropriate for the scale of your deployment.

• Some of the important parameters for the NPS database server are the in-memory caches used by the database engine. These parameters must have correct settings configured to avoid performance problems in report execution.
• Similarly, parameters for the NPS BI server must be tuned appropriately by directly interacting with the NPS.
  
  Finally, you might like to disable the IP Telephony reporting packages for a specific IP Telephony vendor (Avaya or Cisco) if you are not interested in those reports. You can accomplish this by uninstalling the NPS report extension pack containing the specific reporting packages from NNM iSPI for IP Telephony. Refer to the iSPI for IP Telephony and NPS documentation for instructions on uninstalling a specific extension pack.

System sizing NNM iSPI Performance for Metrics/NPS System for Processing of the Reporting Data Generated by the NNM iSPI for IP Telephony

Following table helps you to identify NPS system resources required for the NNM iSPI for IP Telephony reports. These are incremental additional demands on CPU, memory, and disk space on the NPS system because of the IP Telephony report data load, summarization, and retrieval using IP Telephony reports.

^ Refer to tiers in Table 1 and Table 2 for standalone or regional manager instance of the NNM iSPI for IP Telephony deployment.

^^ Indicates that the NNM iSPI Performance for metrics DataDir is configured during installation of the NNM iSPI Performance for Metrics on Windows (C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software by default). You can also set the data archival period in the Configuration utility of the system. If the data archival period for the NNM iSPI Performance for Metrics is set to a high value, make sure that adequate free disk space is available on the system on which you have installed the NNM iSPI Performance for Metrics. You can refer to the NNM iSPI Performance for Metrics Installation Guide to configure these parameters.

Following table provides information on Global Manager instance of the NNM iSPI for IP Telephony integrated with a Global Manager NPS system in Global Network Management (GNM) deployment of the NNM iSPI for IP Telephony.

^ Refer to tiers in Table 3 and Table 4 for Global Network Management (GNM): Global Manager instance of the NNM iSPI for IP Telephony deployment.

^^ Indicates that the NNM iSPI Performance for metrics DataDir is configured during installation of iSPI Performance for Metrics on Windows (C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software by default). You can also set the data archival period in the Configuration utility of the system. If the data archival period for the NNM iSPI Performance for Metrics is set to a high value, make sure that adequate free disk space is available on the system on which you have installed the NNM iSPI Performance for Metrics. You can refer to the NNM iSPI Performance for Metrics Installation Guide to configure these parameters.

Tuning the jboss Memory

To change the jboss Maximum Java Heap Size (‑Xmx) or other Java Virtual Machine parameters, follow these steps:

1. Stop the NNM iSPI for IP Telephony process by the following command: ovstop –c iptjboss
2. Edit the nms-ipt.jvm.properties file available in the %nnmdatadir%\shared\ipt\conf directory
3. Update the Maximum Java Heap Size to the required value. For example, a snippet of the nms-ipt.jvm.properties file appears as:
   #
   # JVM Memory parameters
   #   ‑Xms: Initial Java Heap Size
   #   ‑Xmx: Maximum Java Heap Size
   #
   ‑Xms1024m
   ‑Xmx2048m
4. Start the NNM iSPI for IP Telephony process by the following command: ovstart –c iptjboss

For more information related to NNMi values, see the NNMi Support Matrix.

Operating System

Windows

• Windows Server 2008 x64 Datacenter Edition with Service Pack 2
• Windows Server 2008 R2 x64 Datacenter Edition with Service Pack 1
• Windows Server 2008 x64 Enterprise Edition with Service Pack 2
• Windows Server 2008 R2 x64 Enterprise Edition with Service Pack 1
• Windows Server 2008 x64 Standard Edition with Service Pack 2
• Windows Server 2008 R2 x64 Standard Edition with Service Pack 1

  Notes

  • Windows operating systems on Itanium Processor Family (IPF) is not supported.
  • Windows 32-bit operating systems are not supported.
  • IPv6 is not supported on Windows operating systems.
  • The Windows SNMP Trap service (or any other service that takes UDP Port 162) must be disabled.
  • Anti-virus and backup software can interfere with NNMi operation if this software locks files while NNMi is running. Any application that locks files should be configured to exclude the NNMi database directory (on Windows 2008, C:\ProgramData\HP\HP BTO Software\databases).

Virtual Memory/Swap Space

• Recommended size is at least equal to the physical memory
• Verify and adjust the virtual memory: 
• Windows: Use System Properties.

High Availability

The NNM iSPI for IP Telephony can run on certain high availability systems with additional configuration. See the NNMi Deployment Reference and NNM iSPI for IP Telephony Installation Guide on how to install and configure NNM iSPI for IP Telephony on high availability systems. The following configuration is supported:

Microsoft: Microsoft Cluster Service version 6.0 and above (with Microsoft recommended patches) for Windows 2008.

Note: Recommended version for Microsoft Cluster Service is 6.1 (with Microsoft recommended patches)

Database

The database(embedded or Oracle)selection for the NNM iSPI for IP Telephony should be the same as NNMi. The Oracle database instance must be different from NNMi database instance. See the NNM iSPI for IP Telephony Installation Guide for more information.

• Embedded database on the management system
  • The embedded database is automatically installed, initialized and maintained by NNMi and NNM iSPI for IP Telephony.
  • The embedded database comes with tools for re-initialization, online backup, and restore.
  • The embedded database performs well for most deployments.
• Oracle 10g Release 2 (10.2.0.x) or Oracle 11g Release 2 (11.2.0.x) installed on a remote system::
  • It is recommended that the network connection between the NNMi management server and the database server be at least 1 GB.
  • Database user must be created before installation with appropriate tablespace.

Web Browser

General Web Browser Requirements

• Disable all pop-up window blockers for the browser.
• Enable cookies for the browser.
• Enable JavaScript for the browser.
• Enable VML for Internet Explorer browsers.
• Install Adobe Flash.
• The resolution of the client display should be at least 1024x768.

• Caution: The following browsers are not supported:

  • Microsoft Internet Explorer version 8 or version 9 when running in Compatibility View mode
    Be sure to disable Compatibility View in Internet Explorer using Tools → Compatibility View Settings (clear all check boxes).
    
  • Microsoft Internet Explorer version 7: Internet Explorer 7 (or Internet Explorer in Compatibility View mode) has many known issues, including many layout issues, no ability to close the Help → System Information window, and inability to change selections for CSV export.
    
  • Microsoft Internet Explorer version 6
    
  • Mozilla Firefox 3.6.x through 9.x
  • Mozilla Firefox 11.0 and other non-ESR versions of Firefox.
    
  • Apple Safari (all versions)
  • Opera (all versions)
  • Google™ Chrome (all versions)

Web Browser Running on a Remote Client System (for operational use)

• Microsoft Internet Explorer (32-bit and 64-bit) version 8 (not running in Compatibility View mode).
• Microsoft Internet Explorer (32-bit and 64-bit) version 9 (not running in Compatibility View mode).
• Mozilla Firefox version 10.0 ESR or later minor version on a Windows or Linux client. The Firefox browser is available from www.mozilla.org/firefox. The Firefox browser works best if new windows are opened as separate windows, not tabs.

Web Browser Running on the Local Management Server System (for initial installation and configuration use)

Any browser supported for operational use (see above) when running on the NNMi management server.

Adobe Flash Player Plug-in

The Real-time Line Graphs (Actions → Graphs) and the SNMP MIB Browser (Tools → Browse MIBs) require the Adobe Flash Player Plug-in version 10.0.32.18 or higher. The Adobe Flash Player is available from www.adobe.com/go/getflash/.

Internationalization and Localization Support

NNM iSPI for IP Telephony is internationalized and can be used on operating systems configured for non-US-English locales that are supported by the operating systems. Those locales include variants of
Japanese, Korean, Simplified Chinese, Traditional Chinese, Western and Central European locales, and Russian.

On Windows systems, the NNM iSPI for IP Telephony does not support installation using directory paths with localized characters; path names for %NnmInstallDir% and %NnmDataDir% can contain English characters only.

The NNM iSPI for IP Telephony is not localized; therefore, NNM iSPI for IP Telephony specific strings appear in English. However, the NNMi-specific views and strings appear in the non-English language (that is supported by NNMi). For the list of languages supported by NNMi, see NNMi Support Matrix, 9.20.

Supported Devices

IP Telephony Devices

The following tables list the IP telephony devices supported by this version of the NNM iSPI for IP Telephony:

• Cisco IP telephony:
  
  

  Devices/Entities	Version/Model/Type/Supported Protocol
  Cisco Unified Communications Manager	5.x,6.x,7.x, and 8.x
  Voice Gateway	All Cisco IOS-based gateways, Cisco VG224 Analog Gateways, and Cisco VG 248 Analog Gateways (supports Cisco Voice Gateways running MGCP and H.323 protocols; supports T1/E1 PRI, T1/E1 CAS, FXS, FXO, E&M voice interfaces).
  IP Phone	Supports IP phones running on the SIP and SCCP (or Skinny) protocols. Supports Cisco IP Communicator Soft Phones. Also supports all other models of Cisco Unified IP Phone appliances.
  Gatekeeper	All Cisco IOS routers that can run the Cisco H.323 Gatekeeper service. CISCO-GATEKEEPER-MIB must be accessible on the Cisco IOS-based device that runs the Cisco Gatekeeper Service.
  Unity	Cisco Unity 5.x, 7.x, 8.x Cisco Unity Connection 7.x, 8.x SNMP MIB CISCO-UNITY-MIB must be accessible on the Unity and Unity Connection systems.
  Cisco Call Manager Express (CCME)	All Cisco IOS routers that can run the CCME service.
  Survivable Remote Site Telephony (SRST)	All Cisco IOS routers that can run the SRST service.
  Intercluster IP Trunk	Gatekeeper-controlled intercluster trunks and non- gatekeeper-controlled intercluster trunks.

  
  
• Avaya IP telephony:
  
  

  Devices/Entities	Version/Model/Type/Supported Protocol
  Communication Manager	Supports Communication Manager software/Firmware version 4.x/ 5.x/6.x on the following servers : s88xx s87xx s85xx s84xx s83xx Note: If you are using version 5.x of the Avaya Communication Manager, you must install service pack 6 (Patch 18576) or later versions of the service packs on the Avaya Communication Manager. If you are using version 6.x of the Avaya Communication Manager, you must install service pack 2 (Patch 18567) or later versions of the service packs on the Avaya Communication Manager.
  Local Survivable Processor	Supports Communication Manager software/Firmware version 4.x/5.x/6.x on the following servers : s8500 s8300
  H.248 Media Gateways	Supports Communication Manager software/Firmware version 4.x/5.x/6.x on the following media gateways: G250 G350 G430 G450 G700
  Port Network Media Gateway	Supports Communication Manager software/Firmware version 4.x/5.x/6.x on the following port network media gateway: G650
  IP Phones	Communication Manager software/Firmware 4.x/5.x/6.x compliant IP phones. The supported protocols include SIP and H.323. On the Avaya ONE –X soft phones, at the least, Avaya one-X Communicator Release 5.2 with Service Pack 4 (Product Version 5.2.0.23) or its equivalent Service Pack for Avaya one-X Communicator Release 6.x must be installed. The Service Pack level must include the fix for the issue with malformed CNAME in RTCP packets or the enhancement titled “Updated the CNAME in the RTCP packet for more accurate monitoring traceability.”

• Nortel IP telephony:
  
  

  Devices/Entities	Version/Model/Type/Supported Protocol
  Call Server	Models running the software version 5.x
  Signaling Server	Models running the software version 5.x
  Media Gateway	Media Gateway Controller Card (MGC) with DSP daughter boards, Media Card (MC), Voice Gateway Media Card (VGMC); MC 32 and MC 32S cards are supported in the MC or VGMC category.
  IP Phone	The following Nortel IP phone models are supported: NORTEL IP PHONE 2001 NORTEL IP PHONE 2002 NORTEL IP PHONE 2004 NORTEL IP PHONE 2007 NORTEL IP PHONE 2033 NORTEL IP PHONE 1110 NORTEL IP PHONE 1140E NORTEL IP SOFTPHONE 2050 MULTIMEDIA CLIENT

• Microsoft IP telephony:
  
  

  Devices/Entities	Version/Model/Type/Supported Protocol
  Microsoft Lync Server 2010  Gateway	NET UX 1.3
  	HP Survivable Branch Module (HP SBM) 1.1.19.0

  
  
  

HP Software Support

This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.

HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:

• Search for knowledge documents of interest
• Submit and track progress on support cases
• Submit enhancement requests online
• Download software patches
• Manage a support contract
• Look up HP support contacts
• Review information about available services
• Enter discussions with other software customers
• Research and register for software training

To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.