SOLVED

Question about Teams QoS guidance - port range sizes

%3CLINGO-SUB%20id%3D%22lingo-sub-1406866%22%20slang%3D%22en-US%22%3ETeams%20QoS%20guidance%20-%20%22matching%20settings%22%20and%20port%20range%20sizes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1406866%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fmeeting-settings-in-teams%23set-how-you-want-to-handle-real-time-media-traffic-for-teams-meetings%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ETeams%20QoS%20documentation%3C%2FA%3E%20there%20are%20a%20couple%20pieces%20of%20information%20that%20I%20have%20questions%20about%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%22If%20you%20enable%20QoS%20or%20change%20settings%20in%20the%20Microsoft%20Teams%20admin%20center%20for%20the%20Microsoft%20Teams%20service%2C%20you%20will%20also%20need%20to%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fqos-in-teams-clients%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eapply%20matching%20settings%20to%20all%20user%20devices%3C%2FA%3E%3CSPAN%3E%26nbsp%3Band%20all%20internal%20network%20devices%20to%20fully%20implement%20the%20changes%20to%20QoS%20in%20Teams.%22%20-%20%3CFONT%20color%3D%22%23008000%22%3ERe%3A%20Windows%20Clients%20-%20Why%3F%26nbsp%3B%20Don't%20the%20meeting%20settings%20in%20the%20console%20apply%20to%20packets%20coming%20from%20the%20service%2C%20while%20your%20GPO%20handles%20packets%20coming%20from%20the%20client%3F%26nbsp%3B%20Or%20does%20this%20setting%20also%20configure%20QoS%20in%20the%20client%20in-band%20using%20the%20ports%20configured%20in%20the%20admin%20center%3F%26nbsp%3B%20Maybe%20similar%20to%20the%20old%20Set-CsConferencingConfiguration%20cmdlet%20for%20SfB%3F%3C%2FFONT%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%22Selecting%20a%20port%20range%20that%20is%20too%20narrow%20will%20lead%20to%20dropped%20calls%20and%20poor%20call%20quality.%20The%20recommendations%20below%20should%20be%20a%20bare%20minimum.%22%20-%20%3CFONT%20color%3D%22%23008000%22%3EI%20was%20planning%20on%20using%20the%20default%2050000%3A50019%2C%2050020%3A50039%2C%2050040%3A50059%20ranges.%26nbsp%3B%20Is%20there%20guidance%20for%20taking%20a%20more%20educated%20guess%20at%20these%20port%20ranges%3F%3C%2FFONT%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1406866%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Enetwork%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1408671%22%20slang%3D%22en-US%22%3ERe%3A%20Question%20about%20Teams%20QoS%20guidance%20-%20port%20range%20sizes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1408671%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F13364%22%20target%3D%22_blank%22%3E%40David%20Phillips%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEnabling%20QoS%20on%20the%20meeting%20policy%20is%20a%20good%20start.%20That%20switch%20will%20force%20certain%20clients%20-%20mobility%20%26amp%3B%20Mac%20OS%20clients%20-%20to%20mark%20packets%20as%20they%20leave%20their%20respective%20devices.%20That%20switch%20does%26nbsp%3B%3CU%3Enot%3C%2FU%3E%3CSTRONG%3E%26nbsp%3B%3C%2FSTRONG%3Eguarantee%20QoS%20for%20packets%20that%20leave%20the%20Microsoft%20service%20and%20traverse%20the%20internet.%20Microsoft%20will%20provide%20QoS%20by%20default%20for%20their%20networks%20up%20until%20the%20point%20it%20leaves.%20After%20that%2C%20no%20QoS%20is%20present%2C%20and%20the%20customer%20must%20re-enable%20QoS%20markings%20upon%26nbsp%3B%3CEM%3Eingress%26nbsp%3B%3C%2FEM%3Eto%20their%20network%20(typically%20at%20the%20firewall).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWindows%20client%20endpoints%20still%20require%20Group%20Policy%20Based%20settings%20to%20get%20DSCP%20tags%20applied.%20The%20meeting%20policy%20configuration%20has%20zero%20bearing%20on%20Windows%20endpoints.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStick%20with%20the%20default%20port%20ranges%20unless%20you%20have%20a%20reason%20to%20go%26nbsp%3B%3CEM%3Elarger%3C%2FEM%3E%2C%20not%20smaller.%20ICE%2FSTUN%2FTURN%20will%20negotiate%20several%20ports%20per%20call%2C%20so%20the%20default%20settings%20will%20allow%20at%20least%20some%20level%20of%20having%20multiple%20calls%20active%2Fon-hold.%20If%20you%20know%20people%20will%20need%20to%20handle%2010%2B%20simultaneous%20calls%2C%20you%20can%20bump%20the%20range%20up%20to%20what%20it%20used%20to%20be%20in%20the%20OCS%20days%2C%20which%20was%2040%20ports%20per%20modality.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1408871%22%20slang%3D%22en-US%22%3ERe%3A%20Question%20about%20Teams%20QoS%20guidance%20-%20port%20range%20sizes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1408871%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F84875%22%20target%3D%22_blank%22%3E%40Trevor%20Miller%3C%2FA%3E%26nbsp%3Byour%20explanation%20and%20answer%20makes%20complete%20sense.%26nbsp%3B%20I'm%20still%20stuck%20in%20SfB%20Server%20admin%20mode%2C%20I%20need%20to%20start%20breaking%20out%20of%20that!%26nbsp%3B%20Thanks%20for%20the%20answer%2C%20super%20helpful.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Super Contributor

In the Teams QoS documentation there are a couple pieces of information that I have questions about:

 

"Selecting a port range that is too narrow will lead to dropped calls and poor call quality. The recommendations below should be a bare minimum." - I was planning on using the default 50000:50019, 50020:50039, 50040:50059 ranges.  Is there guidance for taking a more educated guess at these port ranges?

2 Replies
Highlighted
Best Response confirmed by David Phillips (Super Contributor)
Solution

@David Phillips 

Enabling QoS on the meeting policy is a good start. That switch will force certain clients - mobility & Mac OS clients - to mark packets as they leave their respective devices. That switch does not guarantee QoS for packets that leave the Microsoft service and traverse the internet. Microsoft will provide QoS by default for their networks up until the point it leaves. After that, no QoS is present, and the customer must re-enable QoS markings upon ingress to their network (typically at the firewall).

 

Windows client endpoints still require Group Policy Based settings to get DSCP tags applied. The meeting policy configuration has zero bearing on Windows endpoints.

 

Stick with the default port ranges unless you have a reason to go larger, not smaller. ICE/STUN/TURN will negotiate several ports per call, so the default settings will allow at least some level of having multiple calls active/on-hold. If you know people will need to handle 10+ simultaneous calls, you can bump the range up to what it used to be in the OCS days, which was 40 ports per modality.

Highlighted

@Trevor Miller your explanation and answer makes complete sense.  I'm still stuck in SfB Server admin mode, I need to start breaking out of that!  Thanks for the answer, super helpful.