Teams Business Voice Call Latency

%3CLINGO-SUB%20id%3D%22lingo-sub-1389895%22%20slang%3D%22en-US%22%3ETeams%20Business%20Voice%20Call%20Latency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1389895%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22_1qeIAgB0cPwnLhDF9XSiJM%22%3ETeams%20call%20latency%20is%20waaaay%20better%20than%20we%20were%20getting%20with%20our%20previous%20VOIP%20provider%20(Mitel)%20but%20I%20still%20felt%20it%20was%20a%20bit%20worse%20than%20PSTN-%26gt%3BPSTN%20calling.%20I%20grabbed%20an%20audio%20recorder%20and%20audio%20editing%20software%20and%20did%20some%20testing%20to%20see%20what%20the%20actual%20mouth%20to%20ear%20latency%20was.%3C%2FP%3E%3CP%20class%3D%22_1qeIAgB0cPwnLhDF9XSiJM%22%3E%26nbsp%3B%3C%2FP%3E%3CUL%20class%3D%22_33MEMislY0GAlB78wL1_CR%22%3E%3CLI%3E%3CP%20class%3D%22_1qeIAgB0cPwnLhDF9XSiJM%22%3E%3CSTRONG%3EPSTN%20(Bell%20Canada%20Cell%20Network)%20to%20Windows%20(Teams)%3A%20450ms%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%20class%3D%22_1qeIAgB0cPwnLhDF9XSiJM%22%3E%3CSTRONG%3EWindows%20(Teams)%20to%20PSTN%20(Bell%20Canada%20Cell%20Network)%3A%20630ms%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%20class%3D%22_1qeIAgB0cPwnLhDF9XSiJM%22%3E%3CSTRONG%3ETotal%20round%20trip%3A%201080ms%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%20class%3D%22_1qeIAgB0cPwnLhDF9XSiJM%22%3EFor%20reference%2C%20the%20general%20accepted%20round%20trip%20latency%20limit%20for%20decent%20call%20quality%20is%20300ms%20(%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fwww.lifewire.com%2Fwhat-is-latency-and-how-it-can-be-reduced-3426314%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20ugc%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.lifewire.com%2Fwhat-is-latency-and-how-it-can-be-reduced-3426314%3C%2FA%3E%2C%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fgetvoip.com%2Fblog%2F2018%2F12%2F20%2Facceptable-jitter-latency%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20ugc%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgetvoip.com%2Fblog%2F2018%2F12%2F20%2Facceptable-jitter-latency%2F%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E)%3C%2FP%3E%3CP%20class%3D%22_1qeIAgB0cPwnLhDF9XSiJM%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22_1qeIAgB0cPwnLhDF9XSiJM%22%3E1080ms%20leaves%20something%20to%20be%20desired.%20It's%20workable%20but%20I%20still%20find%20parties%20interrupting%20each%20other%20on%20calls%20fairly%20often.%20I%20didn't%20test%20PSTN-%26gt%3BPSTN%20but%20I'm%20sure%20it%20will%20be%20much%20lower.%3C%2FP%3E%3CP%20class%3D%22_1qeIAgB0cPwnLhDF9XSiJM%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22_1qeIAgB0cPwnLhDF9XSiJM%22%3EFor%20reference%2C%20my%20Windows%20desktop%20is%20on%20a%20gigabit%20fiber%20internet%20connection%20with%204ms%20latency%20to%20Google%20DNS%20servers.%20At%20the%20time%20of%20testing%20there%20was%20very%20little%20utilization%20of%20my%20internet%20link%20or%20the%20compute%20resources%20of%20my%20fairly%20modern%20Windows%20desktop.%3C%2FP%3E%3CP%20class%3D%22_1qeIAgB0cPwnLhDF9XSiJM%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22_1qeIAgB0cPwnLhDF9XSiJM%22%3EI'm%20curious%20as%20to%20how%20much%20the%20recent%20surge%20in%20Teams%20demand%20is%20a%20factor%20here%20and%20how%20much%20of%20this%20latency%20is%20base%20system%20latency.%20Has%20anyone%20else%20done%20measurements%20like%20these%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1389895%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECommunity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1680742%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Business%20Voice%20Call%20Latency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1680742%22%20slang%3D%22en-US%22%3EI%20appreciate%20the%20detail%20of%20your%20testing%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F668210%22%20target%3D%22_blank%22%3E%40davegravy%3C%2FA%3E%2C%20I%20am%20just%20running%20a%20POC%20now%20and%20am%20testing%20a%20multi%20region%20deployment%2C%20I%20have%20had%20some%20test%20calls%20within%20the%20EU%20and%20within%20the%20US%2C%20I%20found%20that%20the%20latency%20was%20unnoticeable%20on%20my%20EU%20based%20calls%20(user%20in%20EU%20calling%20via%20SBC%20and%20VG%20in%20EU%20to%20a%20cell%20phone%20in%20the%20EU).%3CBR%20%2F%3E%3CBR%20%2F%3EBut%20the%20calls%20in%20the%20US%20are%20experiencing%20about%20a%201%20second%20latency%20for%20calls%20routing%20from%20a%20US%20based%20Teams%20user%20%26gt%3B%20Via%20US%20based%20SBC%20%26amp%3B%20VG%20%26gt%3B%20US%20cell%20phone.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20will%20have%20to%20record%20it%20and%20confirm%20if%20this%20issue%20is%20a%20US%20only%20based%20issue.%3CBR%20%2F%3E%3CBR%20%2F%3ENow%2C%20I%20did%20run%20a%20test%20where%20I%20connected%20to%20a%20VPN%20gateway%20in%20Japan%20to%20force%20my%20client%20to%20route%20from%20Japan.%20In%20that%20call%20where%20I%20was%20looping%20my%20voice%20traffic%20around%20the%20world%20(from%20EU)%20I%20was%20getting%20about%20a%202%20second%20delay.%3CBR%20%2F%3E%3CBR%20%2F%3EMakes%20we%20wonder%20if%20the%20NSA%20is%20forcing%20MS%20Teams%20traffic%20via%20their%20DC%20for%20them%20to%20monitor%20communications.%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Teams call latency is waaaay better than we were getting with our previous VOIP provider (Mitel) but I still felt it was a bit worse than PSTN->PSTN calling. I grabbed an audio recorder and audio editing software and did some testing to see what the actual mouth to ear latency was.

 

  • PSTN (Bell Canada Cell Network) to Windows (Teams): 450ms

  • Windows (Teams) to PSTN (Bell Canada Cell Network): 630ms

  • Total round trip: 1080ms

