Teams Diagnostic code 500/16825
Teams Diagnostic Code 500/16825 error message when trying to contact external user from Teams. I need help please.
Forum Discussion
Did you ever get a fix or an root cause for this please as i am experiencing the same issues between SFB2015 and Teams TomArbuthnot
In our case, we believe it was some type of deep packet inspection running on a firewall but we don't have exact proof since the customer decided not to troubleshoot this any further. From sfb CLS logs and wire shark on edge servers we saw the following:
In a bad example (with Diagnostic code 500/16825) we are not getting "ACK" message from Microsoft 365. Comparing it to a good IM example, we do get "ACK" message but there is still a 14 second delay sometimes.
This makes us think there is possible packet inspection going on on firewall side but we didn't have access to firewall to check that.
In a bad example (with Diagnostic code 500/16825) we are not getting "ACK" message from Microsoft 365. Comparing it to a good IM example, we do get "ACK" message but there is still a 14 second delay sometimes.
This makes us think there is possible packet inspection going on on firewall side but we didn't have access to firewall to check that.
I'm currently looking at a similar issue.
Tenant 1 is Teams Only (upgrade from hybrid Skype for Business) - unable to communicate with multiple external Skype for Business estates.
Tenant 2 is Teams Only - able to communicate with the above external Skype for Business estates.
I'm performing the Tenant 1 and Tenant 2 tests from the same machine/network. Microsoft say the issue is with the external Skype estate(s). Sounds like a config issue with Tenant 1?