> For the complete documentation index, see [llms.txt](https://docs.mikopbx.com/mikopbx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mikopbx.com/mikopbx/english/manual/telephony/sound-files.md).
# Sound files
Adding/Creating Audio Files in MikoPBX
## Uploading a sound file to the PBX
{% hint style="warning" %}
Supported file formats: **wav**, **mp3**, **ogg**, **m4a**, **aac**.
{% endhint %}
Audio files in MikoPBX are used in various call scenarios and interactive voice menus **(**In **IVR menu**, during **non-working hours**, in **call queues**, for various system notifications, and in **hold music**.) to play voice greetings or notify customers.
The list of available sound files is displayed in the "**Telephony"** -> "**Sound files".**
"Sound files" section
To add a new sound file, click "**Add a new sound file"**.
"add a new sound file" button
Click "**Upload a new file**" and select a sound file.
"Upload a new file" button
Correct the file name if necessary.
The name of the recording file
Save settings
"Save settings" button
{% hint style="info" %}
When working over the **https** protocol, it is possible to record an audio file using a microphone.
{% endhint %}
"Start recording" button
Custom sound files are stored on the PBX along the path **/storage/usbdisk1/mikopbx/media/custom**. Music on hold files are stored in **/storage/usbdisk1/mikopbx/media/moh**.
## Music on hold
If a client gets into a queue during a call or is waiting for redirection, the PBX plays a melody for him. It is possible to download your own tunes for listening while waiting.
You can do this on the "**Music on Hold"** tab as described above.
"Music on hold" tab
---
# 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://docs.mikopbx.com/mikopbx/english/manual/telephony/sound-files.md?ask=&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.
