Forum Discussion
'Call Waiting' notification
There's a few threads discussing 'Busy on Busy' (BoB) but I can't find any discussing the terrible user experience when BoB is disabled. With a traditional telephony solution where 'Call Waiting' is...
My apologies but my general frustration with Teams telephony got the better of me... 😉
My main concern is that calls to services with Busy on Busy activated that do not have a call forward no answer destination set fail when the service is already active on a call. The caller should get busy tone under those circumstances. Some users don't want a call forward no answer destination set.
My main concern is that calls to services with Busy on Busy activated that do not have a call forward no answer destination set fail when the service is already active on a call. The caller should get busy tone under those circumstances. Some users don't want a call forward no answer destination set.
Stewart_Ross Haha, no worries 
That's an interesting observation re: the Busy on Busy behavior. I recall seeing that as well when we had a user who requested that setting on their line. Calls from the PSTN got a busy signal as expected, but other Teams users would get a "Call failed" message when calling the "busy" user.
That user got so frustrated with Teams Phone (specifically, the nightmare that is native Teams desk phones) that they complained to upper management and we had to move them back to an analog land line, but that's a story for another time.
- Yes, we have ongoing issues with lack of features, strange behaviour in general, lack of/weird reporting and Teams desk phones in particuar. I don't think Teams Calling is a high priority for Microsoft.