Teams - Group Group Pick up/Delegates
Hello I need some help to understand these features as I am not sure that I understand them correctly. Currently, if I set the group group pickup feature (either through the Teams admin or user driven), then the phones ring the main number and the other users, or one after the other, very similar to a call queue. I have users that want to be able to pick up a call from the colleague. When their colleagues phone rings, they want to be able to pick that call up, not have their phone ring after 20 seconds or so of the opther phone ringing. Am I missing something or is that not available? Also, I have the same question in regard to a call queue. I can get the queueing working fine, but can a member of the call queue pick then call up when thewir phone it not ringing? same as above really? Thanks RIchardNDI audio sync issue
Hi, I recently ran a live event using the NDI function of Teams to pull out the speakers and manipulate them in OBS (layouts etc) and then put into a public Teams Live event. The issue I encountered was with the NDI feed and audio / video sync. Each NDI feed brings in the entire audio feed from the meeting but what I have found is that the audio is only in sync with the video of that feed. To try to explain this clearly, let's say I am pulling two presenters out of the Teams meeting. NDI feed 1 has presenter 1 video and the audio mix NDI feed 2 has presenter 2 video and the audio mix If I have both NDI feeds side by side, and only have the audio of feed 1, presenter 1 is in sync with the audio but presenter 2 is out of sync with audio. If I have both NDI feeds side by side, and only have the audio of feed 2, presenter 1 is out of sync with the audio but presenter 2 is in sync with audio. I obviously can't have both NDI feeds unmuted as the audio doesn't match at all. I can work around this by taking the audio directly out of the meeting (where everything is in sync) and bringing into OBS directly and bypassing NDI. But that just seems silly. Any thoughts? I'm assuming other people see this same issue. Thanks DamienNon-optimized VDI Policy Teams
We are having a bit of a problem with VDI policy application in Teams. We are running Server 2016 terminal services (no Citrix) in the full desktop experience and don't currently run Teams in this setup. We run Teams separately on individual local PCs. Teams is an important LoB application for us as we use it as our complete telephone system. We want to run Teams in our RDS environment as well as on local PCs to get the benefit of integrated chat, Outlook, colloaboration features, etc. Essentially we want the entire Teams experience in RDS, except for audio and video features. This seems entirely possible, but doesn't seem to be working. We have used the IsWVDEnvironment registry key to allow us to install Teams as a machine-wide per machine instance using the current msi with the ALLUSER=1 switch. Teams installs and runs completely in RDS in this way. We have also created a Teams VDI policy in powershell and assigned it to our users. The policy disables audio and video in calls and meetings using the CsTeamsVdiPolicy cmdlets. The policy applies to the required users and we can see that when we query the user via powershell. However, the two things do not join up. When a user signs in to the terminal server via RDS Teams loads in the normal experience. Video is disabled because there is no redirected camera, but since audio is redirected through the rds session the calling option is there. It is as if the Teams VDI policy has not applied to this instance of Teams. Just to confirm, our VDI policy disables all calling features in the non-optimized environment: Identity : Tag:DisableCallsAndMeetingsTrue DisableCallsAndMeetings : True DisableAudioVideoInCallsAndMeetings : True MS does clearly state that the policy will only apply to non-optimized VDI environments. RDS is barely supported for Teams and we have no optimization features in place for it. I'm not sure how to tell if it is technically a VDI optimized environemnt or how we can specifically set it to be non-optimized so that our policy applies to the Teams instance? I hope that all makes sense. Does anyone have any experience of the Teams VDI policies and how we can make sure they apply in the right instances? Thanks
