Hi, Since Docker Hub is not reachable from your network, you can build the three application images yourself directly from their GitHub repositories. Note that the MySQL image and the base OS images (Debian, PHP) still need to be pulled from a registry if you don’t have them already.
1. opensips/opensips:sbc-ce Clone the official OpenSIPS Docker image repository and build with the exact modules the SBC CE requires: git clone https://github.com/OpenSIPS/docker-opensips cd docker-opensips make build \ DEBIAN_RELEASE=bookworm \ OPENSIPS_VERSION=3.6 \ OPENSIPS_BUILD=nightly \ OPENSIPS_CLI=false \ WITH_HEALTHCHECK=false \ OPENSIPS_DOCKER_TAG=sbc-ce \ OPENSIPS_EXTRA_MODULES="m4 gettext-base \ opensips-mysql-module \ opensips-auth-modules \ opensips-http-modules \ opensips-tls-module \ opensips-dialplan-module \ opensips-presence-modules \ opensips-tls-openssl-module \ opensips-tlsmgm-module" cd .. 2. opensips/opensips-cp:latest git clone https://github.com/OpenSIPS/docker-opensips-cp cd docker-opensips-cp make build cd .. 3. fonoster/rtpengine:latest git clone https://github.com/fonoster/rtpengine cd rtpengine docker build -t fonoster/rtpengine:latest . cd .. After these three builds complete, docker compose up -d --build in the opensips-sbc-ce directory will find all three images already available locally and will not attempt to pull them from Docker Hub. Best regards, Darius > On 6 May 2026, at 19:19, 柳永智 <[email protected]> wrote: > > > Environment: > Ubuntu 24.04, Docker and Docker Compose installed and working normally. > Operation steps and full output: > Clone official repository > plaintext > git clone https://github.com/OpenSIPS/opensips-sbc-ce.git > Output: > plaintext > Cloning into 'opensips-sbc-ce'... > remote: Enumerating objects: 540, done. > remote: Counting objects: 100% (540/540), done. > remote: Compressing objects: 100% (222/222), done. > remote: Total 540 (delta 292), reused 538 (delta 290), pack-reused 0 (from 0) > Receiving objects: 100% (540/540), 93.16 KiB | 3.21 MiB/s, done. > Resolving deltas: 100% (292/292), done. > Enter project folder > plaintext > cd opensips-sbc-ce > Edit compose file > plaintext > sed -i 's|image: opensips/sbc|build: .|g' docker-compose.yml > sed -i '/rtpengine:/,/^$/d' docker-compose.yml > Commands executed without error. > Build and start > plaintext > docker compose up -d --build > Error output: > plaintext > failed to resolve reference "docker.io/opensips/opensips:sbc-ce": failed to > do request: Head > "https://registry-1.docker.io/v2/opensips/opensips/manifests/sbc-ce": dial > tcp 208.31.254.33:443: i/o timeout > All operations follow official guide, source code downloaded completely, > docker environment is healthy. > The problem is pulling base image timed out. > Please guide me: > How to deploy and run this SBC only with local source code, without pulling > remote docker.io base image? > > > > > > At 2026-05-06 21:52:58, "Răzvan Crainea" <[email protected]> wrote: > >Hi all, > > > >We are happy to announce the OpenSIPS SBC Community Edition, a > >ready-to-run OpenSIPS-based SBC (Session Border Controller) platform. > > > >The project was presented at OpenSIPS Summit 2026 in Bucharest and > >provides a complete SBC setup for SIP edge deployments, including > >topology hiding, NAT traversal, RTPEngine-based media relay, > >mid-registrar support, core-server failover, PSTN routing, SIP > >authentication, access control and monitoring tools. > > > >You can find more details on the project page: > >https://ce.opensips.org/opensips-sbc/ > > > >The source code and setup instructions are available on GitHub: > >https://github.com/OpenSIPS/opensips-sbc-ce > > > >Feedback, testing and contributions are very welcome. > > > >Best regards, > >-- > >Răzvan Crainea > >OpenSIPS Core Developer / SIPhub CTO > >http://www.opensips-solutions.com / https://www.siphub.com > > > > > >_______________________________________________ > >Users mailing list > >[email protected] > >http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
