Forum Discussion
Team Dial Plans not working in Teams Client
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
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
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.
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
