Re: delivery reports and EMI [known bug issue]

Hi

snips from all the postings
At 07:59 AM 11/13/02 +0100, Andreas Fink wrote:

>>We have a work around, which is a bit hacky but works for us. We use the 
>>8 right most digits of the number to match the DLR in the db/store.
>
>That would not be good enough in most cases.


why? given that there is a timestamp and destination  in the dlr tables. 
one would need multiple messages in quick succession, within 1 second to 
the same nmber, to end up with a clash. This is not ideal but works in most 
cases.


>My approach would simply to specify international and national prefixes 
>and country codes on the SMSC link.

I am not convinced that we can make a unified prefix work in all cases, and 
allow us to still have applications routing dynamically to Kannel. I have 
seen quite diverse numbers comming back from some EMI connections. It might 
also make the Kannel configs quite messy if one has many international and 
national prefixes and country codes on one SMSC link. Upstream providers 
also tend to change coverage patterns quite regularly and this would mean 
restarting Kannel.


>This would also help on the sending side where a + currently is replaced 
>hardcoded with 00 which is not really always true.

The unified-prefix on an SMSC basis can be used to overcome this. I have a 
small patch for EMI2 module to do this.

>I agree on this but a delivery of the first message makes it very likely 
>that the second message gets delivered too. So you would expect to have 
>two identical deliveries or failures.

Not so.. The destination network may bar multiple quick submission of 
messages from the same src to the same destination, the SIM may become full 
etc..

Nisan