Forum Discussion

dennyhanrahan's avatar
dennyhanrahan
Copper Contributor
Jun 15, 2022

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...
calling
Phone Number
teams voice
wombattler's avatar
wombattler
Copper Contributor
Jun 30, 2022

dennyhanrahan Same problem. I thought I was going mad. Started 4-6 weeks ago now.

Long term users complaining their dial pads have disappeared. When I check Teams, the number has been unassigned.

dennyhanrahan's avatar
dennyhanrahan
Copper Contributor
Jun 30, 2022
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!
  • wombattler's avatar
    wombattler
    Copper Contributor
    Jul 01, 2022

    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).

    • MarcR727's avatar
      MarcR727
      Copper Contributor
      Jul 12, 2022

      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.

      • dennyhanrahan's avatar
        dennyhanrahan
        Copper Contributor
        Jul 13, 2022
        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.

Resources