--- title: "Perspective Administration and User Guide" slug: "perspective-administration-and-user-guide-2" updated: 2022-06-06T21:01:19Z published: 2022-06-06T21:01:19Z canonical: "support.nectarcorp.com/perspective-administration-and-user-guide-2" --- > ## 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. # Perspective Administration and User Guide ## Overview Nectar Perspective analyzes network performance delivering real-time traffic. Perspective generates synthetic Real-Time Protocol (RTP) traffic. Metrics are collected and reported to expose underlying network issues, either before or after deployment of a Unified Communications (UC) solution. Perspective is used to perform network assessments, or scheduled to run after hours, pro-actively monitoring network performance when no live traffic exists. Perspective may be deployed locally, reporting to a Client Remote Intelligence Gateway (RIG), while Perspective-as-a-Service (PaaS) uses a cloud-based Controller for Managed Services Providers (MSPs) to perform network assessments. For more information on architecture, see *Section 3* [***Architecture***](/docs/perspective-administration-and-user-guide-2#_bookmark16). ### About this Guide This guide provides the information required to administer the Perspective solution, including: ###### [Prerequisites - End User and Network](/docs/perspective-administration-and-user-guide-2#_bookmark10) ###### [Architecture](/docs/perspective-administration-and-user-guide-2#_bookmark16) ###### [Controller Deployment and Initial Configuration](/docs/perspective-administration-and-user-guide-2#_bookmark31) ###### [Agent Deployment and Registration](/docs/perspective-administration-and-user-guide-2#_bookmark50) ###### [Controller Configuration](/docs/perspective-administration-and-user-guide-2#_bookmark60) ###### [View Active Sessions](/docs/perspective-administration-and-user-guide-2#_bookmark69) ###### [Groups and Group Sessions](/docs/perspective-administration-and-user-guide-2#_bookmark76) ###### [Reports](/docs/perspective-administration-and-user-guide-2#_bookmark82) ###### [Troubleshooting](/docs/perspective-administration-and-user-guide-2#_bookmark92) ### Audience This guide is intended for system administrators or engineers who are responsible for the Perspective solution administration and configuration. Appropriate system administration access and technical knowledge of corporate standards for operating system and security practices along with a familiarity with the deployment of Nectar Unified Communications Management Platform (UCMP) and related components are recommended. A subset of information is intended for service providers, technical resources, and operations in the use of Perspective for voice quality reporting, proactive problem identification, and network pre-assessment deployments. ***** MS 0365**Nectar-certified partners are authorized to use **Perspective for Microsoft O365** readiness assessments. Throughout this document, you will see call out boxes, like this one, to indicate a function, setting or requirement that is specific to O365 testing. ***** MS O365** A special Nectar Analytics license is required to unlock MS O365 reporting. Again, only Nectar-certified partners are authorized to use Perspective for Microsoft O365 readiness assessments. ### Supported Software Versions - - - Perspective Controller v8.1 - Perspective Agents v8.0 ### Operating System The Perspective Controller is supported on the following operating system: | **Platform** | **Version** | | --- | --- | | **Microsoft Windows** | - Windows Server 2012 R2 - Supports English only | | **Linux** | - CentOS 6.x/7.x - RHEL 6.x/7.x - Supports English only | *Table 1-1 Operating System* The Perspective Agents are supported on the following operating systems: | **Platform** | **Version** | | --- | --- | | **Microsoft Windows** | - Windows 7 and Windows 10 - Windows Server 2012 R2 - Supports English only | | **Linux** | - CentOS 6.x/7.x - Supports English only | *Table 1-2 Operating System* ### ## Prerequisites - End User and Network This section provides the prerequisites for: ###### [Users](/docs/perspective-administration-and-user-guide-2#_bookmark11) ###### [Network - Ports and Protocols](/docs/perspective-administration-and-user-guide-2#_bookmark12) ###### [Network - Firewall](/docs/perspective-administration-and-user-guide-2#_bookmark13) ###### [Linux Line Editor](/docs/perspective-administration-and-user-guide-2#_bookmark14) ###### [Linux Line Editor](/docs/perspective-administration-and-user-guide-2#_bookmark14) ### Users Users involved in deploying the Nectar Perspective application should be familiar with Nectar UCMP and participated in Nectar training. ### Network - Ports and Protocols The Nectar components (Perspective Controller, Perspective Agents) use various ports and protocols to communicate with each other. These are defined in *Section 3* [***Architecture***](/docs/perspective-administration-and-user-guide-2#_bookmark16). Users need to be familiar with network communication, ports and protocols. ### Network - Firewall Users must understand Firewall rules in order to accommodate the ports and protocols mentioned above. It is recommended that the Client Network Team is involved during deployment to ensure communication between devices. ### Linux Line Editor It is possible, though unlikely, that knowledge of Linux and its line editor are necessary. ## Architecture This section describes the following: ###### [Components](/docs/perspective-administration-and-user-guide-2#_bookmark17) ###### [Example Deployment](/docs/perspective-administration-and-user-guide-2#_bookmark22) ###### [Ports and Protocols](/docs/perspective-administration-and-user-guide-2#_bookmark28) ### Components This section describes the following Perspective components: ###### [Perspective Controller](/docs/perspective-administration-and-user-guide-2#_bookmark18) ###### [Perspective Agents](/docs/perspective-administration-and-user-guide-2#_bookmark19) ###### [Sessions](/docs/perspective-administration-and-user-guide-2#_bookmark20) ###### [Reports](/docs/perspective-administration-and-user-guide-2#_bookmark21) #### Perspective Controller - - - - A Perspective Controller provides the User Interface (UI) wherein you configure the test(s) you wish to run. The Controller instructs the Agents and collects RTCP feedback from the Agents. - A Controller may be local, within a Client environment, or in the cloud (PaaS). When deployed locally, the RIG functions as the Controller. #### Perspective Agents - - - - Perspective Agents generate RTP Sessions between each other and send their RTCP feedback to the Controller. - Agents connect to a Controller in order to receive their configuration/instructions. - Sending RTCP feedback to the Controller can be configured to use UDP packets or the Agent/Controller configuration connection. - Agents are deployed in various locations and subnets within a Client environment. Placement should be planned to mirror call flows of the UC platform. - Agents can be software or a hardware appliance. Nectar offers a pre-loaded, pre-configured hardware appliance based on the Intel NUC via the Nectar Appliance Program. You can find more information about the Appliance Program and ordering details on the Nectar Partner Portal. - - - - Refer to the Nectar Appliance Sizing Guide for the NUC Agent session capacity. - Agents may be deployed as Software on Client devices. These may be: Windows 7 or above, CentOS Linux 6, physical or virtual. #### Sessions A Session is a RTP communication stream(s) between two Agents. It consists of a codec (such as g.729, g.711, etc.), schedule (such as 24x7, 6pm-8am), DSCP priority tag, and a quantity. For example, you may wish to test a g.729 call between a branch and the Data Center, while you might test a g.711 call between two Agents within a branch. Codec selection, call flows and DSCP should mirror the UC platform. For instance, if all communication flows through the Data Center, then you would not configure Sessions directly between branches. The table below lists the set of codecs that are currently supported. | **Codec** | **Controller** | **Agent** | | --- | --- | --- | | G.722 | 8.1 | 8.0 | | G.729 | 8.1 | 8.0 | | G.711 | 8.1 | 8.0 | | G.726 32k and 40k | 8.1 | 8.0 | | G.723.1A | 8.1 | 8.0 | | H.264 128k, 384k, 512k, 1m and 2m | 8.3 | 8.3 | *Table 3-1 Codecs Supported* ***** MS O365**When testing for MS O365 and Skype for Business, use **g.722**. This most closely aligns to the MS RT-audio codec. ***Note*** *Nectar now supports H.264 video codec* #### Reports - - - - Reports are used to evaluate test results and determine how well the network is delivering real-time, priority traffic. - Reports may be generated by a Controller (RIG), or via Nectar's Analytics Reporting Engine. In either case, you load the respective Nectar Perspective Report Pack that includes the pre-defined Reports. - Report Packs can be found on the Nectar Partner Portal. ### Example Deployment The following [***Figure 3-1***](/docs/perspective-administration-and-user-guide-2#_bookmark23) shows a sample environment. The goal is to isolate network performance issues. To that end, segment the network into call legs. At all times, mirror the call flows of the UC platform (codec, DSCP, do calls route directly between branches?). ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-r9sdlr8j.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 3-1Sample Environment* Based on the diagram, it is recommended to test the following segments: - - - Data Center Core ↔ WAN Access Are there issues within the Data Center? - - - Data Center Core ↔ Internet Access While we cannot affect performance issues on the Internet, we need to monitor remote user performance from the ingress point of the Data Center (VPN concentrator, etc.). If the internal talk path is clean, then the Internet would be the likely cause of the communication issues. - - - Data Center WAN ↔ Branch Edge Isolate and evaluate WAN performance. - Segment the Larger Branch If a Branch is large enough to have multiple subnets, you may deploy multiple Agents to test each network segment. - - - Branch ↔ Branch Only if direct Branch communication is configured. As it is optional, this will be red in the following diagram. The Agents will be placed, and Sessions configured as shown in [***Figure 3-2***](/docs/perspective-administration-and-user-guide-2#_bookmark24): ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-da9h5lq5.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 3-2Configuration* ***** MS O365**The following diagrams describe testing for a MS O365 deployment. Three segments will be tested: - Client Edge **↔** Azure Edge (see [***Figure 3-4***](/docs/perspective-administration-and-user-guide-2#_bookmark25)) - Client LAN **↔** Azure Edge (see [***Figure 3-5***](/docs/perspective-administration-and-user-guide-2#_bookmark26)) If a Branch is large enough to have multiple subnets, you may deploy multiple Agents to test each network segment. - Client LAN **↔** Client Edge (see [***Figure 3-6***](/docs/perspective-administration-and-user-guide-2#_bookmark27)) ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-qzbdax6e.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 3-3Typical Environment* ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-q181337y.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 3-4MS O365 - Client Edge to Azure Edge* ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-vbkyidc4.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 3-5MS O365 - Client LAN to Azure Edge* ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-78lvct5c.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 3-6MS O365 - Client LAN to Client Edge* ### Ports and Protocols The following excerpts are specific to Perspective. ##### Perspective Controller, also known as Nectar Foundation Server/RIG | **Destination** | **Nectar Foundation to Destination** | **Destination to Nectar Foundation** | **Notes** | | --- | --- | --- | --- | | CIP | TCP:443 | | | | NTP Server | UCDP:123 | | Internal or external | | SMTP | TCP:25 | | | | DNS | UDP:53 | | | | Active Directory/LDAP | TCP:389/636 | | External Authentication | | User PC | UDP:69 | TCP:80/443 | Only applies to Client | | UDP:69 | deployments, not PaaS | | Perspective Agents | | TCP:443 | UDP:5005 is not needed if | | | UDP:5005 | the report PQOS RTCP via agent is enabled. See | | | | table 4-4 | *Table 3-2 Perspective Controller* ##### Perspective Agent | **Destination** | **Nectar Foundation to Destination** | **Destination to Nectar Foundation** | **Notes** | | --- | --- | --- | --- | | Perspective Agents (PA) | UDP:6000 - 7000 | UDP:6000 - 7000 | Default setting; configurable | | NTP Server | UDP:123 | | | | DNS | UDP:53 | | | *Table 3-3 Perspective Agent* ##### Nectar Analytics Reporting | **Destination** | **Analytics to Destination** | **Destination to Analytics** | **Notes** | | --- | --- | --- | --- | | User PC | | TCP:80/443 | | | UCD-F | TCP-1527 | | | *Table 3-4 Analytics Reporting* ***Note*** *For more information, see the* ***Ports and Protocols Job Aid*** *on the Partner Portal.* ## Controller Deployment and Initial Configuration This section describes the following: ###### [Ports and Protocols](/docs/perspective-administration-and-user-guide-2#_bookmark32) ###### [Controller (RIG/Nectar Foundation) Installation and Licensing](/docs/perspective-administration-and-user-guide-2#_bookmark33) ###### [Network Mode/Externalize Database (DB) (Optional)](/docs/perspective-administration-and-user-guide-2#_bookmark34) ###### [Detail Table Setting (Optional)](/docs/perspective-administration-and-user-guide-2#_bookmark38) ###### [Controller Module Verification](/docs/perspective-administration-and-user-guide-2#_bookmark39) ###### [Configure Controller](/docs/perspective-administration-and-user-guide-2#_bookmark41) ### Ports and Protocols Confirm with the Client that the necessary Ports/Protocols are open between the various components, as defined in *Section 3.3* [***Ports and Protocols***](/docs/perspective-administration-and-user-guide-2#_bookmark29). ### Controller (RIG/Nectar Foundation) Installation and Licensing Deploying a Perspective Controller is identical to deploying a Nectar Foundation Server (also known as a RIG). Perspective Controller is another function the Nectar Foundation server performs. For instructions regarding installation and licensing of a Nectar Foundation server, see ***Nectar Foundation RIG/EIP Install Guide***. ***Note*** *Prior to deploying your Controller, see the following sections:* - [***Network Mode/Externalize Database (DB) (Optional)***](/docs/perspective-administration-and-user-guide-2#_bookmark34) - [***Detail Table Setting (Optional)***](/docs/perspective-administration-and-user-guide-2#_bookmark38) ### Network Mode/Externalize Database (DB) (Optional) ***Note*** *This step is only necessary if you are using the Nectar Reporting and Analytics solution.* ***** MS O365**MS O365 testing requires Nectar Reporting and Analytics. The dB must be externalized. By default, the Nectar monitoring database is configured in **Embedded** mode, which means only the RIG service can access it. In order for Nectar's Analytics Reporting Server to access the database, it must be in **Network** mode. You can change an existing installation from **Embedded** to **Network**. However, once in **Network** mode, you cannot modify back to **Embedded**. This section discusses **Network** and **Embedded** mode for each of the following: ###### [New Installation](/docs/perspective-administration-and-user-guide-2#_bookmark35) ###### [Upgrade](/docs/perspective-administration-and-user-guide-2#_bookmark36) ###### [Update/Change](/docs/perspective-administration-and-user-guide-2#_bookmark37) #### New Installation During a new installation, the database mode is selectable. It defaults to **Embedded** mode. If you plan to use Nectar Analytics for reporting, select **Network** mode when deploying a Perspective Controller. #### Upgrade During an upgrade, the installer analyzes the existing installation. If it finds that the database is in **Network** mode, there will be no prompting for the database mode. If the database is currently in **Embedded** mode, you will be prompted for the database mode, giving you the option to change it to **Network**, if you plan to use Nectar Analytics for reporting. #### Update/Change If you have already installed the Perspective Controller and need to change it from **Embedded** to **Network** mode, simply re-run the Nectar installer and select **Target an existing installation**. This is functionally the same as an upgrade. However, the version remains the same. Aside from enabling you to change the database mode, this will not affect the current installation or existing data. ***Note*** *Once in* ***Network*** *mode, it is not possible to revert to* ***Embedded*** *mode.* ### Detail Table Setting (Optional) ***Note*** *This step is only necessary if you are using the Nectar Analytics Reporting Solution.* ***Important After upgrading to v8.3****, if you have or plan to manipulate a properties file that uses a file path or directory, then you must verify that you are using the proper backslash (****\****) or forward slash (****/****):* - ***Windows****:* *Use double backslash (****\\****), for example,* ***:\\******\\*** ***or*** *Use single forward slash (****/****), for example,* ***:/******/*** - ***Linux/iOS****:* *Use single forward slash (****/****), for example,* ***/******/*** Follow these steps to edit the **avayaPhone-module.properties** file on the Controller. The file’s default location is **C:Apps/nectar/etc**. 1. Select one of the following - Remote desktop (RDC) to the RIG and edit locally. This only applies to a Controller running on Windows. - Use Nectar's File Manager to download the file to your machine. Edit the file offline; then upload it back to the RIG. - Add the following two lines, exactly as shown, to the end of this file: ###### createDetailTablesEveryHours=4 createDetailTablesThreads=2 1. Restart the RIG for this change to take effect. Navigate to **RIG > Server License**; then click ###### Restart. ### Controller Module Verification Once the Nectar software has been deployed to the Controller, confirm the necessary Modules are active. 1. Navigate to **RIG > Module Configuration** and ensure that the following Modules are checked. - Perspective QoS Configuration/Display - Real-Time Phone QoS Collector - EIP/Perspective Controller (Mother) ***Note*** *Perspective QoS Transponder should not be checked. A Controller cannot be a Transponder (Agent).* 1. If any of the required Modules above are not checked, check them and click **Apply**. 2. Restart the RIG for the changes to take effect. Navigate to **RIG > Server License**; then click **Restart**. After the server is back online, navigate to **RIG > Module Configuration** to confirm the modules from [***Step 1***](/docs/perspective-administration-and-user-guide-2#_bookmark40) are active. 1. Navigate to **Configure > Distributed**. This is where you will see your Agent registration status. At this point, we do not expect any Agents to be registered. We are confirming that the menu option is available. ***Note*** *If this option is not available in the* ***Configure*** *menu, contact Nectar Support to repair your license.* ### Configure Controller This section configures the Controller using the following: ###### [Create Login for Agent Registration](/docs/perspective-administration-and-user-guide-2#_bookmark42) ###### [Configure Real-Time QoS (RTQ)](/docs/perspective-administration-and-user-guide-2#_bookmark45) - - - [***Select* Apply*.***](/docs/perspective-administration-and-user-guide-2#_bookmark46) #### Create Login for Agent Registration You must create a login for the Agent on the Controller (RIG). The suggested credentials are: - - - - **Username:** paSatellite - **Password**: paSatellite ***Note*** ***paSatellite*** *is the default* ***Username*** *and* ***Password*** *an Agent uses. It is recommended that you use* ***paSatellite****. If you wish to use something different, you must modify the credentials on each Agent.* ***Note*** *The user has no rights or privileges. It is used strictly to authenticate the Agents.* Follow these steps to add a user, **paSatellite** (see [***Figure 4-7***](/docs/perspective-administration-and-user-guide-2#_bookmark44)): 1. Navigate to **RIG > Permissions**. The **Permissions - Users** window appears. 2. Click **Add.** The **Add User** dialog window appears. 3. **Username:** Enter ***paSatellite.*** 4. **Password:** Enter ***paSatellite***. 5. **Confirm:** Enter password again. 6. **Organization:** Do not change; leave **root** as default. 7. **Default Dashboard:** Select **default**. 8. Click **OK**. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-d3fndv08.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 4-7Add Permissions Window* #### Configure Real-Time QoS (RTQ) Follow these steps to configure the RTQ module: 1. Navigate to **Configure > Quality Management > Real Time QoS**. The **Real Time QoS** window appears. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-2hf3dq08.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 4-8Real Time QoS* 1. Configure Real-Time QoS using the following data: | **Parameter** | **Description** | | --- | --- | | RTCP Receiver | - Select **Enabled** from the drop-down list and have the Controller listen for RTCP packets. | | Traces | - Select **Enabled** from the drop-down list to enable the Dynamic Trace View with Real-Time QoS. - **Traces** button, located in upper left area of **RTQ** window. | | Receiver Interface | - Identifies the IP address of your RIG. | | Receiver Port | - Should not be changed. - Default is **5005**. | | Default Codec | - Defines which codec is used to calculate MOS when RTP stream is encrypted and codec type is not visible. - Applies to Avaya Communication Manager and has no effect on Perspective (codec is always known). | | Hop Name Lookup | - **Enabled** - Enables use of DNS to translate IP addresses into host names. - Applies to hops in the traceroute. | | Threshold Normalization | - **Disabled**. - Applies to Avaya Communication Manager and should not be enabled for Perspective. | | Use PQoS RTCP Remote Address | - Only applies if a Perspective Agent uses NAT: - **Enable** - to display the NAT (public) address in the **Real- Time Quality** window. - **Disable** - to display the private address. | | Report PQOS RTCP via Agent | - Select **Enabled** if the Agent/Controller configuration connection should be used for RTCP feedback. - Controller and all agents must be on Foundation 8.3 release. - If **Enabled, RTCP Receiver** can be **Disabled** if receiver is not needed. | | Configure Categories (button) | - Do not change. | *Table 4-5 Real-Time QoS* ***Note*** *There is no need to use* ***Configure > Quality Management > Perspective QoS*** *yet.* 1. Select **Apply**. #### Create a Schedule You must create a schedule for sessions to follow. For a Network Assessment, you will likely want a 24x7 schedule. If Perspective is being used to monitor the network after hours, you could create a schedule from 6 pm to 8 am. ***Note*** *At least one schedule is required. If no schedule is assigned, any sessions will not auto-start, nor will they restart if there is a network outage.* Follow these steps to create a 24x7 schedule (see [***Figure 4-9***](/docs/perspective-administration-and-user-guide-2#_bookmark47)): 1. Navigate to **Configure > Quality Delivery > Service Window**. The **Service Window** appears. 2. Click **Add**. The **Add Schedule** dialog window appears. 1. Enter your **Schedule Name**; then click **OK**. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-llfzobz7.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 4-9Add Schedule* The new schedule appears in the **Schedules** pane; the schedule **Status** defaults to **Off**. 1. Select the new schedule (see [***Figure 4-10***](/docs/perspective-administration-and-user-guide-2#_bookmark48)). 2. Click **Add** in the **Windows** pane. The **Add Window** appears. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-2pjfp3sr.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 4-10Add Recurring Schedule* 1. Complete the following: 1. For **Type**, use **Recurring**, which is the default value. 2. For **Days of the Week**, select **Sunday**, **Monday**, **Tuesday**, **Wednesday**, **Thursday**, **Friday**, and **Saturday**. 3. For **Begin Time**, click the down arrow to select the start time for the schedule in the **Hour** field. You can also use **12 am**, which is the default value. - 1. For **Duration**, click the up arrow to enter **24** in the **Hours** field; leave **0** for **Minutes**. 5. Click **OK**. When the new **Service Window** is created, the **Service Window** status is automatically set to **On**, reflecting the 24x7 schedule that was created. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-abkts93d.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 4-11Status Set to On* ## Agent Deployment and Registration This section describes the following: ###### [Configure Domain Name System (DNS)](/docs/perspective-administration-and-user-guide-2#_bookmark51) ###### [Nectar Appliance Agent](/docs/perspective-administration-and-user-guide-2#_bookmark53) ###### [Software Agent/CPE Hardware](/docs/perspective-administration-and-user-guide-2#_bookmark54) ###### [Registration Confirmation](/docs/perspective-administration-and-user-guide-2#_bookmark55) ### Configure Domain Name System (DNS) The recommended method to streamline Agent deployment and configuration is to use the Domain Name System (DNS) to define the Perspective Controller IP address. This simplifies and accelerates deployment by minimizing the necessary amount of staging and configuration. With DNS configured, an Agent connected to the network automatically registers with the Controller, which can be accomplished by creating a Perspective Controller “A” record. ***Note*** *You can skip the following step if you have configured your Agents to register to an fully qualified domain name (FQDN) or a specific IP address, as opposed to the default* ***perspectivecontroller****.* ***** MS O365**Partners conducting tests for O365 will have a centralized Perspective Controller in the cloud. In this case, you should have the Agents configured with the FQDN, or IP address of your cloud-based Controller. For more information, see *Section 5.2* [***Nectar Appliance Agent***](/docs/perspective-administration-and-user-guide-2#_bookmark53). #### Identify Perspective Controller IP Address Follow these steps to identify the Perspective Controller IP address: - - - 1. From the Perspective Controller, navigate to **RIG > Admin > Maritime Terminal**. 2. Enter **tools myip** to view the IP address of the RIG. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-5llnx786.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 5-1IP Address* #### Configure DHCP Option Ensure that **Option 15 - DNS Domain Name** is configured on the Dynamic Host Configuration Protocol (DHCP) Server, or that the base domain/zone is listed in the **DNS Suffix Search** list. #### Create a DNS Entry Follow these steps to create a DNS entry for **perspectivecontroller** using the IP address identified in *Section 5.1.1* [***Identify Perspective Controller IP Address***](/docs/perspective-administration-and-user-guide-2#_bookmark52). - - - 1. From the **DNS Administration Tool**, right-click on the domain/zone being delivered by DHCP Option 15. In ***Figure 5-2***, it is **nectarco.net**. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-8j2vf0iy.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 5-2Example* - - - 1. Select **New Host (A or AAAA)…** The **New Host** window appears. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-4z6zlpoe.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 5-3New Host* - - - 1. Enter **perspectivcontroller** in the **Name** field. 2. Enter the Controller **IP address**. 3. If you are providing Reverse Lookup, click **Create associated pointer (PTR) record**. 4. Click **Add Host**. #### Verify DNS Resolution Once DNS Replication has completed, you can verify using a command prompt on any network device (connected to this Client network). From the command prompt, enter: ###### ping perspectivecontroller - If the ping is successful, DNS is complete. - If the ping does not resolve and repeatedly fails, review the above steps for accuracy. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-1tvr8lhr.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 5-4Ping* ### Nectar Appliance Agent Agents (NUCs) acquired from the Nectar Appliance Program are pre-loaded with the Nectar software and configured to register to **perspectiveController**, leveraging DNS/DHCP, as described in *Section 5.1* [***Configure Domain Name System (DNS)***](/docs/perspective-administration-and-user-guide-2#_bookmark51). Optionally, when ordering the Agent appliance, you may specify an FQDN or IP address for the Controller. If you are deploying these Agents as part of PaaS, the FQDN of your cloud-based Controller is recommended. ***** MS O365**Partners conducting tests for O365 will have a centralized Perspective Controller in the cloud. In this case, you should have the Agents configured with the FQDN, or IP address of your cloud-based Controller. Additional Agent defaults include: - **Customer** - Nectar Customer - **Site** - Nectar Customer Site - **Server Name** - MAC address plus a 10-digit number ***Note*** *You can assign a friendly name to the server later* When delivering Appliance Agents to a Client, note the end (last 6 digits) of the MAC address (which appears on the box). This identifies which Agent is where. In addition, if you set Customer and Site above, those fields are visible on the Controller (**Configure > Distributed**) to identify the Agents. ### Software Agent/CPE Hardware If you plan to deploy the PA as software on a Client device, or provide your own hardware, see ***Nectar Foundation RIG/EIP Install Guide***, available on the Nectar Partner Hive. You need to download the Nectar software to the machine and execute the automated installer. ### Registration Confirmation Once connected to the Client network, the Agents should automatically register to the Controller. This can be verified on the Controller by navigating to **Configure > Perspective Agent Control**. Satellites refer to units registered to this Controller. You should see two connections per Agent. If you do not see all of the deployed Agents, confirm the following: - Port 443 is open from the Agent to the Controller. - You created the **paSatellite** user and password in *Section 4.6.1* [***Create Login for Agent***](/docs/perspective-administration-and-user-guide-2#_bookmark43) [***Registration***](/docs/perspective-administration-and-user-guide-2#_bookmark43). ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-ye64fcu5.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 5-5Satellites* #### Agent Nickname ***** MS O365**If you are using Nectar Appliance Agents, it is likely they will be redeployed at another client in the future. Therefore, it is best to give them a more generic name for reference. This nickname is used to identify the unit in the future. It does not show up in reports. Agents will be given a client-specific name later that is used in reporting. Setting a nickname for the PA speeds identification in the future, if you do not want to use the MAC address. The nickname is sticky, which is helpful if this PA is for PaaS and will travel to different clients in the future. - - - 1. Navigate to **Configure > Distributed**. 2. Select an Agent. 3. Right-click on the Agent Name and select **Edit**. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-ayd23dwd.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 5-6 Edit Satellite* It is recommended to do the same for the backup connection (e.g., Agent 123-backup). Should the primary connection be unavailable (e.g., power outage during an upgrade), it identifies your backup access. After setting the nicknames, you should see something similar to the following: ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-7t9rhcfd.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 5-7Agent Nickname* ### Agent Remote Access Remote access to an Agent, via the Nectar GUI, is helpful in the following instances: - Upgrading the Agent software - Testing port connectivity between Agents #### Add Agent to Management Folder To remotely access an Agent from the GUI, first assign it to a **Satellite Folder**, also known as a ###### Management Folder. Follow these steps to add an agent to a Management Group: - - - 1. Navigate to **Configure > Distributed**. 2. Right-click in the upper left pane and select **Add > Folder**. The **Add Folder** dialog appears. 3. Enter a name for the Folder; then click **OK**. In this example, we will use **Perspective Agents**. You may wish to use a Client name to segment your Agents based on the Client engagement. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-w86e8hcm.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 5-8Add Folder Navigation* - - - 1. Select the new Management Folder name in the upper left window. 2. Select an Agent from the **Satellites** window. 3. Right-click in the top, middle pane and select **Add > Element**. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-ee6yp8zu.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 5-9Add Element Navigation* The **Add Element** dialog window appears. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-18s9bxsn.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 5-10Add Agent to the Group* - - - - - The Agent you highlighted will already be selected in the **Add Element** window. - Notice the Host or Server name is shown in the **Add Element** window. Do not change the name here. The Nickname you assigned will be visible when you wish to connect. - Click **OK** to add the Agent to the Group. - Repeat this process to add all of the Agents to a Management Group. ***Note*** *Deleting an existing Satellite/Management Group has no effect on the underlying Agents.* #### Remotely Connect to a Satellite/Agent Follow these steps to remotely connect to a Satellite/Agent: - - - 1. Navigate to **Tools > Satellites**. 2. Select the Management Group in the **Satellites** window (e.g. **Perspective Agents**). The Agents will populate in the middle column. 3. Double-click an Agent to connect to the Agent remotely and securely. Once connected, any menu actions will affect the Agent, not the Controller. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-x2qazwru.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 5-11Agent Selection* Your connection is indicated in the **Satellite** title bar, as shown below. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-3kouy27k.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 5-12Connection to Satellite* ***Note*** *You have two options to disconnect from this Satellite and return to the Controller.* - *Click the* ***X*** *at the right side of the* ***Satellite*** *title bar.* - *Click the word* ***Satellites*** *in the navigation link above the Satellite Title bar. These are illustrated in the following* [***Figure 5-13***](/docs/perspective-administration-and-user-guide-2#_bookmark57)*.* ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-mqgaxuxy.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 5-13Disconnect from Satellite* ### Simultaneous Session Limit Agents default to a maximum of 50 simultaneous Sessions. To change this limit, remotely connect to the Agent as described above. Follow these steps to edit the **rtppassive-module.properties** file on the agent. The file's default location is **C:Apps/nectar/etc** (Windows) or **/opt/rig/etc** (Linux). 1. Select one of the following: - Remote desktop (RDC) to the RIG and edit locally. This only applies to Agents running on Windows. - Use Nectar's File Manager to download the file to your machine. Edit the file offline; then upload it back to the RIG. 2. Restart the Agent for this change to take effect. To do this, stop and restart the Nectar service on the Agent. 3. You must switch to the Backup Connection. If you stop the service from the primary connection, you will be disconnected from the Agent and will not be able to restart the service. 4. Click on the **Backup** link (the release number of the Backup connection), as shown below. ##### Linux 1. Navigate to **Backup RIG >Admin > Command Line**. 2. Enter **stop NectarRIG**. 3. Enter **start NectarRIG**. ##### Windows 1. Navigate to **Backup RIG >Admin > Command Line**. 2. Enter **net stopservice NectarRIG**. 3. Enter **net startservice NectarRIG**. Alternatively, you can do this via Remote Desktop (Windows only). 1. Remote desktop to the machine by navigating to **RIG > Admin > Remote Desktop**. 2. Open **Services** from the **Control Panel/Administrative Tools**. 3. Restart the NectarRIG Service. ## Controller Configuration This section explains how to configure the Controller using: ###### [Test ID](/docs/perspective-administration-and-user-guide-2#_bookmark61) ###### [Perspective Agent Setup](/docs/perspective-administration-and-user-guide-2#_bookmark63) ###### [Bulk Add Agents](/docs/perspective-administration-and-user-guide-2#_bookmark65) ###### [Sessions](/docs/perspective-administration-and-user-guide-2#_bookmark66) ### Test ID The Test ID is used in PaaS to separate test results from different Clients. If this Perspective deployment is part of your PaaS practice, reporting to your cloud-based Controller, then create a new TestID, using the **Client** or an engagement name (see [***Figure 6-2***](/docs/perspective-administration-and-user-guide-2#_bookmark62)) If this is a local deployment for a Client, reporting to their RIG, **PerspectiveDefault** is sufficient, though you have the option of creating a Test ID here as well. Each configured Test ID has an associated Real Time QOS threshold Category. A default set of threshold values are created automatically. This default thresholds can be modified as well as making the thresholds specific to audio or video codecs. See the Nectar Foundation RIG Administration Guide for more information. Follow these steps to configure the Controller: - - 1. Navigate to **Configure > Quality Management > Perspective QoS**. The **Configure Perspective QoS** window appears; **TestIDs** is the first tab. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-vzys3lb2.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 6-1Configure > Quality Management > Perspective QoS* - - 1. Right-click in the **Test ID** area and select **Add**. The **Add Test ID** window appears. - - 1. Enter the **Test ID Name**; then click **OK**. ***Note*** *No spaces are allowed in the* ***TestID Name****.* ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-hd2rhxe9.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 6-2Add Test ID* ### Perspective Agent Setup ***** MS O365**This is where you give the Agent a specific name that is used in reporting. It is recommended that you append Edge or LAN to an Agent to specify its location in the Client network. This is then leveraged in reporting. Microsoft specifies different performance thresholds for Client Edge to Azure Edge versus Client LAN to Azure Edge. A proper naming convention will prevent any misinterpretation of data when reporting. Follow these steps to set up a PA: - - 1. Navigate to **Configure > Quality Management > Perspective QoS**. 2. Right-click in the pane below and select **Add**. The **Add Perspective Agent** window appears. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-gevhew6g.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 6-3Add Perspective Agent* ***Note*** *The terms,* ***Transponder*** *and* ***Agent*** *are used interchangeably.* - - 1. Enter the following data; then click **OK**: | **Parameter** | **Description** | | --- | --- | | Test ID | - Select the TestID using the drop-down. - If this is a local test, not PaaS, then **PerspectiveDefault** is sufficient. | | Agent Description | - Enter a name for the Agent. - This description is what you will see when creating Sessions, viewing active Sessions, and Reporting. | | Agent Host Name | - Select the specific agent using the drop-down. - The Host Name will be based on the MAC address, as shown in the following view. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-xi2442i1.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) | | IP Interface | - Press the **...** button to select the IP interface of that Agent. | | Port Range Start/Stop | - Default range for Perspective RTP traffic is **UDP:6000-7000**. - These UDP ports need to be open between communicating Agents. - If you change this value, you must ensure that the new port range is open between communicating Agents. | | DNS Name/NAT IP | - If the PA is behind a Firewall or other device that NATs its IP address, you need to use one of these fields to identify the NAT IP address. This is the external IP address, not the one assigned to the PA (above). - Either of these two fields suffice; you do not need both. ***Note:*** *If the NAT IP may change over time, it is recommended that you use DNS.* | | SNMP Community | - Optional; SNMP is not normally used with Agents. - Used for troubleshooting. - By default, SNMP is not installed on an Agent. If needed, install SNMP with the yum command. | *Table 6-1 Add Transponder* - - 1. When complete, view your Agents as shown below in [***Figure 6-4***](/docs/perspective-administration-and-user-guide-2#_bookmark64). ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-fghcoaju.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 6-4Agents* ### Bulk Add Agents The **Bulk Add** command lets you add multiple Agents in a single step. If you use this command, the Agent Description will be the host name (MAC address, plus a 10-digit number). You then edit each individual Agent to assign a name. The system will discover and add all Agents currently registered to the Controller that have not yet been added in the **Agents** tab. Follow these steps to add multiple agents to a Perspective Controller: - - 1. Navigate to **Configure > Quality Management > Perspective QoS**. 2. Click the **Agents** tab. 3. In the **Agents** area, right-click and select **Bulk Add**. The **Bulk Add** dialog window appears. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-c0yakfdi.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 6-5Bulk Add* - - 1. Complete the following fields: | **Parameter** | **Enter/Select ...** | | --- | --- | | **Test ID** | - Select the TestID using the drop-down. - If this is a local test, not PaaS, then **PerspectiveDefault** is sufficient. | | **Configure Community String** | - Check box to enable/configure the community string. ***Note:*** *SNMP is optional and not normally used with Agents. It is used for troubleshooting. By default, SNMP is not installed on an Agent. If needed, install SNMP with the yum command.* *If you wish to configure SNMP, complete the following parameters.* | | **SNMP Version** | - SNMP version from the following: - **V1** - **V2** - **V3** | | **Port** | - SNMP port, such as ***161***. | | **Community** | - Community string. ***Note:*** *Do not include a space in the* ***Community String*** *name.* | | **Authentication** | - Authentication from one of the following (SMNP version **V3** only): - **None** - **MD5** - **SHA** | | **User ID** | - User ID previously set up for the SNMP community string (SMNP version **V3** only). | | **Password** | - Password previously set up for the SNMP community string (SMNP version **V3** only). | | **Privacy Protocol** | - Protocol from one of the following: - **None** - **DES** - **AES** **- AES-192** **- AES-256** ***Note:*** *Enabled for SNMP V3 only.* | | **Privacy Password** | - Password for the Privacy Protocol. ***Note:*** *Enabled for SNMP V3 only.* | - - 1. Click **OK**. *Table 6-2 Bulk Add SNMP Settings* - 1. **Sessions** This section describes the following: ###### [Add a Session](/docs/perspective-administration-and-user-guide-2#_bookmark67) #### Add a Session ***** MS O365**For clarity in reporting, it is suggested that you name Sessions to indicate whether they are from a Client Edge, or LAN. For instance, New York Edge to Azure Edge. This will prevent any misinterpretation of data when reporting. When testing for MS O365 and Skype for Business, use **g.722**. This most closely aligns to the MS RT-Audio codec. Follow these steps to add a RTP session. - - - 1. Click the **Sessions** tab. 2. Right-click in the **Sessions** area and select **Add**. The **Add RTP Session** window appears. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-0vgmpjbw.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 6-6Add RTP Session* - - - 1. Enter the following data: | **Parameter** | **Description** | | --- | --- | | Test ID | - Select the identifier that you have assigned to the Agents. ***Note:*** *Sessions cannot be created between Agents with different TestIDs.* | | Grouping | - Leave **Grouping** set to **No**. - For more information on Group Sessions, see *Section 8* [***Groups and Group Sessions***](/docs/perspective-administration-and-user-guide-2#_bookmark76). This section relates to creating Sessions between two specific Agents. | | Description | - Enter a description of the Session(s), such as **Data Center to New York**. | | Agent 1/Agent 2 | | Agent | - Select each Agent using the drop-down. | | IP Interface | - This field auto-populates. - If it does not or if your device has multiple interfaces, press **...** to select the IP interface. | | Port Range Start/Stop | - Defaults to **6000 - 7000**. ***Note:*** *These UDP ports need to be open between the two Agents.* | | Schedule | - Select the schedule of when the Session(s) will run using the drop-down. ***Note:*** *You must assign a schedule. If a schedule is not assigned, then it is possible that a session(s) may not restart if/ when an outage or reboot occurs.* | | Codec | - Select the codec using the drop-down. | | Frequency/Packet Size | - These fields are populated based on codec and are informational. - They cannot be modified. | | DiffServ (DSCP) | - Assign a DiffServ Code Point (priority tag) for these packets. - This should match what is configured in the network for real-time VoIP traffic. | | Number of Sessions | - Define how many simultaneous Sessions you want between these Agents. ***Note:*** *Be certain that you create the proper number of Sessions. If you activate this Session by clicking* ***OK****, you will not be able to edit the quantity. You would need to create additional Sessions if the quantity is incorrect.* | | Alarm on Route Change with Alert | - Check the box if you wish to receive an Event when the path between these two Agents changes. - This indicates a route outage/re-convergence has occurred during a Session. - Set the Alert level of a route change Event using the drop- down. | *Table 6-3 Add RTP Session* | **Parameter** | **Description** | | --- | --- | | Alarm on DSCP Mismatch with Alert | - Check the box if you wish to receive an Event when the DSCP tag is not maintained from end-to-end. - This indicates that the network is not properly configured for QoS. - Set the Alert level of a DSCP Mismatch Event using the drop-down. | *Table 6-3 Add RTP Session* - - - 1. Review all of your entries; then click **OK** to activate the session(s). ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-6wduqbw4.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 6-7Add RTP Session* - - - 1. After you have created your Session(s), view them in the **Sessions** pane. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-bgsibic0.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 6-8Sessions Pane* ***** MS O365**MOS is not used in O365 testing. Therefore, you may leave the defaults. ## View Active Sessions Active Sessions can be viewed in two places: ###### Health > Quality Management > Perspective QoS ###### Health > Quality Management > Real-Time QoS This section explains how to: ###### [View Active Sessions in Perspective QoS](/docs/perspective-administration-and-user-guide-2#_bookmark70) ###### [View Active Sessions in Real-Time QoS](/docs/perspective-administration-and-user-guide-2#_bookmark72) ###### [Query Historical QoS Statistics](/docs/perspective-administration-and-user-guide-2#_bookmark73) ###### [View Suspect Calls](/docs/perspective-administration-and-user-guide-2#_bookmark74) ### View Active Sessions in Perspective QoS Follow these steps to view the active sessions: - - 1. Navigate to **Health > Quality Management > Perspective QoS**. The **Perspective QoS** window appears. - Only Agents that are involved in an active Session(s) appear in this view. Configured but disabled Sessions/Agents are not visible. - [***Table 7-1***](/docs/perspective-administration-and-user-guide-2#_bookmark71) explains the diagram colors: | **Color** | **Description** | | --- | --- | | Agent Green | Agent state is Good. | | Agent Red | Agent is offline. | | Session Solid Green | Agents are exchanging RTP data. | | Session Dotted Green | Agents are communicating, but RTP data has not yet begun to flow. | | Session Other Solid Colors | Indicates the highest current Alert level of the active Session(s) between two Agents. | *Table 7-1 Diagram Colors* - - 1. Double-click on an individual Session in the lower **Session** pane to open the detail view of the Session, including the trace route and quality metrics histogram. - RTCP feedback is received from each side every 15 seconds. - Traceroute is re-run every 15 seconds as well. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-wmbezeya.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 7-1Active Sessions in Perspective QoS View* ### View Active Sessions in Real-Time QoS Follow these steps to view the active sessions in Real-Time QoS: - - 1. Navigate to **Health > Quality Management > Real Time QoS**. The **Real Time QoS** window appears. - Only active Session(s) appear in this view. Configured but disabled Sessions/Agents are not visible. - Defaults to the **All** view. - **Local Client RIG** - If this RIG is also monitoring an Avaya system, this view includes Perspective Sessions and active Avaya calls. There are three methods to filter to Perspective Sessions: - Select the **Perspective** tab, to the right of the **Phone** tab. This restricts the view to only Perspective activity. - Select the **Category** that reflects your TestID in the **Categories** pane (upper left). - Use the filter below the histogram, to the right. You can filter on a TestID or enter PQoS to view only Perspective activity. - **PaaS Controller** - If this is a cloud-based Perspective Controller for PaaS, this view only includes Perspective Sessions. There are two methods to filter to a specific Client/test: - Select the **Category** that reflects your TestID in the **Categories** pane (upper left). - Use the filter below the histogram, to the right. You can filter on a **TestID** or enter **PQoS** to view only Perspective activity. - - - - Sessions run for 15 minutes; then tear-down and re-initiate. - There may be an overlap between setup and tear down, so it may appear that you are running 1, 2, 4, 5, or 6 sessions instead of 3 (for example). This is normal and only lasts for a few seconds. ***Note*** *In the following figure, the columns have been rearranged from the default order. Your view may differ slightly and can be customized to your preferences.* *Figure 7-2Active Sessions in Real-Time QoS View* ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-susiy3o5.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) - - 1. Double-click on an individual Session in the lower right pane to open the detail view of the Session, including the trace route and quality metrics histogram. - RTCP feedback is received from each side every 15 seconds. - Traceroute is re-run every 15 seconds. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-t46feys1.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 7-3Detailed View in Real-Time QoS* ### Query Historical QoS Statistics Follow these steps to query real-time QoS: - - 1. Navigate to **Health > Quality Management > Real Time QoS.** b. Click **Search** in the upper left-hand corner next to **Traces**. 1. Set **Endpoint 1** to **Extension/Device Name** and set **Endpoint 2** to **IP**. ***Note*** *Be sure to select the appropriate Endpoint for the type of search you are performing, such as select IP, if you put an IP address in the* ***Search*** *box.* 1. If your search is based on a specific date and time, select a date from the drop-down list next to the **Start On** and/or **Stop At** check boxes. 2. When all of your criteria is entered, click **Search** to perform your search and view the results in the table. ### View Suspect Calls Follow these steps to view suspect calls: - - 1. Navigate to **Health > Quality Management > Real Time QoS**. 2. Select a Category, right-click and select **View Suspect Calls**. View the calls that violated their configured MOS, RTD, Jitter, or Loss thresholds. - - 1. Double-click on a session. The **QoS Detail** window appears wherein you can view additional detail about the suspect call. ## Groups and Group Sessions ***** MS O365**Due to reporting requirements, Groups and Group Sessions should NOT be used for MS O365 testing. The **Group** function simplifies Session creation by enabling you to quickly create a hub-and- spoke, or a mesh of Sessions, in one step. The **Group** function automatically creates a Session(s) between all members of two Groups. To create a hub and spoke topology, the single hub Agent must be a member of its own group. All of the spoke Agents are another group. For a mesh, the same Group of Agents is used. The system creates Sessions to and from each of the Agents in that single Group. This section explains how to: ###### [Create an Agent Group](/docs/perspective-administration-and-user-guide-2#_bookmark77) ###### [Create a Group Session](/docs/perspective-administration-and-user-guide-2#_bookmark78) ###### [Assign Agent Groups to a Group Session](/docs/perspective-administration-and-user-guide-2#_bookmark79) ### Create an Agent Group Follow these steps to create an Agent Group: - - 1. Navigate to **Configure > Quality Management > Perspective QoS**. The **Configure Perspective QoS** window appears. 2. Click the **Groups** tab. 3. In the **Session Groups** area, right-click and select **Add**. The **Add Group** window appears. 4. Enter a **Name** for the group, such as ***HUB***; then click **OK**. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-sqv3c7g2.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 8-1Add Group* Notice that the new group appears in the **Session Groups** pane. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-0gzm99yz.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 8-2New Group, Customer1-PA-Group1* - - 1. Select the newly added group, ***HUB***. 2. View the available agents for this group in the **Available Agents** pane. 3. In the **Available Agents** pane, right-click on each Agent that you want to add to the group, ***HUB***, and select **Add**. Each selected Agent moves from the **Available Agents** pane to the **Assigned to Group** pane. In this example, we will be placing only the Data Center in the HUB Group. We will also create a SPOKES Group for the branches. We will then use Group Session to create Hub-to-Spoke Sessions in one step. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-0h1b4m7c.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 8-3Add PA to Group* ***Note*** *Each Agent you add must be assigned to the same Test ID, in this case,* ***NecTech****.* The newly added agents appear in the **Assigned to Group** pane. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-1l0i63wn.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 8-4Add Agents to Assigned to Group* ***Note*** *You can also double-click on an Agent to add it to the* ***Assigned to Group*** *pane.* *If you want to add multiple Agents to a group name at one time, you can hold down the* ***Ctrl*** *key and select multiple agents; then right-click and select* ***Add****.* ### Create a Group Session Follow these steps to create the Group Session that defines the schedule, codec, etc. that will be used. - - 1. Navigate to **Configure > Quality Management > Perspective QoS**. 2. Click the **Sessions** tab. 3. Right-click in **Sessions** area and select **Add**. The **Add RTP Session** dialog window appears. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-uvhxfikb.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 8-5Add RTP Session* - - 1. Enter the following data: | **Parameter** | **Description** | | --- | --- | | TestID | - Select the identifier that you have assigned to the Agents. ***Note:*** *Sessions cannot be created between Agents with different Test IDs.* | | Grouping | - Set to **Yes**. | | Description | - Enter a description of the Session(s), such as **Hub and Spoke**. | | Agent 1/Agent 2 | - This field is grayed out for a Group Session. - You select the Groups later. | | Schedule | - From the drop-down menu select the schedule of when the Session(s) will run. ***Note:*** *You must assign a schedule. If a schedule is not assigned, then it is possible that a session(s) may not restart if/ when an outage or reboot occurs.* | | Codec | - Select the codec using the drop-down. | | Frequency/Packet Size | - These fields are populated based on codec and are informational. - They cannot be modified. | | DiffServ (DSCP) | - Assign a DiffServ Code Point (priority tag) for these packets. - This should match what is configured in the network for real-time VoIP traffic. | | Number of Sessions | - Define how many simultaneous Sessions you want between Agents. ***Note:*** *Be certain that you create the proper number of Sessions. If you activate this Session by clicking* ***OK****, you will not be able to edit the quantity. You would need to create additional Sessions, if the quantity is incorrect.* | | Alarm on Route Change with Alert | - Check the box, if you wish to receive an Event when the path between these two Agents changes. - This indicates a route outage/re-convergence has occurred during a Session. - Set the Alert level of a route change Event using the drop- down. | | Alarm on DSCP Mismatch with Alert | - Check the box, if you wish to receive an Event when the DSCP tag is not maintained from end-to-end. - This indicates that the network is not properly configured for QoS. - Set the Alert level of a DSCP Mismatch Event using the drop-down. | *Table 8-1 Add RTP Session* - - 1. Review all of your entries; then click **OK** to create this Group Session(s). 2. After you have created your Session(s), view them in the **Sessions** pane. ### Assign Agent Groups to a Group Session Follow these steps to assign Agent Groups to a Group Session: - - 1. Navigate to **Configure > Quality Management > Perspective QoS**. The **Configure Perspective QoS** window appears. 2. Click the **Sessions** tab. The **Sessions** pane appears with the **Session Group** pane to the right. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-o1edscf8.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 8-6Session Group - Select Add* - - 1. Select the group session in the **Sessions** pane. 2. Right-click in the **Session Group** window; then select **Add**. ***Note*** *The* ***Session Group*** *pane contains the groups that have been created.* The **Select Agents to Add** window appears. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-9t8mj3j2.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 8-7Select Agents to Add* - - 1. Select an agent to add or hold down the **Ctrl** key to select multiple agents. In this example, we will add both the HUB and SPOKE Groups. This will create a Session between all members of the two groups. As there is only one member in the HUB Group, it will create a Session from the HUB to each of the SPOKES. - - 1. Click **OK**. If you select the Group Session, the **Session Group** pane will contain the Agents belonging to the Group Session. ***Note*** *If you want to make any edits to the default settings before proceeding, see Section 8.3.1* [***Group Sessions***](/docs/perspective-administration-and-user-guide-2#_bookmark80)*.* - - 1. Right-click on the Group Session in the **Sessions** pane and select **Enable**. ***Note*** By default, the Group Session will not be enabled. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-isz2copu.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 8-8Enable a Session* This action creates all of the Sessions, which will be visible in the **Group Sessions** pane. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-js9zn2ew.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 8-9Group Sessions* ***Note*** *All Sessions within the Group can be disabled by right-clicking on the Group Session in the* ***Sessions*** *pane and selecting* ***Disable****.* ## Reports ***** MS O365**MS O365 testing requires Nectar Reporting and Analytics. Only Nectar-certified partners are enabled for MS O365 Analytics Reports. There are two options for reporting: ###### [RIG Reports](/docs/perspective-administration-and-user-guide-2#_bookmark83) ###### [Nectar Analytics Reports](/docs/perspective-administration-and-user-guide-2#_bookmark90) RIG reports run directly on the Perspective Controller (RIG). Nectar Analytics Reports require the Nectar Advanced Analytics Server. For more information on reporting, see ***RIG Administration Guide*** and ***Nectar Analytics Administration Guide***. ### RIG Reports Download the **QoS Report Pack** from the Nectar Partner Portal; then use the following, as needed: ###### [Load Report Packs](/docs/perspective-administration-and-user-guide-2#_bookmark84) ###### [Report Retention](/docs/perspective-administration-and-user-guide-2#_bookmark85) ###### [Enable a Report](/docs/perspective-administration-and-user-guide-2#_bookmark86) ###### [Edit a Report Schedule](/docs/perspective-administration-and-user-guide-2#_bookmark87) ###### [Create a Report Schedule](/docs/perspective-administration-and-user-guide-2#_bookmark88) ###### [Remove a Report](/docs/perspective-administration-and-user-guide-2#_bookmark89) #### Load Report Packs Follow these steps to upload report packs from your computer: - - - 1. Navigate to **Reports > Report Manager**. The **Report Manager** window appears (see ***Figure 9-1***). - - - 1. Right-click on a report name and select **Report Packs > Load Report Pack**. The **Open** window appears (see ***Figure 9-1***). 2. Browse to the report on your computer and click **Open** to load the report. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-shb34g4a.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 9-1Load Report Pack File* #### Report Retention Follow these steps to manage report retention: - - - 1. Navigate to **Reports > Report Manager**. The **Report Manager** window appears. 2. Select a report name; then click **Edit**. The **Edit Report** window appears. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-doy2yr8f.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 9-2Edit Poller Export Report* - - - 1. Define the number of reports to have on file at a time using the following: | **Option** | **Description** | | --- | --- | | **Retain last** *x* **reports** | Enter the number of previous reports you want to retain. | | **Retain reports for** *x* **weeks** | Enter the number of weeks for which you want to retain reports. | - - - 1. Click **Save**. *Table 9-1 Report Retention Properties* #### Enable a Report Follow these steps to enable a report. A report will not run until it is enabled. - - - 1. Navigate to **Reports > Report Manager**. The **Report Manager** window appears. 2. Click on the **Schedules** tab. A list of reports appears. Notice the schedule for each report in the **Frequency** column. - - - 1. Select a report and schedule; then right-click and select **Enable**. ***Note*** *You can select a report; then right-click and select* ***Disable*** *to disable a report.* #### Edit a Report Schedule Follow these steps to edit a report schedule: - - - 1. Navigate to **Reports > Report Manager**. The **Report Manager** window appears. 2. Click on the **Schedules** tab. 3. If you wish to create a different schedule for a report, select the report and schedule; then click **Edit**. The **Edit Report Schedule** dialog appears. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-y6toznap.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 9-3Edit Report Schedule* - - - 1. Define the following parameters for automatic report generation: | **Parameter** | **Description** | | --- | --- | | **Repeat** | - Set as **Hourly**, **Daily**, **Weekly**, or **Monthly**. | | **Days or Weeks** | - Enter number of days or weeks to lapse before the report generates again. Parameter will change based on **Repeat** parameter selected. | | **Day of Week** | - This applies to **Weeks** only. - Select the day of the week to generate the report. | | **Day of Month** | - This is for **Months** only. - Select **First Day**, **Last Day**, or a date between 1 and 31. | | **Hour of Day** | - Enter the hour that the report generator begins to collect data. | - - - 1. Click **OK**. *Table 9-2 Parameters - Automatic Report Generation* The details appear in the **Schedules** pane. - - - 1. Right-click on the report and select **Enable**. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-5smrgofi.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 9-4Enable a Report* The **Next Time Text** field displays the future date and time that the report will run. #### Create a Report Schedule Follow these steps to create a new report schedule. You can assign multiple schedules to a report. - - - 1. Navigate to **Reports > Report Manager**. The **Report Manager** window appears. 2. Click on the **Schedules** tab. 3. Click **Add**. The **Add Report Schedule** dialog appears. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-2i7vbamz.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 9-5Add Report Schedule* - - - 1. Select a **Report** for the new schedule using the drop-down arrow. 2. Use the parameters in ***Table 9-2*** to complete the remaining Report Schedule fields. 3. Click **OK**. #### Remove a Report Follow these steps to remove a report you no longer want to use. - - - 1. Navigate to **Reports > Report Manager**. 2. Select report to remove; then click **Remove**. The **Confirm Remove Report** window appears. 3. Click **Yes**. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-cdw9bsx1.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 9-6Confirm Remove Report* #### Terminate a Report Follow these steps to terminate a report that is executing. - - - 1. Navigate to **Reports > Report Manager**. The **Report Manager - Reports** window appears. - - - 1. From the **Reports** tab, select the report you want to terminate. 2. Click the **Progress** tab. 3. Select the report; then right-click and select **Cancel**. The report is terminated. ### Nectar Analytics Reports Nectar Analytics requires a Nectar Analytics Report Server. To deploy and configure this server, see ***Nectar Analytics Administration Guide*** on the Partner Portal. Once deployed, download the Nectar Analytics Perspective Report Pack from the Partner Portal. This report pack will then be loaded on the Analytics server. For report upload instructions, see ***Nectar Analytics Administration Guide***. ***** MS O365**The following ***Figure 9-7*** is a sample Nectar Analytics Report for MS O365 testing. Microsoft uses the 90th percentile as a passing grade. The percent of Sessions that pass is indicated. If a test does not pass 90 percent of the time or more, it will be highlighted in yellow. Stroke counts are included to indicated where/why a Session did not pass. The six thresholds and the count of breaches are shown in the orange box. A 33 in the **Jitter Breach** column indicates that the Boston-Azure Session had Jitter above the Microsoft-specified threshold 33 times. The arrow points to a toggle wheel that switches between the following two threshold sets: - Client Edge to Azure Edge - Client LAN to Azure Edge Microsoft's threshold specifications can be seen under the **Thresholds** tab in Nectar Analytics. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-dutdh38h.jpe?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 9-7Sample Nectar Analytics Report for MS O365* ## Troubleshooting Troubleshooting includes the following tasks: ###### [Verify Session Status](/docs/perspective-administration-and-user-guide-2#_bookmark93) ###### [Perform Trace Route](/docs/perspective-administration-and-user-guide-2#_bookmark94) ### Verify Session Status All enabled sessions have a status line displayed in **Perspective QoS** window. Navigate to **Health > Quality Management > Perspective QoS**. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-ix8wkamy.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 10-1Perspective QoS* Each line contains the following: | **Value** | **Description** | | --- | --- | | **Alert** | Value that represents the severity of the current session impairment, such as: - 0 – Initializing - 1 – Good - 2 – Warning - 3 – Minor - 4 – Major - 5 – Critical If the session has not yet been established between the agents, the severity will indicate 5. | | **Server 1** | PA name 1 | | **Server 2** | PA name 2 | | **Status/Status Description** | Status of the session establishment details as presented in ***Table 10-2***. | | **Description** | Text defined as part of session configuration. | *Table 10-1 Status Line Values* When a session runs, the system goes through several stages to establish the session between the two Perspective Agents. The follow table summarizes those stages. | **Stage** | **Pass/Fail** | **Condition/Status Description** | **Next Stage** | **Remediation Step(s)** | | --- | --- | --- | --- | --- | | **Initialize** | Pass | - PAs are ready | **Starting: Phase 1** | - N/A | | | Fail | - PA is unknown. - Can occur if RIG cannot communicate with PA. | **Initialize** | - Verify PA is online. | | | Fail | - PA is not installed correct. - RIG can communicate with PA but initial query indicates PA is configured correctly. | **Initialize** | - Verify PA installation successful. | | | Fail | - Waiting for reset. - RIG has not been able to exchange initial reset message with PA. | **Initialize** | - Verify PA is online. | | **Starting: Phase 1** | Pass | - Check inter-transponder reachability. - RIG is requesting each PA to exchange messages. | **Phase 1 - Step 2** | - N/A | | | Pass | - Transponders verified remote IP. - Reachability from each PA is established. | **Starting: Phase 2** | - N/A | *Table 10-2 Session Stages* | **Stage** | **Pass/Fail** | **Condition/Status Description** | **Next Stage** | **Remediation Step(s)** | | --- | --- | --- | --- | --- | | | Fail | - Transponder unable to contact remote transponder. - Indicates a communication problem exists between the PAs. | **Initialize** | - Use UDP trace route with configured port range. | | | Fail | - Transponder did not process discovery. - RIG could not exchange the reachability request messages. | **Initialize** | - Verify PA is online and installed correctly. | | **Cancel Pending** | Fail | - Attempt to cancel session. - If a failure occurs during a starting or started phase, RIG cancels the session. - If messaging fails, the session remains in this state until completed. | **Cancel Pending or Initialize** | - Verify PA is online. | | **Starting: Phase 2** | Pass | - Start transponders. - RIG requests each PA to reserve an RTP port for the session. | **Phase 2 - Step 2** | - N/A | | | Pass | - Transponder allocated port. - Both PAs allocated a port number successfully. | **Starting: Phase 3** | - N/A | | | Fail | - Unable to initialize port. - The description text provides additional details, which includes session limit reach, or session already running that means a duplicate request has been detected. | **Cancel Pending** | - LimitExceeded - Verify PA session limit. - Session Already Running - most likely a transient event. - Port interface error - Verify configured port range allows for two ports per session. | | | Fail | - Unable to locate transponder. - RIG could not exchange the request messages with the PA. | **Cancel Pending** | - Verify PA is online. | | **Starting: Phase 3** | Pass | - Starting/Exchanging ports. - RIG exchanges allocated port information with the PAs. | **Started** | - N/A | *Table 10-2 Session Stages* | **Stage** | **Pass/Fail** | **Condition/Status Description** | **Next Stage** | **Remediation Step(s)** | | --- | --- | --- | --- | --- | | | Fail | - Error in CSocket command. - RIG could not successfully communicate the port exchange. | **Cancel Pending** | - Verify PA is online. | | **Started** | Pass | - Transponders started. - Session has successfully been established. | **rtcpReceived** | - N/A | | **rtcpReceived** **(1, 2, or both)** | Pass | - Transponders started. - RIG has received RTCP reports from one or both of the PAs. | **Complete** | - N/A | | | Fail | - Fail/Transponder has not reported in 60 seconds. - RIG has not received an RTCP report from one or both of the PAs in over 60 seconds. | **Cancel Pending** | - Verify RTCP report reception enabled - **Setup > Phone QoS**. - Verify reachability from PA to RIG using UDP trace route with configured port. | *Table 10-2 Session Stages* If the session will not establish and the root cause is not readily known, a manual trace route can be performed to help isolate the underlying issue. In some cases, it is easier to troubleshoot an issue, if the sessions are stopped. ### Perform Trace Route Using the PA maritime terminal, it is possible to have the transponder send a trace route message using any of the types discussed above. The transponder keeps track of the number of retries before a response was received and the delay time. When the message exchange reaches the destination IP, the transponder sends the trace route message several times to try to detect some sense of packet loss. ***Note*** *The behavior discussed above for the various trace route types may affect the reported results.* View the following examples. The command format is as follows: ###### rtppassive dotraceroute Even though ICMP does not use the port number, it must be specified, because the command format is fixed. The command may take many seconds to complete when timeouts occur. The trace route sends to a maximum of 30 hops before quitting. Because every hop is sent three messages before giving up, the overall execution time can become quite long. Below is an example of using ICMP (see [***Figure 10-2***](/docs/perspective-administration-and-user-guide-2#_bookmark95)). The first line of output is the overall result. It will either be okay or fail. If this result text is not displayed when the command completes, verify that the transponder is running on this PA. The next line of output displays the number of hops discovered. For each hop, the IP address, time delay, received count, and retry count are displayed. In this example, there were no retries. Each intermediate hop is only tested one time. The final hop is sent 50 messages. The largest delay calculated is also displayed. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-uk6ggegk.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 10-2 Example - Using ICMP* A UDP trace route is used in the following example. It shows that 27 messages were received and 23 retry messages were sent, because of the throttling of the port unreachable message and not a result of a packet drop. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-4t3dzpc9.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 10-3Example - UDP Tracer Route* The following is an example of a TCP trace route between two Linux systems. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-ua3w4pnf.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 10-4Example - TCP Trace Route/Two Linux Systems* The following is an example of a TCP trace route from a Linux system to a Windows system. Note the longer delay time measured for the last hop. This is also an example of the behavior explained in the previous section. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-atmhocpa.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 10-5Example - TCP Route from Linux to Windows System* The following is an example TCP trace route from a Windows machine to a Linux machine. ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/perspective-administration-and-user-guide-image-4cxwuwf5.png?sv=2026-02-06&spr=https&st=2026-11-08T17%3A08%3A31Z&se=2026-11-08T18%3A08%3A31Z&sr=c&sp=r&sig=g986J3gBy1zYf3uRyydZF%2FhNgDZ8djiXys3mAZF%2Fua8%3D) *Figure 10-6Example - TCP Trace Route - Windows to Linux Machine* It is possible to use the UDP trace route to test reachability to the RIG. However, if you use the UDP port assigned as the RTCP report, the trace route will not show the RIG properly. This is because the RIG is listening on the port, so no port unreachable message is returned. The RIG simply consumes the message. For this reason, it is better to use a UDP port number not in use but allowed by the firewalls.