As a multi-national organization, it would be nice to have functionality that allowed all users to receive calls from local numbers. We have several conference bridge phone numbers, one for each country we operate in, but for some reason it is impossible to configure multiple "default conference bridge numbers" (the number that shows up on callerID when you add someone to a Skype call).

We can set default conference bridge per user, but this currently only affects the default bridge included in their meeting invite....it doesn't change the bridge that gets used when calling out to add people to a meeting.

Multiple fixes could be done. You could allow the user to explicetly choose the bridge used for calling out. You could use an algorithm to select the "nearest bridge" based on the phone number being dialed (i.e. if US number is dialed, use the US bridge).

After having over 2 years of enterprise experience with SfB-Online automation, talking about Cloud-only solution for over 50k employees cannot believe it is part of the same MS suite as Azure products.
I am really keen to see MS Teams supporting Graph API for all types of identity provisioning including telephony management without 30 years old limitations i.e.:
-throttling (only solution now to use several Admin accounts)
-lack of object layer transparency (unable to create efficient serialization to build enterprise level solutions)
-old dog new tricks (SfB supports OAuth authentication only by passing "password" as password and bearer token as username)

Would be happy to see:
-Teams Graph API being part of Microsoft Graph responding highly efficiently to RESTful requests (NO WINRM)
-Proper object layer documentation handled by online community leveraging GitHub and other modern solutions
-Modern authentication rather than username/password support behind privileged product operations

We have been using Skype Voice and now Teams as our voice solution for couple of years now.

It is still shocking to me the lack reporting available to organization about incoming calls to individual, and call queues. These are essential tools used frequently by organizations to analyze call volume and make decisions accordingly.

As an administrator or manager, I would like to be able to reports to see the number of call made to a certain user or users in my department. The call duration, whether it was answered or not and some other relevant information.

Equally important, I would like to run a report that show me similar information for call queues. Why is this area so behind in Teams compared to other voice service providers?

How long do we need to wait for this? 2025?

• When someone calls the call queue and clicks on the headphone to "accept" the call in MS Teams everything works fine.
• If someone calls the call queue and DO NOT click the headphone in MS Teams, but outside (as in the attached picture), 
then the call seems to be accepted, HOWEVER
o The call was not put through
o It does not even ring with the other participants.
o The caller is still waiting for someone to answer the call
o But this is only with call queue calls like this: if someone calls me directly and I click on any area, I take the call and it works.

With Skype for business we have used Poly's PDMS server to manage the IP phone devices. This also includes the ability to do a screen capture to see what is on the actual poly device's screen. Also they had the ability to do call control so that we could make the phone place a test call. These are both great assets in troubleshooting. When it comes to native Teams phones, can we either get these features native in the panel or just add a setting in phone config to push out the address for the PDMS server once it logs into Teams.