BigHand with AVD and Teams

Question

Hi Allwe have a customer who uses BigHand with AVD, we recently upgraded their AVD and and installed teams, we also configured RDP Shortpath for public networks so the user get a connection over the Azure to site VPN. when configured the Teams audio and video communications were great, however we have found out that BigHand crashes and has audio driver issues if UDP is enabled, the only workaround we have is to disable UDP and force a TCP connection, this then stops the RDP Shortpath connection and we get a web socket only and less performance for Teams. Has anyone managed to get a better fix? it seems daft that we have a solution that can provide great performance to users for audio and video but we have to cripple it to use a one of the key Lob applications, constructive comments welcomed, Andy

kidd_ip · Answer

awoodlandenhanced&nbsp;
&nbsp;
Make sure necessary ports allowed at first place

awoodlandenhanced · Answer

Kidd_Ipthere are no port restriction in place, please re read the question as the answer you have given is not relevant, we know the problem I am trying to ascertain if any one has overcome this restriction caused but using Big hand, Thank you

stevenr · Answer

Hi awoodlandenhanced, have you managed to get round this since the post, when you say it crashed was this at the point you try to access settings in BH to select audio device settings, as this is the issue im facing for a test user, they are potentially on UDP shortpath where as my test dummy user isnt being ran from within the UDP area

awoodlandenhanced · Answer

Hi, Sorry no, its a Big Hand problem please see the below.Workflow Management Enterprise (OnPrem) - v5.16 Supported Platforms and DevicesFor both the AVD and the Terminal End Point we supportMicrosoft Windows 10Microsoft Windows 11UDP over the RDP must be disabled.Although the BigHand audio channel will work as expected during the first logon of the day, allowing the local recording and playback devices to be passed through without any problems for the entire duration of that session, if the Azure Remote Desktop session is later terminated or disconnected, the audio channel will fail to automatically initialise when a subsequent connection is established. This has been raised with Microsoft by our Development team and acknowledged as a bug within the Remote Desktop clients with work currently underway to address the limitation. Microsoft will automatically push out an update once this has been addressed.As a workaround, in order for the virtual audio channel to be initialised during a second logon to the Azure Windows Desktop Platforms, without having to restart the local machine, it is recommended to manually disconnect all sessions from the Remote Desktop icon before attempting to log back in as this will stop any msrdc.exe processes from trying to handle any call-back functions. Once you’ve logged back in, please restart the BigHand client if it’s still running which will start a new virtual channel for your local recording and playback devices.

stevenr · Answer

Hi, Thanks for getting back to me so quick with a detailed response really appreciate this, I see your a year on so I wont hold my hope on MS/BH resolving anytime soon, i presume there has been no indication to when that may get resolved?

Forum Discussion

BigHand with AVD and Teams

Share

Resources