If you use Azure Virtual Desktop or Windows 365 Cloud PC environments, you can run Flex in these environments while maintaining optimal call quality.
Flex UI 2.8.5 and later improves audio quality by supporting Microsoft's multimedia redirection (MMR) browser extension. The Microsoft MMR extension helps your agents avoid potential latency, packet loss, and lengthy round-trip time that would otherwise occur when using Flex on Azure Virtual Desktop or Windows 365 Cloud PC. When agents use Flex on Azure Virtual Desktop or Windows 365 Cloud PC with the MMR extension installed, Flex uses the WebRTC credentials from the browser on the local device, not the browser in Azure Virtual Desktop or Windows 365 Cloud PC. That means that audio packets go directly from the customer to the Flex telephony server to the agent using Flex. Without the MMR extension, audio packets are routed to the Azure Virtual Desktop or Windows 365 Cloud PC browser before reaching the agent in Flex, and that extra step in the path can cause issues with call quality.
Note that while the diagram refers only to Azure Virtual Desktop, the architecture is the same for Windows 365 Cloud PC.
To set up Flex on Azure Virtual Desktop or Windows 365 Cloud PC, complete the following steps:
Set up your local Windows environment. Note that there are separate tabs at the top of the page for Azure Virtual Desktop and Windows 365.
Set up the Azure Virtual Desktop environment. Note that there are separate tabs at the top of the page for Azure Virtual Desktop and Windows 365.
Self-hosted Flex only: Upgrade the Flex UI library to a version that supports Azure Virtual Desktop or Windows 365 Cloud PC:
Validate your setup to ensure that Flex will automatically detect if you're running in a Virtual Desktop or Cloud PC environment:
If MMR does not show that the call is being redirected, see "The MMR extension is not loaded" in the troubleshooting section.
Voice Over Internet Protocol (VoIP) call quality is influenced by environmental factors, such as:
It's important you review our deployment best practices and connectivity requirements documentation before taking your app to production. Browsers that support DSCP are able to tag call media packets sent by the voice client. Your router or network element can then use these tags to prioritize call media packets over other traffic on the network.
To capture logs from the MMR extension, open the MMR extension in your browser and select Show Advanced Settings. Next to Collect logs, click Start.
If you followed step 4 in the the setup instructions above to validate the Azure Virtual Desktop setup and the MMR extension is not loaded, check the following:
If you have checked your environment and configuration and still have issues, contact Twilio support.
Microsoft and Twilio jointly support the delivery of Flex on Azure Virtual Desktop or Windows 365 Cloud PC. If you experience an issue, open a support ticket with the vendor whose product you suspect to be causing the issue.
When Twilio or Microsoft receives the ticket, they will triage the issue and escalate it as appropriate. If they determine that the problem is caused by the other company's product, they will advise you to create a support ticket with the other company.