Share via

How to remove “This call is being recorded” audio message played on analog Teams endpoint (AudioCodes MediaPack / SIP Gateway / Direct Routing)

PawarUlhas-6153 0 Reputation points
2026-04-08T15:05:05.7+00:00

I am working on a issue where customer ask is, “This call is being recorded” audio message played on analog Teams endpoint (AudioCodes MediaPack / SIP Gateway / Direct Routing) to be removed.

In my research I found why this message plays and the reason is:

When a Teams call is recorded (compliance recording, 3rd‑party recording, or transcription), Microsoft Teams injects an audio notification into the call to meet legal and regulatory requirements for call recording consent—especially for PSTN and analog endpoints that do not have a visual UI to show a recording banner.

There is possibility that announcement may change to a Beep by a settings change in Microsoft Compliance Recording policy if the analog phones are covered under Compliance Recording policy. Unfortunately they are not. Due to the same, Set-CsTeamsComplianceRecordingPolicy and -DisableComplianceRecordingAudioNotificationForCalls options ruled out.

Customer current concern is, this issue is safety critical element as the extra seconds listening to the message could delay a time critical message to remove power from the railway should an incursion happen. The fact that these calls are all internal to our tenant and there will be visual signage installed at the phone locations advising of the recording.

If anyone can help here if their is an way to get this message removed or turn into beep (something save time)? Also, I have tried to search for Microsoft article or document which clearly mentioning about this by default behavior which will be a good evidence for the customer.

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Audio and video
0 comments No comments

2 answers

Sort by: Most helpful
  1. Alexis-NG 14,895 Reputation points Microsoft External Staff Moderator
    2026-04-08T16:23:05.7233333+00:00

    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:

    Diagram of the flow for when a Teams meeting or call is sent and received.

    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.User's image

    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.

    0 comments No comments

  2. Q&A Assist
    2026-04-08T15:05:34.29+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The “This call is being recorded” audio message on analog/SIP/PSTN endpoints is part of the mandatory notification behavior for Teams recording and can’t be removed or selectively disabled. For non-UI endpoints (such as analog devices via AudioCodes MediaPack, SIP Gateway, or Direct Routing), Teams uses audio notices specifically to satisfy legal and regulatory requirements when calls are recorded.

    From the documented behavior:

    • Compliance recording notifications are enforced for Teams participants.
    • For “other endpoints” (including SIP phones and PSTN callers), only audio notice is supported, not visual banners.
    • With third‑party compliance recording, “participant notification [is] enforced” and “participant consent [is] not supported,” meaning the system must always inject a recording notice when recording is active.

    Relevant details:

    • Compliance recording is implemented via certified third‑party solutions and Teams compliance recording policies. When such recording is in effect, Teams injects either a spoken notice or (where supported by policy) a tone, but the notification itself is not optional.
    • The documentation explicitly lists SIP phones and PSTN callers under “Other endpoints – audio notice,” which is the category that covers analog/SIP endpoints.
    • Microsoft only supports compliance recording solutions from certified partners and reserves the right to reject support when non‑certified solutions are used.

    Regarding changing the message to a beep:

    • The context provided only documents that notifications for “other endpoints” are audio notices; it does not document a supported way to suppress or replace the audio message with a simple beep outside of what is configurable in a Teams compliance recording policy.
    • The only configurable behavior mentioned in the context for compliance recording is via compliance recording policies and partner solutions; there is no documented option here to remove the notification entirely.

    For evidence to present to the customer, the following points from the documentation are key:

    • “Compliance recording notifications are supported for the Teams client experiences. The experiences can be both visual and audio.”
    • Under “Other endpoints – audio notice,” SIP phones and PSTN callers are explicitly listed, which aligns with analog/SIP endpoints.
    • In the comparison of convenience vs. compliance recording, “Participant notification enforced: Yes” for third‑party compliance recording.

    Based on the provided documentation, there is no supported method to remove the “This call is being recorded” audio message for analog Teams endpoints when recording is active. The notification is a required part of the compliance recording feature set.


    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.