Forum Discussion
Team Dial Plans not working in Teams Client
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.
- rverbiestFeb 18, 2020Copper Contributor
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 : FalseShould 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- LinusCansbyFeb 21, 2020MVP
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?
- nirispaApr 09, 2020Copper Contributor
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