Extension Dialplan

My newest suspicion is that everyone on Microsoft Teams Version 1.5.00.28567 (64-bit) windows app cant process such translation -> $(\d{4})$ to +123456789;ext=$1. It will be translated to base DID e.g dialing 2222 will result to +123456789 instead +123456789;ext=2222. Already  more than 20 users found in my tenant site after updating. 

New ticket was opened, but in the meanwhile I hope someone with current and previous version would confirm this.

Hi RealTime_M365 

Thank you for responding. There is no mac device on the location, so I am afraid I cant produce this problem on it. But there are iPhone and iPad users experiencing the same. I will be back at you for the versions. 

But I think I just learned something.

I have to get out regular ip pbx mentality, that dialplans are processed in the call control/ip pbx itself.

In Microsoft Teams, I think the dialplans are "fetched" into the client apps. On windows pc, when dialing, there will be autocompletion for full translation shows up after we type the extension like this:

Although on desktop this works by typing number on keybord instead, but not when clicking onscreen dialpad buttons. When clicking the onscreen dialpad it will be translated as 1103;ext=1103 like following:

The Androids seem able to process the dialplans perfectly. Some androids at first cant process the dialplans assigned to them. But after logout and login back, the dialplan can be processed perfectly. Hence my guess that the dialplans are fetched to the client apps. But I may be wrong too.