-
-
Notifications
You must be signed in to change notification settings - Fork 244
Docker Install
https://github.com/sipcapture/homer-docker
- debian/jessie (base image)
- Kamailio4.x:9060 (sipcapture module)
- Apache2/PHP5:80 (homer ui/api)
- MySQL5.6/InnoDB:3306 (homer db/data)
git clone https://github.com/sipcapture/homer-docker.git
cd homer-docker
docker-compose build
docker-compose up
It's encouraged as a best practice to deploy separate containers for each process. To specify what's required to build & run each container, it's recommended to use docker-compose. The linked document explains a number of ways to install it, however, we'll recommend installing it using Docker (as if you're using this, your system likely has it!). Requires Docker 1.10 or greater.
$ curl -L https://github.com/docker/compose/releases/download/1.6.2/run.sh > /usr/local/bin/docker-compose
$ chmod +x /usr/local/bin/docker-compose
$ docker-compose --version
All that should be required is to, in the root of this clone, issue:
$ docker-compose up
Which will spin up all the containers, and it will show you the logs (the STDOUT from the foreground process) as you move along. You can stop the containers by hitting ctrl-c
. In production, you'll want to detach from the docker-compose up
command which can be achieved with the -d
option, a la...
$ docker-compose up -d
If you need
$ docker-compose build
Also see the man
There's a homer.env
file with environment variables in the root of the clone, which by default should work just fine.
For example you may choose to use a remote mysql host rather than have the one contained herein, if that is so, change the USE_REMOTE_MYSQL
to false, and specify the DB_HOST
as
It is recommended to change the MySQL and homer passwords in your own setup, especially in production.
The docker-compose
scheme will create named data volumes to store the mysql data. You can find the volumes it has created with:
$ docker volume ls | grep -i homer
So, you'd like to remove everything you've done up to this point? And start 'er fresh run docker-compose down
and remove the data containers...
$ docker-compose down
# Warning this will delete all of your mysql data!
$ docker volume rm $(docker volume ls | grep -i homer | awk '{print $2}')
Docker will warn if you the data container is already in use, and you must stop and remove any containers which have those volumes in use.
While the multi-container setup is recommended, you can find the legacy container for running all processes in a single volume in the everything/
folder.
docker pull sipcapture/homer-docker
docker run -tid --name homer5 -p 80:80 -p 9060:9060/udp sipcapture/homer-docker
By default, the container runs with a local instance of MySQL running. It may be of interest to run MySQL with a host directory mounted as a volume for MySQL data. This will help with keeping persistent data if you need to stop & remove the running container. (Which would otherwise delete the MySQL, without a mounted volume)
You can run this container with a volume like so:
docker run -it -v /tmp/homer_mysql/:/var/lib/mysql --name homer5 -p 80:80 -p 9060:9060/udp sipcapture/homer-docker
If you'd like to run with an external MySQL, pass in the host information for the remote MySQL as entrypoint parameters at the end of your docker run
command.
docker run -tid --name homer5 -p 80:80 -p 9060:9060/udp sipcapture/homer-docker --dbhost 10.0.0.1 --dbuser homer_user -dbpass homer_password
For single-container only.
Homer5 Docker parameters:
--dbpass -p MySQL password (homer_password)
--dbuser -u MySQL user (homer_user)
--dbhost -h MySQL host (127.0.0.1 [docker0 bridge])
--mypass -P MySQL root local password (secret)
--hep -H Kamailio HEP Socket port (9060)
git clone https://github.com/sipcapture/homer-docker; cd homer-docker
docker build --tag="sipcapture/homer-docker:local" ./everything/
docker run -t -i sipcapture/homer-docker:local --name homer5
docker exec -it homer5 bash
(C) 2008-2023 QXIP BV
HEP/EEP Agent Examples:
- CaptAgent
- HEPlify
- Kamailio
- OpenSIPS
- FreeSwitch
- Asterisk
- sipgrep
- sngrep
- RTPEngine
- RTPProxy
- Oracle ACME SBC
- Sonus SBC
- Avaya SM
- Sansay SBC
HEP/EEP Agent Examples (LOGS):
HEP/EEP Proxy:
Extra Examples:
- Custom JSON Stats
- RTCP-XR Stats
- GEO IP Maps
- Janus/Meetecho-WebRTC
- Cloudshark Export
- Encrypted HEP Tunneling
- SNMP Monitoring
- FreeSWITCH ESL Monitoring
- Kazoo Monitoring
- Speech-to-Text-to-HEP
Extra Resources: