06-15-2020 10:59 AM
06-15-2020 10:59 AM
1. Is there an snooper equivalent for Teams which can show what candidate were build and finally which ones were used, i know there is one on github trickle ice or to use test webrtc options and does work a bit but not sure if it is applicable for teams.exe
2. If not is there a way today to find all these details using any other tool as of today
3. I know CQD report does show these details but that is for reporting
4. I need a way to able to trace live sessions these connectivity flows for end to end understanding and to be able to provide correct details to my network team
5. If there is a cloud proxy service which controls all http traffic
6. UDP is allowed for specific scenarios only like not is corpnet but when in VPN
7. Does Media traffic in Teams works differently for P2P and Conferencing
8. When in Conferencing does all media traffic also goes through Teams Server(s)
9. Why does teams have so many instances running on the same machine,
06-22-2020 03:54 PMSolution
Hello @Himanshu Singh
Have you had an opportunity to view this documentation which I believe answers most of you questions? https://docs.microsoft.com/en-us/microsoftteams/microsoft-teams-online-call-flows
What's not answered above:
1. How to see client candidates during call setup for troubleshooting media path while working with network team.
There is nothing native built into the client that will allow this like Skype for Business tracing tools read with Snooper. However, you can view the candidates for an outbound call from the Teams client via an HTTPs trace. The easiest way to accomplish this is use developer tools (F12) in Microsoft Edge browser (or Chrome) to view network trace during outbound call. Then search on renegotiate and expand the response for the Media Content;. The blog data will contain the SDP information.
Copy the contents of the blob and paste in text editor; my preference is Visual Studio Code. Note I have had some people report this doesn't always work so perhaps something on network preventing connecting to our service where the negotiation is happening.
2. Why are there so many processes for Teams? Each process is handling a specific workload. It's the way it's designed.