Note: If ICA audio redirection needs to be available in your environment then ensure that none of the Audio options are enabled in the Client Settings. (In Windows Server 2008/R2 for 6.0 & 6.5 this will be the Remote Desktop Session Host Configuration GUI). On the server, go to Terminal Services Configuration under the Client Settings tab and verify if Audio Mapping is enabled or disabled.On the client operating system, verify that sound is enabled and not muted.If either the client machine or XenApp Server has sound capabilities disabled, then ICA audio redirection does not work. Sound must be enabled on both client and server. The following is a list of basics for enabling sound through an ICA session:Ī sound card is required to be installed only on the client device the client sound card needs to be configured and fully functional for audio sound. The server does not require a sound card as the Citrix Virtual Audio Driver redirects the sound back to the client through the audio ICA virtual channel. Basics of Enabling Sound Through an ICA Session I think the Frequency 48000Hz might not be supported then, based on your description.This article provides troubleshooting and configuration steps to resolve audio issues within ICA sessions. WebRTC looks for some fixed audio quality settings on the physical client, not the VDA, and unfortunately if even one of the devices does not comply, it can break redirection and peripheral enumeration. Mar 31 09:05:57.525 webrtcapi.WebRTCEngine Error: init. Mar 31 09:05:57.43 webrtcapi.WebRTCEngine Info: init. I feel like I cannot troubleshoot that until I am sure it is not the sound devices being set to None possibly causing the issue. I am also not sure if this is the issue that is causing Teams to not be able to join any meetings with Audio Off entry, it instantly leaves the meeting. These seem to be within the specified ranges unless I am reading this wrong. I disabled all audio devices except for my Teams approved Jabra Speak 710 puck ( VDA mmsys.cpl Settings - Playback: 16 bit, 44100 Hz Recording: 1 Channel, 16 bit, 44100 Hz) ( Physical Client mmsys.cpl settings - Playback: 2 Channel, 16 bit, 48000 Hz Recording: 1 Channel, 16 bit, 16000 Hz Grayed out ). I am having the same exact issue and I am following the doc to try and disable incompatible playback/recording devices. couldn't create audio module!Īny help would be much appreciated! I've also attached the Microsoft Teams log in case that of use. Mar 29 13:23:57.520 webrtcapi.WebRTCEngine Error: init. Mar 29 13:23:57.232 webrtcapi.WebRTCEngine Info: init. I'm struggling to find any further log files or information on why it's having issues creating the module. All I get is two lines suggesting it couldn't create the audio module. Some troubleshooting guides online suggest checking the webrpc log. If I take the App out of VDI mode (regedit) I can see all of the audio devices in the Teams menu, can make calls, so it must be something with the Teams Redirection. I've tried deploying both the application and desktop, both have the same symptoms. Teams is version 1., which the About-> version menu displaying "Optimized for Citrix". Teams is running on a Server 2019 image running VDA 1912. I'm having an issue where Microsoft Teams doesn't appear to be detecting Audio devices.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |