You have a Microsoft Teams Phone deployment. You need to implement Local Media Optimization for Direct Routing users at a site. Users at the site frequently perform the following actions: - Park…

Question

Options

• APark calls.
• BTransfer calls to other users.
• CEscalate calls to conference calls.
• DPlace calls on hold.

• A
  11% (3)
• B
  15% (4)
• C
  70% (19)
• D
  4% (1)

Explanation

Escalating to a conference call (C) is correct because Local Media Optimization (LMO) routes media directly between Teams clients and the Session Border Controller (SBC) without passing through Microsoft's cloud media processors. When a call is escalated to a conference, Teams must engage its cloud-based Multipoint Control Unit (MCU) to mix audio/video from multiple participants - this inherently breaks the optimized local media path and forces traffic through Microsoft's servers.

Why the distractors are wrong:

• A (Park calls): Call parking is a signaling/hold-orbit operation; media isn't re-routed through cloud conferencing infrastructure, so LMO remains unaffected.
• B (Transfer calls): Transfers are handled via SIP re-INVITE signaling. If both parties are behind the same SBC, media can stay local; LMO is not disrupted.
• D (Place on hold): Hold is a simple media-direction change (sendonly/inactive) handled at the SIP level - no cloud media processor involvement, so LMO is unaffected.

Memory tip: Think of LMO as a "local express lane." All basic call operations (hold, park, transfer) can stay on that lane. Conferencing is the one feature that forces a detour through Microsoft's cloud mixing engine - the only action that kicks traffic off the local route.

No community discussion yet for this question.