AVD Standard Windows client has horrible audio quality on Azure Virtual Desktops. Works great with M

Copper Contributor

A bit of a long story, so please be patient :)

Our environment has got RDP shortpath enabled and clients make successful UDP connections to the Windows 11 Enterprise 21H2 AVD's. RTT is very low as well within 20 ms. We don't plan to use Windows 10 OS, hence QOS enablement is not done for the AVD's

 

When the agent connects to the AVD using standard Windows client available at link and takes calls on Avaya One-X Communicator App version 6.2.7.03-SP7 , the call is jittery and it crackles as well. The agent can hear the customer fine, but it is mainly the customer which faces issue with the jitter. The QOS call quality shows 'good' on the Avaya app. We haven't done deep level troubleshooting and log collection on the Avaya app, since it's working fine in other environments as you will find below (so not an internal infrastructure issue which involves the Avaya server or it's DB)

When the same agents connects to the same AVD using the MS Store RDP client available at link, they don't face any audio problems. The customer and the agent can hear each other and converse much better with minimum jitter and delay in audio. It is at an acceptable.

 

Additionally, we have the same set of users who don't face any problem on AWS Workspace as well. The difference in AWS Workspace and AVD is AWS uses Teradici audio drivers and the OS is Windows 2019 with desktop experience. We pay per-user licence fee to AWS for potentially the Teradici offering which allows us to connect to the AWS VDI's using PCOIP protocol. instead of RDP/UDP that we have on Azure Virtual Desktops

I am at a loss right now to think of what else may be causing these jittery and poor call quality issues, and why we don't face it on the Microsoft store RDP client. The only reason we can't use the Microsoft store RDP client because it doesn't support dual monitor.

I have been looking at the Teradici offering for Azure Virtual Desktops (thinking that may be PCOIP connectivity is the solution using Teradici audio drivers) and had the below questions :

1. Without moving to Teradici, is there any other piece that I am missing which may resolve the issue without moving the architecture to PCOIP which means involving Teradici ?

2. Need to understand the pricing, is it 86.427 £ per user per month with a minimum of 5 users to subscribe ? Does the one-time payment mean we pay only once 86.427£  for each user and the CAS licence will be valid for a year, post which it gets renewed with another 86.427£

 

3. After going through the documentation, it seems that Teradici has a PCOIP client for Ubuntu OS to connect to an existing Azure Virtual Desktop. Is this correct ? Our users are all windows users. How will they connect using PCOIP to the existing Azure Virtual Desktop hosted in Azure ?

0 Replies