Forum Discussion
psychobunny83
Feb 15, 2023Brass Contributor
Extension dialling on Teams Phone doesn't work on Auto Attendant and won't transfer to the user
We are looking to switch to Teams Phone but we need to maintain our 4 digit extensions for the time being. I'm having a weird issue though where I can never get it to transfer to any user from the a...
- Mar 11, 2023I figured this out in case anyone else has this issue. +14083030000;ext=0000 is not the correct format for me at least the Microsoft documentation says put the number ;ext= extension but the correct format to make it work for us was:
+14083030000x0000
I had been trying for weeks using the ;ext= format and it never works. As soon as I used x instead, it immediately worked for all users. I could even set it in AzureAD without using Power Shell.
I'm using Calling Plan and Operator Connect on 2 different tenants and using the format about with x was the only way for us to get either tenant to work.
PattiCav_patticav
Oct 17, 2023Copper Contributor
If using on-prem AD and this syncs to AD Connect, where do I store the phone number with the extension? I see one reply that they added this to the M365 Admin Center. Do I need to add this to the on-prem AD as well?
thanks!!
Sunil Chittor
Dec 02, 2023Copper Contributor
To keep it uniform, Make the change within user account's properties from on-premise active directory and it will eventually sync to M365/Intra. Once the change is replicated, run the teams cmdlet to assign the same extension number within teams PowerShell module. Example (Set-CsPhoneNumberAssignment -Identity email address removed for privacy reasons -PhoneNumber "+14255551000;ext=1234" -PhoneNumberType DirectRouting). Note: By running this cmdlet, this feature will still work only from within auto attendants.