pjproject VS embox

Hello, I'm in the process of developing a multiplayer FPS game and recently delved into ICE connectivity (STUN/TURN). Currently, my setup involves a custom matchmaking server in C++, with UDP port handling on the client side through UPnP or a fallback custom relay server. While the current approach works well, I'm exploring options to simplify the project by incorporating existing technologies. I've come across Libjuice and Libpjsip for NAT traversal. Libjuice offers a nice and simple API, but it supports only one person. Hence, I'm considering Libpjsip. I came across their ICE demo script at https://github.com/pjsip/pjproject/blob/master/pjsip-apps/src/samples/icedemo.c and I'm curious about its performance, particularly the pj_ice_strans_sendto2 function. I'm keen to understand how it compares to my current implementation with Berkeley Sockets and whether Libpjsip is a suitable choice for multiplayer P2P games. Any insights or assistance would be highly appreciated. Thanks!

Things improved a lot thanks to the adoption of the pjsip stack.

When I look at stuff like pjsip, I get the impression, it would be huge amount of work. Am I mistaken?

The first issue I'm facing is I can't find lib folder which is mentioned in Using pjproject libraries for your own application heading in the above-mentioned link. I download the source code from this link.

For client and server, I'm only really familiar with https://www.pjsip.org/. It also comes with a bunch of code for doing phone calls, which really most SIP Stacks were built around. But those parts can just not be used.

PJSIP (https://github.com/pjsip/pjproject) is used as SIP framework

Embox is a configurable RTOS designed for resource constrained and embedded systems. Embox main idea is using Linux software without Linux. (https://embox.github.io/ ) If you want use complex Linux Software and Linux is huge for your goals. Embox is the best idea, as I think. For example Embox is the only RTOS that allows to use OpenCV on Cortex-m MCUs https://www.embedded.com/benchmarking-opencv-on-stm32-mcus/

Look at Embox (https://github.com/embox/embox). It can run on EFM32ZG with 32kB ROM 4kB RAM

Take a look at Embox - https://github.com/embox/embox

As for Linux, it allows easy and fast creating a device with reach features, but it requires more powerful and expensive hardware platforms, it has some questions with hard real-time, and it is less secure after all it is a general-purpose OS. We try to solve these cons of Linux in Embox. It combines prop RTOSes and Linux and allows run Linux software everywhere including MCUs

We try to solve these Linux disadvantages in our way in Embox project. The project allows run Linux software everywhere including MCUs.