Device Report
Topic Last Modified: 2011-02-01
This report provides a summary of devices that are used for Enterprise Voice calls and it includes the average media quality of the calls by device.
Filters
Filters provide a way for you to return a more finely-targeted set of data or to view the returned data in different ways. For example, the Device Report enables you to filter on such things as call type (that is, was the call a client call), a conference call, or a public switched telephone network (PSTN) call. You can also choose how data should be grouped. In this case, devices are grouped by hour, day, week, or month.
The following table lists the filters that you can use with the Device Report.
Device Report Filters
Name | Description |
---|---|
From |
Start date/time for the time range. To view data by hours, enter both the start date and time as follows: 1/1/2011 1:00 PM If you do not enter a start time, the report automatically begins at 12:00 AM on the specified day. To view data by day, enter just the date: 1/1/2011 To view by week or by month, enter a date that falls anywhere within the week or month that you want to view (you do not have to enter the first day of the week or month): 1/3/2011 Weeks always run from Sunday through Saturday. |
To |
End date/time for the time range. To view data by hours, enter both the end date and time as follows: 1/1/2011 1:00 PM If you do not enter an end time, the report automatically ends at 12:00 AM on the specified day. To view data by day, enter just the date: 1/1/2011 To view by week or by month, enter a date that falls anywhere within the week or month that you want to view (you do not have to enter the first day of the week or month): 1/3/2011 Weeks always run from Sunday through Saturday. |
Voice switch cause |
Reason why a call had to be placed into half duplex mode in order to prevent echo. In half duplex mode, communication can travel in only one direction at a time, similar to the way users take turns when communicating with a walkie-talkie. Select one of the following:
|
Echo cause |
Reason why echo above the accepted level was detected in a call. (In telecommunications, echo is a reflection of sound, the same phenomenon you will hear if you yell down to the bottom of a well.) Select one of the following:
|
Call type |
Indicates the type of call that was made. Select one of the following:
|
Access type |
Indicates whether the client was logged on to the internal network or the external network when the call was placed. Select one of the following:
|
Network type |
Indicates the type of network the client was connected to when the call was placed. Select one of the following:
|
VPN |
Indicates whether an external client was using a virtual private network (VPN) connection when the call was placed. Select one of the following:
|
Device type |
Indicates the type of device. Select one of the following:
|
Device name |
Name of the capture or render device. You can enter the complete device name or any portion of the device name. For example, to find the device Microphone (Microsoft LifeCam VX-1000.), you can enter the complete device name as follows: Microphone (Microsoft LifeCam VX-1000.) Or, you can enter just a portion of the name. For example: LifeCam Note that the preceding filter returns any device that contains the string "LifeCam" anywhere in its name. |
Metrics
The following table lists the information provided in the Device Report.
Device Report Metrics
Name | Can you sort on this item? | Description |
---|---|---|
Capture device |
Yes |
Device (for example, a microphone or webcam) used for transmitting audio. |
Render device |
Yes |
Device (for example, a headset or speakers) used for receiving audio. |
Call volume |
Yes |
Total number of calls placed. |
Poor call percentage |
Yes |
Percentage of calls that were classified as "poor." A poor call is any call which at least one of the measured metrics exceeded the allowed value (for example, a call that experienced excessive jitter). |
Unique users |
Yes |
Unique users who used the device. If a user used the device 13 times he or she would count as one unique user, the same as a user who only used the device a single time. |
Ratio of voice switch time |
Yes |
Percentage of the call that had to be conducted in half duplex mode in order to prevent echo. In half duplex mode, communication can travel in only one direction at a time, similar to the way users take turns when communicating with a walkie-talkie. |
Ratio of microphone not functioning |
Yes |
Percentage of the call in which the capture device was not functioning at an acceptable level. A high values suggests that quality issues with the call were primarily due to the capture device not working as expected. |
Ratio of speaker not functioning |
Yes |
Percentage of the call in which the render device was not functioning at an acceptable level. A high values suggests that quality issues with the call were primarily due to the render device not working as expected. |
Calls with voice switch (%) |
Yes |
Percentage of the total calls which had to be placed into half duplex mode. In half duplex mode, communication can travel in only one direction at a time, similar to the way users take turns when communicating with a walkie-talkie. |
Echo microphone in (%) |
Yes |
Percentage of echo that was present in the microphone. (In telecommunications, echo is a reflection of sound, the same phenomenon you will hear if you yell down to the bottom of a well.) Typically you will see low values for headsets or handsets, and higher values for speaker phones or stand-alone speakers. |
Echo send (%) |
Yes |
Percentage of echo transmitted to other users. |
Calls with echo (%) |
Yes |
Percentage of the total calls that had echo exceeding the acceptable level. |