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 created a new dialplan to also include extension dialing and to make the step towards Teams Phone System smaller. The problem is that this dialplan is not working in the Teams Client, though the Get-CsEffectiveTenantDialPlan -Identity mailto:xxx@yyy.com command tells me that the dial plan is correctly applied to the user. It is not client related, as I have the same issue on my Audiocodes C450HD phone and my Teams App on my mobile. Any ideas?

Hello rbuedi, so the External Consultant who has GREAT knowledge about the SBC and SIP told me that I did everything right with the Dial Plan, he also doesn't know what exactly is going wrong here... but he has also told me that MS is not his strength and gave me the name of someone else to contact.For now, we have made rules on the SBC (Audiocodes Mediant VE hosted in Azure) to translate the rules and so on but I think this is not the way to go because it is to much manual work... so I will do this now with the SBC but also will keep trying to find a solution for the Cloud Phone System (Teams) to do this.I will keep you in the loop 🙂 BrS

Hi, Can you send an example of the Dial Plan that doesn't work? Do you have any other custom Dial Plans that does work or can you create a new simple one and test that one. It could be something wrong with the DP you created.

LinusCansby This is the first dialplan we have created.This what I have:NormalizationRules : {Description=BE-Service;Pattern=^\+?(1\d{2,3}|116\d{3})$;Translation=1200$1;Name=BE-Service;IsInternalExtension=False, Description=BE-Extensions;Pattern=^(\d{3})$;Translation=3201$1;Name=BE-Extensions;IsInternalExtension=False}ExternalAccessPrefix : 0OptimizeDeviceDialing : False Should be straight forward. I have done a test in PS and this works:PS C:\Users\[]> Get-CsEffectiveTenantDialPlan -Identity xxx@yyy.com | Test-CsEffectiveTenantDialPlan -DialedNumber 112TranslatedNumber : 1200112MatchingRule : Description=BE-Service;Pattern=^\+?(1\d{2,3}|116\d{3})$;Translation=1200$1;Name=BE-Service;IsInternalExtension=False

Hi, Sorry for a late answer. The Translation should be a E.164 number, ex: Translation=+3201$1. If not and you dial 123 will end up calling +323201123. I see that you have a ExternalAccessPrefix, is that intentional? If you from your client dials 300 what happens?

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

Team Dial Plans not working in Teams Client

12 Replies

LinusCansby
MVP
Feb 17, 2020
Hi,

Can you send an example of the Dial Plan that doesn't work? Do you have any other custom Dial Plans that does work or can you create a new simple one and test that one. It could be something wrong with the DP you created.
- rverbiest
  Copper Contributor
  Feb 18, 2020
  LinusCansby
  This is the first dialplan we have created.
  This what I have:
  
  NormalizationRules : {Description=BE-Service;Pattern=^\+?(1\d{2,3}|116\d{3})$;Translation=1200$1;Name=BE-Service;IsInternalExtension=False, Description=BE-Extensions;Pattern=^(\d{3})$;Translation=3201$1;Name=BE-Extensions;IsInternalExtension=False}
  ExternalAccessPrefix : 0
  OptimizeDeviceDialing : False
  
  Should be straight forward. I have done a test in PS and this works:
  PS C:\Users\[]> Get-CsEffectiveTenantDialPlan -Identity xxx@yyy.com | Test-CsEffectiveTenantDialPlan -DialedNumber 112
  
  TranslatedNumber : 1200112
  MatchingRule : Description=BE-Service;Pattern=^\+?(1\d{2,3}|116\d{3})$;Translation=1200$1;Name=BE-Service;IsInternalExtension=False
  - LinusCansby
    MVP
    Feb 21, 2020
    Hi,
    
    Sorry for a late answer. The Translation should be a E.164 number, ex: Translation=+3201$1. If not and you dial 123 will end up calling +323201123.
    
    I see that you have a ExternalAccessPrefix, is that intentional?
    
    If you from your client dials 300 what happens?

Forum Discussion

Team Dial Plans not working in Teams Client