Skip to main content

Call glossary

Application​

After you register for a Nexconn Console account, you can create applications for your calling business. Each application has separate Development and Production environments, with different App Keys and isolated data.

If your business includes multiple client roles, you can use the same App Key with multiple application identifiers to create multiple final applications.

User​

Your app server provides a user ID (userId) to Nexconn and exchanges it for a Token. This step is completed by calling the Chat Server API Get Token endpoint.

Users must hold a valid Token to connect to Nexconn through the Chat SDK and use calling-related services.

Room​

A room is a virtual space for 2 or more users to conduct audio/video sessions via Call SDK. Users in the same room can send and receive real-time audio/video media streams to/from each other.

  • Rooms don't support direct creation. Nexconn creates the room internally when the first user joins.
  • Depending on the client request, Nexconn can create a calling room, conference room, or live streaming room.
  • A user can only be in one audio/video room at a time. To enter another room, they must exit the previous room.
  • For mobile network and device constraints, we recommend no more than 16 video participants or 32 audio-only participants in a room.

RoomID​

RoomID (room number / room ID) identifies a room, maintaining uniqueness at any given moment. RoomIds can be reused.

CallID​

When using Call SDK, the SDK creates and manages the underlying audio/video room as part of the calling flow. CallID is the unique identifier for a call.

In a calling scenario, when the caller joins first, the SDK creates the room and the room ID is the same as the CallID. The callee then uses the CallID to join the same room.

Session​

When using Call SDK, a session represents the lifecycle of the current call activity.

SessionID​

SessionID is the unique server-side identifier for a session. Nexconn generates it when the first user enters the room, and the session ends when everyone leaves the room or the server determines that all users are offline.

You can use SessionID for backend queries, troubleshooting, and communication with Nexconn support.

Main stream​

A video stream category referring to the stream with larger resolution when main-sub stream functionality is enabled. When enabled, the video encoder outputs two streams for the same video.

Low-resolution stream​

A video stream category referring to the stream with smaller resolution when main-sub stream functionality is enabled. When enabled, the video encoder outputs two streams for the same video.

Participant

In conference mode, people who can publish resources in the room.

Audio/Video signaling messages​

Audio/video signaling messages are messages Nexconn uses to implement SDK business functions. Developers don't need to handle them. Instant messaging service's Full Message Routing data includes these message types. Message Callback service supports configuring these message types.

See Audio/Video Signaling Messages for specific signaling message list.

Call SDK​

Call SDK is Nexconn's audio and video calling SDK. It provides an independent Call Server service and encapsulates the full calling flow, including dialing, ringing, answering, and hanging up, so developers can quickly build one-to-one and multi-party calling capabilities.

Last updated on