Home
%3CLINGO-SUB%20id%3D%22lingo-sub-327015%22%20slang%3D%22en-US%22%3EThe%20Rise%20of%20Drop%20Failure%20Rate%20and%20Unclassified%20Streams%3A%20Explained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327015%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20customers%20start%20transitioning%20from%20Skype%20for%20Business%20to%20Microsoft%20Teams%20for%20calling%20and%20meetings%2C%20a%20lot%20of%20attentions%20have%20been%20given%20to%20understanding%20how%20Teams%20behave%20in%20their%20environment%20where%20Skype%20for%20Business%20has%20been%20operating%20previously.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmicrosoftteams%2Fdifference-between-call-analytics-and-call-quality-dashboard%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ECall%20Quality%20Dashboard%3C%2FA%3E%20(CQD)%20is%20the%20tool%20of%20choice%20that%20allows%20us%20to%20gain%20insights%20into%20the%20reliability%20and%20quality%20of%20calls%20made%20using%20Teams%20over%20a%20period%20of%20time%2C%20and%20you%20can%20also%20use%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmicrosoftteams%2Fdifference-between-call-analytics-and-call-quality-dashboard%23whats-call-analytics-and-when-should-i-use-it%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ECall%20Analytics%3C%2FA%3E%20for%20a%20point-in-time%2C%20call%20reliability%20and%20quality%20troubleshooting%20efforts.%20We%20have%20also%20published%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmicrosoftteams%2Fquality-of-experience-review-guide%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EQuality%20of%20Experience%20Review%3C%2FA%3E%20(QER)%20guidance%20that%20complements%20CQD%20by%20providing%20a%20comprehensive%20guide%20to%20leverage%20it%20to%20achieve%20and%20maintain%20high%20quality%20experiences%20for%20your%20end%20users.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3ELooking%20at%20the%20several%20customers%E2%80%99%20data%20from%20the%20past%20six%20months%2C%20we%20have%20noticed%20a%20trend%20of%20increased%20audio%20drop%20failure%20rate%20in%20the%20order%20of%20extreme%20magnitude%20and%20unclassified%20audio%20stream%20counts%20affecting%20several%20customers%20that%20we%E2%80%99ve%20been%20working%20with%2C%20especially%20from%20the%20middle%20of%20November%20onwards.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F71287iC92ED7092FEB98D0%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22CQD-1.png%22%20title%3D%22CQD-1.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3ECustomer%201%20Summary%20Report%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F71288iBDF73D8D8C5B9F9B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22CQD-2.png%22%20title%3D%22CQD-2.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3ECustomer%202%20Summary%20Report%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBased%20on%20our%20investigation%2C%20the%20dropped%20calls%20and%20%E2%80%98unclassified%E2%80%99%20calls%20are%20inactive%20audio%20sessions%20in%20a%20screen%20sharing%20only%2C%20two-person%20ad-hoc%20group%20call.%20There%20is%20no%20real%20user%20impact%2C%20but%20there%20is%20an%20artefact%20due%20to%20how%20the%20feature%20was%20implemented%2C%20which%20was%20the%20extra%20dropped%20calls%20and%20%E2%80%98unclassified%E2%80%99%20calls.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EWe%20realize%20accurate%20telemetry%20is%20critical%20for%20our%20customers%E2%80%99%20operations%2C%20therefore%2C%20we%20will%20deploy%20a%20change%20to%20exclude%20these%20sessions%20from%20the%20Call%20Quality%20Dashboard%20by%20February%201st%2C%202019%2C%20and%20in%20the%20coming%20weeks%20the%20fix%20will%20be%20implemented%20in%20Call%20Analytics%20as%20well.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E(Kudos%20to%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F50347%22%20target%3D%22_blank%22%3E%40Siunie%20Sutjahjo%3C%2FA%3E%20for%20the%20collaboration%20to%20co-author%20this%20blog%20post)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-327015%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20noticed%20a%20trend%20of%20increased%20audio%20drop%20failure%20rate%20in%20the%20order%20of%20extreme%20magnitude%20and%20unclassified%20audio%20stream%20counts%20reported%20in%20CQD%20for%20customers%20that%20have%20transitioned%20to%20Teams%2C%20and%20we%20would%20like%20to%20address%20your%20concerns%20on%20this%20issue.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-327015%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECall%20Quality%20Dashboard%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECalling%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMeetings%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EQuality%20of%20Experience%20Review%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-334356%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Rise%20of%20Drop%20Failure%20Rate%20and%20Unclassified%20Streams%3A%20Explained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-334356%22%20slang%3D%22en-US%22%3E%3CP%3EAppreciate%20the%20transparency.%20Good%20work.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327830%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Rise%20of%20Drop%20Failure%20Rate%20and%20Unclassified%20Streams%3A%20Explained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327830%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F15793%22%20target%3D%22_blank%22%3E%40Aaron%20Steele%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327163%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Rise%20of%20Drop%20Failure%20Rate%20and%20Unclassified%20Streams%3A%20Explained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327163%22%20slang%3D%22en-US%22%3EWe%20are%20testing%20the%20backfill%20at%20this%20time%20to%20see%20if%20we%20can%20correct%20the%20historical%20data.%20TBD.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327161%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Rise%20of%20Drop%20Failure%20Rate%20and%20Unclassified%20Streams%3A%20Explained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327161%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20findings%20guy!%20Do%20you%20plan%20to%20apply%20those%20new%20filters%20to%20exiting%20data%20or%20will%20it%20apply%20only%20for%20calls%20staring%20after%201st%20February%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327135%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Rise%20of%20Drop%20Failure%20Rate%20and%20Unclassified%20Streams%3A%20Explained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327135%22%20slang%3D%22en-US%22%3EGreat%20job%20Agus%20and%20everyone%20involved%20on%20root-causing%20this%20and%20coming%20to%20quick%20resolution%20for%20our%20customers.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327070%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Rise%20of%20Drop%20Failure%20Rate%20and%20Unclassified%20Streams%3A%20Explained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327070%22%20slang%3D%22en-US%22%3E%3CP%3EAgreed%20with%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72542%22%20target%3D%22_blank%22%3E%40adam%20deltinger%3C%2FA%3E%20-%20a%20good%20idea%20moving%20forward.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327055%22%20slang%3D%22en-US%22%3ERe%3A%20The%20Rise%20of%20Drop%20Failure%20Rate%20and%20Unclassified%20Streams%3A%20Explained%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327055%22%20slang%3D%22en-US%22%3E%3CP%3ESounds%20like%20a%20good%20idea%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

