Forum Discussion
Shared calling policy enabled user can not login to teams sip gateway enabled phones like VVX400/500
We have enabled shared calling policy with Rogers Operator connect and assigned to users, which works great but while logging in to sip gateway enabled device like Polycom vvx400s/500s it throws erro...
looks like Microsoft has on roadmap to remove the requirement of extension for sip-gateway registration. No timeline at the moment
Ideally they'd allow us to assign just an extension for internal calling but remove the requirement either way for a unique phone number for SIP Device sign-in.
- Can you please share link to this roadmap item here? Thank you.
- sorry, this roadmap is not published public. I will publish here, if available
Any update on this? I have several tenants that want to move to Teams phone but we need this feature first.
I've migrated a few customers that only use the teams app for calling and shared calling works great for them.
But I have a few customers on Cisco Call Manager Express that want to move to teams but all outgoing their calls go through 1 or 2 main numbers with each user having extensions. DID numbers for each user is just a waste of numbers since they're never used. They already use teams internally and have all AA's and CQ's set up with shared calling using dummy numbers. We're just waiting to port the actual main numbers, migrate the phones to teams once this features is enabled.
