You have a Microsoft Teams Phone deployment. The 613 7010 5XXX phone number range is allocated to the Session Border Controller (SBC). A user named User1 is configured as shown in the following…

Question

Exhibit

Options

• AGrant-CsOnlineVoiceRoutingPolicy -Identity [email protected] -PolicyName $null
• BRemove-CsPhoneNumberAssignment -Identity [email protected] -PhoneNumber
• CSet-CsPhoneNumberAssignment -Identity [email protected] -PhoneNumber +61370105555 -
• DSet-CsUser [email protected] -EnterpriseVoiceEnabled $false
• ESet-CsOnlineVoiceUser [email protected] -TelephoneNumber "+61370105555"

• A
  6% (1)
• B
  6% (1)
• C
  71% (12)
• E
  18% (3)

Explanation

C assigns the correct phone number (+61370105555, which falls within the SBC-allocated 613 7010 5XXX range) to User1 via the current Set-CsPhoneNumberAssignment cmdlet - this resolves both the failed inbound routing and the missing outbound caller ID. D first clears the conflicting EnterpriseVoice state (the exhibit likely shows EnterpriseVoiceEnabled $true with an improperly configured or absent number assignment); Set-CsPhoneNumberAssignment then automatically re-enables it correctly when the Direct Routing number is applied.

Why the distractors fail: A sets the voice routing policy to $null, which removes the policy entirely and would break the outbound calls that currently work. B removes a phone number assignment rather than correcting it, making the inbound problem worse. E uses the legacy Set-CsOnlineVoiceUser cmdlet, which has been superseded by Set-CsPhoneNumberAssignment and is not the correct approach for modern Direct Routing deployments.

Memory tip: Think "Reset, then Reassign with the Right cmdlet" - for Direct Routing issues, clear the broken EnterpriseVoice state first (Set-CsUser), then use the new cmdlet (Set-CsPhoneNumberAssignment) to assign the SBC-range number. If you see Set-CsOnlineVoiceUser on the exam, it's almost always the legacy trap answer.

No community discussion yet for this question.