Jim Bunch schrieb: > I need an open source C or C++ SMPP stack that I can integrate into a > product that needs to send and receive SMS messages. The Kannel WAP and > SMS Gateway has SMPP support. However, I do not need the WAP capability. > Is it possible to breakout the SMPP files as a standalone capability > that could be integrated into another product? If yes, is there a > document that clearly defines the SMPP files and other related files > that might be needed?
now, Kannel has the SMPP client stack included in it's abstracted SMSC connection layer in bearerbox. Relevant files are gw/smsc/smsc_smpp.c and gw/smsc/smpp* But beware, we use a lot of pre-processor magic in there ;) In fact "isolating" the SMPP client stack will be some tackle, but possible. What bearerbox does is to map Kannel's msg strcut <-> SMPP PDU and vice versa. In terms of isolation, keep in mind that Kannel is NOT designed as protocol library, it is designed as transport layer stack, which abstracts all the supported SMSC protocols to the HTTP application layer. Can you point out what the "another product" shall do with the SMPP stack and describe the architecture? Stipe -- ------------------------------------------------------------------- Kölner Landstrasse 419 40589 Düsseldorf, NRW, Germany tolj.org system architecture Kannel Software Foundation (KSF) http://www.tolj.org/ http://www.kannel.org/ mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org -------------------------------------------------------------------
