[EMAIL PROTECTED] schrieb:
Hi List,
has anyone experienced a similar effect?

(from Mantis bug report 000444):
Hi,
we're testing kannel to communicate with mobile GSM modems in trucks. These 
modems are mostly active, but sometime are switched off. Recently we added 
Delivery Reports to our application. Now we're facing the effect that after 
getting a DLR with status 4 (message buffered), some following DLRs are wrong. 
The message from the SMSC inside the DLR states a different originator than the 
Parameter for the SMS Service URL. This problem can be reproduced by sending 
SMS to five cell phones, if one of them has been switched of, some of the 
messages are wrong. The EMI/UCP logfile for the shows a correct result for the 
notifications, but kannelaccess.log and smsbox.log do not. We discovered the 
problem while connected with T-Mobile SMSC using a windowing parameter of 4, 
which is set in our large account with T-Mobile-SMS-Support. Is it possible 
that DLRs don't work very well with windowing?

example:
2008-02-07 13:14:51 Receive DLR [SMSC:d1InternetG] [SVC:smsuser] [ACT:] [BINF:] 
[from:+4900100] [to:+491752462477] [flags:-1:-1:-1:-1:1] [msg:97:Vielen Dank. 
Ihre Mitteilung 080207140844 ist bei 01754161594 am 07.02.08 um 14:08:51 
angekommen.] [udh:0:]

Hi Holger,

ok, this means you receive a final DLR for a SMS where the phone (GSM modem) is switched off, right?

This should be the infamous EMI/UCP limitation for not being able to reference the msg ID "systematically correct", as SMPP does ie.

Can you provide more details from the log files please?

In addition I may suggest to move the thread to 'devel' mailing list, which is more adequate for development purposes.

Thanks,
Stipe

-------------------------------------------------------------------
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany

tolj.org system architecture      Kannel Software Foundation (KSF)
http://www.tolj.org/              http://www.kannel.org/

mailto:st_{at}_tolj.org           mailto:stolj_{at}_kannel.org
-------------------------------------------------------------------

Reply via email to