Re: [PATCH] Re: MO Concatenation

Paul Bagyenda <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
So we have some sort of agreement, except that I can't seem to find  
any reference to 'smsc-group-id' in the conf or the structure, so I  
shall use smscid instead. A new patch will be forthcoming once I have  
successfully fought a few local fires!


P.

On Jan 09, 2007, at 11:08, Andreas Fink wrote:

>
>
> On 09.01.2007, at 08:59, Δημήτρης Ευμορφόπουλος  
> wrote:
>
>> So you mean msisdn + refnum + smsc-group-id not smscid ... That is  
>> valid!
>
> well group-id seems to be new and I have not looked at this part  
> for a while.
> but sounds logical.
>
>> BTW, what do you think that the time-to-live for each part should  
>> be? We show that anything over 3 minutes is already too much.
>>
> 3 minutes doesnt sound that wrong to me. You must consider an  
> incoming SMS from a SIM card where the second part cant be hit  
> because the phone was processing the first part (yes there are  
> still bogous SMSC's out there) so the second part would deliver as  
> retry a few minutes later. This can be even 10 minutes. Maybe make  
> it default to 3 minutes and make it uer configurable.
>
>> Dimitris Evmorfopoulos
>>
>> -----Original Message-----
>> From: Andreas Fink [mailto:[email protected]]
>> Sent: Monday, January 08, 2007 7:45 PM
>> To: Δημήτρης Ευμορφόπουλος
>> Cc: [email protected]; Alexander Malysh
>> Subject: Re: [PATCH] Re: MO Concatenation
>>
>>
>> On 08.01.2007, at 17:38, Δημήτρης Ευμορφόπουλος
>> wrote:
>>
>>> The triple key is not valid. From personal experience I was getting
>>> the SMS parts from all SMSC's not the one that transmitted the
>>> first part only. All the operators I worked with do the same thing.
>>> So the key should remain msisdn + refnum only.
>>
>> msisdn + refnum + smscid.
>>
>> multiple SMSC's behaving the same are / must be grouped in the same
>> smsc-id for DLR consolidation too.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
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.