How herlesupreeth/kamailio_ims_config works
Project type and purpose
• This is an IMS (IP Multimedia Subsystem) configuration repository. It provides Kamailio‐based implementations of P-CSCF, I-CSCF, and S-CSCF for VoLTE and VoIP testing, integrating with an EPC (Open5GS) and HSS (Fraunhofer OpenHSS), plus RTPEngine for media anchoring.
File structure
• Top‐level files: README.md, two host files (epc.mnc001…, ims.mnc001…)
• Subdirectories for each network function:
• kamailio_pcscf/ (P-CSCF configs, dispatcher lists, route scripts, SEMS profiles, TLS)
• kamailio_icscf/ (I-CSCF configs, XML schemas, SQL schema)
• kamailio_scscf/ (S-CSCF configs, XML schemas, dispatcher list)
• Each directory contains:
• .cfg files (Kamailio configuration)
• .xml/.xsd files (SIP headers & Diameter interfaces)
• SQL or dispatcher lists (database schema, load balancing)
README for additional insights
• Components: Kamailio (5.2.4), RTPEngine (7.4.1.5), Fraunhofer OpenHSS
• Testbed: UEs ↔ eNodeB ↔ EPC+IMS VM (OpenStack or bare metal)
• Two scenarios: VoLTE (UE–IMS+EPC–UE) and VoIP (UE–IMS–UE)
Main components & their relationships
a. User Equipment (UE1, UE2 or Alice/Bob SIP clients)
b. eNodeB (radio access)
c. EPC Core (MME, SGW, PGW from Open5GS)
d. IMS Core:
• P-CSCF (kamailio_pcscf) – first SIP contact point
• I-CSCF (kamailio_icscf) – SIP routing/discovery
• S-CSCF (kamailio_scscf) – SIP session control
• HSS (Fraunhofer OpenHSS) – subscriber database (uses Diameter)
• RTPEngine – RTP media anchoring / NAT traversal
e. Network elements: DNS (dispatcher lists), TLS for SIP over TLS
Data flows:
• SIP REGISTER/INVITE from UE → P-CSCF → I-CSCF → S-CSCF → (S-CSCF→HSS via Diameter for auth)
• RTP/RTCP streams anchored via RTPEngine
• Diameter Cx and Sh between S-CSCF/I-CSCF and HSS
Architectural patterns & design principles
• Microservices‐style split of IMS functions (three separate Kamailio instances)
• Dispatcher lists provide load balancing/failover
• SEMS scripting for SBC‐like media policy enforcement in P-CSCF
• Config directories mirror 3GPP IMS functional split (Cx interfaces, XML schemas)