Hi Mike, With this config, all should be fine. Do you have this problem too using a live SMSC?
-- Regards Kenny On Thu, Jan 5, 2012 at 9:09 AM, Niel Smith <daniel.alfred.sm...@gmail.com>wrote: > Hi, > > I've also noticed the same behaviour when using a fake smsc, and as far as > I can tell this is normal. > > When sending a looong MTSMS, the message is fragmented / broken into > pieces and sent as separate SMSs. Normally you will be charged for each > one. (See max-messages under group = sms-service). Each part will have a > specific data header to specify the total number of messages, the order of > each, and some ID. > > It is then role of subscriber's handset to wait for all the pieces and > combine them into a single message. > > The same happens in reverse for long MOSMS messages, the handset again > fragments the messages into parts, and kannel will then reassemble them. > (See the sms-combine-concatenated-mo and > sms-combine-concatenated-mo-timeout parameters in the group = core) > > So in short, the fake smsc does not automatically reassemble messages. > > Regards, > > > > On 24 December 2011 14:30, michael osakede <ire...@yahoo.com> wrote: > >> Hi, >> >> below is my kannel config, when i send a 3 part message it is delivered >> in 3 separate messages,instead of one message with 3 pages. what do i add >> to my config to enable all the message parts to be packaged as one message? >> I amusing SQLBOX with my Kannel >> >> group = smsc >> smsc = fake >> smsc-id = FAKE >> port = 20000 >> group = smsc >> smsc = smpp >> smsc-id = xxxxx >> host = smsplus1.routesms.com >> port = 2345 >> receive-port = 2345 >> msg-id-type=0x01 >> smsc-username = xxxxxx >> smsc-password = xxxxxx >> system-type = NULL >> dest-addr-ton = 1 >> address-range = >> bind-addr-ton = 0 >> bind-addr-npi = 1 >> dest-addr-ton = 1 >> dest-addr-npi = 1 >> source-addr-ton = 5 >> source-addr-npi = 1 >> enquire-link-interval = 60 >> interface-version = 34 >> reconnect-delay = 30 >> allowed-smsc-id = xxxxxx >> > >
