> 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/modules/miko.md).

# MIKO modules

- [Dial groups management](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-users-groups.md): Installation and step-by-step module configuration
- [Autoprovision](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-autoprovision.md): Automatic configuration of IP phones in MikoPBX. The module discovers phones on the local network, sends them a ready-to-use SIP configuration, and can even host firmware images for centralised upgrad
- [Let's Encrypt](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-get-ssl-lets-encrypt.md): Instructions for issuing trusted SSL certificates
- [Access control management](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-users-u-i.md): The module allows creating access groups with specific permissions and assigning these permissions to company employees.
- [Module auto dialer](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-auto-dialer.md)
- [Backup](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-backup.md)
- [Synchronization with LDAP/AD](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-ldap-sync.md)
- [Phrase Studio (TTS)](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-phrase-studio.md): Offline Piper-powered TTS studio for MikoPBX: generate IVR/voicemail phrases on the PBX, reuse them from a searchable history, and one-click drop the result into the standard Sound Files editor.
- [Callback module](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-callback-queues.md)
- [Extended call history](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-extended-cdr.md)
- [Call Routing Map](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-routing-map.md): Read-only routing diagram for MikoPBX: inspect incoming and outgoing call paths as an interactive graph built from the current PBX configuration.
- [Beeline Cloud PBX integration](https://docs.mikopbx.com/mikopbx/english/modules/miko/beeline-cloud-pbx-integration.md): The module imports call history and recordings from Beeline Cloud PBX into MikoPBX and can send real-time call events to 1C:Enterprise.
- [VPN](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-vpn.md): The VPN module connects MikoPBX to a remote network over a secure tunnel. Supports OpenVPN, WireGuard (including traffic obfuscation) and Tailscale on the x86\_64 and arm64 platforms.
- [GeoIP Filtering](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-geo-ip.md): The GeoIP module blocks incoming connections to MikoPBX from selected countries at the firewall level. It protects the PBX from SIP scanners, password brute-forcing and unwanted calls. Works for both
- [Local Transcription](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-local-speech-to-text.md): Local call transcription in MikoPBX: recordings remain within the PBX, recognition runs on a Mac worker, and completed transcripts are available in the module interface and through the API.
- [Quick Start](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-local-speech-to-text/quick-start.md): Quick start for the Local Speech To Text module and Local STT Worker
- [Local STT Worker](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-local-speech-to-text/miko-ai-worker.md): Local STT Worker for macOS: connecting to MikoPBX, local transcription, history, models, diagnostics, settings, and Worker API updates.
- [Docker worker (Linux)](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-local-speech-to-text/docker-worker.md): Docker worker for local transcription: installing it on a Linux server from scratch, connecting it to MikoPBX, checking that it works, updating and removing it.
- [Windows worker](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-local-speech-to-text/windows-worker.md): Windows worker for local transcription: installing the service from the MSI or ZIP, connecting it to MikoPBX, checking that it works, updating and removing it.
- [REST API](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-local-speech-to-text/rest-api.md)
- [Local AI Supervisor](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-a-i-supervisor.md): Local AI analysis of MikoPBX call transcripts: summary, call outcome, risks, tone, and employee performance scoring. The analysis runs on a Mac within your infrastructure.
- [Quick Start](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-a-i-supervisor/quick-start.md): Quick start for the Local AI Supervisor module and AI Supervisor Worker
- [AI Supervisor Worker](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-a-i-supervisor/miko-ai-worker.md): Installing and using AI Supervisor Worker: connecting to MikoPBX, local models, job processing, voice analytics, and diagnostics on a Mac.
- [Cloud Speech-to-Text](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-cloud-speech-to-text.md): Module description
- [REST API](https://docs.mikopbx.com/mikopbx/english/modules/miko/module-cloud-speech-to-text/rest-api.md): Route descriptions


---

# 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/modules/miko.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.