The SIP.TG platform provides the ability to run your own server modules:
These modules can be hosted on your own server in a Docker container, with a dedicated IP address and guaranteed availability. Below is a description of how this works and what steps are needed for setup.
Worker processes and converts audio streams from SIP to Telegram format and vice versa in real time.
Obtaining Certificates
/workers
command and click “New”.Server Preparation
docker-compose.yml
or in the corresponding configurations (SIP port, RTP range, etc.).Starting the Worker
Start the Docker service:
Make sure the Worker container has successfully started and is listening on the specified ports.
Check the container logs (command docker-compose logs
) if errors occur.
Connecting to the Worker
/workers
, select the created Worker and click “Address”.After enabling the Worker, you can specify:
Storage — a server on which keys and login data for Telegram accounts are stored. Without it, Telegram sessions live in the SIP.TG “cloud”, but if desired, you can store everything on your side.
Obtaining Certificates
/storage
command and click “New”.Server Preparation
docker-compose.yml
).Starting the Storage
Execute in the folder with the configuration:
Check the container logs (docker-compose logs
) for errors.
Make sure the specified TCP port is accessible externally.
Connecting to the Storage
/storage
in the @siptg_bot bot, select your storage and click “Address”./gateway
mode), choose your Storage.What if my Worker (or Storage) suddenly becomes unavailable?
Can I use only a Worker without my own Storage (or vice versa)?
Yes. These modules are independent. You can store Telegram sessions in the SIP.TG cloud but process SIP streams on your Worker. Or vice versa: use public Worker servers but store sessions on your side.
How labor-intensive is it to maintain these modules?
The main task is to keep Docker containers operational, update software (Worker/Storage image) as new versions are released, and monitor network availability. If you don’t have your own DevOps specialist, it’s easier to use SIP.TG public resources.
What about security and licensing?
How do I provide other users access to my Worker?
Change the Worker mode to “Public”. Then any SIP.TG user can assign your Worker to themselves. You can also keep the Worker “Personal”, but manually allow access to specific SIP accounts in the @siptg_bot.
For full operation of Worker and Storage, a stable connection with the SIP.TG platform (Manager) is required. Make sure your server can access the internet without blockages and that ports are not filtered by the firewall.