Managing sound and video settings during Teams meetings and calls for optimal communication
Hi PawarUlhas-6153,
Good day, and thank you for articulating your concern so clearly.
As of now, Microsoft Teams enforces an audible recording notification (“This call is being recorded”) for calls involving analog, SIP, or PSTN endpoints connected via AudioCodes MediaPack, SIP Gateway, or Direct Routing when call recording, transcription, or compliance recording is active.
For these endpoints, the audio announcement cannot be disabled, shortened, or replaced with a beep unless the endpoint is explicitly supported under a Teams Compliance Recording policy.
Using a partner solution to record Teams calls, meetings, and events lets compliance officers securely capture required communications to meet regulations like MiFID II, Dodd-Frank, FDCPA, HIPAA, and GDPR.
Compliance recording partner solutions are integrated with Teams as shown in the following diagram:
This limitation applies to:
- Analog phones connected through AudioCodes MediaPack or equivalent ATAs
- SIP Gateway–connected devices
- Direct Routing analog and PSTN endpoints
- Internal and tenant‑only calls
- Calls recorded via native recording, transcription, or third‑party/compliance recording solutions
Microsoft Teams requires participant notification when recording is active. For endpoints that do not support a visual user interface, such as analog and SIP devices, audio notification is the only supported method to indicate recording status.
Teams Compliance Recording policies provide limited control over audio notifications; however, analog and Direct Routing endpoints are not supported targets for these policies. As a result, tenant‑level configuration options (including PowerShell parameters related to compliance recording notifications) do not apply to these devices.
Furthermore, this line of service is explicitly documented as unsuitable for emergency or safety‑critical scenarios.
Microsoft Learn documentation for Teams compliance recording clearly states that participants must be notified when recording is in progress, and that notification methods depend on endpoint capabilities. For endpoints without a visual UI (such as SIP, analog, or PSTN), audio notification is required.
Changing the notification to a beep is considered a workaround and may not function reliably in all scenarios. There is no official Microsoft documentation that supports or guarantees this behavior.
For more information about compliance recording policy, please consult this document: Introduction to Microsoft Teams third-party compliance recording - Microsoft Teams | Microsoft Learn
I hope this provides enough clarity and helps you stay inform with your current situation.
In the meantime, if you see my replies bring helpful information, please kindly accept it as an answer and vote it up by your original account, which raised this question. Once marked, it will automatically pin to top. As other users will also search information in this community, your valuable vote up will definitely also help other users who have similar queries easily to find the correct channel and useful information more quickly.
Thank you for your patience and your understanding. 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.
Note: Follow the steps in this documentation to enable email notifications if you want to receive email notifications related to this topic.
