---
title: "Avaya IP Office r10.0 and prior Deployment Guide"
slug: "deployment-guide-avaya-ip-office"
tags: ["IPO Report Pack", "Report Schedule"]
updated: 2023-08-03T14:51:08Z
published: 2023-08-03T14:51:08Z
canonical: "support.nectarcorp.com/deployment-guide-avaya-ip-office"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.nectarcorp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Avaya IP Office r10.0 and prior Deployment Guide

## Overview

This guide provides instructions to configure the monitoring and management of Avaya IP Office using Nectar’s IP Office Module.

### Audience

This guide is intended for system administrators or engineers who have system administration access and technical knowledge of Avaya IP Office and a familiarity with deploying Nectar’s software.

### Supported Software Versions

- Avaya IP Office r5-10.0

NOTEThis document is for support of Avaya IP Office systems running r10.0 and prior. For support of Avaya IP Office systems running r10.1 or later, refer to document **Nectar Deployment Guide: Avaya IP Office r10.1 and above**.

### 

### 

### 

### Requirements

The Avaya IP Office (IPO) VKM can run co-resident on the Windows VM Pro Server or standalone on a separate RIG. You must have a minimum of 100MB of disk space, and 4GB of RAM available. You will need administrative and SNMP access to the VM Pro Server or separate RIG.

NOTEIf you are deploying Nectar Real-Time Quality Monitoring for the IP Office, then Nectar must run on a dedicated RIG. It is not supported on the VM Pro Server.

## RIG Preparation

