[cisco-voip] Cellphone with pararell calls

[ROZA, Ariel]

The downside is that is very prone to human error, and it may end. up in calls being evasdropped. I can´t think of any webex user fond of something like that ☹

De: Pawlowski, Adam <ajp26 at buffalo.edu>
Enviado el: martes, 16 de junio de 2020 21:41
Para: ROZA, Ariel <Ariel.ROZA at LA.LOGICALIS.COM>; cisco-voip (cisco-voip at puck.nether.net) <cisco-voip at puck.nether.net>
Asunto: RE: Cellphone with pararell calls

This sounds like an interaction with the type of phone or phone OS, and not related to Webex Teams.

I do not have this issue with hybrid calling on Teams on iOS, it appears to hook the native dialer, at least for now, which will not allow this scenario to occur.

Whoever is operating the cell will have to … well end the Teams call since there is no hold in hybrid, or not answer the cellular call ?



From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of ROZA, Ariel
Sent: Tuesday, June 16, 2020 5:59 PM
To: cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [cisco-voip] Cellphone with pararell calls

I have this situation with Webex Teams running on a cellphone:
A user has his cellular phone line and Webex Teams with Hybrid calling enabled.
He receives a call at his cellular phone line.
Then he gets a second call via Webex Teams. When he answers the second call, the first one keeps running in the background, still listening to the user having the second conversation.
Is there a way to better control this scenario? The first call should be ended or put on hold, but as those are two different apps with two unrelated audio streams, I don´t know if there is a proper way to handle them

Does anyone have any suggestions?

Thanks,

Ariel.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200617/0d30b3b2/attachment.htm>