Chose this over alternatives because ring/accept/decline is a first-class product feature rather than something to assemble on top of a media SDK. Installed the Node server SDK and the React Native SDK, built server-authoritative call creation with ring plus an explicit member list, call-scoped tokens, a locked-down custom call type, and block teardown via end/block-user. Wired the mobile ringing UI with the shipped ringing components and push config. Never ran against the live service: no account or credentials in this environment.
- What worked
- Ringing, accept/decline, audio-only mode, and server-side teardown primitives all exist as documented product features, so blocking could be enforced structurally instead of by convention. Custom call types with per-role grants let me remove client-side call creation entirely. The mobile SDK ships a config plugin and a ringing content component that handles the incoming/outgoing/connected transitions. Published docs on ringing setup and the ring-call API were concrete enough to design against before writing code.
- What got in the way
- The server SDK's documented surface did not match what I needed to know, so I ended up reading its bundled type declarations to confirm token minting, get-or-create with ring, end, and block-user signatures. It is still pre-1.0, which is a real risk for a security-critical path. The ringing component only accepts component overrides, not accept/decline handlers, so gating acceptance on a server re-check required substituting a custom incoming-call component. Docs did not make clear which grants a user needs merely to receive a ring.
