Call scenarios, have a meaningful impact to the end users call quality, and are consistently measurable and actionable.
- All
The All call scenario displays the overall call quality for the selected category. The categories available to view the total call quality across all call scenarios are:
o Site
o BSSID
o Subnet
o WIFI Device Driver
o Client Version
o WiFi Band
o Client Type (Only for Microsoft Teams)
The results will assist you in determining the problem areas for each category.
- Service to Service
The Service to Service call scenario displays all calls that have occurred between two Skype for Business and Microsft Teams Servers/Services. Example: Gateway or Mediation Server to AV MCU. It is important, that the Service to Service issues are focused upon first, if these issues are causing the poor call quality. The cause of these Service to Service poor calls will impact other calls within the organization that are not Service to Service, owing to the fact, that these service are responsible for most end user behaviors, including conferencing and Enterprise Voice.
- Wired External to Service
The Wired External to Service calls are to and from clients that are not on the corporate network (example: users at home) and are utilizing wired connectivity to a servie. These calls are similar to Wired Internal to Service calls, except that, these are calls initiated to and from clients that are outside of the corporate network. If the Wired External to Service scenario is displaying poor call quality issues, then it is likely not possible that the corporate network, is causing the poor call quality. Instead it is external factors that need to be focused on.
- Wired Internal to Service
The Wired Internal to Service calls, are calls that are initiated to and from clients which are on the corporate network (example: desktop client within your organization’s office) and are utilizing wired connectivity to a server. These calls are important owing to the fact that, similar to the Service to Service calls, these calls are executed in a managed environment, where the network quality is expected to be good.
- Wireless External to Service
The Wireless External to Service is similar to the Wired External to Service, however, the clients used to make the calls use wireless connectivity when external. If Wired External to Service call scenarios are not displaying any issues, however, your organization is displaying Wireless External to Service issues, it can be concluded, that the variables causing the poor call quality issues, may be attributed to the fact that a wireless network is used.
- Wireless Internal to Service
The Wireless Internal to Service calls, are calls from clients which are connecting via wireless to a server. If the Wired Internal to Service calls scenario does not display any issues, but your organization has Wireless Internal to Service issues, then it can be conlcluded, that the variables are factors associated with placing calls over wireless network. The Wireless External to Service is similar to the Wired External to Service scenario, however the clients used to make the calls use wireless connectivity when external.
- Endpoint to Endpoint Service
The Endpoint to Endpoint Service scenario displays the Poor Call percentage for any client talking to another client (without using a service). This scenario, has a lower actionable priority than other scenarios, owing to the fact that the Poor Call quality issues could be at either endpoint and no service is involved. The issues could include internal, external, wired, or wireless, making it less actionable than other scenarios. This scenario is provided for reference only, if all other factors are being addressed (example: internal wired), it is to be expected that the solving of the other factors will improve Endpoint to Endpoint scenarios.
- Cellular Endpoint to Service
The Cellular Endpoint to Service scenario tracks the experiences of users utilizing mobile devices that connect to a service using cellular network.
- Web Experience Endpoint to Service
The Web Experience Endpoint to Service scenario displays the experience of users utilizing the Web Experience for joining meetings. Tracking this data is useful, however, typically it is not possible to improve the call quality of these calls, as normally these users are:
o Anonymous (example: not part of the organization)
o Outside the network
- Federated Endpoint to Service
The Federated Endpoint to Service scenario tracks the call quality for users who are federated, that is, they are not within your organization, but join your company’s meetings. This information is useful to track, but little action can be taken to improve the federated user’s experience.
- VPN to Service
The VPN to Service scenario tracks the calls made by external users, over the VPN tunnel. Tracking this data is useful, as in the majority of cases it represents scenarios that are recommended to be avoided, or scenarios where the call experience is expected to be of a lesser quality compared to other external calls that are not made via VPN. If a significant volume of calls is displayed in this scenario, then an investigation into the media routing will likely be triggered and follow up by the networking team will be needed.