Pure C WebRTC Client for Amazon Kinesis Video Streams
- Audio/Video Support
- Developer Controlled Media Pipeline
- Raw Media for Input/Output
- API emits feedback for QoS (bitrate suggestions)
- STUN/TURN Support
- IPv4/IPv6 TODO
- Signaling Client Included
- Tested on Linux/MacOS
- Tested on x64, ARMv5
- Build system designed for pleasant cross-compilation
- Small Install Size
- Sub 200k library size
- OpenSSL, libsrtp, libjsmn, libusrsctp and libwebsockets dependencies.
To download run the following command:
git clone --recursive https://github.com/awslabs/amazon-kinesis-video-streams-webrtc-sdk-c.git
You will also need to install
CMake and a build enviroment
Create a build directory in the newly checked out repository, and execute CMake from it.
mkdir -p amazon-kinesis-video-streams-webrtc-sdk-c/build; cd amazon-kinesis-video-streams-webrtc-sdk-c/build; cmake ..
We have provided an example of using GStreamer to capture/encode video, and then send via this library. This is only build if
GStreamer is installed on your system.
By default we download all the libraries from GitHub and build them locally, so should require nothing to be installed ahead of time. If you do wish to link to existing libraries you can use the following flags to customize your build.
If you wish to cross-compile
CXX are respected when building the library and all its dependencies. You will also need to set
BUILD_LIBSRTP_DESTINATION_PLATFORM. See our .travis.yml for an example of this. Every commit is cross compiled to ensure that it continues to work.
You can pass the following options to
-DADD_MUCLIBC-- Add -muclibc c flag
-DBUILD_DEPENDENCIES-- Whether or not to build depending libraries from source
-DBUILD_OPENSSL-- If building dependencies, whether or not building openssl from source
-DBUILD_OPENSSL_PLATFORM-- If buildng OpenSSL what is the target platform
-DBUILD_LIBSRTP_HOST_PLATFORM-- If buildng LibSRTP what is the current platform
-DBUILD_LIBSRTP_DESTINATION_PLATFORM-- If buildng LibSRTP what is the destination platform
-DBUILD_TEST=TRUE-- Build unit/integration tests, may be useful for confirm support for your device.
-DCODE_COVERAGE-- Enable coverage reporting
-DCOMPILER_WARNINGS-- Enable all compiler warnings
-DADDRESS_SANITIZER-- Build with AddressSanitizer
-DMEMORY_SANITIZER-- Build with MemorySanitizer
-DTHREAD_SANITIZER-- Build with ThreadSanitizer
-DUNDEFINED_BEHAVIOR_SANITIZERBuild with UndefinedBehaviorSanitizer`
To build the library and the provided samples run make in the build directory you executed CMake.
Setup your environment with your AWS account credentials:
First set the appropriate environment variables so you can connect to KVS
export AWS_ACCESS_KEY_ID= <AWS account access key> export AWS_SECRET_ACCESS_KEY= <AWS account secret key>
Setup desired log level:
Set up the desired log level. The log levels and corresponding values currently available are:
To set a log level, run the following command:
export AWS_KVS_LOG_LEVEL = <LOG_LEVEL>
export AWS_KVS_LOG_LEVEL = 2 switches on DEBUG level logs while runnning the samples
Note: The default log level is
Running the Samples
make you will have the following sample applications in your
kvsWebrtcClientMaster- This application sends sample H264/Opus frames (path:
/samples/opusSampleFrames) via WebRTC. It also accepts incoming audio, if enabled in the browser. When checked in the browser, it prints the metadata of the received audio packets in your terminal.
kvsWebrtcClientViewer- This application accepts sample H264/Opus frames and prints them out.
kvsWebrtcClientMasterGstSample- This application sends sample H264/Opus frames from a GStreamer pipeline. It also will playback incoming audio via an
Run any of the sample applications by passing to it the name that you want to give to your signaling channel. The application creates the signaling channel using the name you provide. For example, to create a signaling channel called myChannel and to start sending sample H264/Opus frames via this channel, run the following command:
When the command line application prints "Signaling client connection to socket established", you can proceed to the next step.
Now that your signaling channel is created and the connected master is streaming media to it, you can view this stream. To do so, open the WebRTC SDK Test Page using the steps in Using the Kinesis Video Streams with WebRTC Test Page and set the following values using the same AWS credentials and the same signaling channel that you specified for the master above:
- Access key ID
- Secret access key
- Signaling channel name
- Client ID (optional)
Choose Start viewer to start live video streaming of the sample H264/Opus frames.
This library is licensed under the Apache 2.0 License.