Watch and subscribe on YouTube.
We discuss:
- Microsoft Teams will support standard SIP phones in the first half of 2021
- Microsoft Teams lower cost basic IP Phones and USB Phones
- Avaya Session Border Controller for Enterprise (Avaya SBCE) certified for Microsoft Teams Direct Routing
- Microsoft Teams Rooms and Surface Hub working together with Coordinated Meetings
- Microsoft Teams PSTN Call Records Log / Bill from Microsoft Graph API
- NDI with Microsoft Teams rolling out
- Teamsfest - 7th October
This month's Microsoft Teams News Update is sponsored by Ribbon Communications.
Thanks for watching, if you'd like more like this, don't forget to SUBSCRIBE to our YouTube channel.
You can also join in the conversation on our Twitter, LinkedIn and Facebook pages.
Decoding the MS Teams September Update with Tom Arbuthnot
Every month we sit down with Office Servers and Services MVP and Microsoft Certified Master, Tom Arbuthnot, for a behind-the-scenes glimpse of what’s new with Microsoft Teams. MS follows a mid-year fiscal, and we expected September to be relatively quiet. “Everybody takes leave around this time, plus all the other world events,” Tom agreed. So, understandably, we were surprised that our discussion stretched into an incredible variety of topics – from SIP phones to old school handsets, from unexpected integrations to a couple of small but critical features.
Watch the video to know the full story (thank you, Ribbon Communications, for sponsoring the video). Here are the key highlights from our conversation, and Tom’s perspective on what lies ahead for Microsoft Teams.
Teams Support for SIP Phones to Help Save Significantly
Most of us think of standard SIP phones as legacy technology, quickly giving way to smarter VoIP devices. However, Microsoft isn’t ready to say goodbye to SIP just yet.
“Microsoft is going to natively support standards-based SIP phones against Teams,” Tom says. He also explained how this would work. “Many environments out there have investments in Cisco phones (or an equivalent). Microsoft is now going to support this in their cloud. You’ll literally take your Cisco handset, flash its standard SIP, register it against Teams, and have it work as a Teams phone.”
We wanted to understand Microsoft’s motivations for this update. After all, a standard Teams phone is far more feature-rich than a standard SIP device. “You got a fancy calendar, click-to-join, and all sorts of fancy features,” notes Tom. And the answer is pretty simple: from an accounting perspective, you can add on Teams capabilities without changing the base device.
“You don't want to spend $250 or $300 a desk, swapping a piece of plastic for a piece of plastic. From an accounting point of view, they're like, yeah, you pick it up, you talk you hang up. This enables you to move to the cloud into Teams and reuse that investment in those pieces of plastic on the desk basically,” Tom tells us.
Another reason is extending Teams’ support to the less-common 3PIP phones. According to Tom, 3PIP phones run a special firmware to register Skype for Business, which is scheduled for retirement. Many customers have bought tens of thousands of these phones, and they need a long-term migration path for that investment. “Microsoft will support customers who have sunk money in the Skype journey – bought those 3PIP phones – by giving them a longer life on Teams,” says Tom.
The final reason for providing SIP support was surprised us: some users still prefer handsets to headsets – or at least they think they do.
Are Old-School Handsets Making a Comeback? 🤔
“I see this all the time,” says Tom.
“Before people get the headset, they can't imagine using it! They're like, ‘no, I’ve always used a handset-based phone. I want a phone!’ So, the company provides a phone plus a headset. And then, people use the headset while the phone gathers dust. It's really hard upfront to convince users that they don't need the handset. But, companies can reuse the handset they’ve got with no additional cost. You solve that problem with Teams SIP support.”
There is a cultural issue here. For generations, we have equated telephony with a handheld device, and that continues to be an initial expectation for users.
Instead of forcing adoption, Microsoft’s foray into SIP is a clever way to circumvent the issue. On similar lines, Microsoft has also brought back its old-school USB handset that will now work with Teams. “It looks like an IP handset, but doesn't have the guts, doesn't have an ethernet connection – it just has a USB cable that goes into a PC. The PC is doing most of the brainwork of it. But physically, you have dial buttons, a screen, and a handset. Again, the perception is – I can get one of those cheaply. I've already got a PC, my users want the “phone” form factor, they don't wear a headset, and they want to pick up the phone. They could do that with this USB device,” Tom breaks down this use case.
We were curious to know about Tom’s own experience with USB handsets, and if there are benefits apart from novelty or familiarity (depending on how you look at it).
“I would never use it because I’m a headset user really. However, there are some users who don't like the idea of headsets but have a wired-in permanent PC. So, there's no reason why they couldn't use a USB device,” he said. “But it's really a cost play. If you want an IP phone and can afford it, you’d probably buy a proper IP phone, with Power over Ethernet (POE), a dedicated network connection, and dedicated hardware. However, sometimes they just want the form factor at a low cost,” he adds.
SIP for Microsoft Teams will necessitate new partnerships and a degree of interoperability – what does this mean for long-time competitors?



