Voice & Telecom / Built
FIMI VoIP Protocol Demo
Small end-to-end protocol implementation using custom TCP signaling, SDP offer/answer, direct RTP media and RTCP receiver reports.
OVERVIEW
What I built.
Small end-to-end protocol implementation using custom TCP signaling, SDP offer/answer, direct RTP media and RTCP receiver reports.
Built a small educational call stack without SIP to expose the underlying concepts directly.
Implemented custom JSON/TCP signaling, SDP offer/answer, RTP media and minimal RTCP receiver reports.
Kept media peer-to-peer instead of proxying it through the signaling server.
SYSTEM ARCHITECTURE
How the system is divided.
Alice/Bob -> TCP signaling server for REGISTER/CALL/RINGING/ACCEPT/HANGUP.
SDP exchanges each endpoint's media address and ports.
RTP/RTCP flow directly over UDP between endpoints after call acceptance.
NETWORK / DATA FLOW
What talks to what.
TECHNOLOGY STACK
The technical surface.
IMPLEMENTATION
How it works in practice.
- 01
Alice/Bob -> TCP signaling server for REGISTER/CALL/RINGING/ACCEPT/HANGUP.
- 02
SDP exchanges each endpoint's media address and ports.
- 03
RTP/RTCP flow directly over UDP between endpoints after call acceptance.
TESTING & VALIDATION
How I know it works.
Three-process local demo
REGISTER/CALL/RINGING/ACCEPT/HANGUP flow
SDP port exchange
Direct RTP packet exchange
Minimal RTCP Receiver Report generation
EXTERNAL SERVICES & DEPENDENCIES
What sits outside the core.
ENGINEERING EVIDENCE
Artifacts behind the claims.
BOUNDARIES / CONSTRAINTS
What the project does not pretend to solve.
—Intentionally not SIP
—Designed as a learning/protocol lab
—Minimal RTCP rather than a complete production implementation
RESULT / CURRENT STATE
What this produced.
A compact protocol lab that makes the separation between signaling, session description and media transport explicit.