Microsoft announced today (16th Feb) that they'll be "enhancing" the sign-in experience for Teams SIP Gateway devices.
There's not a whole load of detail published so far outside of the message center post so there's nothing much to explain other than what Microsoft have announced here as the improvements.
The ability to authenticate once and pair multiple SIP devices sounds like a nice feature, I assume this will be a time bound access period where you'll not need to go through the full sign in process to authenticate to SIP Gateway (username/password, any MFA prompts, confirm you're signing into SIP Gateway etc).
The other feature which is interesting is the last one around seeing any pairing related errors such as policy assignment or missing phone numbers. I assume this relates to the pre-requisites you need to be able to sign in to a SIP Gateway device, such as having "SIP devices can be used for calls" enabled in the users assigned Teams Calling Policy and having a valid DDI number assigned to the user.
Not having these things correctly configured currently means you don't get any notifications on the device and once you go through the sign in process, the phone just sits there and doesn't do anything. I've learnt that the hard way before wondering why a SIP device isn't signing in and then remembering I've not enabled the user for Enterprise Voice and assigned an number or not enabled that setting in the Calling Policy. I assume the device will alert you to the issue now rather than just ignoring you!
The other two points mentioned sound like bug fixes/application improvements rather than feature updates.
The additional information link just takes you to the Microsoft page on how to configure SIP Gateway and it currently doesn't look like any new information has been posted there in relation to this update.
I'll come back and update the article if further info is provided
Comments