# Basic Data Types and Enumerations

# Statuses

The list of user statuses, including the SDK instance itself, is the same across all development platforms, but the names of the constants in the enumeration may differ.

# Android

In Android Studio development, the following statuses are available, provided by the PresenceStatus enumeration:

  • UNDEFINED (-127) — user status information is unavailable

  • INVALID (-1) — the server does not recognize the user's status

  • LOGOFF (0) — the user is not connected to the server

  • ONLINE (1) — the user is authenticated on the server and available for calls

  • BUSY (2) — the user is in a call or conference

  • MULTIHOST (5) — the user is in a conference and is the owner. Different types exist to support various kinds of conferences. You can check this with: status >= BUSY.

# iOS

The following statuses are available in the iOS SDK, provided by the enumeration TCSDKUserPresStatus:

  • Undef (-127) — no information about the user's status is available

  • Unknown (-1) — the server does not know the user's status

  • Offline (0) — the user is not connected to the server

  • Online (1) — the user is authenticated on the server and available for calls

  • Busy (2) — the user is on a call or in a conference

  • Busy3 (5) — the user is in a conference and is its owner. Different types exist to support various kinds of conferences. You can check the status like this: status >= Busy.

# .NET

In the .NET SDK, the following statuses are available, provided by the TUserPresStatus enumeration:

  • userUndef (-127) — user status information is unavailable

  • userUnknown (-1) — the user's status is unknown to the server

  • userOffline (0) — the user is not connected to the server

  • userOnline (1) — the user is authorized on the server and available for calls

  • userBusy (2) — the user is in a call or conference

  • userBusy3 (5) — the user is in a conference and is its owner. Different types exist to support various kinds of conferences. You can perform the check as follows: status >= userBusy.