02-15-2019 09:35 AM
02-15-2019 09:35 AM
Regarding the video Network Planning for Microsoft Teams:
at the time linked above... the slide mentions "End Points will connect directly via random high ports if possible". What is the range of the high ports? I haven't don't see the information published in O365 Endpoints documentation.
02-15-2019 11:23 AM - edited 02-15-2019 11:23 AM
Teams will try with a random high ports first (50,000-59,999) and if that is not possible it will relay traffic via a Transport Relay on 3478-3481 UDP.
Check this blog .
02-15-2019 11:27 AM
If you don't specify a range it will use a random port in the range 1024 - 65535. It's perfectly normal to define the range through the Teams admin meeting settings, and push it to the same range that Skype used to existing optimisations work the same, so ..
02-15-2019 01:00 PM
Thanks - this is what I was looking for. The ports in your screenshot are mentioned later in the video, but not the 1024-65535 if the automatic settings are set.
02-18-2019 01:23 AMSolution
I hope this explains everything :)
If you think we should update the training, please let me know.
02-18-2019 07:11 AM
Next major revision of the video maybe consider mentioning the port ranges or is there already a docs page that references the full listing of the ports (including 1,024-65,535 UDP ports) - set up an aka.ms to it? Coming from the background of Skype for Business... Having the full documentation is essential to identify the what and hows to justify unblocking firewall and ACL ports.
02-18-2019 07:15 AM
Thanks @Timothy Balk, I will get sure to mention that the we list the high ports and stress that they don't need to be optional and that we only mention them so firewall admins will understand why they are seeing the client trying to connect :)
02-18-2019 08:50 AM - edited 02-18-2019 08:52 AM
It's always better to publish the simple ports information like all other platforms do.
Look at that video explanations, Tunneling with proxy chains with FEC, this UDP at the raw level packet explanation.. wow.. took an hour in the video, when it could've been an only few seconds by pulling out those 3-4 words.
we are having problems. we can't hear. this is the end point problem, from us.
however MS tunnels are not nearly perfect as Skype in any situation here and there
so here goes the documents that require two hours and mostly useless at most and stressful.
answers are here, in the community. not from the very cultural style documents.
You know it, we the one who initiate the connection to let you guys in., then it should work no matter what, and Teams should especially work on easy networks when depreciating Skype. like the guy in the video mentioned about old centralized server network systems, then let the magic happens?. Also Teams doesn't know how to penetrate BOGUS configured routers with that 443 backup plan. Teams will slowly wouldn't go through as the hardwares and softwares are changing even ISPs too, We have got to hang up on them and call back unprofessionally.
Too bad, I will not open that wide high-port range forwarding to Microsoft Windows OS? Would you?
So let us simply solve this problem but we need the product information, I really hope there is 1-2 pages optional manual per every office 365 product. not over 100 pages from everyone.
not this one, never thought dos had netstat command,
02-19-2019 12:28 AM
Did you try to run the Skype for Business Network Assessment Tool with the following parameters?
If so, what did it show?
06-05-2019 02:16 AM
Right now I'm facing issues:
users are complaining that they have drops and audio\video loss while on the Teams meeting.
After checking logs I found that Temas generating traffic sourcing from UDP 50000-50059 but the destination ports are not limited to range UDP 50000-59999, I see a lot of sessions trying to use lower and higher ports which are blocked by my firewall. I can't find any official MS documentation which says that destination is UDP\dynamic and not UDP\50000-59999.
Do you have any ideas where I can find proper docs or proof that MS Teams generates this traffic?
06-21-2019 03:23 PM
06-27-2019 01:26 PM
@Tommytong I think you'll want to look in the Teams Admin area in O365 Admin - https://docs.microsoft.com/en-us/microsoftteams/meeting-settings-in-teams
That should be the place where you can reduce the range of ports used by Teams.
There is also a known set of ports, IP addresses and URLs that are used by O365 services to make sure they are accessible through all firewalls to ensure things are working and that documentation is here: https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges