SOLVED

Call Quality Dashboard and QoS

%3CLINGO-SUB%20id%3D%22lingo-sub-1756178%22%20slang%3D%22en-US%22%3ECall%20Quality%20Dashboard%20and%20QoS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1756178%22%20slang%3D%22en-US%22%3E%3CP%3EI%20know%20the%20CQD%20provides%20information%20regarding%20call%20quality%2C%20but%20does%20it%20specifically%20provide%20information%20to%20verify%20that%20QoS%20is%20being%20applied%20to%20calls%3F%26nbsp%3B%20%26nbsp%3BI%20have%20read%20that%20to%20validate%20QoS%20implementation%2C%20you%20need%20to%20verify%20that%20the%20DSCP%20value%20exists%20at%20each%20end%20of%20the%20call%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fqos-in-teams%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fqos-in-teams%3C%2FA%3E)%2C%20but%20I%20guess%20I'm%20not%20sure%20of%20the%20easiest%20way%20to%20go%20about%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20CQD%20doesn't%20provide%20that%20kind%20of%20info%2C%20I'm%20assuming%20basic%20traffic%20monitoring%2Fpacket%20capturing%20with%20a%20tool%20like%20NetMon%20or%20WireShark%20would%20do%20it%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1756178%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1756686%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20Quality%20Dashboard%20and%20QoS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1756686%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F308557%22%20target%3D%22_blank%22%3E%40PMorgan_1116%3C%2FA%3E%26nbsp%3BHey%20there-%20this%20is%20a%20good%20article%20that%20summarizes%20how%20to%20ensure%20you%20have%20turned%20on%20the%20QoS%20markers%20in%20the%20Teams%20Meeting%20Policies%20setting%20(I%20have%20seen%20some%20tenants%20that%20have%20missed%20turning%20this%20part%20on%20and%20ended%20up%20not%20even%20having%20traffic%20prioritized).%26nbsp%3B%20The%20article%20also%20gives%20a%20great%20overview%20of%20how%20to%20use%20WireShark%20to%20check%20the%20DSCP%20value%20exists%20at%20each%20end.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcloudbrothers.info%2Foptimize-your-microsoft-teams-traffic-with-qos-on-a-unifi-usg%2F%3Flang%3Den%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcloudbrothers.info%2Foptimize-your-microsoft-teams-traffic-with-qos-on-a-unifi-usg%2F%3Flang%3Den%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20this%20helps.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1757055%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20Quality%20Dashboard%20and%20QoS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1757055%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F308557%22%20target%3D%22_blank%22%3E%40PMorgan_1116%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt's%20not%20really%20'both%20ends'%2C%20QoS%20won't%20be%20there%20when%20it%20crosses%20the%20internet%2C%20only%20from%20the%20client%20as%20far%20as%20your%20network%20perimeter.%20CQD%20can't%20know%20how%20far%20it%20gets.%20Validate%20that%20the%20router%20is%20seeing%20DSCP%20values%2C%20it'll%20have%20some%20kind%20of%20function%20to%20show%20the%20amount%20of%20traffic%20in%20each%20queue.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fforum.networklessons.com%2Ft%2Fhow-to-debug-qos-on-switches-and-routers%2F1615%2F2%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fforum.networklessons.com%2Ft%2Fhow-to-debug-qos-on-switches-and-routers%2F1615%2F2%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

I know the CQD provides information regarding call quality, but does it specifically provide information to verify that QoS is being applied to calls?   I have read that to validate QoS implementation, you need to verify that the DSCP value exists at each end of the call (https://docs.microsoft.com/en-us/microsoftteams/qos-in-teams), but I guess I'm not sure of the easiest way to go about that.

 

If CQD doesn't provide that kind of info, I'm assuming basic traffic monitoring/packet capturing with a tool like NetMon or WireShark would do it??

 

 

 

7 Replies
Highlighted

@PMorgan_1116 Hey there- this is a good article that summarizes how to ensure you have turned on the QoS markers in the Teams Meeting Policies setting (I have seen some tenants that have missed turning this part on and ended up not even having traffic prioritized).  The article also gives a great overview of how to use WireShark to check the DSCP value exists at each end.

 

https://cloudbrothers.info/optimize-your-microsoft-teams-traffic-with-qos-on-a-unifi-usg/?lang=en

 

I hope this helps.

Highlighted
Best Response confirmed by ThereseSolimeno (Microsoft)
Solution

@PMorgan_1116 

 

It's not really 'both ends', QoS won't be there when it crosses the internet, only from the client as far as your network perimeter. CQD can't know how far it gets. Validate that the router is seeing DSCP values, it'll have some kind of function to show the amount of traffic in each queue.

 

https://forum.networklessons.com/t/how-to-debug-qos-on-switches-and-routers/1615/2

Highlighted

@Ethan Stern Thanks for sharing this information! That was very helpful :)

Highlighted

@TheM365Guy glad I could help.  Awesome username, btw :)

Highlighted

@Ethan Stern thanks! :) 

Highlighted

@Ethan Stern Thanks for the link..great article!

Highlighted

@Steven Collier Thank you for the info and the link!