TeamTalk 5 .NET DLL Version 22.214.171.12452
This section contains the list of new features and API changes in TeamTalk SDK releases.
The server API has been updated in this release so it's possible to restrict logins to your TeamTalk server to only your own client application. If the "normal" TeamTalk client tries to connect to your TeamTalk server then it will be possible to reject it.
To limit access to your TeamTalk server you can use the
szSystemID parameter of TeamTalkSrv.StartServerSysID(). When a client has to connect then the chosen system-ID will also have to passed to TeamTalk.ConnectSysID(). If it's not then the connecting TeamTalk client will receive the CMDERR_INCOMPATIBLE_PROTOCOLS. The szSystemID of the default TeamTalk application is "teamtalk". This is what you see when you connect with Telnet on port TCP port 10333 (non-encrypted).
On top of the system-ID restriction it's now also possible to do a check on the client name connecting by using the extended TeamTalk.DoLoginEx(). When a client tries to connect to a TeamTalk server you can then check the
szClientName property of BearWare.User to ensure only your client application is allowed to connect.
Audio device "Voice-Processing I/O Unit" added as sound device ID 1 on iOS. The Voice-Processing I/O Unit sound device is designed to eliminate echo when using speaker output and also enable automatic gain control. Read more on audio units here: https://developer.apple.com/library/ios/documentation/MusicAudio/Conceptual/AudioUnitHostingGuide_iOS/UsingSpecificAudioUnits/UsingSpecificAudioUnits.html
The video capture API on Linux has been updated to it now uses V4L2 instead of the obsolete V4L API.
The previously used video capture API, QTkit, on Mac OS has been replaced by AVFoundation. Apple's AppStore doesn't accept apps which link to QTkit, so therefore this replacement was nescessary.
Previous releases of TeamTalk 5 shared library depended on WebM (libvpx), Speex (libspeex), OPUS (libopus), etc. Now this has been limited to C++ standard library (libstdc++) and ALSA (libasound).
The Speex sound preprocessing library (SpeexDSP) is now also supported on iOS platforms.
Previously the TeamTalk sample application (TeamTalkAndroid) was using Eclipse but this project has now been converted to Android Studio 2.0.
When storing audio to files it's now possible to specify AFF_CHANNELCODEC_FORMAT which is part of the enumeration BearWare.AudioFileFormat. The 1AFF_CHANNELCODEC_FORMAT will store in the audio format configured by a BearWare.Channel's BearWare.AudioCodec.
nEncodeDeadline to BearWare.WebMVP8Codec which specifies quality of the video encoder. Values are BearWare.WebMVP8CodecConstants.WEBM_VPX_DL_REALTIME, BearWare.WebMVP8CodecConstants.WEBM_VPX_DL_GOOD_QUALITY and BearWare.WebMVP8CodecConstants.WEBM_VPX_DL_BEST_QUALITY.
This file layout change has been made so the projects are more aligned with TeamTalk 5 on GitHub.
TeamTalk 5 iOS SDKs can now be compiled with "Enable Bitcode" (
A quite severe bug which caused files on the server to end up in the wrong channels has been fixed in this minor release. The issue only affects the standalone servers which are included in the SDK. Custom servers created by the TeamTalk server API should not be affected.
Previously it has only been possible to record own audio streams by subscribing to them. Now it's, however, possible to call TeamTalk.SetUserMediaStorageDir() with user ID 0 to record own audio stream.
Windows developers can now also use Java for client development. The TeamTalk JNI DLL is located in
The inclusion of the TeamTalk Server API has caused quite a bit of reorganization of the TeamTalk SDK's file layout. Previously the TeamTalk DLL only allowed client operations and was therefore located in the
Client folder. Now that the TeamTalk DLL (in the Professional edition) also allows users to develop a TeamTalk server then the core TeamTalk library projects have been moved to the
Library folder in the root of the SDK.
Library C-API Java NET Documentation C-API Java NET Examples C-API Java NET Server Demo Client
The TeamTalk 5 Professional Edition now includes a TeamTalk Server API which enables developers to instantiate a TeamTalk server by calling the TeamTalk DLL. With the server API it's possible to do basic operations like authentication users and updating server properties.
Now that the TeamTalk SDK is also available for Android the Java API used for Android development has also been ported to Linux and Mac OS X.
Open the Java documentation to see how to use the new Java API. The Java TeamTalk classes greatly ressemble the .NET classes therefore the API documentation for Java is the same as .NET. Hopefully this doesn't cause too much confusion.
In TeamTalk 4 events were posted in a
TTMessage containing a WPARAM and LPARAM where the WPARAM would typically contain an ID and the LPARAM some extended information about the event. When an event occured the client application would query the TeamTalk client instance to extract information about what had changed to the current state. Since the client instance was running in its own thread the state change could, however, have become unknown in the meantime. If e.g. a text message was received from a user and the user would immediately quit afterwards then the text message would be lost since the text message was "attached" to the user who was no longer there. In TeamTalk 5 a BearWare.TTMessage now contains a copy of what changed as a cause of the event. If e.g. a text message is received from a user then the BearWare.TTMessage will contain a full copy of the BearWare.TextMessage which was received. Also if a new channel is created then it's no longer required to extract the BearWare.Channel object through the TeamTalk client instance (using TeamTalk.GetChannel()) now the new channel is part of the BearWare.TTMessage using the BearWare.TTMessage's data container.
Theora video codec was used in TeamTalk 4 to encode video from webcam and media files but this has now been replaced by the more recent Google-backed WebM codec. Check out WebM website for more information about the new video codec. Currently it's only possible to configure the bitrate in the codec but should you need access to more codec configuration options then feel free to request these.
CELT is no longer being developed and has been replaced by OPUS. Check out OPUS website for more information.
In TeamTalk 4 streaming a media file would replace voice input from microphone and video from a media file would replace webcam input. In TeamTalk 5 a new stream type for media files has been introduced so it's still possible to talk and show webcam video while streaming a media file to a channel.
In TeamTalk 4 all users of the default user type had the same user rights on the server which were set up in BearWare.ServerProperties. The user rights (BearWare.UserRight) are now part of BearWare.UserAccount so each user can have different BearWare.UserRight on the server.
TeamTalk 5 doesn't support P2P connections since the 'forward through server' is required for desktop sharing to work.
BearWare.ServerStatistics now includes the number of users served, the highest number of users and server's uptime.
The TeamTalk server in the Professional SDK (tt5prosrv) now also supports non-encrypted mode. Whether to run in encrypted or non-encrypted mode is configured when running the setup wizard. See more in TeamTalk Server Setup Guide.
supportedSampleRatesdue to change of TeamTalk.GetSoundDevices() instead of
nStreamID. Stream ID changes whenever push-to-talk or voice activation are toggled.
frameBufferwith pointer to data and
nFrameBufferSizewith size of bffer.
opus, i.e. BearWare.OpusCodec.
nVideoBytesTXreplaced by nVideoCaptureBytesTX.
nVideoBytesRXreplaced by nVideoCaptureBytesRX.
uAFF. Format in CLIENTEVENT_USER_RECORD_MEDIAFILE.
szAudioFileName. File name in CLIENTEVENT_USER_RECORD_MEDIAFILE.
nAudioPacketsRecvreplaced by nVoicePacketsRecv.
nAudioPacketsLostreplaced by nVoicePacketsLost.
nVideoPacketsRecvreplaced by nVideoCapturePacketsRecv.
nVideoFramesRecvreplaced by nVideoCaptureFramesRecv.
USERRIGHT_DOUBLE_LOGINreplaced by USERRIGHT_MULTI_LOGIN.
USERRIGHT_CLIENT_BROADCASTreplaced by USERRIGHT_TEXTMESSAGE_BROADCAST.
USERRIGHT_FORWARD_AUDIOreplaced by USERRIGHT_TRANSMIT_VOICE
USERRIGHT_FORWARD_VIDEOreplaced by USERRIGHT_TRANSMIT_VIDEOCAPTURE
USERRIGHT_FORWARD_DESKTOPreplaced by USERRIGHT_TRANSMIT_DESKTOP
USERRIGHT_FORWARD_DESKTOPINPUTreplaced by USERRIGHT_TRANSMIT_DESKTOPINPUT
USERRIGHT_CHANNEL_CREATION. See User rights now moved to user account.
USERRIGHT_SUBSCRIPTIONS. Subscriptions are now mandatory.
USERRIGHT_STRICT_UTF8. UTF-8 is now mandatory.
CHANNEL_STATICreplaced by CHANNEL_PERMANENT.
CHANNEL_ECHO. Use SUBSCRIBE_VOICE instead.
CHANNEL_ECHO_AUDIO. Use SUBSCRIBE_VOICE instead.
CHANNEL_ECHO_VIDEO. Use SUBSCRIBE_VIDEOCAPTURE instead.
CHANNEL_ECHO_DESKTOP. Use SUBSCRIBE_DESKTOP instead.
CLIENT_TX_AUDIOreplaced by CLIENT_TX_VOICE.
CLIENT_TX_VIDEOreplaced by CLIENT_TX_VIDEOCAPTURE.
CLIENT_P2P_AUDIO. See Peer to peer support has been removed.
CLIENT_P2P_VIDEO. See Peer to peer support has been removed.
CLIENT_P2P. See Peer to peer support has been removed.
bCompletedinverted and now states
TeamTalk4.StartStreamingAudioFileToUser()replaced by BearWare.TeamTalk.StartStreamingMediaFileToChannel()
nBitmapSizeare now part of BearWare.DesktopWindow.
nUserIDparameter. All in channel will receive.
lpAudioBlockparameter. Now returns BearWare.AudioBlock.
nVolumeVoicein BearWare.User instead.
nGainLevelVoicein BearWare.User instead.
nStoppedDelayVoicein BearWare.User instead.
soundPositionVoicein BearWare.User instead.
uUserStatein BearWare.User instead.
The TeamTalk 4 SDK is now also available for Mac OS X 64-bit.
Released on 2014/07/20.
The TeamTalk server now also includes
-l command line argument for specifying the location of the log-file. Previously only the
-wd argument could be used for changing the location of the log file.
The log-file of the TeamTalk server now also includes entries for when a user acount is added or deleted and also a log entry for when users are moved between channels.
Released on 2014/02/20.
Shared desktops can now be controlled remotely using mouse and keyboard input. Check out Remote Desktop Access to read on how to control remote desktops.
Released on 2013/05/13.
Previously it's only been possible to stream 16-bit signed PCM wave-files to a channel but in the 4.5 release it's now possible to stream mp3, mpg, avi, wma, wmv, etc. to a channel. On Windows you can basically stream whatever Windows Media Player can play to a channel. Checkout BearWare.TeamTalk.StartStreamingMediaFileToChannel() for more information.
To prevent a brute force login attempt it's now possible to limit the number of login attempt before banning an IP-address. Checkout
nMaxLoginAttempts property of BearWare.ServerProperties. It's now also possible to limit the number of logins per IP-address by specifying
nMaxLoginsPerIPAddress in BearWare.ServerProperties.
Previously it was only possible to ban a user's IP-address if the user was present on the server. Now it's, however, possible to ban an IP-address using BearWare.TeamTalk.DoBanIPAddress().
Released on 2012/10/15.
Windows Audio Session is a new sound system available in Windows Vista and later versions of Windows. It's a sound system which provides significantly lower latency than both DirectSound and Windows default sound devices. Check out BearWare.SoundSystem SOUNDSYSTEM_WASAPI for more information.
When the TeamTalk client is initially start it scan the system for all sound devices but if a user later plugs in a USB sound card then this device will not be detected automatically in TeamTalk.GetSoundInputDevices() and TeamTalk.GetSoundOutputDevices().
TeamTalk.RestartSoundSystem() can now be used to shut down the sound systems can rescan for new devices.
If a sound card doesn't support the sampling rate of a codec or if the codec requires stereo input then TeamTalk now automatically resamples audio so it fits the proper format. DirectSound e.g. had problems with input devices which only allowed mono and therefore couldn't be used with stereo codecs.
A new channel type, BearWare.ChannelType
CHANNEL_OPERATOR_RECVONLY has now also been introduced which only allowed administrators and operators of a channel to receive audio and video. This can be useful if bandwidth is a problem.
BearWare.VideoCaptureDevice now shows the name of the video device in Unicode on Windows.
Released on 2012/03/26.
The major new feature in the 4.3 release is the ability to share desktop applications. When sharing a desktop application you send a bitmap, using TeamTalk.SendDesktopWindow(), to the local client instance. The bitmap is then split into in small blocks and transmitted to the server using the UDP connection. Read more about this feature in the section Desktop Sharing.
A BearWare.UserAccount now has the
szInitChannel property which holds the channel a user should join after login. The user can join this channel without passing a password. Use TeamTalk.GetMyUserAccount() to get the local instance's BearWare.UserAccount after login has completed.
Some routers don't allow UDP packets over a given size so use TeamTalk.QueryMaxPayload() after connecting to a server to detect the maximum size for UDP packets. The event TeamTalk.OnMaxPayloadUpdate() is triggered when the client instance has finished querying.
The raw audio, which has been playing when a user is talking, can now be accessed by calling TeamTalk.EnableAudioBlockEvent(). The event TeamTalk.OnUserAudioBlock() is triggered when a new BearWare.AudioBlock is available.
If audio files are being recorded separately for every BearWare.User, using
TeamTalk.SetUserAudioFolder, the file name of the file currently being recorded to can be found in the
szAudioFileName property of the BearWare.User struct.
To cancel and start recording to a new audio file pass AudioFileFormat AFF_NONE as parameter to
TeamTalk.SetUserAudioFolder. This will reset the current recording and generate the TeamTalk.OnUserAudioFile() event.
A BearWare.Channel configured using ChannelType CHANNEL_CLASSROOM was previously limited to 16 people transmitting either video or audio. Now it's, however, possible to add BearWare.TeamTalk.TT_CLASSROOM_FREEFORALL to the "enabled" users properties to allow everyone to transmit.
Released on 2011/11/02.
It is now possible to store "muxed" audio files, i.e. audio from all users are written to the same audio file. Check out BearWare.StartRecordingMuxedAudioFile() on how to do this.
The Windows Firewall, included in XP and later Windows versions, can sometimes block network traffic to and from applications which uses the TeamTalk DLL. Check out the section Windows Firewall on how to use the Windows Firewall functions.
Voice activation is by default disabled if no audio has reached the voice activation level for 1.5 seconds. This option can now be changed by calling TeamTalk.SetVoiceActivationStopDelay(). Also users who are talking are set to non-talking after 0.5 seconds if no new voice data has been received. This value can now be changed by calling TeamTalk.SetUserStoppedTalkingDelay().
Speex and CELT can now be used in VBR mode by creating a BearWare.Channel with the BearWare.SpeexVBRCodec or
BearWare.CELTVBRCodec. To limit bandwidth usage it is advised to use the VBR codecs. Especially the Speex VBR codec with DTX enabled reduces throughput when there's silence.
CELT 0.5.2, which was used in v 4.1 and previous of the SDK, has been replaced by CELT 0.11. Note that encoding and decoding of CELT 0.5.2 is no longer supported. Check out http://www.celt-codec.org
Client and server now support IPv6. To make the server run in IPv6 mode the server must bind to an IPv6 address. Check out Configurating the TeamTalk Server on how to specify the bind IP-address (<bind-ip> tag).
Note that the TeamTalk DLL can no longer run on Windows 2000 since this platform does not support IPv6.
BearWare.CELTCodecstruct updated for CELT 0.11.
BearWare.CELTVBRCodecstruct for CELT VBR.
CELT_0_5_2_OBSOLETE_CODEC, Codec SPEEX_VBR_CODEC, Codec
Released on 2010/10/30.
The new features in the TeamTalk 4 SDK v. 4.1a has are described in the following subsections.
The .NET wrapper for the TeamTalk 4 C-API DLL is now written in C# so there's no longer a need to include the Microsoft C Runtime files.
Mac OS X is now supported using the C-API DLL. The C-API DLL is compiled for i386 uses QuickTime for video and CoreAudio for audio. Windows Mobile support is now also supported using both the C-API DLL and the .NET Framework DLL.
When initializing the client instance's sound system in duplex mode it is now possible to enable echo cancellation. Note, however, that echo cancellation performs poorly on Windows whereas it's very effective on Mac OS X and Linux. Check out BearWare.TeamTalk.InitSoundDuplexDevices() and BearWare.TeamTalk.EnableEchoCancellation() on how to use echo cancellation.
A new channel-type called classroom has now been introduced where the channel's operator can control who is allowed to transmit audio and video to a channel. The channel operator can then work as sort of a teacher where the teacher selects the people who should answer questions. Check out BearWare.ChannelType CHANNEL_CLASSROOM for how to create classroom channels.
Often users have set their microphones to different audio levels so it's hard to hear certain users and others are too loud. When creating a channel it's now possible to use BearWare.Channel's audiocfg member to set the same audio level for all users. Note that all users must use the v. 4.1a release for this to work.
Administrators can now query a server statistics using the command BearWare.TeamTalk.DoQueryServerStats() and thereby get an overview of bandwidth usage.
Using BearWare.TeamTalk.GetUserVideoFrame() is quite tricky to use since the developer must first query for how much memory must be allocated to store the video frame. In this new release it's possible to share memory with the client instance so one simply calls BearWare.TeamTalk.AcquireUserVideoFrame() to get a pointer to a user's video data. when one has completed using the video frame call BearWare.TeamTalk.ReleaseUserVideoFrame() to release the shared memory. Note that only one video frame can be extracted each time, therefore calling BearWare.TeamTalk.AcquireUserVideoFrame() twice will simply result in getting the same video frame.
Released on 2010/03/16.
The new features in the TeamTalk 4 SDK v. 4.0c has are described in the following subsections.
The BearWare.UserAccount struct now has a new member called szNote which can contain extra information about a user account. The BearWare.UserAccount and BearWare.User structs now also has a nUserData integer field which can be used by developers to store an application specific value. After a successful login the nUserData field on BearWare.UserAccount will be transferred to the nUserData field on the BearWare.User struct.
After login it's now possible to retrieve one's own BearWare.UserAccount by calling BearWare.TeamTalk.GetMyUserAccount(). BearWare.TeamTalk.GetMyUserData() can be used to extract one's nUserData of one's BearWare.UserAccount.
All users who are connected to a server can now be retrieved using BearWare.TeamTalk.GetServerUsers().
Here a list of bugs fixed in this release:
Released on 2009/11/23.
The new features in the TeamTalk 4 SDK v. 4.0a has are described in the following subsections.
TeamTalk can now capture video from webcams and encode it for transmission. Bandwidth usage can be as low as a 2-3 KBytes/sec in low resolutions. High resultions are, of course, also supported.
To start using the new video features checkout the following new functions:
The TeamTalk server can now be set to only allow users to log on if they have a user account on the server. The user account also introduces user types, so some users can have administrator capabilities.
Read the section Configurating the TeamTalk Server on how to configure the server with user accounts. To see the new functions in the TeamTalk DLL for handling user accounts check out the following new functions:
When calling any of the client to server commands listed in section Client/Server Commands a command ID is returned to the user application. This command ID can be used to track when the server has started and finished processing the command using the TeamTalk.OnCmdProcessing() event.
The TeamTalk client now has better support for peer to peer data transmission and can now penetrate most NAT devices.
Check out section REMOVED for more information on P2P networking. P2P networking is enabled using the following functions:
TeamTalk now not only supports the Speex codec, but also the CELT codec. The CELT codec gives much better audio quality but also requires higher bandwidth usage. If a user application is used to transmit music it is advised to use CELT since the sound quality will be must better than Speex. Speex is mainly for voice transmissions. Check out section Audio and Video Codecs to read more about the new codec.
Also note that the audio codec used by a client is now configured on a BearWare.Channel and not on each individual client. This means that all users in a channel must now use the same audio settings. This restriction has been set to support echo-cancellation which is on the Known Issues.
The COM DLL has been removed from the SDK since most developers used .NET for their client applications. These developers should now use the .NET DLL instead. Here are the changes from the TeamTalk 3 COM DLL to the TeamTalk 4 .NET DLL.
TeamTalk3.SetLocalBindIPsee Known Issues it will be available again.
TeamTalk3.RegisterTalkingCallbacksee Known Issues it will be available again.
TeamTalk3.UnregisterTalkingCallbacksee Known Issues it will be available again.
TeamTalk3.OnUserAudioDatasee Known Issues