TeamTalk 5 Documentation

The ttserverlog client example is a C++ implementation designed to demonstrate how to intercept and record voice conversations.

Key Features:

• Prompts for login credentials.
• Records all intercepted conversations to .wav files.

Requirements for Recording: To record conversations across all channels, the client must use an administrator account. This allows the client to utilize the intercept subscription mechanism to capture voice data directly from the server.

The TeamTalk C-API is split into two primary header files depending on your application type:

• Client Applications: Use TeamTalk.h to access the API for creating TeamTalk client applications.
• Server Applications: Use TeamTalkSrv.h to access the API for creating TeamTalk server applications. Note that the server API is exclusive to the TeamTalk 5 Professional Edition.

This project provides a .NET managed DLL containing wrapper classes for the TeamTalk C-API (TeamTalk DLL). It allows .NET developers to interface with the TeamTalk core functionality through managed code.

To use this, you must build the appropriate DLL based on whether you are using the standard or Pro version of the TeamTalk library.

The TeamTalk application interface is organized into several key areas:

• Menu Bar: Located at the top, providing access to Client, Me, Users, Channels, Server, and Help menus.
• Toolbar: Provides quick access to common tasks like connecting, push-to-talk, and video transmission.
• Channels View: Located on the left side, displaying channels (folder icons) and users. The root channel is represented by a computer icon.
• Volume Controls: Located below the Channels View, containing master volume, microphone gain, and voice activation sliders.
• Tab Control: Located on the right side, containing the Chat, Video, Desktops, and Files tabs.
• Splitter: A draggable element between the Channels View and the Tab Control used to resize the panels.

You can configure specific user accounts to automatically receive Channel Operator status in certain channels via the User Accounts Dialog:

• Selected Channels: The user automatically becomes an operator in a specific list of channels.
• Available Channels: The user automatically becomes an operator in any channel from a predefined list. Note: This mode only supports static channels.

A Channel Operator (or Op) is typically the channel owner or a user granted permissions to manage a specific channel.

Capabilities

• Kick users from the channel.
• Modify channel properties.
• Control transmission rights (who can speak) using the Transmit Control menu.

Management

• Operator Password: When creating a channel, you can set a password so others can become operators.
• Automatic Assignment: Users can be configured to automatically become channel operators via the User Accounts Dialog.

Channel operators use the Transmit Control-menu to manage what users are allowed to send to a channel. This is useful for managing classroom-style environments.

Individual User Controls

Toggle these to allow or deny a specific user the ability to transmit:

• Allow Channel Text Messages
• Allow Voice Transmission
• Allow Video Transmission
• Allow Desktop Transmission
• Allow Media File Transmission

Global Channel Controls

Toggle these to set the permission level for all users in the channel:

• Allow All Channel Text Messages
• Allow All Voice Transmission
• Allow All Video Transmission
• Allow All Desktop Transmission
• Allow All Media File Transmission

A Classroom channel allows an operator to control which users are permitted to transmit audio, video, or media files.

Operator Controls

• User Checkboxes: In the Channels view, operators can check/uncheck boxes next to users to grant permission for specific types of transmission (e.g., allowing a user to share a desktop but not video).
• Global Shortcuts: Checkboxes next to the channel name act as shortcuts to allow/disallow everyone in the channel to transmit voice or media files.
• Transmit Control menu: An alternative way to toggle transmission permissions.

Non-Operator View

• Non-operators cannot modify transmission settings. They must request permission from the channel operator.

TeamTalk uses CMake's ExternalProjects to build dependencies. You can control whether TeamTalk builds its own dependencies or uses libraries already installed on your host system using TOOLCHAIN_ prefixed options.

Note: Setting a TOOLCHAIN_ option to OFF is generally only supported on Linux distributions and is recommended for them to avoid version conflicts (e.g., OpenSSL).

# Example: Use host-installed OPUS instead of building it
cmake -DTOOLCHAIN_OPUS=OFF -S TeamTalk5 -B builddir