How ilkermansur/gadget_record works
Gadget Record receives CUCM BiB SIP recording calls, captures call audio with Asterisk, then converts and stores recordings with metadata in PostgreSQL. Users manage recordings through a FastAPI interface for listing, metadata lookup, download, playback, and deletion. The graph reflects the sampled API and recording-worker code plus README-described capabilities; Asterisk configuration details are not sampled, so its internal call handling is represented only at a high level.
Main entry points: recordings.py Recording routes · save_recording.py Recording worker · extensions.conf Asterisk server · main.py FastAPI app
Components 11
Call capture
- Asterisk server
asterisk/extensions.conf - RTP recording
asterisk/extensions.conf
Recording archive
- Recording worker
asterisk/save_recording.py - Recordings store
db/init.sql
Management API
- FastAPI app
api/main.py - Recording routes
api/routers/recordings.py - DB connection pool
api/database.py
API contracts
- Response schemas
api/schemas.py
Other components
- CUCM BiB
- FFmpeg tools
- API user
Connections 10
- CUCM BiB → Asterisk server: sends SIP calls
README.md - Asterisk server → RTP recording: captures streams
README.md - RTP recording → Recording worker: processes recordings
README.md - Recording worker → FFmpeg tools: transcodes audio
asterisk/save_recording.py - Recording worker → Recordings store: inserts audio
asterisk/save_recording.py - API user → FastAPI app: calls API
README.md - FastAPI app → Recording routes: registers routes
api/main.py - Recording routes → DB connection pool: gets connections
api/routers/recordings.py - Recording routes → Recordings store: queries recordings
api/routers/recordings.py - Recording routes → Response schemas: builds responses
api/routers/recordings.py