Hotspot Question You have a Microsoft Teams Phone deployment. Direct Routing is enabled for all users. The users can place and receive PSTN calls. You are implementing emergency numbers in Teams…

The correct answer is 'sbc1.contoso.com'; 'sbc2.contoso.com'; 'sbc3.contoso.com'; 'sbc3.contoso.com'. Explanation: Teams Emergency Calling - Stripping "+" for 3-Digit Numbers Context This is an MS-721 (Microsoft Teams Voice Engineer) exam scenario. The goal is to configure outbound number translation on each SBC so that when a user dials a 3-digit emergency number (e.g., +911)…

Plan and configure Direct Routing

Question

Hotspot Question You have a Microsoft Teams Phone deployment. Direct Routing is enabled for all users. The users can place and receive PSTN calls. You are implementing emergency numbers in Teams. You need to remove the + symbol from any three-digit calls to the Session Border Controller (SBC). How should you complete the PowerShell script? To answer, drag the appropriate values to the correct targets. Each value may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Answer:

Exhibit

Answer Area

Drag items

'sbc3.contoso.com''sbc1.contoso.com''sbc2.contoso.com'

Correct arrangement

'sbc1.contoso.com'
'sbc2.contoso.com'
'sbc3.contoso.com'
'sbc3.contoso.com'

Explanation

Explanation: Teams Emergency Calling - Stripping "+" for 3-Digit Numbers

Context

This is an MS-721 (Microsoft Teams Voice Engineer) exam scenario. The goal is to configure outbound number translation on each SBC so that when a user dials a 3-digit emergency number (e.g., +911), the + is stripped before the call reaches the SBC - because many SBCs do not accept + on short emergency strings.

What the Script Is Doing

The PowerShell script almost certainly follows this pattern:

Creates a CsTeamsTranslationRule that matches ^\+(\d{3})$ and outputs $1 (stripping the +)
Applies it to each SBC via Set-CsOnlinePSTNGateway using -OutboundTeamsNumberTranslationRules

Why Each Blank Gets Its Value

Position	Value	Reason
1	`sbc1.contoso.com`	First SBC in the deployment - receives the translation rule to strip `+` from 3-digit calls
2	`sbc2.contoso.com`	Second SBC - same rule applied; all gateways handling PSTN must be configured consistently
3	`sbc3.contoso.com`	Third SBC - same rule applied for completeness
4	`sbc3.contoso.com`	`sbc3` is referenced again - this second reference is for a separate cmdlet (e.g., configuring `sbc3` as the gateway on a dedicated emergency voice route, or as a failover gateway in a `New-CsOnlineVoiceRoute -OnlinePstnGatewayList`)

The repeat of sbc3 reflects a two-part configuration: first applying the translation rule to the gateway object, then referencing that same gateway in a voice routing context.

Common Mistakes

Not applying translation rules to all SBCs - If even one SBC is missed, emergency calls routed through it will fail or be rejected because of the unexpected +.
Confusing inbound vs. outbound translation - The stripping happens outbound from Teams to the SBC, so you use -OutboundTeamsNumberTranslationRules, not inbound.
Assuming sbc3 appearing twice is an error - It's intentional: one instance configures the gateway object, the other references it in a route or policy.
Not scoping the pattern to exactly 3 digits - Using ^\+\d+$ instead of ^\+(\d{3})$ would strip + from ALL calls, not just emergency short codes.

Topics

#Direct Routing#Emergency Calling#Number Translation#SBC Configuration

Community Discussion

No community discussion yet for this question.

Full MS-720 Practice