Secondary ringer does not work and the setting is not saved

Question

Hello everyone,

We are currently experiencing two issues with the secondary ringer in Microsoft Teams:

1. Secondary ringer does not work

In Teams, the headset is configured as the primary speaker, while the notebook’s built-in “Speakers (SoundWire)” device is selected as the secondary ringer.

However, when an incoming Teams call is received, the ringtone is played only through the headset. The SoundWire speakers remain silent.

We have already performed the following checks and configuration steps:

The SoundWire speakers were explicitly selected as the secondary ringer in Teams.

The SoundWire speakers were set as the default output device in the Windows sound settings.

The headset was configured as the default communication device.

The SoundWire speakers were tested through the Windows sound settings, where audio playback works correctly.

Teams was completely closed and restarted.

The secondary ringer was changed to another device and then changed back to the SoundWire speakers.

The behaviour was tested using an actual incoming Teams call.

The issue occurs both in the locally installed Teams client and in the optimised Citrix environment.

Despite these checks, incoming calls continue to ring only through the headset.

2. The setting is not saved permanently

Additionally, the secondary-ringer selection is not saved reliably. The SoundWire speakers must repeatedly be selected again as the secondary ringer in Teams. After a restart or a new login, the setting is sometimes no longer present or is no longer applied by Teams.

Is this a known issue in the new Microsoft Teams client or in combination with SoundWire audio devices? Is there a solution or recommended workaround?

Thank you for your support.

Answer 1

Hi zana,

Welcome to the Microsoft Q&A forum.

Thank you for providing the detailed information.

I can see that you have completed the configuration and performed several troubleshooting steps; however, the issue still persists.

In this situation, I recommend creating a support ticket with Microsoft Technical Support for further investigation. The Microsoft support team has access to specialized diagnostic tools that can be used to analyze your environment and determine the root cause of this issue.

To create a support ticket with Microsoft Technical Support, please refer to the following documentation:

 Get support - Microsoft 365 admin | Microsoft Learn

If you have any questions or need further assistance, please feel free to share them in the comments on this post so I can continue to support you.

I look forward to continuing the conversation.

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.