There's nothing inherently problematic or particularly poorly-performing about using Kamailio as a bridge to a protocol it does not natively speak -- and thus, no need for a single-minded fixation on a C module. At this point, all the latter would provide is syntactical sugar. Kamailio offers: 1) Extensive packaged async capabilities; 2) Manual management of asynchronous workloads using mqueue + timer; 3) KEMI embedded scripting API framework; 4) Numerous embedded language interpreters, e.g. app_python, which perform very admirably. In the case of app_python, it loads once on startup, byte-compiles the script it will run, and the byte-compiled version sits as an in-memory resident. You can string this together with async workers to make Kamailio lift even some very heavy weight outside the main SIP worker process pool. Small differences in performance between native config script and external scripts were far more relevant in a different era of computing hardware, and are unlikely to be relevant to your application. In a sense, Kamailio already has an SMPP module. You just need to wire the connectors together. -- Alex On Sat, Apr 11, 2020 at 09:20:24PM +0100, David Villasmil wrote: -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/