It worked — but it was repetitive, fragile, and hard to replicate in new environments.

That’s what led me to this.

I decided to containerize Asterisk using Docker — not just to make it easier for myself, but for anyone who wants a clean, repeatable VoIP setup. And let me be clear: just containerizing Asterisk isn’t enough.

To make this production-ready, ODBC integration with PostgreSQL is crucial. That’s why I’ve documented this process in detail — for those who are truly keen to understand how to build a modern Asterisk environment that talks to a real database.

Let’s dive into how it’s done.

Why Containerize Asterisk?

When you’re setting up Asterisk on bare metal, every misstep can break the system. Dependencies mismatch. Configurations get overwritten. Permissions cause silent failures.

Containerizing solves all that:

a. Reproducibility across systems
b. Faster rebuilds and upgrades
c. Isolation from the host OS
d. Data persistence via Docker volumes
e. Portability and ease of testing

Building Asterisk with Docker

The Dockerfile is where the magic starts. It uses a base Debian image and installs all dependencies including:

• Asterisk build tools

• PostgreSQL ODBC driver

• Core libraries like libjansson, libxml2, libedit, libssl

FROM debian:bullseye
RUN apt-get update && apt-get install -y \
  build-essential git wget \
  unixodbc unixodbc-dev odbc-postgresql libpq-dev

Then fetch and build Asterisk from source:

RUN wget http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-18-current.tar.gz && \
    tar xvfz asterisk-18-current.tar.gz && \
    cd asterisk-18.* && \
    ./configure && \
    make && make install && make samples

Why this way? Because it gives full control over module selection and version consistency.

docker-compose: Container Lifecycle Simplified

The docker-compose.yml simplifies deployment and allows for persistent data:

services:
  asterisk:
    build:
      context: .
      dockerfile: Dockerfile.ast
    ports:
      - "5060:5060/udp"
      - "8088:8088/tcp"
    volumes:
      - asterisk_configs1:/etc/asterisk
      - asterisk_logs1:/var/log/asterisk
      - asterisk_voicemail1:/var/spool/asterisk/voicemail

With volumes mapped to key directories, even after a container is destroyed, your configs, logs, voicemails, and recordings persist.

ODBC Integration: The Backbone of Real-Time CDR

Setting up Asterisk is just the start. Without ODBC connectivity to a database, you’re missing the real-time power of Asterisk.

I’ve meticulously set up the ODBC layer so Asterisk can talk directly to PostgreSQL, store CDRs, and dynamically read or write configuration.

You need to configure:

# cat /etc/odbc.ini

[dsn_name]
Driver = PostgreSQL
Database = your_db
Servername = your_db_host
Port = 5432
Username = your_user
Password = your_password

# cat /etc/asterisk/res_odbc.conf

[dsn_name]
enabled => yes
dsn => dsn_name
username => your_user
password => your_password
pre-connect => yes

# cat /etc/odbcinst.ini

[PostgreSQL]
Description = ODBC for PostgreSQL
Driver = /usr/lib/x86_64-linux-gnu/odbc/psqlodbcw.so

# cat /etc/asterisk/modules.conf 

load => res_odbc.so
load => cdr_odbc.so
load => func_odbc.so
load => res_config_odbc.so
load => chan_sip.so

# append these line, don't overwrite

This ODBC setup ensures Asterisk can insert CDRs into PostgreSQL in real-time, query dynamic dialplans, and scale effortlessly with database-level access control.

Validation & Restart

Once everything is in place, restart and test:

# inside asterisk container

asterisk -rx "core restart now"
asterisk -rvv
odbc show
module show like odbc
sip show peers
...

Check ODBC connectivity directly with:

isql -v dsn_name user 'password'

Database Permissions Matter

For Asterisk to fully leverage the DB, the right permissions are essential:

GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO your_user;
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES TO your_user;

These permissions ensure CDRs log correctly, and future tables remain accessible.

Wrapping Up: From Kernel to Containers

Coming from a background of setting up Asterisk the traditional way — command by command on bare metal — this shift to Docker has been powerful.

I’ve experienced firsthand how painful it is to debug missing modules, broken libraries, and permission issues. This containerized approach eliminates all of that.

Now, with Asterisk in a Docker container + ODBC to PostgreSQL, I can:

• Deploy with one command

• Scale easily

• Rebuild or replicate the entire setup instantly

If you’re serious about Asterisk or VoIP in general, and want a future-proof way to deploy, manage, and scale it — this is the setup you need.