Forum Discussion
Delays when trying to answer an incoming call cloudpbx
Looks like it have been a problem for a verry long time.
Here is a possible workaround.
http://windowspbx.blogspot.no/2012/05/microsoft-lync-simple-ring-group-for.html
- Tom NoheltyNov 03, 2017Brass Contributor
We implemented this fix with our customer to get around the problem in the short term. We have had Microsoft give us 3 trail E5 and calling plan licenses to get this implemented (1 E5 for each of the office locations/ring groups). This actually works very well except for the potential long term maintenance of the solution and the wasted license cost of a dummy user and plan. We are hoping that Microsoft can fix this prior to year end so we don't have to go back to the customer and have them pay $150/month to get around an obvious design flaw with the auto attendant. If there is a way to have "free licenses" for this type of situation, that would be great so the pressure on Microsoft getting this fixed can be lessened.
- Nicholas SemenkovichDec 15, 2017Brass Contributor
We still see significant media establishment delays (4-5+ seconds) for incoming calls to call queues.
Supposedly the latest Polycom firmware (5.7.0) fixes this issue on Polycom's end (issue EN-32447) -- but we've deployed that firmware and don't see any changes -- Call Queue answering still has a huge delay.
Has anyone heard more about this issue?
- Tom NoheltyDec 17, 2017Brass Contributor
We have been working with MS advanced support. They have acknowledged the problem and are working to get the delay down to 2 seconds. There is no ETA at this point.
- Chad RoweOct 03, 2017Brass Contributor
Thanks for the feedback on this! I finally was able to get a solid answer from Microsoft that this is a known issue and they have the fix "on the roadmap." There is no solid date for fixing this, but they are trying to fix it before the end of the year. Of course, this is coming from an engineer and not a public statement so take it with a grain of salt.
Statement from a Microsoft engineer:
As discussed, this is something which is an ongoing issue in Online Auto-Attendant. As you are well aware that this feature is recently introduced in the Online and the engineering team is working on it.
The delay of calls in the call queue (something around 5seconds) is a known issue and the engineering team is already aware about the same. We have also raised our concern since we had multiple queries regarding the delay earlier. It has been reduced than before and still the scope is to reduce it lesser than 2 seconds and as I mentioned the team is working on it and we do not have an ETA for now.
I sincerely apologies for that and at present we do not have a work around to overcome this situation. However, once this is fixed or we get any update from the backend, we will keep you updated on the same.
But soon we can expect that the delay will be reduced lesser than two seconds.
However, I request you to add your valuable feedback in the below link which will be viewed by Product level group directly and we can expected this sooner.
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.skypefeedback.com%2F&data=02%7C01%7Ccrowe%40pltechnology.com%7Cb3c029dfc1a14f2a592a08d506abf68e%7Cba50d067b3dc47f5bb987d403083ef97%7C1%7C0%7C636422258014742093&sdata=1tGaIvpFwXBCRvSMKuwPNUeAOXMPhwjTV5Qp%2FIpeKEA%3D&reserved=0
Soooo I guess I'll watch the forums to see when this issue has been resolved.
- Wim AllegaertNov 21, 2019Copper ContributorAnd? 2 years later?
- Raffi_TFeb 15, 2022Copper ContributorIt is now 2022, still experiencing a delay when answering a call with Polycom vvx desk phones. I think MS is considering these phones legacy devices which do not fully support their new Teams calling service (PSTN). They say these phone will have limited functionality. So it's their way of avoiding actually addressing it. Change the name of the service (multiple times) and call the existing devices legacy. Nice solution MS.
- OliverRadcliffeOct 03, 2017Brass Contributor
I've got roughly the same answer from multiple support folks over at MS, and escalated as far as it would go. Hopefully this gets solved relatively soon.