> For the complete documentation index, see [llms.txt](https://docs.omnileads.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnileads.net/instalacion-de-omnileads/deploy-utilizando-docker/deploy-en-docker-para-vps-cloud-o-vm.md).

# Deploy en Docker para VPS Cloud o VM

Ya se ha visto como levantar OMniLeads utilizando Docker Dekstop. Sin embargo, para ambientes que utilicen Virtual Machines (VM) o Virtual Private Servers (VPS), es preciso trabajar sobre algunas variables de configuración.

Para ello, dentro del Linux Host haremos uso del script de despliegue **deploy.sh** de nuestro repositorio "prod-env" mediante el siguiente comando:

```
$ curl -o deploy.sh -L "https://gitlab.com/omnileads/omldeploytool/-/raw/main/docker-compose/prod-env/deploy.sh?ref_type=heads" && chmod +x deploy.sh
$ export DOCKER_ENGINE_IPV4=X.X.X.X && ./deploy.sh
```

Una vez que el entorno es iniciado, se puede proceder al login de plataforma accediendo a la URL <https://X.X.X.X>, utilizando username y password "admin".

<mark style="color:red;">**Importante para entornos detrás de NAT**</mark>

Dado que el protocolo VoIP es sensible a ambientes de NAT (Network Address Translation), y dado que OMniLeads es usualmente desplegado a partir de una IP LAN, ciertos ajustes son necesarios para asegurar conectividad en sus componentes.

Específicamente, para conectar a PBXs y/o Session Border Controllers (SBCs) mediante SIP Trunk y permitir acceso de usuario mediante internet, se debe considerar agregar la IP de NAT mediante argumento. Ésto se muestra en el siguiente ejemplo:

```
$ curl -o deploy.sh -L "https://gitlab.com/omnileads/omldeploytool/-/raw/main/docker-compose/prod-env/deploy.sh?ref_type=heads" && chmod +x deploy.sh
$ export DOCKER_ENGINE_IPV4=X.X.X.X NAT_IPV4=Z.Z.Z.Z && ./deploy.sh
```

<figure><img src="/files/os7yt4i9zKcJJSsNg6St" alt=""><figcaption></figcaption></figure>

En el apartado de [First Login](/instalacion-de-omnileads/first-login.md), se pueden revisar los pasos necesarios para obtener el primer acceso a la UI con usuario Administrador.

Para mayor información, sugerimos visitar la documentación expuesta en el [repositorio oficial del proyecto](https://gitlab.com/omnileads/omldeploytool).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.omnileads.net/instalacion-de-omnileads/deploy-utilizando-docker/deploy-en-docker-para-vps-cloud-o-vm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.