Teams Auto Attendant Calls Not Ringing Agents
Hello Community, We are facing a recurring issue with our Microsoft Teams Auto Attendant (AA) setup. Incoming calls to our main AA number do not ring the assigned agents' Teams clients. Instead, agents only receive a "Missed Call" notification once the caller disconnects or the AA timeout expires, even though the call never audibly rang on their end. We are looking for a reliable way to ensure calls are properly routed, audibly ring for agents, and are accurately logged for follow-up. Environment Details Platform: Microsoft Teams (Admin Center, New Teams Client) Licenses: Microsoft 365 E3/E5 for users; Teams Phone Resource Account licenses assigned to AA resource accounts Routing: Auto Attendant routes directly to a person within the organization Observed Behavior A customer calls the Auto Attendant number. The customer selects an option that routes to a person in the organization. The customer disconnects while waiting in the AA queue, or the AA timeout is reached. Agents see a "Missed Call" entry in their Teams activity feed, but no ringing notification or active call alert ever appeared in the Teams client. Troubleshooting Performed Microsoft Diagnostics: The M365 Admin Center diagnostic tool flagged the existing AA resource account as invalid and recommended deletion and recreation. Recreated Resource Account: Deleted the old resource account, created a new one, reassigned licenses and phone numbers, and re-linked it to the Auto Attendant. Despite these steps, the issue persists. We have an open case with Microsoft Support, but we are hoping the community might have additional insights or workarounds for this "ghost missed call" scenario. Questions for the Community Has anyone else experienced missed call notifications without the call actually ringing on the agent's Teams client? Are there any PowerShell configurations, Teams policies, or advanced Teams Phone settings that could be causing or resolving this behavior?Overriding Original Number in Call Transfer
Hello I have Teams with Direct Routing setup. I understand that in a call transfer, the phone number from original caller will be preserved up until the call reach to final transferee. But I have a case that this original caller number must be replaced by the Teams user's DID who does the transfer. I already disabled the Forward History, switching settings on Forward PAI even playing with Caller ID policy but still the original caller number shows up. I got recommendation doing it on SBC level but I will try as much as possible not to touch the SBC unless I really have to. Can it be done on Teams side or is it really need to be done on SBC level? Thank you in advance.
Please tell me how to disable the Pin Copilot message
Morning! I wrote a message yesterday but nobody replied, so here's another one so it doesn't get lost Can somebody tell me how to disable the annoying "Pin Copilot Chat" popup? every morning I have to say "Maybe Later" when I really mean to say NEVER IN A THOUSAND YEARS
Test call option not showing up in Teams?
Hi I've downloaded a personal version of Teams and need to test it. However, the 'Test call' option is not available? I've tried 2 methods: 1) typing 'Test call' in the search bar and pressing enter - nothing happens when I do this! 2) going to Settings then Devices then checking for the 'Test call' option - but it's not there! I've attached what I can see when I got to Devices and what I should be able to see (from a video I watched online) I'm using Version 1.4.00.22472 (64-bit). Can anyone please advise?
Camera works fine, except it won't transmit video in Teams
This problem is baffling me completely, and I've worked in IT Application support for almost 40 years. I hope someone can help me resolve it. A family member has a very important family court hearing to attend via Teams in a few weeks so I'd like to help her out. This is a Lenovo laptop (Ideapad 330S-14IKB) with a built in SunplusIT webcam. The camera works perfectly in Google Meet and Zoom, but not in Teams. I can see my own video feed on my screen but the other Teams meeting users cannot see my image. The camera is enabled in Teams. Some things I have already tried: Updated webcam driver from Windows Updated webcam driver directly from Lenovo site Ensured Windows 11 is up to date Checked privacy settings to ensure Teams app is permitted to use camera Uninstalled any other apps (e.g. Zoom, Skype) that may be using the camera Cleared Teams cache folders and restarted Uninstalled and reinstalled Teams Performed a partial Windows reset, retaining user data Performed a full Windows reset, erasing the hard drive Some other symptoms and things I've noted Camera works fine on my own Teams window and I can see my own image Camera transmits video correctly when the other party is on Android Camera stops transmitting video when other party is using Windows The same problem occurs using Teams in a browser web app, with either Edge or Chrome Screen sharing works fine Camera works fine in Google Meet (web) and Zoom (app) The problem persists if I log into the laptop with another user account The laptop has a fresh install of Office 365 What on earth is happening and what else can I try? I'm very technical but this has beaten me!Error code 0xA00F4244 NoCamerasAreAttached
The other day my integrated laptop webcam stopped working. When I opened the Windows native Camera App, I received the error code 0xA00F4244 NoCamerasAreAttached. I have an Asus Tuf Gaming F17 notebook running Windows 11 operating system. Typically in Device Manager, the camera showed up as USB2.0 HD UVC WebCam. I followed all the troubleshooting steps from the following Asus support site, https://www.asus.com/me-en/support/FAQ/109836/#Win11_A5 , with no luck. I also worked with Asus support but did not resolve the issue. After further investigation, I discovered the camera would disappear from the Device Manager when Microsoft Teams was open and running. When I quit the Teams application, the camera would re-appear in the list. I experienced this same behavior when using the Microsoft Teams Web Client. Is this related to a Microsoft Teams Update, or has this problem always existed? This is a new computer, and I do not have previous history with this issue.
Microsoft is removing the ability to dial 0 during a personal greeting in Teams Phone voicemail
An FYI for those of you using Teams Phone: We recently learned, due to customer complaints, that Microsoft is rolling out an update to the "voicemail bot" in Microsoft Teams Phone that takes personal voicemail messages. This new version of the bot has removed the ability for customers to press 0 to follow the configured opt-out (transfer) option for the mailbox (i.e. operator, call queue, etc). Pressing zero is ignored and does not interrupt the greeting. I'm specifically referring to setting VoicemailWithTransferOption with an associated TransferTarget. We see this as a customer service disaster that is not aligned with industry conventions or customer service best practice. We have pushed back strongly on Microsoft's decision making but they say that only a handful of customers have complained. This new bot is 70% rolled out to tenants as we speak. Microsoft customer support has associated our tenants to the "old bot" for the time being, but saying they are unsure how long they can maintain this as the rollout continues.
Client authentication EKU changes in public TLS certificate
Hi, Can someone clarify the upcoming change to remove the client authentication EKU and the conflicting information within MS docs for Teams Direct Routing certificates? As stated here from October 2025 there is an industry wide change to remove the client authentication EKU from issued TLS certificates: https://knowledge.digicert.com/alerts/sunsetting-client-authentication-eku-from-digicert-public-tls-certificates However, both server and client EKU's are required for mTLS and Microsoft states here that both server and client EKU's are required: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-whats-new#sbc-certificates-eku-extensions-test Digicert are offering an X9 PKI that includes both server and client EKU's but it seems the signing CA is not trusted by Microsoft at this stage. What guidance are Microsoft offering with this upcoming change to ensure that customers are not affected when renewing their certificates?
