PBX Auto Attendant and msDS-PhoneticDisplayName

%3CLINGO-SUB%20id%3D%22lingo-sub-201061%22%20slang%3D%22en-US%22%3EPBX%20Auto%20Attendant%20and%20msDS-PhoneticDisplayName%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-201061%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20some%20users%20who%20are%20not%20pleased%20with%20the%20way%20the%20Auto%20Attendant%20pronounces%20their%20names.%26nbsp%3B%20We%20are%20running%20a%20hybrid%20environment%2C%20so%20we%20have%20an%20AD%20server%20on%20site%20and%20AADC.%26nbsp%3B%20We%20have%20been%20experimenting%20with%20one%20user's%20name%20to%20try%20to%20fix%20this%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EWe%20tried%20using%20the%20PowerShell%20command.%26nbsp%3B%20It%20returned%20a%20message%20to%20the%20effect%20that%20we%20cannot%20control%20that%20function%20through%20PowerShell.%26nbsp%3B%3C%2FLI%3E%3CLI%3EWe%20changed%20the%20msDS-PhoneticDisplayName%20in%20Attribute%20Editor%20in%20the%20local%20AD%20server.%26nbsp%3B%20We%20waited%2024%20hrs.%20to%20see%20if%20the%20PBX%20servers%20would%20pick%20it%20up%2C%20but%20there%20was%20no%20change.%20%26nbsp%3B%3C%2FLI%3E%3CLI%3EWe%20changed%20the%20msDS-PhoneticLastName%20and%20msDS-PhoneticFirstName%20to%20see%20what%20that%20would%20do%20after%20resetting%20the%20PhoneticDisplayName%20to%20%3CNOT%20set%3D%22%22%3E.%26nbsp%3B%20No%20change.%3C%2FNOT%3E%3C%2FLI%3E%3CLI%3EWe%20tried%20changing%20all%20three%20PhoneticDisplayName%20options.%26nbsp%3B%20No%20change.%3C%2FLI%3E%3CLI%3EWe%20tried%20removing%20the%20user%20from%20the%20Auto%20Attendant%20after%20making%20the%20PhoneticDisplayName%20change%2C%20then%20putting%20him%20back%20in%20after%2024%20hrs.%26nbsp%3B%20No%20change.%3C%2FLI%3E%3C%2FOL%3E%3CP%3EIt%20appears%20that%20the%20PBX%20servers%20are%20not%20picking%20up%20the%20changes.%26nbsp%3B%20We%20are%20out%20of%20ideas%20and%20welcome%20any%20suggestions.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJulie%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-201061%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAuto%20Attendant%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECloud%20PBX%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ephonetic%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EVoice%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-388885%22%20slang%3D%22en-US%22%3ERe%3A%20PBX%20Auto%20Attendant%20and%20msDS-PhoneticDisplayName%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-388885%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F386%22%20target%3D%22_blank%22%3E%40Bradley%20Weir%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20far%20as%20I%20know%2C%20there%20is%20no%20way%20to%20do%20this%20with%20the%20current%20controls.%26nbsp%3B%20Here's%20what%20we%20did%20as%20a%20workaround%3A%3C%2FP%3E%3COL%3E%3CLI%3EAccount%201%20is%20the%20original%20Active%20Directory%20(AD)%20and%20Skype%20account%20with%20the%20correctly%20spelled%20AD%20name.%3C%2FLI%3E%3CLI%3ESet%20up%20a%20second%20AD%20and%20Skype%20account%20(jointly%20referred%20to%20as%20Account%202).%3C%2FLI%3E%3CLI%3EBe%20sure%20to%20assign%20the%20appropriate%20phone%20licenses%20to%20Account%202.%26nbsp%3B%20I'm%20attaching%20a%20snap%20of%20what%20we%20assigned%20to%20our%20Account%202.%3C%2FLI%3E%3CLI%3EIn%20Account%202%2C%20change%20the%20spelling%20of%20the%20name%20in%20the%20AD%20name%20field%20until%20the%20auto%20attendant%20pronounces%20it%20correctly.%3C%2FLI%3E%3CLI%3EList%20Account%202%20in%20the%20Skype%20auto%20attendant%20(instead%20of%20Account%201).%3C%2FLI%3E%3CLI%3EForward%20Account%202's%20Skype%20to%20Account%201's%20Skype.%3C%2FLI%3E%3C%2FOL%3E%3CP%3EYou%20get%20the%20correctly%20spelled%20name%20for%20e-mail%20purposes%20and%20the%20correctly%20pronounced%20name%20for%20auto%20attendant%20purposes.%20The%20downside%20is%20paying%20for%20an%20additional%20account.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EObviously%20this%20is%20not%20a%20great%20fix%20for%20more%20than%20about%205%20users%2C%20but%20it%20worked%20for%20us%20because%20we%20only%20had%20one%20user%20who%20was%20high%20priority.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386682%22%20slang%3D%22en-US%22%3ERe%3A%20PBX%20Auto%20Attendant%20and%20msDS-PhoneticDisplayName%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386682%22%20slang%3D%22en-US%22%3EDid%20you%20figure%20this%20out%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2203695%22%20slang%3D%22en-US%22%3ERe%3A%20PBX%20Auto%20Attendant%20and%20msDS-PhoneticDisplayName%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2203695%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20posting%20your%20workaround%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F153376%22%20target%3D%22_blank%22%3E%40Julie%20Fisher%3C%2FA%3E!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20consider%20voting%20for%20this%20suggestion%20on%20the%20Teams%20UserVoice%20site%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F33980866-voicemail-customize-name-pronunciation-by-settin%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EVoicemail%20-%20Customize%20name%20pronunciation%20by%20setting%20phonetics%20%E2%80%93%20Microsoft%20Teams%20UserVoice%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

