Forum Discussion

rverbiest's avatar
rverbiest
Copper Contributor
Feb 17, 2020

Team Dial Plans not working in Teams Client

Hi All,   We are in the process of setting up a pilot for Teams Direct Routing. Direct route is working fine and all is working when using the default Service Country plan for Belgium.   I have ...
microsoft teams
nirispa's avatar
nirispa
Copper Contributor
Apr 09, 2020

Hello,

I would like to continue this thread because I currently have the same issue.

As the person described before me the rule seems to work at least when checking with Powershell.

 

When I actually try to call lets say 499, the number changes in Teams to just +43 499

 

And not to the number that I have set with the rule.

 

I hope it is okay to continue this thread because I have the same question 🙂

 

BrS

LinusCansby's avatar
LinusCansby
MVP
Apr 09, 2020

nirispa So, I guess you are located in Austria. So the normalization for Austria kicks in. The number will always be in E164 format when it leaves Teams. So your normalisation rule have to do that. 

  • nirispa's avatar
    nirispa
    Copper Contributor
    Apr 10, 2020

    LinusCansby 

     

    This is correct.

    My normalization rule should add +43XXXXX before the number if it is a 3 Digit extension.

     

    So it should've been+43XXXXX499 and not  +43499 which it is, so there is something wrong here.

     

    I don't have a dial plan besides the global default one.

     

    BrS

    • rbuedi's avatar
      rbuedi
      Copper Contributor
      Apr 28, 2020

      @nirispa Did you get this solved? I am stuck with exactly the same issue. Using PowerShell and checking the policy for the User, everything works perfectly fine. But in the Teams Client, it does not. I even waited for 24 hours now, just in case it takes time for the Teams Client to pick up the policies. No change...

       

      A small edit: When looking at the Dial Plan via PowerShell I see 3 additional normalization rules on that User which I can not see anywhere in the Admin interface. Are there additional normalization rules on a tenant level maybe which are causing our problems?

      • nirispa's avatar
        nirispa
        Copper Contributor
        Apr 28, 2020

        Hello rbuedi,

         

        yes I do still have this issue, Microsoft couldn't help me so far.

        I hae also found the "additional" Normalization rules, those are provided automatically and depend on your "Country" settings in Office365. So this is the "Service Country" dial plan.


        More about dial plans:

        https://blog.kloud.com.au/2019/09/19/inheritance-in-office-365-tenant-dial-plans/

         

        I'm still trying to find a solution and I will have a meeting soon where I might get this solved and will share the solution here 🙂

        BrS