For reference, the general accepted round trip latency limit for decent call quality is 300ms ( https://www.lifewire.com/what-is-latency-and-how-it-can-be-reduced-3426314, https://getvoip.com/blog/2018/12/20/acceptable-jitter-latency/ )

 

1080ms leaves something to be desired. It's workable but I still find parties interrupting each other on calls fairly often. I didn't test PSTN->PSTN but I'm sure it will be much lower.

 

For reference, my Windows desktop is on a gigabit fiber internet connection with 4ms latency to Google DNS servers. At the time of testing there was very little utilization of my internet link or the compute resources of my fairly modern Windows desktop.

 

I'm curious as to how much the recent surge in Teams demand is a factor here and how much of this latency is base system latency. Has anyone else done measurements like these? 

1 Reply
Highlighted
I appreciate the detail of your testing @davegravy, I am just running a POC now and am testing a multi region deployment, I have had some test calls within the EU and within the US, I found that the latency was unnoticeable on my EU based calls (user in EU calling via SBC and VG in EU to a cell phone in the EU).

But the calls in the US are experiencing about a 1 second latency for calls routing from a US based Teams user > Via US based SBC & VG > US cell phone.

We will have to record it and confirm if this issue is a US only based issue.

Now, I did run a test where I connected to a VPN gateway in Japan to force my client to route from Japan. In that call where I was looping my voice traffic around the world (from EU) I was getting about a 2 second delay.

Makes we wonder if the NSA is forcing MS Teams traffic via their DC for them to monitor communications.