UC Monitor administrators create Locations that correspond to network entities such as branch offices, departments, or buildings. Location definitions determine how data is displayed in reports. Reports organize call performance data based on Location or Sending Location. These categories are further identified as <Unassigned>, <None>, or <External>, as explained in the following list:
Call data that is categorized as Location was received by the indicated Location.
Call Data that is categorized as Sending Location was sent from the indicated Location.
The <Unassigned> Location identifies IP phones that were observed during monitoring but whose IP addresses are not part of the subnets in your Locations. An <Unassigned> Location is not the same as a Location of <None>.
A Location is <Unassigned> for reasons such as:
Call traffic from endpoints in new subnets is labeled as <Unassigned> until the administrator creates a Location definition for those subnets. Periodically, the administrator exports a list of current Location definitions and verifies that it reflects recent changes to the network and telephone system.
A Receiving Location or Sending Location of <None> indicates that the IP address of the endpoint was not determined, for reasons such as the following:
Note: Abandoned call legs that have metrics are displayed in the Call Leg Details report. In addition, you can see these calls in the Calls Overview when the option to “Show abandoned calls” is enabled in the Settings dialog.
(Microsoft OCS only) The <External> Location identifies endpoints that are reported to the front-end server as being "remote." UC Monitor uses this Location definition for endpoint addresses that are outside your firewall, or behind a NAT device, that make remote access connections through an edge server.
|
Copyright © 2012 CA.
All rights reserved.
|
|