Teams Phone - "You're not setup to use this feature"
We are testing out Teams Phone for our org. I keep getting the same message when trying to dial an outbound call with a Poly CCX400 device. Here's what I've done so far: Acquired number from MS, and assigned it to "Main Line" resource account as voice app Configured our "Main Line" resource account with a calling plan and resource license Assigned Main Line to "Auto Attendant" resource account Created an Entra group called "Teams Phone Users" and added users with Teams Phone license Assigned Entra group to an outbound call queue that has the "Calling ID" set to the Main Line Configured custom policies for Calling, Caller ID, and Shared Calling, and assigned to Entra group Enabled setting "SIP devices can be used for calls" under the custom Calling policy Made sure Poly phone profile was setup as "Teams" and not "Generic" or "USB optimized" Signed into Poly phone using "Front Desk" user with Teams Phone with Domestic Calling license Enabled "Enterprise Voice" for Front Desk account Verified shared number was showing under the Front Desk account I have still not been able to make an outbound call with the Front Desk account on the Poly phone using that shared primary number. Does it take some time for the settings to update throughout Teams? If I look at the Activity Log, I can see that my "Shared outbound calls" policy is still "Rolling out to users." Thanks in advance for anyone who reviews this and tries to help!1:1 calls, user is muted as soon as PSTN ringing starts
This only occurs on certain headsets, and started for our users after yesterday's Windows patch went out (10/19/2021). We're on Windows 10. User has Bose headphones; haven't confirmed if they are certified device but they've been working great until yesterday. Now when the user makes a call in Teams via PSTN (we have direct routing), as soon as the call is initiated the user is put on mute. This is a 1:1 phonecall initiated by the user, not joining a meeting where the client mutes you (and notifies you). When the user joins another meeting or makes a 1:1 call to another Teams user, it works fine. It only does this when it interprets that it's a phonecall, and the bluetooth headphones put it in mute. Has anyone else seen this, or know of any controls in the Teams app that can control this? There is no error, it's just a default behavior that I think should be changed, or there's a bug somewhere. The user can only tell because they can see their microphone icon showing it's muted, as soon as the call starts. They have to manually unmute their phone call (that they just initiated) every time they call out to PSTN or anything across Direct Routing link.
How to get a list of UNASSIGNED Teams Phone numbers
I haven't been able to figure out to get a list of unassigned Teams phone numbers. I am trying to do it with Powershell and I don't see a cmdlet that allows me to do this. We have numerous numbers that have been unassigned from users and I'd like to see what numbers are available for reassignment. If you have a way, I would very much appreciate some help. 🙂Teams Phone Needs 1st Party Call Center Native Dashboard Out of Box
We are a loyal customer of your Teams phone service, and we appreciate the many features and benefits it offers for our communication needs. However, we would like to request two important functionalities that are currently missing or inadequate in your service: Parked Calls and Call Center Dashboard. Parked Calls is a feature that allows us to place a call on hold on one device and pick it up from another device, using a unique code. This is very useful for scenarios where we need to switch devices, transfer calls, or collaborate with other agents. We know that you have some options for call parking in Teams, but they are not sufficient for our needs. For example, the Connect model requires us to use certified SBCs and Direct Routing, which adds complexity and cost to our infrastructure. The Extend model requires us to use Azure bots and Microsoft Graph Communication APIs, which are not easy to implement and maintain. The Power model, which promises to use an SDK to embed native Teams experiences in our app, is not yet available. We would like to have a simple and seamless way to park and retrieve calls within Teams, without relying on third-party solutions or complicated integrations. The Call Center Dashboard is a feature that allows us to monitor and analyze the quality and performance of our calls and meetings, using metrics and KPIs. This is very important for us to optimize our network, troubleshooting issues, and improve customer satisfaction. We know that you have a Call Quality Dashboard (CQD) for Teams, but it is not designed for contact center scenarios. For example, CQD does not provide real-time data, agent-level reports, call recording, or customer feedback. It also does not support advanced analytics, such as sentiment analysis, speech recognition, or natural language processing. We would like to have a comprehensive and customizable dashboard that can provide us with the insights and tools we need to manage our contact center operations effectively. We believe that having these two features as 1st party solutions in Teams would greatly enhance our experience and productivity as a contact center. We also think that these features would benefit many other customers who use Teams phone for their business communication. We hope that you will consider adding these features to your roadmap and prioritize their development. Thank you for your attention and support.
Teams setup issues
Hi all, I'm hoping you can help. I've tried using over the phone help but they aren't quite understanding what I'm after. I run a small business with one other person. We have our primary business number which is associated with a teams account (which we share over a number of devices). All I want is a greeting message before the phone rings! However, I've set up an auto attendant, while this fixes this, it also assigns a new number. When I make an outgoing call, it only allows me to call from the Autoattendant number, not the main number which our clients call. Obviously I want to mask the Autoattendant number but it won't let me do it for some reason. Does anyone have any ideas where I might be going wrong? Thanks 🙂Teams on smartphone should only ring if connected to company WLAN
Hello, I have a client who wants to switch to Teams with their telephony. The company would like to have the following for certain people: - The smartphone should only receive incoming calls when connected to the company WLAN. However, if you are outside the network, you should simply be able to make calls, but not receive calls. Is there a way to configure this? So far I have found this from Skype for Business, where you can set a policy with WifiOndly. https://learn.microsoft.com/de-de/powershell/module/skype/set-csteamsmobilitypolic New-CsTeamsMobilityPolicy -Identity "Test-WifiOnly" -IPVideoMobileMode WiFiOnly Grant-CsTeamsMobilityPolicy -Identity email address removed for privacy reasons -PolicyName "Test-WifiOnly". However, this policy does not work in my tests either. What options are there for configuring this?
Teams Phone at Work and Home
We have a situation where several employees work from the office and from home. What is the best way to handle their Teams phones since they all want a physical phone in both locations? I do not see any way to assign a location to a device, which impacts e911 setup. Dynamic location lookup also doesn't seem to be an option since each of the home networks is not controlled by the company. I know setting up duplicate users, whereby I can assign a number and phone to each user, then setup a resource group per user such that both phones ring, etc., but what are the pitfalls of this approach besides having to pay for another license? Is there a way to do it with a single user ID?