NOTEYou only have to complete the steps in this chapter if you are installing Nectar software on the VM Pro Server. If you are not installing Nectar on the VM Pro Server skip to section [**IPO Configuration**](/v1/docs/deployment-guide-avaya-ip-office#ipo-configuration).

The Nectar module for IP Office connects to Avaya IP Office through System Status. Avaya IP Office will accept up to two simultaneous connections to System Status. However, they cannot be from the same IP address.

A client will commonly run System Status on the VM Pro Server, which is normally where Nectar software resides. If the client runs the System Status application, it will disconnect the Nectar RIG and interrupt monitoring since both sessions originate from the same IP address.

To avoid this conflict and allow Nectar software monitoring to continue, even if the client initiates a System Status session from the VM Pro Server, assign a secondary static address to the VM Pro Server as discussed below.

NOTEThis functionality is supported on Nectar CMP r5.3 or greater.

### Secondary IP Address for RIG

We will assign a secondary, static IP address to the VM Pro Server. Going forward, this is what the client will use to launch a System Status session.

In this example, the VM Pro Server is running on 10.65.22.5. We will assign 10.65.22.9 as a secondary IP address. These steps are based on a **Windows 7** PC running **VM Pro**.

1. Open the **Windows Control Panel**:
  - On **Windows 7**, click the **Start** icon and select **Control Panel**.
  - On **Windows 10**, right-click on the **Start** icon and select **Control Panel**.
2. Click **View network status and tasks**.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-5qcfcazy.jpe?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Computer Settings
3. Click **Local Area Network.**  
  
**![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-bvhjuawg.jpe?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Network Settings**
4. In the **Local Area Connection Status** window, click the **Properties** button.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-91djr7zy.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Local Area Connection Status
5. In the **Local Area Connection Properties** window, select **Internet Protocol Version 4 (TCP/IPv4)**. Then, click the **Properties** button.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-brwib17j.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Local Area Connection Properties
6. In the **Internet Protocol Version 4 (TCP/IPv4) Properties** window, click **Advanced** button.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-afnndgk1.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Internet Protocol Version 4 (TCI/IPv4) Properties
7. In the **Advanced TCP/IP Settings** window, click **Add**.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-0zroc4fd.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Advanced TCP/IP Settings
8. In the **TCP/IP Address** dialog window, enter the secondary **IP address** and **Subnet mask**. Then, click **Add.**  
  
**![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-oir7yr1t.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)TCP/IP Address**  
The **Network Interface Controller (NIC)** now has two IP addresses.
9. Click **OK** (three times), then click **Close** (two times) to close previous configuration windows. A restart is not required.

## IPO Configuration

the IPO by doing the following:

- [**Specify the SNMP Community String**](/v1/docs/deployment-guide-avaya-ip-office#specify-the-snmp-community-string)
- **[Specify the SNMP Trap Destination](/v1/docs/deployment-guide-avaya-ip-office#specify-the-snmp-trap-destination)**
- **[Specify Firewall Settings](/v1/docs/deployment-guide-avaya-ip-office#specify-firewall-settings)**
- **[Set Up RTCP Collector](/v1/docs/deployment-guide-avaya-ip-office#set-up-rtcp-collector)**
- [**Restart the IPO**](/v1/docs/deployment-guide-avaya-ip-office#restart-the-ipo)

### Specify the SNMP Community String

1. Connect to the IPO using **Avaya’s IP Office Manager** application.
2. Select System in the left-hand pane.
3. Select the **System Events** tab.
4. On the **Configuration** tab:
  1. Confirm that the **SNMP Enabled** box is checked.
  2. Enter the **Community** string, and confirm the **SNMP Port** is **161**.
  3. Click **OK** when done.

![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-q0dblncc.jpe?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Avaya IP Office Manager

### Specify the SNMP Trap Destination

1. In **System Events** tab, select the **Alarms** tab.
2. Click **Add**.
3. Select the **Trap** radio-button.
4. Enter the **Server Address,** which is the IP address of the Nectar RIG.
5. Confirm that the **Port** defaults to **162**.
6. Enter the SNMP **Community**. In this example, we use **NectarCMPr**.
7. Under **Events**, select all check boxes. (The list extends off the screen.)
8. Click **OK** when done.

![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-zpa12oib.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Edit Alarms

### Specify Firewall Settings

1. Select **Firewall Profile** in the left-hand panel.
2. In the **SNMP** field, select **Bothway** from the drop-down menu.
3. Click **OK** when complete.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-69wr3lhl.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Firewall Settings

### Set Up RTCP Collector

Follow these steps to set up the RTCP Collector if you are deploying Nectar Real-Time Quality Monitoring.

NOTEReal-Time Quality Monitoring requires Real-Time Quality Licensing. Without these licenses, Real-Time Quality Monitoring will not function.

1. Navigate to the **LAN1** tab.
2. In the sub menu, select **VoIP**.
3. Enter the RIG address in the **RTCP collector IP address for phones** field.  
The RIG IP address must be entered in **Step 3** prior to being able to complete **Step 4**.
4. Within the **RTP** panel, **Enable RTCP Monitoring on Port 5005** is selected by default and directs RTCP feedback to the IP Office. Click the check box to deselect this selection.

NOTEThe checkbox will empty and **Enable RTCP monitoring on Port 5005** will gray out. That is expected behavior. As long as the IP address is still present, it will send RTCP feedback to Nectar.  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-58gcu7ca.jpe?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)RTCP Collector

### Restart the IPO

Save the configuration and restart the IPO for these changes to take effect.

## VM Pro Configuration

If you will be monitoring the VM Pro Server, Nectar needs **SNMP read only** access to the device. Follow these steps to configure the VM Pro server for SNMP:

1. Click **Start** icon; then enter **services.msc**. in the **Search programs and files text window**.
2. Right-click on **SNMP Service** and select **Properties**.
3. Select the **Security** tab.
4. Click **Add**.
5. Select **Read Only** from the **Community Rights** drop-down list.
6. Enter the **Community Name**.
7. Click **Add**.
8. Click **OK** to close the **Properties** window.
9. Restart the SNMP service.

## Nectar Configuration

Before configuring Nectar software, the Nectar software must be loaded and the Nectar software license must be applied.

Configure the Nectar software doing the following:

- [**IP Address Binding**](/v1/docs/deployment-guide-avaya-ip-office#ip-address-binding)
- [**Nectar IP Office Module Execution**](/v1/docs/deployment-guide-avaya-ip-office#nectar-ip-office-module-execution)
- [**Configure Real-Time Quality Monitoring**](/v1/docs/deployment-guide-avaya-ip-office#configure-realtime-quality-monitoring)
- [**Phone Alarms**](/v1/docs/deployment-guide-avaya-ip-office#phone-alarms)
- [**Report Pack**](/v1/docs/deployment-guide-avaya-ip-office#report-pack)
- [**Report Agent Selection**](/v1/docs/deployment-guide-avaya-ip-office#report-agent-selection)
- [**Report Schedule**](/v1/docs/deployment-guide-avaya-ip-office#report-schedule)

### IP Address Binding

If Nectar is co-resident on the VM Pro Server and you have completed the instructions in section [***Secondary IP Address for RIG***](/v1/docs/deployment-guide-avaya-ip-office#secondary-ip-address-for-rig), now bind the Nectar software to this secondary address. We recommend doing this through a Remote Desktop Connection (RDC) session to the RIG.

We will do this to both the primary and backup Nectar services.

1. Stop these Nectar services through Windows services using the following steps:
  - Nectar RIG Server
  - Nectar RIG Backup
2. To edit the **server.properties** file; follow the steps below:
  1. Enter **C:\Apps\nectar\etc** into the Windows Explorer address bar.
  2. Find and double-click on **server.properties** file.
  3. In the **server - Notepad** window, add the following line: **bindAddress = 10.65.22.9**.  
  
NOTEThis is an example IP address. Please substitute it with your IP address. For consistency and troubleshooting, create this new entry immediately following the **satelliteType = RIG** line, which is near the top of the file.  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-ulw9xyjt.jpe?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)IP Address Binding
3. Save the file.
4. Navigate to **C:\Apps\nectar\backup\etc** to edit the **server.properties** file.
5. Add the following line:  
**bindAddress = 10.65.22.9.**  
  
**NOTE This is an example IP address. Please substitute it with your IP address. For consistency and troubleshooting, create this new entry immediately following the satelliteType = RIG line, which is near the top of the file.**
6. Save the file.
7. Restart both RIG services through Windows Services:
  - Nectar RIG Server
  - Nectar RIG Backup

### Nectar IP Office Module Execution

Follow these steps to execute the IP Office module:

1. Navigate to **Modules** > **Avaya** > **IP Office (prior to r10.1)**.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-d2my7fhh.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Avaya > IP Office (prior to 10.1)
2. In the **Avaya IP Office (prior to r10.1) Setup** panel, locate and select **Add**.  
The **Add IP Office Connection** dialog box appears (Figure **Add IP Office Connection**).
3. In the **General** tab, Input the required information:
  1. **Name**: enter the name of the IPO system.
  2. **Description**: enter a description for the IPO system.
  3. **Address**: enter the IP address of the IP Office.
  4. **Secure Service**: select the check box.
  5. **Username** and **Password**: enter the username and password to login to System Status.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-pkw3fxn3.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Add IP Office Connection
4. In the **Community** tab, first select the **SNMP Version** that you are using then enter SNMP credentials (for **V3**, you will have to enter additional authentication values).
5. Enter the **Community** string.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-fvme0vg0.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Add IP Office Connection II
6. If you want to monitor the VM Pro server, in the **Voicemail Pro** tab, enter the following information:
  1. Select the **Enable Monitoring** check box.
  2. In the **Address** field, enter the VM Pro server IP address.
  3. Select the **SNMP Version** you are using (for **V3**, you will have to enter additional authentication values).
  4. Enter the **Community** string.
  5. Click **OK**.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-24f8jaid.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Add Avaya IP Office Connection III
7. The system will now appear within the **IP Office** window.

- The **Status** column should indicate **online**. This means that Nectar is successfully communicating with the IPO.
- If the status reads **Result: Invalid user or password**, try reconfirming your password.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-7l59k9m1.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)IP Office Online

### Configure Real-Time Quality Monitoring

Follow these steps to configure Real-Time Quality Monitoring, if deploying.

NOTEThis requires Real-Time Quality licensing. Please confirm with your Nectar Channel Account Manager if necessary

1. Navigate to **Configure** > **Quality Management** > **Real Time QoS**.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-2xkmtwiw.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Image Caption  
In the **Configure Real Time QoS** dialog window (Figure 19) make the following selections:
2. **RTCP Receiver**: set to **Enabled**
3. **Traces:** set to **Enabled**.
4. **Receiver Interface**: select or enter the RIG IP address.
5. **Receiver Port:** remains **5005**.
6. **Default Codec**: occasionally the codec cannot be determined within the RTCP feed. In that case, Nectar will default to this codec when calculating MOS. Please select the primary codec that your platform uses.
7. **Hop Name Lookup:** set to **Enabled**. This will use DNS to show layer-3 device names in trace routes, in addition to their IP addresses.
8. **Threshold Normalization:** this is optional (It is a step function for alert level. One packet with bad metrics will not trigger a critical alert level. It will require several packets in sequence and the alert level will gradually increase).
9. **Use PQOS RTCP Address:** leave as is—default.
10. **Configure Categories**: do not change—it is specific to Avaya’s Communications Manager.
11. Click **Apply** to start the **RTCP Receiver**.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-ca7zuzlt.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)RTCP Receiver

### Phone Alarms

You can monitor the status of individual stations. The Stations Traffic Light on the Dashboard, and the underlying Dependency Tree will represent these stations. By default, no stations will be included in Alarming.

Follow these steps to set up **Phone Alarms**:

1. Navigate to **Modules** > **Avaya** > **IP Office (prior to r10.1)**.
2. In the **Avaya IP Office (prior to r10.1) Setup** window, select the desired system to highlight it; then select **Phone Alarms**.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-d7pak5my.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Phone Alarms  
The **IP Office Phone Alarms** window will display all the extensions in the system.
3. Select the check boxes next to the station(s) that you want to monitor.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-l2jo5bh5.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Phone Alarms II
4. Click **Update** in the lower right-hand corner.

### Report Pack

The following reports are included in the IPO Report Pack, which are available on the Nectar Partner Hive:

##### IPO Resource Utilization (Monthly):

- Trunks
- Conference Bridge Channels
- VM Channels
- VCM Channels
- Data Channels
- Modem Channels

##### IPO VMPro Report (Monthly):

- CPU
- RAM
- Disk
- Etc.

##### Phone QoS Report-Expanded Summary (Weekly):

- Call Quality Metrics

NOTEThe Phone QoS Report only applies if you have deployed Real-Time Quality Monitoring.

Follow these steps to load an IPO Report Pack:

1. Download the **IPO Report Pack** from the **Nectar Partner Hive**.
2. Navigate to **Reports** > **Report Manager**.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-lg2gmfle.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Report Manager
3. To upload the IPO Report Pack, right-click in the **Reports** pane and select **Report Packs** > **Load Report Pack**.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-hgixhykw.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Report Manager - Load Report Pack  
The **Open** dialog window appears.
4. Locate and select the report pack from the location where it was saved (i.e., Documents folder, Desktop, etc.).
5. Click **Open**.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-0mmbpf6z.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Open Dialog Window  
The reports should appear in the **Report Manager** > **Reports** panel.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-i4v36dj0.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Reports

### Report Agent Selection

Follow these steps to associate each of the reports with their respective Nectar Agent.

1. Navigate to **Reports** > **Report Manager**.
2. Find and double-click the **IPO Resource Utilization Report (Monthly)** report to launch the **Edit Report** dialog window.  
The report name will display in the **Report Name** field.  
.
3. Select the **Components** tab.
4. Select **Rcp#-1 Group all Functions in Agent**.
5. Select the corresponding agent from the **Agent** drop-down list.  
In the example below (Figure Report Agent Selection), we selected agent **Nectar IPO Trunks.**
6. Click **Save**.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-qugveq86.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Report Agent Selection  
Follow the preceding steps to set the agent for the **IPO VMPro Report (Monthly)**.  
No changes need to be made to the **IPO Phone QoS-Expanded Summary (Weekly)** report.

### Report Schedule

Reports **will not** automatically execute, unless you assign a schedule to them: Follow these steps to assign a report schedule:

1. Navigate to **Reports** > **Report Manager**.
2. Select the **Schedules** tab.
3. Select a report to highlight it, then select **Edit** from the menu.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-83101okx.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Report Schedules
4. In the **Edit Report Schedule** dialog box, confirm or select **Monthly** as the interval for the **Repeat** parameter.
5. Click **OK**.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-szpmhagt.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Edit Report Schedule  
The **Frequency** status appears set to monthly.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-e5zp3dlm.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Schedule Frequency

#### Enable Report Schedule

To enable a report schedule(s):

1. Select a schedule to highlight it, then right-click and select **Enable**. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-j2b8cqo5.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Enable Report Schedule The report schedule should now read **Enabled** in the **Status** column. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-7tmxwxv7.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Enable Report Schedule II

#### Add Report to Schedule

To add a report to the list of schedules, proceed with the following steps:

1. Within the **Schedules** tab, right-click in a blank area of the screen, then select **Add...** from the pop-up menu.
2. In the **Add Report Schedule** dialog box (Figure 32), click the drop-down arrow next to **Report**.
3. Select the report you want to add (e.g., IPO Resource Utilization).
4. Click **OK**.  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-sxspretm.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Add Report Schedule  
The report should appear in the list of schedules.

## Verification

Your system is now being monitored by Nectar. This section contains examples of what you should see.

Follow these steps to verify your system is working properly:

- [**Dashboard**](/v1/docs/deployment-guide-avaya-ip-office#dashboard)
- [**Inventory**](/v1/docs/deployment-guide-avaya-ip-office#inventory)
- [**Real-Time Quality Monitoring**](/v1/docs/deployment-guide-avaya-ip-office#realtime-quality-monitoring)
- [**Conclusion**](/v1/docs/deployment-guide-avaya-ip-office#conclusion)

### Dashboard

The following Dashboard is automatically created for you.

1. Navigate to **Dashboards** > **Dashboard** (click **IP Office** tab in Dashboard panel if applicable).  
  
![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-yzfdn06g.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Dashboard

You will see statistics for:

**System Channels**

- Data Channel
- VCM Channel
- VM Channel
- Modem Channel
- Conference Channel
- **Trunk Channels** for each Trunk Group
- **VM Pro** Server Metrics
- VM Pro Service Active Traffic Light
- Disk Usage
- Total CPU Usage
- VM Process CPU Usage
- VM Process Memory Usage

You will see Traffic Lights for the following items. Double-click to see the corresponding Dependency Trees.

- **Connectivity**: Reflects Nectar connectivity to the IPO
- **Trunks**: Digital Trunk Alarms
- **System**: System Hardware Traps
- **License**: License Traps
- **Voice Mail**: The VM Pro metrics and service(s)
- **Stations**: Individual station alerts

### Inventory

Follow these steps to view inventory information:

1. Navigate to **Reports > Inventory** > **Avaya** > **IP Office (prior to r10.1)**.
2. In the **IP Office (prior to 10.1) Inventory** panel, select the system components you want to see.
  - **Inventory** - Full hardware inventory
  - **Extension Information**
  - **Trunk Summary Information**
  - **System Channels**
    - Conference Bridge Channels
    - Data Channels
    - Modem Channels
    - Voice Compression Module (VCM) Channels
    - Voice Mail (VM) Channels
  - Licenses

![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-cj6fqvam.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)IP Office Inventory

### Real-Time Quality Monitoring

Navigate to **Health** > **Quality Management** > **Real Time QoS.** **![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-1fl06kb3.png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Real-Time Quality Monitoring**

The **Real Time QoS** panel will appear showing all active calls. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/deployment-guide-avaya-ip-office-image-npbtydt5.jpe?sv=2026-02-06&spr=https&st=2026-11-08T16%3A36%3A23Z&se=2026-11-08T17%3A36%3A23Z&sr=c&sp=r&sig=gxYStGOQ4aezO24BtoWPwoA%2Fbrn46V1OP9ExxlwDcxM%3D)Real-Time QoS Panel

### Conclusion

Your IP Office system is now being monitored by Nectar.