Teams Call Queue + iOS Application call handling is broken

%3CLINGO-SUB%20id%3D%22lingo-sub-331368%22%20slang%3D%22en-US%22%3ETeams%20Call%20Queue%20%2B%20iOS%20Application%20call%20handling%20is%20broken%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331368%22%20slang%3D%22en-US%22%3E%3CP%3E%26gt%3B%20Steps%20to%20replicate%3C%2FP%3E%3CP%3E%26gt%3B%20Setup%20Call%20Queue%3C%2FP%3E%3CP%3E%26gt%3B%20Put%20Agents%20with%20domestic%20calling%20plan%20in%20Call%20Queue%3C%2FP%3E%3CP%3E%26gt%3B%20Dial%20Call%20Queue%26nbsp%3B%3C%2FP%3E%3CP%3E*Teams%20App%20Rings*%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpon%20answer%2C%20the%20outbound%20caller%20can%20hear%20the%20person%20who%20answered.%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20inbound%20caller%20audio%20is%20completely%20broken.%20You%20must%20toggle%20the%20speaker%20phone%20button%20(on%20the%20teams%20app)%20from%20speaker%2C%20back%20to%20earpiece%20(and%20often%20do%20it%20again)%20in%20order%20for%20the%20inbound%20audio%20to%20even%20connect%20at%20all.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMost%20of%20the%20time%20this%20is%2020-30%20seconds%20into%20the%20call%20with%20completely%20muted%20inbound%20audio.%20While%20the%20caller%20can%20hear%20the%20person%20who%20answered%20(my%20helpdesk%20agent)%20the%20entire%20time.%20Note%3A%20The%20inbound%20audio%20will%20not%20connect%20at%20all%20if%20you%20do%20not%20manually%20toggle%20the%20speaker%2Fearpiece%20option%20on%20and%20off%20(inside%20the%20teams%20application).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20were%20attempting%20to%20use%20the%20Teams%20phone%20application%20to%20run%20our%20call%20queue%2C%20but%20this%20is%20unacceptable%20for%20production%20use.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-331368%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-1473701%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Call%20Queue%20%2B%20iOS%20Application%20call%20handling%20is%20broken%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1473701%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20a%20similar%20problem%20right%20now.%20The%20user%20has%20to%20communicate%20via%20speaker.%20So%20we%20can't%20even%20just%20toggle%20the%20speaker%20on%20and%20off%2C%20we%20have%20to%20use%20the%20speaker.%3CBR%20%2F%3EPersonal%20calls%20have%20no%20issues%20whatsoever.%3CBR%20%2F%3E%3CBR%20%2F%3EAt%20the%20moment%20it%20seems%20like%20only%20iPhone6%20S%20has%20this%20issue.%20But%20I%20have%20to%20check%20if%20this%20is%20a%20100%25%20accurate%20or%20not.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F270811%22%20target%3D%22_blank%22%3E%40Mike6-_-7%3C%2FA%3E%26nbsp%3B%20Did%20you%20find%20a%20solution%20for%20this%20in%20the%20meantime%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Regular Visitor

> Steps to replicate

> Setup Call Queue

> Put Agents with domestic calling plan in Call Queue

> Dial Call Queue 

*Teams App Rings*

 

Upon answer, the outbound caller can hear the person who answered. 

The inbound caller audio is completely broken. You must toggle the speaker phone button (on the teams app) from speaker, back to earpiece (and often do it again) in order for the inbound audio to even connect at all. 

 

Most of the time this is 20-30 seconds into the call with completely muted inbound audio. While the caller can hear the person who answered (my helpdesk agent) the entire time. Note: The inbound audio will not connect at all if you do not manually toggle the speaker/earpiece option on and off (inside the teams application).

 

We were attempting to use the Teams phone application to run our call queue, but this is unacceptable for production use. 

1 Reply
Highlighted

We have a similar problem right now. The user has to communicate via speaker. So we can't even just toggle the speaker on and off, we have to use the speaker.
Personal calls have no issues whatsoever.

At the moment it seems like only iPhone6 S has this issue. But I have to check if this is a 100% accurate or not.

@Mike6-_-7  Did you find a solution for this in the meantime?