Forum Discussion
Solved
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...
- I 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.
Hi,
Do you have a on-premises Active Directory? Please run the following commands for the user in your tenant and check
Set-ADUser -UserPrincipalName email address removed for privacy reasons -TelePhonenumber "+14083030000;ext=0000"
With Regards,
Satish U
Do you have a on-premises Active Directory? Please run the following commands for the user in your tenant and check
Set-ADUser -UserPrincipalName email address removed for privacy reasons -TelePhonenumber "+14083030000;ext=0000"
With Regards,
Satish U
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!!
- 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.
- I just have AzureAD nothing is on premise. If I try your command it says Set-AdUser is not recognized. The one I was using was:
Set-CsUser -Identity "email address removed for privacy reasons" -OnPremLineURI tel:"+1xxxx600130;ext=2199"
When using Direct Routing I would issue this one:
Set-CsPhoneNumberAssignment -Identity email address removed for privacy reasons -PhoneNumber "+1xxxx129586;ext=2122" -PhoneNumberType DirectRouting
In AzureAD it shows the extension, I've just never once been able to get an auto attendant to dial it.- I 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.psychobunny83 This works with Operator Connect users as well? Can you please share the output of below for an OC user ?
Get-Csonlineuser -Identity user | fl LineURI, TeamsCarrierEmergencyCallRouingPolicy, OnPremLineURI, EnterpriseVoiceEnabled
TIA
