How opensips/opensips-softswitch-ce works
Project type and purpose
• This is a full-blown SIP SoftSwitch platform, delivered as a set of cooperating Docker containers.
• Purpose: provide SIP proxying (OpenSIPS), media services (FreeSWITCH, RTPProxy), a web control panel (OpenSIPS-CP), persistent storage (MySQL), and optional call-flow visualization (Homer).
File structure
• Top-level: docker-compose.yml orchestrates all services.
• etc/opensips, etc/opensips-cp, etc/freeswitch, etc/mysql: each directory holds container initialization and configuration scripts.
• docs/: describes components, provisioning, testing, and how they interact.
• tests/: SIPSsert scenarios driving SIP UAs through OpenSIPS and validating behavior.
README
• Lists core components: OpenSIPS SIP proxy, RTPProxy, FreeSWITCH for voicemail/announcements, MySQL for database, OpenSIPS Control Panel (PHP), optional Homer for SIP trace capture.
• Explains how Docker Compose brings them up, where to configure IPs, how provisioning and tests run.
a. Main components
• Docker Host (the machine running Docker).
• Docker Compose network connecting:
• OpenSIPS SIP Proxy
• MySQL Database
• OpenSIPS Control Panel (Web UI)
• RTPProxy (media relay)
• FreeSWITCH (media services: voicemail/announcements)
• Optional: Homer Server (call capture & visualization)
• External SIP endpoints (User Agents, PSTN gateways)
b. Relationships & interactions
• SIP UA ↔ SIP Proxy: UDP/TCP signaling.
• SIP Proxy ↔ Database: reads/writes user credentials, dial plans, ACL flags via MySQL.
• SIP Proxy ↔ RTPProxy: instructs relay for media packets.
• SIP Proxy ↔ FreeSWITCH: hands off calls for voicemail or announcement services.
• Control Panel ↔ Database: CRUD operations for provisioning subscribers, domains, dialplans, ACLs.
• Homer ↔ OpenSIPS: receives SIP call detail records for visualization.
• SIP Proxy ↔ PSTN Gateway: external trunk for outbound/inbound PSTN.
c. Architectural patterns & principles
• Micro-services style using Docker Compose for isolation of control plane (CP, DB) vs data plane (OpenSIPS, RTPProxy, FreeSWITCH).
• Clear separation of concerns:
• Signaling (OpenSIPS),
• Media relay (RTPProxy),
• Media application (FreeSWITCH),
• Persistence (MySQL),
• Presentation (CP, Homer).
• Infrastructure-as-code and container initialization scripts for reproducible provisioning.
d. Key technologies/frameworks
• OpenSIPS (event-driven C SIP server)
• MySQL (InnoDB)
• PHP + Apache/Nginx (OpenSIPS-CP)
• RTPProxy (C RTP relay)
• FreeSWITCH (C media server)
• Homer (Elasticsearch/Graphana based SIP-RT-capture)
• Docker & Docker Compose
Detail level
• Inter-container network links defined in docker-compose.yml.
• Initialization order or dependencies indicated by entrypoint scripts in etc/.