Home

Teams Voice configuration Slowness and other voice issues

%3CLINGO-SUB%20id%3D%22lingo-sub-699548%22%20slang%3D%22en-US%22%3ETeams%20Voice%20configuration%20Slowness%20and%20other%20voice%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-699548%22%20slang%3D%22en-US%22%3E%3CP%3EAnyone%20else%20experiencing%20extreme%20slowness%20when%20provisioning%20almost%20anything%20in%20teams%20voice%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20setup%20is%20Hybrid%20with%20Direct%20routing.%26nbsp%3B%20%26nbsp%3BRoughly%203500%20total%20users%2C%203000%20of%20them%20on-prem%20voice%20in%20SfB%2C%20another%20500%20have%20made%20the%20journey%20to%20Teams%20voice.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20found%20that%20moving%20users%20from%20SfB%20to%20Teams%20an%20excruciating%20slow%20one.%26nbsp%3B%20The%20commands%20'take'%20instantly%20-%20but%20the%20application%20of%20the%20commands%20take%20forever.%26nbsp%3B%20%26nbsp%3BFor%20instance%20-%20I%20can%20do%20a%20move%20of%20a%20user%20from%20on-prem%20to%20cloud%2C%20and%20it%20shows%20the%20user%20in-cloud%20reasonably%20within%20a%20few%20moments.%26nbsp%3B%20%26nbsp%3BHowever%20-%20it%20takes%20(seemingly)%20minimal%20of%204-6%20hours%2C%20but%20usually%20closer%20to%2020-22%20hours%20before%20a%20user%20gets%20policy%2C%20a%20dial-pad%2C%20the%20ability%20to%20call%20etc.%26nbsp%3B%20%26nbsp%3B(Receiving%20calls%20is%20usually%20near%20instant%20-%20but%20the%20ability%20to%20get%20a%20dial-pad%20takes%20forever).%26nbsp%3B%20Creating%20a%20new%20call%20queue%20(Resource%20account%2C%20queue%2C%20adding%20a%20%23%20etc)%20takes%20similar%20times.%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BWe%20even%20tried%20to%20pre-build%20accounts%20(unassign%20a%20phone%20%23%20and%20assign%20it%20later)%20and%20even%20assigning%20a%20fake%20%23%20and%20flipping%20it%20during%20a%20migration%20window.%26nbsp%3B%20%26nbsp%3BBoth%20of%20which%20caused%20outages%20between%2012-20%20hours%20for%20those%20call%20queues.%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EQueue%20memberships%20are%20done%20via%20security%20group%20on%20prem%26nbsp%3B%20(AD%20connect%20to%20Azure%2C%20etc).%26nbsp%3B%20%26nbsp%3BChanging%20group%20membership%20takes%204%2B%20hours%20(minimum)%20and%20worst%20I've%20had%20is%2014%2B%20hours.%26nbsp%3B%20%26nbsp%3B%20I%20can%20force%20a%20delta%20sync%2C%20and%20see%20it%20in%20Azure%20AD%20near%20instantly%2C%20but%20before%20Teams%20picks%20it%20up%20or%20'applies'%20the%20change%20is%20forever.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20-%20Hybrid%20routing%20(Audiocodes%20SBC)%20there's%20a%20substantial%20lag%20in%20answering%20calls%20(5-10%20seconds%20regularly).%26nbsp%3B%20%26nbsp%3BWe're%20not%20using%20Direct%20Media%20which%20may%20make%20this%20better%3B%20but%20driving%20our%20users%20nuts%20(we%20didn't%2Fdon't%20have%20this%20issue%20in%20SfB%20on%20premise%20before).%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20on%20the%20call%20queues%20-%20(not%20a%20slowness%20issue%2C%20but%20just%20another%20issue%20reporting)%3A%26nbsp%3B%20SfB%20firmware%20phones%20(3pip)%20cannot%20answer%20a%20cloud%20call%20queue%20(yet%20it%20rings)%20-%20it%20must%20be%20answered%20by%20a%20Teams%20Client%20(3pip%20phones%20can%20answer%20direct%20calls%20just%20fine).%26nbsp%3B%20%26nbsp%3BAlso%20-%20any%20response%20group%20(on%20premise)%20if%20it%20includes%20any%20'Teams'%20user%20-%20the%20calls%20to%20queue%20instantly%20get%20picked%20up%20by%20the%20voicemail%20of%20that%20Teams%20user.%26nbsp%3B%20%26nbsp%3BHowever%20-%20if%20you%20have%20a%20Teams%20call%20queue%2C%20it%20appears%20you%20can%20have%20an%20on-premise%20SfB%20user%20answer%20fine.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETeams%20as%20a%20single-line%20handset%20seems%20to%20work%20well%20(direct%20calls%20in%2Fout%20-%20once%20you%20move%20past%20the%20delay%20in%20provisioning)%20-%20but%20any%20advanced%20feature%20and%20it%20seems%20to%20completely%20fall%20apart.%26nbsp%3B%20%26nbsp%3BEverything%20else%20about%20Teams%20is%20fantastic%20-%20I'm%20a%20huge%20advocate%20for%20Teams%3B%20but%20this%20delay%2Fprovisioning%20is%20killing%20us.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELast%20note%3A%20We%20did%20bring%20up%20the%20slowness%20with%20MSFT%20Premier%20(which%20we%20talked%20directly%20to%20product%20group)%3B%20and%20the%20answer%20was%20%22Well%20we%20met%20a%2024%20hour%20SLA%22%20which%20is%20complete%20b.s.%26nbsp%3B%20Try%20troubleshooting%20something%20with%20your%20end%20users%20-%20make%20a%20change.%26nbsp%3B%20Take%20a%20guess%20if%20it%20will%20take%20effect%20within%202%20hours%20or%2020%20hours%2C%20try%20again%20-%20and%20only%20then%20to%20realize%20you%20need%20one%20more%20change%20and%20rinse%2Frepeat.%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-699548%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-709495%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Voice%20configuration%20Slowness%20and%20other%20voice%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-709495%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20are%20not%20the%20only%20one%2C%20I%20also%20see%20the%20slowness%20when%20doing%20changes%20in%20Teams%20like%20assigning%20policies.%20I%20heard%20that%20Microsoft%20are%20aware%20of%20this%20and%20working%20to%20get%20an%20better%20solution%20but%20I%20don%20know%20when.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20the%20Direct%20Routing%20and%20lag%20when%20answering%20calls%20I've%20not%20noticed.%20I've%20seen%20that%20problem%20when%20answering%20Call%20Queues%20calls%20on%20a%203PIP%20phone%2C%20then%20you%20have%20to%20wait%20for%20a%20couple%20of%20seconds%20before%20the%20Callee%20can%20hear%20anything%20from%20the%20Caller.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20should%20also%20talk%20to%20your%20Service%20Delivery%20Manager%20at%20Microsoft%20and%20they%20will%20be%20able%20to%20get%20some%20attention%20to%20this%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-710101%22%20slang%3D%22en-US%22%3ERE%3A%20Teams%20Voice%20configuration%20Slowness%20and%20other%20voice%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-710101%22%20slang%3D%22en-US%22%3EI%20had%20to%20wait%20one%20Week%20after%20the%20Teams%20direct%20routing%20configuration%20to%20see%20the%20phone%20working%20on%20Teams.%20The%20same%20issue%20cofiguring%20AA%2FCQ%20.%20Hope%20that%20MS%20will%20fix%20a.s.a.p.%3C%2FLINGO-BODY%3E
Samuel Bentrup
New Contributor

