How celer228/sipcall works
SIPCALL is an HTTP API for initiating calls, with documented endpoints at /api/call and /api/call/<UserID>. The tree suggests separate call handling, SIP client/server, user handling, and OTP application/supervision components. No source excerpts were provided, so internal call paths and runtime wiring cannot be verified; dashed edges mark those uncertainties.
Main entry points: call_handler.erl Call API · sipcall_sup.erl Supervisor · users_handler.erl Users API · sipcall_app.erl Application
Components 8
SIP calling
- SIP client
src/sip_client.erl - SIP server
src/sip_server.erl
OTP runtime
- Application
src/sipcall_app.erl - Supervisor
src/sipcall_sup.erl
Other components
- HTTP caller
Connections 7
- HTTP caller → Call API: requests calls
README.md - Call API → SIP client: dispatches calls
- Call API → Users API: uses user handling
- Users API → User data: reads users
- Application → Supervisor: starts supervision
- Supervisor → Call API: starts handler
- Supervisor → SIP server: starts server