> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors/alarm-sounds-do-not-play.md).

# Alarm sounds do not play

Understand why lower-priority alarms make no sound while a higher-priority alarm is active.

Lower-priority alarms make no sound while a higher-priority alarm is active.

### Symptom

Alarms that should make their alarm sound are silent. For example, Medium Priority alarms in the Alarm Viewer play no sound.

### Cause

This is typically caused when the sound configuration in **Configuration Client → Server Properties → Event Priorities** has been altered from the default.

In the example below, **Medium High Priority** has been set to **No Sound**. The expectation is that the Medium Priority alarms should still make their alarm sound, because only Medium High Priority was set to No Sound.

![Alarm Viewer with a Medium High Priority alarm and two Medium Priority alarms, beside Server Properties, Event Priorities, where Medium High Priority is set to No Sound and every other priority to Default Sound](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d06f4ee1a573fe446844a673883687928c61ceb2%2FSECHUB-TS-ALARM-SOUNDS-01-medium-high-no-sound.jpg?alt=media)

However, the system uses only **one audio channel**. It mutes the Medium Priority sound to play the Medium High Priority sound, even though that sound is set to No Sound. So if a higher-priority alarm is active and has **No Sound** selected, the audio of lower alarms is muted to play the null "No Sound".


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors/alarm-sounds-do-not-play.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
