Hi, it should be possible in bearerbox and in smsbox but smsbox will need to be modified.
In bearerbox you have to use max-sms-octets config variable to set maximum length for SMSC module/connection. Btw. SMPP allow message up to 64K using message_payload... Thanks, Alex Am 30.10.2010 um 17:53 schrieb Luca Corti: > On Sat, 2010-10-30 at 18:16 +0300, Nikos Balkanas wrote: >> No, you cannot do that, it is in a violation of the SMS spec. After all SMS >> stands for "Short Messaging System". If you want to create an SMSc just for >> you, be my guest, but it won't be able to handle any other traffic other >> than yours. > > As I clearly stated, I'd like to *abuse* kannel. Obviously, these are > not SMS messages, since they do not adhere to the SMS specs, but they > share enough common traits with SMS messages that the only limitation I > see is the message length. > > I know implementing my own protocol/driver will not allow me to route > such messages through standard SMSCs. I asked if the kannel internal > architecture allows larger messages larger to flow through kannel > (smsbox, bearerbox) and be delivered to a driver which talks > non-standard protocols to non-standard SMSCs. > > If my understanding of how kannel works is correct, this is the flow of > a message submitted through sendsms and terminated via a driver to an > SMSc: > > HTTP -> sendsms -> smsbox -> bearerbox -> smsc driver > > Are there internal data formats or validity checks in place which > explicitly forbid this? > > I realize I'm trying to bend kannel to my needs, I'd just like to know > if this is theoretically possible before considering the possibility of > implementing an smsc driver. > > I'm currently looking at the code, but I thought this is a question > kannel developers may be able to quickly respond to. > > thanks for your feedback > > Luca > >
