03-27-2019 03:49 PM
03-27-2019 03:49 PM
So, our boss is a huge MSFT fan and wants to put all our eggs in the MSFT basket. That being said we are looking to move away from our current VoIP provider and move to Teams for a permanent solution. We currently have 2 Yealink T58A phones that are working great with our E3 license skus with phone system and domestic calling plans.
So, we attempted to set up an auto attendant. We got some voice recordings done for the greetings and menu options. Built out a couple of queues and tried to test them.
Mind you, we have had zero issues making or receiving calls to or from the DID lines.
When you call the queue line, there is a 3-5 second delay before the call is connected. (I understand this is a current issue being worked on) But, even once the call does connect, the agent cannot hear the caller. The caller can hear the agent with no issue. But the agent must place the call on hold and retrieve it for the audio to connect properly.
This has been tested and reproduced now with the Yealink T58A, Yealink T56A, and Audiocodes C450HD.
Anyone else out there experience this? If so, how did you resolve it? Is it just me? What am I missing?
I've had a ticket open with MSFT support for almost 3 weeks and it just got escalated to Tier 3 today. I have almost $1300 tied up in phones that are basically paperweights until they can do what the boss wants.
I'll try anything you can throw at me.
Thanks in advance!
03-27-2019 04:41 PM
How's your experience when you directly call to your call queue sip/teams address?
Are you using direct routing? or using Microsoft Phone system?
I have done some testing with Yealink T58A and T56A and didn't see any issues with Call Queues with using MSFT Phone System.
There was no delay or Audio issues..
03-27-2019 05:00 PM
@heartfrappe - YES! We are having the exact same issue with call queues, both when answering from the Teams desktop client and a Yealink T56A in S4B mode (the Teams firware is buggy still on this phone).
Agent picks up and either it takes a few seconds or it doesn't connect at all and the caller is stuck somewhere in between. Callers report still hearing the queue music, but can also sort of hear the agent. Agents then have to try multiple times of hanging up and answering to retrieve a call before it actually retrieves.
After a full frustrating day of this (probably over 100 lost calls) we disabled the queue and are now using call groups, which works reliably. I have a support ticket open, but they're just data gathering at this point.
03-27-2019 05:59 PM
Geez is this STILL an issue after all this time? We had this problem with Polycom handsets but were led to believe it was a Microsoft problem and not a phone vendor problem. We couldn't answer/connect with CQ calls at all and had to abandon using them. I've recently been testing the Yealink native teams phones also, hoping maybe they had a better solution, but haven't gotten around to testing CQs yet.
03-28-2019 08:39 AM
We have the issue too with Yealink T56A with Teams firmware. Call Queues get one way audio. Same question is being asked in the Yealink forums too: http://forum.yealink.com/forum/showthread.php?tid=42450
03-28-2019 08:50 AM
@Bob Manjoney - I was never able to get CQ's working with our Polycom VVX phones, either, which is why I bought the Yealink. However since we're having problems even with the desktop client, it leads me to think it isn't just the phones that are causing the problems. Of course, it could be network related, but outbound, DID, and transferred calls all operate fine and have great audio quality, so I'm not sure what network issue would prevent CQ's from working correctly.
04-09-2019 06:00 AM
04-09-2019 06:29 AM - edited 04-09-2019 06:31 AM
What I have done is burn a couple additional E3 license to create full users accounts that I have named Sales Queue, Operator Queue, TechSupport Queue.
I have enabled these users for voice and given them a phone number. (in my case it is with Direct Routing)
After the user is provisioned I will log in as the user and create a call group and set calls to forward directly to the call group. (call groups can be up to 5 users and can be rung all at once or in order they are added.)
In the Auto Attendant, instead of sending the call to a Call Queue, i send to user and select the Queue user i have set for that.
When you do this, it eliminates the 3-4 second delay as the calls to the call group act like a DID call. It has also fixed all issues I have had in one way audio and disconnected calls on SfB firmware phones.
It can be a little more costly but it does resolve all of the issues that I had with Call Queues.
06-07-2019 02:47 AM
@Stephan SwinfordWe're having the exact same issues on a Yealink T58A - we're noticing that inbound calls to our service number which are routed through Auto Attendant and then distributed to agents via Call Queue, that when the agent tries to pick up there is about a 5 second delay in the call being transferred and that the calls are often stuck on hold when they are transferred with no clear way of taking them off hold. Have you or anybody else in the thread heard any more about a fix for this issue?
06-08-2019 01:04 PM
@ciaranmadden our issues with the call queue appear to have been resolved with the recent update to AA & CQ that moved those services from Skype Admin to Teams Admin. There is still a slight delay, less than a second, however our T56A is still using the S4B firmware since I'm still finding the Teams firmware to be too buggy for production use.
06-13-2019 03:22 AM
@Stephan Swinfordi'm experiencing a similar issue. Using Teams only mode, and Yealink Teams edition T56A, updated with the latest firmware and Teams update:
-accepting direct calls, transfer and hold ✔
-accepting queue calls, transfer and hold :cross_mark:
The … button is grayed out when accepting queue calls. What to do?
06-13-2019 03:25 AM
06-13-2019 04:29 AM
06-13-2019 04:44 AM
@ciaranmaddenso I did some testing. The issue with the display saying, the call is on hold, still occurs from time to time. But If the call is connected correctly you can use the hard (phone) buttons to put a call on hold or transfer it :ok_hand:
06-13-2019 04:54 AM
06-13-2019 05:10 AM
06-14-2019 01:33 PM
@ciaranmaddenin the following discussion, the issue regarding 'you are on hold' is being discussed about.. https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/Auto-Attendant-and-Call-Queues-Service-U...
07-29-2019 08:22 AM
@heartfrappe - I am having the same issues, which I reached out to the community. I am working with the Audiocodes C450HD model phones. I set them up pretty much you would setup an IP phone with the sharing of the data port with the PC and phone, since the phone is POE. All calls began experiencing the delay when the company switch from Cisco. What we are experiencing is first there is the "Team" ring of about 5 seconds, then you get the regular phone ring for about 5 seconds. Then once the call is connected, we can hear the other person, but it takes up to 10 seconds for them to hear us. However, once the called is successful with bidirectional connectivity, the call is good. Currently, what I did was gave each phone it's own ethernet port connection, and the issue still exist. This happens with calling and more so, receiving calls.
11-05-2019 08:09 AM