You have a Microsoft Teams Phone deployment that uses Direct Routing. The deployment has the following configurations: - Direct Routing Session Border Controller (SBC) public IP subnet: 198.51.100.0/2

Question

Options

• A52.112.0.0/14
• B198.51.100.0/24
• C203.0.113.0/24
• D192.168.0.0/24

• B
  13% (2)
• C
  81% (13)
• D
  6% (1)

Explanation

Trusted IP addresses in Teams represent the external (internet-facing) IP addresses of your corporate network locations. When a Teams client's public IP matches an entry in the trusted IP list, Teams recognizes the client as being at a known corporate site and can apply the correct network site - which in turn enables dynamic emergency calling with accurate location information. The Teams client external IP subnet (203.0.113.0/24) is the public IP range clients present when connecting through the corporate internet gateway, so this is the range to add. The SBC public IP (198.51.100.0/24) is the SBC's address, not a client location indicator. The internal subnet (192.168.0.0/24) is private and not routable on the internet. Microsoft's own infrastructure IPs (52.112.0.0/14) are Microsoft's, not yours.

No community discussion yet for this question.