Re: Multipart DLR issue

Alexander Malysh <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
it may not work for load balanced connection via different SMSCs...

Thanks,
Alexander Malysh

Am 17.06.2010 um 18:32 schrieb Rene Kluwen:

> So what I will continue to do send a DLR for each part. Even if Kannel
> doesn't like it.
> 
> == Rene
> 
> -----Original Message-----
> From: Alexander Malysh [mailto:[email protected]] On Behalf Of
> Alexander Malysh
> Sent: donderdag 17 juni 2010 18:25
> To: Rene Kluwen
> Cc: 'Kannel Devel'
> Subject: Re: Multipart DLR issue
> 
> Hi Rene,
> 
> this is a known Kannel limitation. Kannel request DLR only for the first
> part.
> 
> Thanks,
> Alexander Malysh
> 
> Am 17.06.2010 um 14:46 schrieb Rene Kluwen:
> 
>> This is the setup:
>> 
>>           KANNEL 1                                                 KANNEL
> 2
>> CGI PUSH -- SMSBOX 1 -- BEARERBOX 1 ------ SMPP LINK ------ Open SMPPBOX
> --- BEARERBOX 2
>> 
>> I am working on smppbox sending multi-part messages via the same SMSC (on
> Kannel 2). I do this by reassembling the submit_sm pdu's in smppbox back to
> one large SMS and sending it to bearerbox as a whole.
>> This works now and will be submitted to svn shortly.
>> 
>> I keep track of which smpp id's the message originally consisted of and
> when I get a DLR, I send a deliver_sm for each of these pdu's.
>> 
>> As you can see in the log files (attached) the second PDU doesn't seem to
> be stored in the DLR database of bearerbox 1. What exactly is the procedure
> here to be followed?
>> 
>> I assume that if an sms message consists of multiple parts, each part
> needs to be matched with a corresponding DLR receipt. But it seems that
> Kannel only stores the first part in the DLR table and is not interested in
> the rest.
>> 
>> Thank you for your time,
>> 
>> == Rene
>> 
>> <bearerbox1.log><smppbox2.log>
> 
> 
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.