Forum Widgets
Latest Discussions
Not receiving any notifications in my Samsung S26 Ultra
Hello, Since I moved to Samsung S26 Ultra, I am not getting any notifications. Following are my settings. Please help to fix the issue. Following are settings in Samsung phone Following are settings in my Teams app in deskop Following is the settings set for all my channels Thanks
Direct Routing PSTN calls to Teams Auto Attendant does not forward to Shared Voicemail
Hi all, I’m running into a strange issue with a Teams Auto Attendant and I’m hoping someone here has seen it before. We have a Direct Routing number where business hours calls go to a Call Queue, which works, and after hours calls should go to Shared Voicemail for a Microsoft 365 Group. If I call the Auto Attendant from inside our Teams tenant, the after-hours Shared Voicemail works correctly. I can leave a message and the voicemail is delivered to the group inbox as expected. If I call the same number from the PSTN over Direct Routing, I hear the after-hours greeting, so the schedule and call flow are clearly being hit, but once the greeting finishes I get: “Sorry, we cannot connect your call at the moment, please try again later.” I have already verified that the resource account has the correct Teams Phone Resource Account license, Enterprise Voice is enabled, the LineURI is assigned, the Online Voice Routing Policy is assigned, the Direct Routing route and SBC look healthy, the Auto Attendant is associated with the correct resource account, the after-hours call flow points to the correct Microsoft 365 Group, and the group mailbox exists and is healthy. What makes this more confusing is that redirects to internal or tenant-side destinations work, but redirect to Shared Voicemail from a PSTN-originated call does not work. I also tested redirect to an external PSTN number, and that fails with the same error as well. Because the after-hours greeting plays correctly, and because internal Teams calls can successfully leave voicemail in the shared mailbox, I do not think the issue is with the Auto Attendant configuration itself or with the Microsoft 365 Group mailbox. At this point it looks more like the handoff or redirect path for PSTN-originated calls over Direct Routing is where things break. Has anyone run into this with a Teams Auto Attendant, Shared Voicemail, and inbound PSTN over Direct Routing? I’m trying to figure out whether this is a known limitation, a bug, or if there is some specific setting related to PSTN-originated redirects that I am missing. Thanks!
Feature request: "AFK" status whilst on call
We would like to use Microsoft Teams calls as a continuously open call for long periods of time whilst working remotely as a team. However the current inability to visually see on the call screen whether another attendee is at their keyboard, without everyone having their cameras on all the time (which eats a lot of bandwidth) limits our ability to do so. I would like the ability to have an "away from keyboard" status, similar to the "raise hand" status, that can be set by each attendee when they step away from their desk/keyboard to grab a drink or take a comfort break. This could either be implemented by: adding a new group in which "raise hand" is one option, and "step away" is another adding a new option along the tool bar specifically for "step away" The only way to do this currently is to create another meeting (with yourself) and join that meeting so that you appear 'on-hold' within the previous call. This is very tedious to implement for every attendee involved.
Teams Desktop and Microphone
It appears I am flogging a dead horse here. My microphone works everywhere on my laptop except Desktop Teams I have tried every possible solution available in these discussions, and everywhere else on the Internet. Basically, they all take you through the same steps. It is not like I do not know how to solve hardware issues. I will never recover the amount of time I have spent trying to fix this. I have tried Windows troubleshooters (the ones still active). On Windows 11, using the microphone test available in System > Sound > Properties, it works 100%. The microphone works 100% using Teams web It works using onlinemictest.com Testing it in Teams (Make a test call), no sound is played back. . On closing, the microphone and speakers are ticked in green. This is a recent development with the latest Teams. I did not change anything. I'm aware of hidden issues like Teams concurrently running on your phone, etc. I recently reinstalled Windows 11, so it is not a driver issue. It is HUGELY frustrating. P.S. When I tried to publish this, using YOUR built-in editor, I got a notification. Your post contains invalid HTML. I had to go into the code to remove <span> tags!Stop Automatic Calling when Screensharing
I screenshare a lot in my position; I call the coworker (Phone/Headset) and train them on what I need them to look at. I am in a large office building, and the automatic calling of the receivers' PC is disruptive, as I do not was the whole office to hear my conversation or have people hear my trainee. I see no way to disable the team auto-call once I start to screen share or in the Options. All my coworkers feel this frustration as well. I do use the computer microphone/speaks aspect when working from home, but would disable it totally, if it would stop the auto-call. I do not want it to affect meeting invites to others, as others around the country can use their PC speak/microphone, if they want. Please advise.
Allow muting a person only for me
Sometimes I am in a meeting where one of the persons in the meeting is actually near me in the world outside the screen. In this case the sound is a bit maddening since there is a small delay between the sound from the person and the sound through the teams interface. In these cases, I would like to mute the person only for me since I am sitting near and can hear the person fine without headphones. Right now I need to takeoff headphones when the person is talking and putting it back as the person finishes talking.
