ntgcalls 2.2.1b3

A Native Implementation of Telegram Calls in a seamless way.

A Native Implementation of Telegram Calls in a seamless way.
Examples • Documentation • PyPi • Releases • Channel • Chat

NTgCalls

NTgCalls is a lightweight open-source library for media streaming in Telegram calls. Built from scratch in C++ with WebRTC & Boost, it prioritizes accessibility to developers and resource efficiency.

Powerful	Simple	Light
Built from scratch in C++ using Boost and libwebrtc	Simple Python, GO, C Bindings and Java for Android SDK	We removed anything that could burden the library, including NodeJS

Build Status

Architecture	Windows	Linux	MacOS
x86_64
ARM64

Features

• Pre-built binaries for macOS (arm64-v8a), Linux (x86_64, arm64-v8a), Windows (x86_64), and Android (x86, 86_64, arm64-v8a, armv7)
• Call flexibility: Group and private call support
• Media controls: pause/resume and mute/unmute
• Codec compatibility: H.264, HEVC (H.265), VP8, VP9, AV1, AAC, MP3, Opus
• Content sharing: Screen streaming, Microphone and Camera streaming
• Pre-built wheels for Python & AAR SDK library for Android

Compiling

Python Bindings

NTgCalls includes Python bindings for seamless integration. Follow these steps to compile it with Python Bindings:

1. Ensure you are in the root directory of the NTgCalls project.

2. Run the following command to install the Py Bindings:

   python3 setup.py install
   

Go Bindings

[!WARNING] Static linking for Windows is not supported yet since our library is built with MSVC and Go uses MinGW for static linking. More info can be found here

NTgCalls includes Go Bindings, enabling seamless integration with Go. Follow these steps to compile it with Go Bindings:

1. There is an example project for Go in ./examples/go/ directory, ensure you are in that directory
2. Prerequisites for building are the same as for building a library itself and can be found here
3. Download shared or static release of the library from https://github.com/pytgcalls/ntgcalls/releases
4. Copy ntgcalls.h file into ./examples/go/ntgcalls/ directory
5. The rest of the files should be copied to ./examples/go/ directory
   • ntgcalls.dll or ntgcalls.lib files in case of Windows amd64
   • libntgcalls.so or libntgcalls.a files in case of Linux amd64
   • libntgcalls.dylib or libntgcalls.a files in case of macOS
6. Then in ./examples/go/ directory run go build or go run . with CGO_ENABLED=1 env variable set
   • $env:CGO_ENABLED=1; go run . for Windows PowerShell
   • CGO_ENABLED=1 go run . for UNIX

C Bindings

For developers looking to use NTgCalls with C and C++, we provide C Bindings. Follow these steps to compile it with C Bindings:

1. Ensure you are in the root directory of the NTgCalls project.
2. Run the following command to generate the library:

   # Static library
   python3 setup.py build_lib --static
   
   # Shared library
   python3 setup.py build_lib --shared
   

3. Upon successful execution, a library will be generated in the "shared-output" or "static-output" directory, depending on the chosen option. Now you can use this library to develop applications with NTgCalls.
4. To include the necessary headers in your C/C++ projects, you will find the "include" folder in the "shared-output" or "static-output" directory. Use this folder by including the required header files.

Key Contributors

• @Laky-64 (DevOps Engineer, Software Architect, Porting Engineer):
  • Played a crucial role in developing NTgCalls.
  • Created the Python Bindings that made the library accessible to Python developers.
  • Developed the C Bindings, enabling the library's use in various environments.
• @dadadani (Senior C++ Developer, Performance engineer):
  • Contributed to setting up CMakeLists and integrating with pybind11, greatly simplifying the library's usage for C++ developers.
• @kuogi (Senior UI/UX designer, Documenter):
  • As a Senior UI/UX Designer, Kuogi has significantly improved the user interface of our documentation, making it more visually appealing and user-friendly.
  • It Has also played a key role in writing and structuring our documentation, ensuring that it is clear, informative, and accessible to all users.
• @vrumger (Mid-level NodeJS Developer):
  • Avrumy has made important fixes and enhancements to the WebRTC component of the library, improving its stability and performance.

Junior Developers

• @TuriOG (Junior Python Developer):
  • Currently working on integrating NTgCalls into PyTgCalls, an important step in expanding the functionality and usability of the library.
• @doggyhaha (Junior DevOps, Tester):
  • Performs testing of NTgCalls on Linux to ensure its reliability and compatibility.
  • Specializes in creating and maintaining GitHub Actions, focusing on automation tasks.
• @tappo03 (Junior Go Developer, Tester):
  • Performs testing of NTgCalls on Windows to ensure its reliability and compatibility.
  • It Is in the process of integrating NTgCalls into a Go wrapper, further enhancing the library's versatility and accessibility.

Special Thanks

• @shiguredo: We extend our special thanks to 時雨堂 (shiguredo) for their invaluable assistance in integrating the WebRTC component. Their contributions, using the Sora C++ SDK, have been instrumental in enhancing the functionality of our library.

• @evgeny-nadymov: A heartfelt thank you to Evgeny Nadymov for graciously allowing us to use their code from telegram-react. His contribution has been pivotal to the success of this project.

• @morethanwords: We extend our special thanks to morethanwords for their invaluable help in integrating the connection to WebRTC with Telegram Web K. Their assistance has been instrumental in enhancing the functionality of our library.

• @MarshalX: for their generous assistance in answering questions and providing insights regarding WebRTC.

• @LyzCoote: for providing an ARM64 Server and allowing us to build an image with clang-18 preinstalled on manylinux2014 arm64.

We would like to extend a special thanks to @null-nick and @branchscope for their valuable contributions to the testing phase of the library and to @SadLuffy for his assistance as a copywriter. Their dedication to testing and optimizing the library has been instrumental in its success.

Additionally, we extend our gratitude to all contributors for their exceptional work in making this project a reality.