To use our site, please take one of the following actions: Thank you, Re: Still connecting to remote devices - Microsoft Community Hub While the actual service (Citrix HDX HTML5 Video Redirection) might be running in theservices.mscconsole, the localhost127.0.0.1:9002TCP socket is never in listening mode as seen in netstat. #4.1 As an example we will investigate a p2p audio call between two VDI users. Media Engine multimedia stream processing. Also, keep in mind that Teams feature set is different when comparing optimized vs non-optimized. You'll be joined in the room and on your iPhone at the same time. HdxTeams.exe supports only these specific audio device formats (channels, bit depth, and sample rate): Even if one speaker or microphone does not match the expected settings, device enumeration in Teams fails andNonedisplays underSettings > Devices. If you're an IT admin, go to the Microsoft Endpoint Manager admin center and delete the AAD device profile. 7/21/2020 : Screensharing from Chat window is now availablein GA (Ring4). Sharing best practices for building any app with .NET. Teams calls disconnects / dropped / terminated when users are logged There is a registry entry MSTeamsReditSupport, which is set every time you connect to your VDI with Citrix Workspace. Then start Teams again. 8/11/2020 : Optimization is now available for Microsoft Teamsin GCC High. You can set your audio and video preferences for the meeting on the new device, then select Join. Block and Allowlist. Holly Lehman Upgrade your version of Internet Explorer. 2. Really appreciate the follow-up post with your fix. 1/26/2023 - The issue with the Intel graphics device driver has been fixed. Fix Microsoft Teams: Still Connecting to Remote Devices " or "Es gibt ein Problem mit Ihrer Verbindung. Endpoints using this driver can experience call freezes or disconnections in meetings or calls. For the scenario, deleting the AAD managed device profile cleared the issue on wdesk (Citrix VDI) for MS Teams Optimized client. Unable to call or video call in MS Teams - Microsoft Community Most likely, VDA Services (Citrix HDX HTML5 Video Redirection, Citrix HDX Teams Redirection) or in Workspace app.If there is no legendwith the word Citrix, then Teams did not load in VDI mode at all:The VDA regkey MsTeamsRedir is set by a Citrix service (CtxSvcHost.exe) when the user logs on or reconnects to the virtual desktop. In these VDAs, WebSocketService.exe can crash and cause Teams call failures ("Still connecting to remote devices. Relaunching Teams might be required. Der Anruf ist noch nicht verfgbar." in German. Public Microsoft Teams roadmap is available. Once there is a successful secure WebSocket (wss) connection, WebSocketService.exe will create a new process in the users session called WebSocketAgent.exe: This process can also be spotted in Director: The last part of this second phase is the establishment of the Teams virtual channel (CTXMTOP), and this process is ultimately handled by the Citrix HDX Teams Redirection Service (CtxSvcHost.exe in the VDA). FIX Teams: "Still Connecting to Remote Devices. What's new for security in the new Microsoft Teams? The issue is seen irrespective of the CWA or VDA versions. However, for those who, for technical reasons, must still connect via ID and password, this option is still available. Fix Microsoft Teams: You Can't Get There from Here, How to Fix Microsoft Teams Env_Check_Error. Call Device Used Audio: audio device used for the last active call, Call Device Used Video: video device used for the last active call, Call Duration Audio: last active audio call duration in seconds, Call Duration Video: last active video call duration in seconds, Call Duration Conference: last active conference call duration in seconds, Call Duration Screenshare: last active desktop sharing call duration in seconds, Call Establishment Duration Incoming: last active incoming call establishment in sec, Call Establishment Duration Outgoing: last active outgoing call establishment in sec, Call Type: Audio, Video, Conference, Screenshare, Version - Endpoint OS: not filled currently, Version - WebrtcCodec: webrtc codec version, 180,240,360,540,720,1080 (Teams supported Resolutions), {{ feedbackPageLabel.toLowerCase() }} feedback, Please verify reCAPTCHA and press "Submit" button, See HDX Microsoft Teams Optimization Crash or Video Freeze, HDX Microsoft Teams Optimization Crash or Video Freeze on newer Intel-based clients, keep in mind that Teams feature set is different when comparing optimized vs non-optimized, Media Engine multimedia stream processing, #1.1: Teams must launch in optimized mode, Teams conference servers are all hosted in O365, 4. Calling is not available yet"). This upgrade can take 24 hours to happen. I originally thought that maybe the user had an active remote session at home, after checking any active remote sessions and even doing a reboot of the system this error still comes up. Use a room remote to control a Teams Room device [HDX-24350]. explicit proxies or pac files).#3.3 RTP media flowsIf the connection was established using TCP through a TURN server, you will not be able to decode the traffic in Wireshark as RTP since it is encrypted using TLS.In case of a peer-to-peer connection or conference via UDP, then Wireshark will show more detailed info that can be used to understand the traffic flow between the participants.Wireshark recommendations:RTP cannot be automatically analyzed by Wireshark.