Forum Discussion
Teams Phone Numbers Mysteriously Unassigned
Over the last 2 weeks or so, we've noticed a handful of our Teams phone numbers which were assigned to users, become Unassigned. We have no automation in place - everything move, add or change we p...
That's very interesting...and unsettling! Did this happen with using Operator Connect? If so, who is your Operator Connect vendor? or did it happen with numbers provided directly by Microsoft? Thanks a bunch for replying!
dennyhanrahan I'm not familiar with Operator Connect, but a quick Google shows these providers offer Session Border Controllers as a Service (SBCaaS) so our setup is similar.
We are using Session Border Controllers and Direct Routing. Our carrier is Optus.
We have reserved number ranges for each of our offices, and these number ranges are hosted by Optus. We pay Optus for our call charges (not Microsoft).
We are facing the same issue. We do run Operator Connect but have been able to check and see there have been no changes through iPilot. It's very frustrating that there aren't activity logs to go back to on the MS side. We thought we've been going crazy since we asked MS and they said there is no way that should be happening.
- Thanks MarcR727 for your feedback! I did get a root cause from Microsoft that it was a bug fix: The AD attribute OnPremLineUriManuallySet bit was false due to the bug. There was a bug in the legacy TAD cmdlet because of which assigning OC number did not set OnPremLineUriManuallySet flag.
- Good to know, thanks Denny. I have a case open with Microsoft for this issue but they didn't mention that. I'll add your info to the case notes.
