Mar 24 2022 10:55 AM - edited Mar 24 2022 01:42 PM
Hi all,
I'm attempting to sign in to a Polycom CCX VVX 411 desk phone I have onboarded to the Teams SIP Gateway by following the instructions here. As far as I can tell, the device has been configured correctly; it's got the Teams background image and when I press the Sign In button, it displays the https://microsoft.com/devicelogin sign in URL and pair code.
When I visit the URL, enter the pair code, and sign in with my credentials, the web page says that I have successfully signed in. However, nothing happens on the phone. I've made multiple attempts from a couple different phones over the past few days.
I've got a ticket open with Microsoft 365 Support, which is going about as well as you would expect. Is it just me, or are others having this issue as well?
Edit: I mixed up the model name.
Mar 24 2022 01:40 PM
Mar 24 2022 01:42 PM
Mar 30 2022 03:16 PM - edited Mar 30 2022 03:17 PM
Am I getting no replies because it's working fine for everyone else, or is nobody else using this feature? :)
Mar 31 2022 12:24 PM
SolutionApr 01 2022 03:34 AM
May 18 2022 08:06 PM
I bumped into this issue too recently. It was working months ago but unfortunately not now.
I've confirmed the SIP Calling was enabled on the call policy. So we may need to drill down further with Microsoft Support.
May 19 2022 09:34 AM
@Andy_Chau I discovered this article the other day; perhaps you may find it useful:
Common issues when using SIP devices with Teams - Microsoft Teams | Microsoft Docs
May 27 2022 08:14 AM
Sep 12 2022 07:58 AM - edited Sep 12 2022 07:58 AM
I have found a solution to this issue that seems to work. I'm using Poly VVX 410/411 phones as Common Area Phones via the SIP gateway.
I found that with some newly-created CAP user accounts, I would log into the account using https://microsoft.com/devicelogin but the phone doesn't do anything except to continue to display the code. Eventually the code display times out and the phone returns to the login screen.
I discovered that the CAP user account didn't have a phone number assigned, even though I had set the number using PowerShell. I assume I had tried setting the phone number too soon after creating the user account and background processing hadn't completed yet. I re-assigned the phone number using the Teams Admin center under Manager users and the phone now completes the login and provisions itself in Teams as expected.
Sep 12 2022 06:20 PM
Sep 13 2022 10:27 AM
@Andy_Chau Having MFA authentication enabled won't prevent a user from signing in to the Teams SIP Gateway. However, if you have a Conditional Access policy configured that restricts the locations a user can sign in from, you do need to make sure the SIP Gateway IP addresses are allowed, as documented here.
Jan 27 2023 01:36 PM
Jan 27 2023 02:56 PM - edited Feb 05 2023 12:55 PM
@Olusteve There is a known issue which affects devices that were enrolled in Poly Lens while they were signed in to the 3PIP server. When the factory reset is initiated, the phone backs up its local configuration to Lens, and these settings get written back to the device after the reset completes. This breaks the SIP gateway configuration. Could this be impacting you?
The workaround is to delete the device from Lens, then re-enroll the factory reset device. More info in my comment on this blog post: Upgrade Skype for Business Online (3PIP) phones to Microsoft Teams using SIP Gateway - Microsoft Com...
Jun 13 2023 08:52 AM