Beeping When Transferring Calls
Whenever I go to transfer a call in Teams, there is an annoying beep that sounds over and over again until I make a new call. It is like a hold signal. This needs done away with.
Anonymous
shared this idea
43 comments
-
Stefan
commented
I have the same issue. Not suitable for working like that. Quick fix is needed
-
Anonymous
commented
Very loud beeping/alarm sound when trying to join a group call in MS Teams. But with making a test call no issue is observed. Looks like everyone in this forum has the same issue. So annoying. Teams, please do something about it.
-
Anonymous
commented
Still no fix on this issue? How long will it take. This first post was from 5/2019... I think it's time Microsoft fixed this issue.
-
Anonymous
commented
I have the same issue! It's so annoying. I called Plantronics and they said it was a bug and if I could wait a few months, they were developing a fix for it. Heck with that, this is going back today!!!
-
Anonymous
commented
TO make the beeping stop until the next transfer. Click on your picture. Go to settings. Go to devices. Open a test call. Close the test call. No more beeping. Now hopefully MS Teams can stop pointing the finger and fix it.
-
Wusaweki
commented
Same issue here. Using Jabra headset.
Conference sessions are basically working but only for about 30 seconds, and joined with annoying 'alarm' sound.Attached is a recording of the sound.
-
Anonymous
commented
Microsoft, any update here, please?
-
Andy Baker
commented
We recently migrated to Teams calling about 3 weeks ago. We are configure for direct routing and our circuit is an AT&T PRI.
We have experienced this issue on both internal calls placed on hold and incoming calls to our main line which rings both reception desk phones who are part of a call queue.
The reception desk uses Yealink T56A desk phones and not headsets. Most other staff are using Audiocodes C450HD desk phones, Yealink T55A or using Teams on their computer or mobile phones. The issue is the same on all devices. Our "on hold" music is just a wave file of a phone ringing with a pause. Many callers hang up while being transferred because the beeping makes them think the call has disconnected. This has been one of the most frustrating things with using Teams Calling for us. -
Garrett
commented
We just bought all new Voyager Focus UCs for our office to switch to Teams calling and encountered this double beep issue after transferring calls. Restarting Teams will stop the beeping, but restarting the headset itself will not.
-
Martin
commented
Having this same issue after the voicemail migration from Skype to Teams...
-
Anonymous
commented
Having this issue with multiple accounts on various make and model of headset.
Please resolve this ASAP.
-
Dustin Estep
commented
I am having this issue with PLT Voyager 4210 and Blackwire 5210
-
John Thorburn
commented
Please resolve
-
George Lomboy
commented
I use Plantronics Voyager UC 5200. I tried every trick by the book to resolve the double beep that suddenly came out of nowhere when my headset switched to answer a phone call while I was doing a Teams meeting to no effect.. Stumbled on this thread... it certainly cleared up the situation that I was faced with.
Initiating another call (a test call under Audio devices settings) within Teams did the trick.
-
Al
commented
@Ben - I'll doublecheck this but it seems there is a recognised fix on the way from what you say. I won't hold my breath though!
-
Ben Cromie
commented
Update from Microsoft voice TSP: Microsoft and Plantronics/Poly, as well as Jabra and other headset brands are aware of the issue and developing a fix. The issue arises from a software fault with both the headset and Teams client (i.e. on both sides).
"Plantronics/Poly has already released a temporary fix for this issue, applicable to some of their headset models. I can check what’s the status for Jabra, but the Teams-side of the fix is still to come. No confirmed ETA on the fix from Teams-side though."
-
Ben Cromie
commented
@Al - are you sure about that, note that the issue only affects OUTBOUND calls that are being transferred (and calls received from an Office 365 Call Queue are outbound calls from the perspective of the client). I'm still able to reproduce the problem on Teams client using both "Transfer" or "Consult then transfer". Running Teams v1.3.00.2160 and Plantronics Voyager Focus UC v.366.
If I transfer an INBOUND call (i.e. that came into my direct number, not via a Call Queue) then the double-beep issue post-transfer doesn't occur.
-
Al
commented
I sorted out what it is for us on our site (with mixed environment of Teams + SfB).
We are using Plantronics 300/315 headsets.
It is to do with transferring a call from Teams to a Skype user using either the 'Transfer' or 'Transfer with Consult' options.
If you use 'Transfer with Consult' from Teams to a Teams user there is no beep.
We still have some staff on SfB but we plan on moving everyone across in the next few months. Once that is done, our issue should go away.
If you have the Plantronics software loaded you may want to unload that from your Taskbar as well.
Hope this helps some of you.
Rgds
Alan
-
Scott Balthazor
commented
Adding to this as we are having it affect our users as well. We were trying to standardize on Plantronics Voyager 5200 with UC (using BT600). Any work around other than having to dial and hang up would be useful.
-
Patrick Teas
commented
This phantom hold beeping also happens to all of our users. Specifically, it happens to me with Teams 1.3.00.362 (64-bit) using a Plantronics Voyager Focus UC with firmware v.366 using a BT600 dongle with firmware v.1615.