As customers start transitioning from Skype for Business to Microsoft Teams for calling and meetings, a lot of attentions have been given to understanding how Teams behave in their environment where Skype for Business has been operating previously.

 

Call Quality Dashboard (CQD) is the tool of choice that allows us to gain insights into the reliability and quality of calls made using Teams over a period of time, and you can also use Call Analytics for a point-in-time, call reliability and quality troubleshooting efforts. We have also published the Quality of Experience Review (QER) guidance that complements CQD by providing a comprehensive guide to leverage it to achieve and maintain high quality experiences for your end users.


Looking at the several customers’ data from the past six months, we have noticed a trend of increased audio drop failure rate in the order of extreme magnitude and unclassified audio stream counts affecting several customers that we’ve been working with, especially from the middle of November onwards.

 

CQD-1.pngCustomer 1 Summary Report

 

CQD-2.pngCustomer 2 Summary Report

 

Based on our investigation, the dropped calls and ‘unclassified’ calls are inactive audio sessions in a screen sharing only, two-person ad-hoc group call. There is no real user impact, but there is an artefact due to how the feature was implemented, which was the extra dropped calls and ‘unclassified’ calls.


We realize accurate telemetry is critical for our customers’ operations, therefore, we will deploy a change to exclude these sessions from the Call Quality Dashboard by February 1st, 2019, and in the coming weeks the fix will be implemented in Call Analytics as well.

 

(Kudos to @Siunie Sutjahjo for the collaboration to co-author this blog post)

7 Comments

Sounds like a good idea :)

Respected Contributor

Agreed with @adam deltinger - a good idea moving forward.

Microsoft
Great job Agus and everyone involved on root-causing this and coming to quick resolution for our customers.
Occasional Contributor

Great findings guy! Do you plan to apply those new filters to exiting data or will it apply only for calls staring after 1st February

 

Thanks

Microsoft
We are testing the backfill at this time to see if we can correct the historical data. TBD.
Occasional Contributor

Thanks @Aaron Steele 

Senior Member

Appreciate the transparency. Good work.