Page History

...

For a Teams client located inside the corporate network: Place a call to the Carrier access on the Downstream SBC. If the call has media optimization, the Proxy SBC's Monitor screen displays DA; this indicates the media is direct between the Teams client and the Downstream SBC (see below). If the Proxy SBC's Monitor screen displays B, the Proxy SBC proxies the media and the media is not optimized.

...

1. On the laptop running the Teams Client:
   1. Access  http://www.myipaddress.com/what-is-my-ip-address/ and take note of the Teams Client Public IP.
      
      

   2. Start a Command terminal, type the following command, and take note of the Teams Client internal IPv4 Address and Subnet Mask.

      
      

      Code Block
      ipconfig

      
      

2. Connect Office 365 Tenant via Powershell.
   
   

   1. Verify the Public IP address displayed earlier is listed when you type the following Office 365 Powershell command:

      Code Block
      Get-CsTenantTrustedIPAddress

      
      

   2. Verify the internal IPv4 Address and Subnet Mask displayed earlier is listed when you type the following Office 365 Powershell command:

      Code Block
      Get-CsTenantNetworkSite

      
      

TLS 1.2 Ciphers 

...

11.0.1To avoid any service impact, ensure your SBC Edge platforms are configured to support TLS 1.2 and connect using one of the following cipher suites for the Direct Routing SIP interface:

...

For more information, refer to MC297438.

"Replaces" Header

...

MS Teams Direct Routing will stop processing inbound SIP Requests which have "Replaces" headers. This change is automatically done by the SBC Edge software upgrade. No configuration changes are needed. For more information, refer to MC299922.

...