How infobip/infobip-rtc-android works
This repository snapshot contains only README.md and assets/images; no SDK source is available. The graph therefore captures documented product behavior and capabilities, not verified internal implementation. The README describes token generation, SDK call creation, call events/actions, permissions, and several call types; wiring beyond those stated relationships is omitted.
Components 16
Identity and Access
- Token HTTP API
- Subscriber token
Android SDK
- InfobipRTC client
- Device permissions
Call Experiences
- Call request
- WebRTC call
- WebrtcCall handle
- Call events
- Call actions
- Phone endpoint calls
- Viber calls
- Conversations calls
- Room calls
Infobip Platform
- Infobip platform
Other components
- Android application
- Subscriber identity
Connections 17
- Subscriber identity → Token HTTP API: identity submitted
- Android application → Token HTTP API: requests token
- Token HTTP API → Subscriber token: returns token
- Android application → InfobipRTC client: gets instance
- Android application → Call request: builds request
- Subscriber token → Call request: supplies credential
- Android application → Device permissions: requests access
- Android application → InfobipRTC client: invokes callWebrtc
- InfobipRTC client → WebRTC call: creates call
- WebRTC call → WebrtcCall handle: returns handle
- WebrtcCall handle → Call events: delivers events
- Android application → Call actions: invokes actions
- InfobipRTC client → Infobip platform: connects calls
- InfobipRTC client → Phone endpoint calls: supports
- InfobipRTC client → Viber calls: supports
- InfobipRTC client → Conversations calls: supports
- InfobipRTC client → Room calls: supports