Anyone else experiencing extreme slowness when provisioning almost anything in teams voice?

 

Our setup is Hybrid with Direct routing.   Roughly 3500 total users, 3000 of them on-prem voice in SfB, another 500 have made the journey to Teams voice.  

 

We've found that moving users from SfB to Teams an excruciating slow one.  The commands 'take' instantly - but the application of the commands take forever.   For instance - I can do a move of a user from on-prem to cloud, and it shows the user in-cloud reasonably within a few moments.   However - it takes (seemingly) minimal of 4-6 hours, but usually closer to 20-22 hours before a user gets policy, a dial-pad, the ability to call etc.   (Receiving calls is usually near instant - but the ability to get a dial-pad takes forever).  Creating a new call queue (Resource account, queue, adding a # etc) takes similar times.       We even tried to pre-build accounts (unassign a phone # and assign it later) and even assigning a fake # and flipping it during a migration window.   Both of which caused outages between 12-20 hours for those call queues.   

 

Queue memberships are done via security group on prem  (AD connect to Azure, etc).   Changing group membership takes 4+ hours (minimum) and worst I've had is 14+ hours.    I can force a delta sync, and see it in Azure AD near instantly, but before Teams picks it up or 'applies' the change is forever.

 

Also - Hybrid routing (Audiocodes SBC) there's a substantial lag in answering calls (5-10 seconds regularly).   We're not using Direct Media which may make this better; but driving our users nuts (we didn't/don't have this issue in SfB on premise before). 

 

Also on the call queues - (not a slowness issue, but just another issue reporting):  SfB firmware phones (3pip) cannot answer a cloud call queue (yet it rings) - it must be answered by a Teams Client (3pip phones can answer direct calls just fine).   Also - any response group (on premise) if it includes any 'Teams' user - the calls to queue instantly get picked up by the voicemail of that Teams user.   However - if you have a Teams call queue, it appears you can have an on-premise SfB user answer fine. 

 

Teams as a single-line handset seems to work well (direct calls in/out - once you move past the delay in provisioning) - but any advanced feature and it seems to completely fall apart.   Everything else about Teams is fantastic - I'm a huge advocate for Teams; but this delay/provisioning is killing us. 

 

Last note: We did bring up the slowness with MSFT Premier (which we talked directly to product group); and the answer was "Well we met a 24 hour SLA" which is complete b.s.  Try troubleshooting something with your end users - make a change.  Take a guess if it will take effect within 2 hours or 20 hours, try again - and only then to realize you need one more change and rinse/repeat.

 

 

2 Replies

Hi,

 

You are not the only one, I also see the slowness when doing changes in Teams like assigning policies. I heard that Microsoft are aware of this and working to get an better solution but I don know when.

 

For the Direct Routing and lag when answering calls I've not noticed. I've seen that problem when answering Call Queues calls on a 3PIP phone, then you have to wait for a couple of seconds before the Callee can hear anything from the Caller.

 

You should also talk to your Service Delivery Manager at Microsoft and they will be able to get some attention to this problem.

I had to wait one Week after the Teams direct routing configuration to see the phone working on Teams. The same issue cofiguring AA/CQ . Hope that MS will fix a.s.a.p.
Related Conversations