We use a proxy that can subscribe to managed lists so these were referred to as "Lync Online IPv4 Ranges" so some are probably related to old Lync / SfB rather than Teams, but it worked. I don't like doing that, as we can only trust that nothing else runs on the same IP's, but who has a choice. We had to bypass SSL inspection for that entire range along with other identified ones, before it would work. A VPN is commonly used when an employee is working from a remote location and needs to access different organizational resources (e.g., network drives, customer database management software, etc. That IP address (in our case were seeing things like and ) were being blocked as failing the SSL inspection - the certificate common names didn't match the host name, again, terrible practice Microsoft. The most commonly used VPN is the Cisco An圜onnect Secure Mobility Client. ![]() We spotted that our proxy was blocking some traffic that wasn't obviously teams related.Īt the moment where the "receiver" inside the network clicks the button to accept the incoming call Teams tries to connect out to an IP address rather than to a hostname, which is awful practice of course. So the 21H1 thing was a false alarm sorry, but we have we think solved it.
0 Comments
Leave a Reply. |