Forum Discussion
PSTN Call Drops if you put the call on hold then resume and hit transfer
Hi jxace
Our root cause was someone had defined an extra sip port on the hosted SBC trunk in our Direct routing setup
The hosted SBCs were load balancing between 2. Unfortunately though, the fqdn in the contact header means this caused problems with TEAMS.
Our SBC provider disabled the 'bad' port - then all calls were fine in the respect of any ACKs or re-invites etc between TEAMS and the SBC.Not sure if this helps but good luck
This seems to be the issue with the Latest Teams Client which is causing the issue. I have mine customer also facing the same issue. We have reported the same to Microsoft Engineering on the same.
Since we are on the latest version of the Teams Client we don't see any issues on the same.
With Regard,
Satish U
RealTime_M365 are there any further updates from engineering team.
Following are the workarounds
1. It seems I can Pick up PSTN Calls> Hold>Resume > transfer works if I unplug the headset using Teams Desktop Client.
2. Also above with Teams Web client works with headset
I am using Team certified headsets.
Teams version below
Can you please check in case MusicOnHold Capability is enabled on the policies? In case yes please try to disable the same and test the feature. This should fix it.
Let me know outcome post which we can have future insight from Internal Microsoft Team.
With Regards,
Satish U
RealTime_M365 , while I appreciate the work around, I do not want to disable MOH on the policies as its very important feature. I will work with previous work around but would appreciate if you could provide an ETA on the Teams Client used by yourself which has no issues.
Can you please check it seems that the issue is resolved on the Client for the other customer?
With Regards,Satish U
- This exact issue was happening for me. I disabled the MusicOnHold capabiity and the issue no longer persists. This is a nice workaround, but at the cost of hold music.
Also note, that when you disable hold music, it takes several hours for the change to take effect. I have had this issue and can reproduce at will. The workaround I have found is to use the web client. While using the web client calls can be placed on hold and then transferred with no issue. Also, this issue has not been seen on the Mac Teams client. It seems to be an issue only affecting. the Windows desktop client.
We also experience the same issue within Teams with calls which drops after a second time on hold or transfer.
This is only happening using a headset which is using an USB dongle or USB cable. It does not happen when connecting a headset directly on the Bluetooth of the laptop.
We have tried several brands of headset, but all of them the same issue.
So it has something to do with the Teams client.
