The Lync collector should receive data within minutes after configuration in an environment where calls are running. In the management console, you can confirm that the Lync collector is operational by clicking Administration, Data Collection, Collectors. Confirm that the Collection Device List contains an entry for the Lync collector. The Last Collection field shows whether reports have been sent.
If the Last Collection field is empty after 15 minutes, verify your configuration. Confirm that the Lync collector is sending data to the correct report recipient. The topics in this section identify issues that you can address.
After you configure the Lync collector, the Collection Device List shows a blank space for the “Last Collection” field. The lack of a Last Collection time indicates that no reports were received from the Lync collector. If calls are active, run the following command on the management console server to look for Lync report files:
dir <install path>\voipmonitor\datafiles\q*.xml /s /b
If no files are returned from this directory command, restart some services. Try the following tasks, which are listed in order from least disruptive to most disruptive to your Lync system:
After you try a task, wait 15 minutes and run the directory command again.
A lack of the required login permissions is the most common reason for problems in setting up monitoring in a Lync environment. Your Windows login account needs Domain User and Local Administrator privileges on the management console computer.
Note: The members of the RTCUniversalServerAdmins security group can manage all aspects of Lync within the Active Directory forest, including all server roles and users. Members of this group can retrieve settings on the Microsoft server but cannot save them to the UC Monitor database.
Verify that the Lync collector server is configured to receive data from the endpoints in the Microsoft system.
Follow these steps:
In a Microsoft Lync environment, a monitoring, or back-end, server is associated with a front-end server. However, the UC Monitor system works with or without the back-end server.
The Microsoft Administrative interface displays the following error message when a third-party consumer is configured to receive quality reports without a Microsoft back-end server.
QoE monitoring and/or call detail recording is enabled, but at least one Front-End Server does not have an associated Monitoring Server. Please assign a Monitoring Server to all Front-End Servers in the pool.
If you see this error, click OK in the error dialog. Then click Apply or Cancel in the Properties dialog to ignore the error.
Firewalls in your network must allow communication between the Lync collector server and the management console.
These communications begin by using port 135, however port selection is dynamic because the processes use DCOM. You can edit some Registry keys to restrict the ports that are used. The following article from Microsoft provides more information: http://support.microsoft.com/kb/154596.
If you think that a firewall is causing an issue, test the connectivity between the management console and the Lync collector server.
In a few cases, issues with firewalls or similar security measures affect the metrics that are collected and reported. For example, UC Monitor cannot find the address of the endpoint that sent the call quality report when an intervening HTTP proxy is active. All traffic that the proxy forwards is associated with the IP address of the proxy. Verify that one of the following statements is true:
|
Copyright © 2013 CA.
All rights reserved.
|
|