How to rectify the "Sorry we couldn't connect you" situation when making audio calls in Ms Teams on Linux

Daren Neil Grant 126 Reputation points

My linux installation of ms teams is unable to make voice calls, receive voice calls or attend meetings. Any attempt to do so results in the connection being attempted and a ding ding of the ring, then I am presented with a view with the message "Sorry we couldn't connect you". Anyone calling in to me goes immediately to voicemail, which I am able to pickup and listen to.

I am running on a very stripped down Debian sid installation, having installed the ms teams .deb file downloaded from the 'Download Microsoft Teams' webpage.

The logs.txt file in .config/Microsoft/Microsoft Teams/ gives no information as to the call being initiated and no further information as to why the call failed.

How can I get more information about why I cannot connect to voice chats so I can rectify the situation ?



Skype for Business Linux
Skype for Business Linux
Skype for Business: A Microsoft communications service that provides communications capabilities across presence, instant messaging, audio/video calling, and an online meeting experience that includes audio, video, and web conferencing.Linux: A family of open-source Unix-like operating systems.
453 questions
0 comments No comments
{count} votes

Accepted answer
  1. Daren Neil Grant 126 Reputation points

    Resolution found:

    It would appear that the teams deb file makes no mention of being dependant upon openssl and ca-certificates and without these installed making voice calls or attending meetings ends up with the error message "Sorry we couldn't connect you"

    Installing ca-certificates and openssl rectifies the situation.

1 additional answer

Sort by: Most helpful
  1. JimmyYang-MSFT 39,141 Reputation points Microsoft Vendor

    Hi Daren!

    Does this issue persist all the time?

    Can this issue reproduce in Teams for Windows?

    What is your version of Teams for Linux?

    To narrow down this issue, it recommends you try to update the Teams for windows client version to see if it can be fixed. For more details about how to update it manually, you can refer to: