Dec 12 2018 09:44 AM
Dec 12 2018 09:44 AM
Are there any updates on when NATIVE Teams Desk Phones will be available for purchase? Per this MSFT Page, Everything is either COMING SOON or shipping with SfB Client using Teams Gateway & will be upgradable via free software update "soon". Users of the "fastest growing MSFT BIZ app of all time" are hungry for NATIVE Teams experience deskphones - do we have a firm date when the YEALINKs will GA? YeaLink seems to be the closest to going to market (not to mention the Crestrons are built on YeaLink hardware).
Still surprised that Polycom says they won't have anything until Q2 2019, thats a huge miss.
Dec 12 2018 09:47 AM
Dec 12 2018 10:27 AM
Benjamin, We have many customers using both the Teams client Softphone (PC and/or Mobile) with a bluetooth earpiece or headset -AND- SfB endpoints (legacy or new pre-Teams) via the gateway successfully. However, the appetite for the Native Teams Experience on deskphones is huge especially for org's like yours who are replacing a on-prem PBX or inferior Hosted Voice solution. Hopefully something will GA very soon.
Look us up when you are ready to move - we provide a unique Teams PSTN calling plans solution (shared trunks instead of per user plans). Thx, email@example.com
Dec 12 2018 10:41 AM - edited Dec 12 2018 10:42 AM
Also, the deskphones on the below page say "Power Supply Optional" but does not give you an option to add it when ordering. So can I assume that these endpoints (which appear to be sourced via "UnifiedCommunications.com official partner of the Microsoft Teams devices marketplace") are PoE only and if so how does one add the optional Power Supply?
Ilya Bukshteyan perhaps you can answer?
Dec 18 2018 10:33 PM
Hi Gary, Two of our Yealink phones just became available last week. You can check them out at: https://products.office.com/en-us/microsoft-teams/across-devices/devices/category?categoryid=c6536b3...
Dec 19 2018 08:48 AM
Thanks for the reply.
Are you referring to the T56A, T58A Teams devices that have been shipping for a couple months now? Per my thread, Yes those are Teams devices but to the best of my knowledge are still shipping with SfB software and using the Teams gateway. According to my contacts at YeaLink those phones should GA with the NATIVE TEAMS software before end of this month. Do you have different information? Thank You
Dec 19 2018 10:24 AM
@gary woods Native Teams phones from Yealink (desk phones and conference room phones) and Crestron Mercury are currently under certification. We expect certification to be complete before EOY. As you mentioned, the firmware on the marketplace is Skype for Business but it can be updated to Teams when we complete certification.
We expect Crestron desk phones to GA early next year (Q1CY19).
Jan 22 2019 03:47 PM
Jan 24 2019 10:01 AM
A few more thoughts on Native Teams endpoints for this thread. Please share any feedback if you have similar experiences. Lots of activity on Social Media from YeaLink & Crestron saying they are ready to go but here are a few of the challenges our customers are bringing up;
1- None of the distributors/VAR's/etc seem to have the phones ready to sell. MSFT's own sales channel (via UnifiedCommunicaitons.com) is still showing SfB devices upgradable to Teams, NOT native Teams. Two very large distributors that we use both said they are 30 days out (that is 6 weeks after the Native Teams phones GA'd).
2- Customers with upgraded endpoints are still lacking the ability to make a 3 way PSTN call from the phone (although it works from their Teams softphone - calling plan and audio conf lic required).
3- CP960 not showing meetings and occasionally "spinning circle" locks up the phone for a few mins at a time.
Jan 28 2019 06:56 AM
Aug 06 2019 01:47 PM
@steve_ci Intune has a feature in TAP that enables customers to apply one set of policies for Android smartphones and another set of policies for Teams IP phones. This should allow tenant admins to not require encryption for Teams phones. Please DM me your customer name, and if they are interested, they could get onto the TAP program to test this feature out.