> For the complete documentation index, see [llms.txt](https://docs.videsk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videsk.io/es-console/recomendaciones/ajustes-de-sonido.md). # Ajustes de sonido Al estar utilizando un navegador como medio de acceso a aplicaciones 100% web, existen restricciones de privacidad y consumo de energía el cual se aplican sobre los aplicativos. Por lo que es requerido realizar ciertos ajustes para maximizar la compatibilidad. {% hint style="warning" %} Los siguientes ajustes se realizan desde tu navegador, no de tu sistema operativo. {% endhint %} ## Google Chrome En el caso que estés utilizando Google Chrome deberás ir al siguiente enlace (copia/pega) ``` chrome://settings/content/siteDetails?site=https%3A%2F%2Fconsole.videsk.io ``` Una vez en la nueva pestaña deberás buscar dentro del listado de **Permisos** el ítem **Sonido** con un ícono ![](https://3156735785-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Ma4PUmP-cXr1lEzvL1q%2Fuploads%2FsqRiBgTk3qoBQWKAGD4g%2Fimage.png?alt=media\&token=f287ed93-fdb0-4e1a-af3f-453d7f146235). Deberás asegurarte que esté en **Permitir**, y no en Automático o Bloquear.
El modo automático es válido, pero el comportamiento variará en base al uso y decisión de tu propio navegador el cual por defecto previene la reproducción automática de videos o audios mientras la pestaña esté en segundo plano (no en primera vista) pasado unos minutos. Lo anterior, podría provocar que no oigas el sonido de llamada entrante. --- # 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.videsk.io/es-console/recomendaciones/ajustes-de-sonido.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.