This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 8%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBD%3C/text%3E%3C/svg%3E)
Hi,
I try to use the new sip gateway with a polycom vvx210. I made all the configuration and so far, the phone receive it configuration and it show in teams admin.
But I'm unable to sign-in. I use the page microsoft.com/devicelogin with the code, login with my account (with a phone system licence) and get the page saying that I can now close the page.
But after that, noting append on the phone. I just said - press "sign-in" - and the phone stay "disconnected in the admin teams console.
Any Idea?
Ok, after some test, I can log-in with a standard user.
But I am still unable to sing-in as a common area phone user to a SIP device.
any Idea?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 77%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EI%3C/text%3E%3C/svg%3E)
Hi Ben, did you ever come across and answer to this. I was just trying this as well, and had the same result... a regular user will work, but common area phone user will not.
Hi Paul,
Yes, I manage to have it working. first, I wan't using the north-america server.
After that, I follow the instruction down there (send to me by Ms support):
Configure Phone Policies
Simply assigning a Common Area Phone license to a user account will not apply the Common Area Phone experience as licenses only control what online services and features are available to the account. A custom IP phone policy must be setup in the tenant and then assigned to this user account in order to control the user experience on any phone it signs into. These policies are currently only configurable via PowerShell and are assigned to user accounts (not to devices) at the global level (by default) or the user level.
First determine if a common area phone sign-in policy has already been created in the tenant.
NEXT
following
There are additional parameters on this policy which can be customized if desired. If common area phones are to be placed in spaces where non-employees may have access to them then it might not be ideal for them to be able to search for other users in the environment by name. Or a phone might need to always be signed in with a specific user and phone number and never as a different user, so the hotdesking option should be hidden. In Skype for Business some of these options existed and some could be controlled, but typically only at the global level. With user-based phone policies available in Teams it is now possible to create multiple policies with different parameter configurations for a much more granular level of control. For example, one policy could be created with CAP and search enabled for phones located in internal office spaces while another with only CAP enabled and with search disabled for phones in unsecure locations.
As an optional example this step will disable user search by removing the Search icon from the CAP interface.
Set-CsTeamsIPPhonePolicy -Identity ‘CAP’ -SearchOnCommonAreaPhoneMode ‘Disabled’
After that, I can add the phone to the interface, activate it with the code *55*123456 (where 12345 is the activation code on teams admin) and finnaly login with a CAP user.