Nexconn documents web SDK for 16-person video calls
Nexconn has published documentation for its Call SDK for Web, detailing how developers can integrate 1-to-1 and group voice and video calling functionalities into their web applications. The SDK supports both audio and video calls, including group calls with up to 16 video participants or 32 audio participants, and provides steps for installation, initialization, media access requests, event handling, and media playback integration.
Key Takeaways
- The Call SDK for Web supports 1-to-1 calls and group calls through `NCCallType.SINGLE` and `NCCallType.MULTI`.
- Group video calls support up to 16 participants, while group audio calls support up to 32 participants.
- Nexconn requires separate App Keys for development and production, with data isolated between the two environments.
- The SDK depends on `@nexconn/engine`, `@nexconn/chat`, and `@nexconn/call`, installed via `npm install @nexconn/engine @nexconn/chat @nexconn/call`.
- Developers must register `NCCallEventHandler` to receive events such as `onCallReceived`, `onRemoteUserStateChanged`, `onCallConnected`, and `onCallEnded`.
Why It Matters
Nexconn is giving web developers a documented path to add browser-based voice and video calling without building the signaling and media flow from scratch. The SDK’s setup sequence is specific: HTTPS or localhost, separate development and production App Keys, token-based auth, event handlers, and explicit local and remote video bindings before a call starts. For the broader streaming stack, this is another packaged real-time communication layer that sits alongside existing chat and engine components. Watch for implementation details in the 1-to-1 and group-call docs, especially how `NCCallType.MULTI` is used once teams move beyond single-party calls.
Read full article at docs.nexconn.ai