We have some users who are not pleased with the way the Auto Attendant pronounces their names.  We are running a hybrid environment, so we have an AD server on site and AADC.  We have been experimenting with one user's name to try to fix this problem.

 

  1. We tried using the PowerShell command.  It returned a message to the effect that we cannot control that function through PowerShell. 
  2. We changed the msDS-PhoneticDisplayName in Attribute Editor in the local AD server.  We waited 24 hrs. to see if the PBX servers would pick it up, but there was no change.  
  3. We changed the msDS-PhoneticLastName and msDS-PhoneticFirstName to see what that would do after resetting the PhoneticDisplayName to <not set>.  No change.
  4. We tried changing all three PhoneticDisplayName options.  No change.
  5. We tried removing the user from the Auto Attendant after making the PhoneticDisplayName change, then putting him back in after 24 hrs.  No change.

It appears that the PBX servers are not picking up the changes.  We are out of ideas and welcome any suggestions.

 

Julie

3 Replies
Did you figure this out?

@itsbrad 

As far as I know, there is no way to do this with the current controls.  Here's what we did as a workaround:

  1. Account 1 is the original Active Directory (AD) and Skype account with the correctly spelled AD name.
  2. Set up a second AD and Skype account (jointly referred to as Account 2).
  3. Be sure to assign the appropriate phone licenses to Account 2.  I'm attaching a snap of what we assigned to our Account 2.
  4. In Account 2, change the spelling of the name in the AD name field until the auto attendant pronounces it correctly.
  5. List Account 2 in the Skype auto attendant (instead of Account 1).
  6. Forward Account 2's Skype to Account 1's Skype.

You get the correctly spelled name for e-mail purposes and the correctly pronounced name for auto attendant purposes. The downside is paying for an additional account.

 

Obviously this is not a great fix for more than about 5 users, but it worked for us because we only had one user who was high priority.

Thanks for posting your workaround, @Julie Fisher!

 

Please consider voting for this suggestion on the Teams UserVoice site:

Voicemail - Customize name pronunciation by setting phonetics – Microsoft Teams UserVoice