ntgcalls

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

NativeTgCalls

Welcome to NativeTgCalls, an innovative open-source project. NativeTgCalls represents the next evolution in Telegram calling, building on the foundation laid by PyTgCalls.

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

...and more, without even rewriting your code that uses PyTgCalls!

Overview

NativeTgCalls, often referred to as NTgCalls, is an exciting open-source venture. This project redefines the Telegram calling experience and introduces innovative features while preserving the legacy of PyTgCalls.

Build Status

Architecture	Windows	Linux	MacOS
x86_64
ARM64

Key Features

Experimentation and Customization

NativeTgCalls is a playground for experimentation. We understand the importance of customization for developers, empowering you to tailor your Telegram calling solutions to your precise requirements.

Advancing with PyTgCalls

Building upon the success of PyTgCalls, NativeTgCalls provides a natural progression for developers familiar with its predecessor. This evolution streamlines the development process and extends the capabilities of Telegram calling.

Importantly, PyTgCalls will seamlessly integrate the new core (NTgCalls) to ensure backward compatibility.

Compiling

Python Bindings

NativeTgCalls offers Py Bindings, enabling seamless integration with Python. Follow these steps to compile NativeTgCalls with Python Bindings:

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

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

   python3 setup.py install
   

Go Bindings

NativeTgCalls offers Go Bindings, enabling seamless integration with Go. Follow these steps to compile NativeTgCalls 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 library itself and can be found here
3. Download shared release of the library from https://github.com/pytgcalls/ntgcalls/releases
   1. Static won't work
4. Copy ntgcalls.h file into ./examples/go/ntgcalls/ directory
5. The rest of the files should be copied to ./examples/go/ directory
   1. ntgcalls.dll and ntgcalls.lib files in case of Windows amd64 shared release
6. Then in ./examples/go/ directory run go build or go run . with CGO_ENABLED=1 env variable set
   1. $env:CGO_ENABLED=1; go run . for Windows PowerShell
   2. CGO_ENABLED=1 go run . for UNIX

C Bindings

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

1. Ensure you are in the root directory of the NativeTgCalls project.
2. Run the following command to generate the shared libs:

   python3 setup.py build_shared
   

3. Upon successful execution, a shared library will be generated in the "shared-output" directory. You can now use this library to develop applications with NativeTgCalls.
4. To include the necessary headers in your C/C++ projects, you will find the "include" folder in the root of the project. Utilize this folder for 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, utilizing 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. 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.