>Hi,
>
>I am testing DLR (&dlrmask=3) with emi2 but I have that problem :
>
>2001-09-06 14:45:35 [11] DEBUG: boxc_receiver: sms received
>2001-09-06 14:45:35 [7] DEBUG: emi2 sending packet:
><39/00087/O/51/0033607957104/0D46761D5F9FCB00//1//3/////////////3//31///////
>/5039/////F3>
>2001-09-06 14:45:35 [7] DEBUG: Got packet from the main socket
>2001-09-06 14:45:35 [7] DEBUG: emi2 parsing packet:
><39/00044/R/51/A//33607957104:060901144535/83>
>2001-09-06 14:45:35 [7] INFO: Adding to DLR list smsc=Mobileway2,
>ts=060901144535, dst=33607957104, keyword=DLR, id= mask=3
>2001-09-06 14:45:35 [7] INFO: appended
>2001-09-06 14:45:52 [6] DEBUG: Got packet from the receive connection.
>2001-09-06 14:45:52 [6] DEBUG: emi2 parsing packet:
><00/00127/O/53/805/0033607957104/////////////060901144552/0//060901144552/3/
>/44656C69766572656420746F20534D5343///////////////CC>
>2001-09-06 14:45:52 [6] WARNING: get_fields: EMI message of type 53/O has 2
>more fields than expected.
>2001-09-06 14:45:52 [6] INFO: Looking for DLR smsc=Mobileway2,
>ts=060901144552, dst=0033607957104, type=1
>2001-09-06 14:45:52 [6] INFO: checking entry 0 in list
>2001-09-06 14:45:52 [6] INFO: dlr->smsc = 'Mobileway2'
>2001-09-06 14:45:52 [6] INFO: dlr->timestamp = '060901144535'
>2001-09-06 14:45:52 [6] INFO: dlr->destination = '33607957104'
>2001-09-06 14:45:52 [6] INFO: dlr->keyword = 'DLR'
>2001-09-06 14:45:52 [6] INFO: dlr->id = ''
>2001-09-06 14:45:52 [6] INFO: dlr->mask = 3
>2001-09-06 14:45:52 [6] INFO: DLR not found!
>2001-09-06 14:45:52 [6] DEBUG: emi2 sending packet: <00/00020/R/53/A///96>
As you can see above. your sending out a message to
33607957104 with a timestamp of 060901144535
The SMSC then returns with a delivery report for that number
but with ANOTHER timestamp. So it is a delivery report for a previous
try to that number or your SMSC is acting very strange.
The DLR you get back from the SMSC is definitively violating the
specifications. It has two fields more than normal. All 50 messages
however use the same message format so this is not a standard message
as it should be. Not surprisingly the timestamp istn correct either.
I would say you do not connect to a CMG SMSC but to some badly
written simulator or front end. The content of the DLR text is saying
"Delivered to SMSC" which I also have never seen on real SMSC's. I
usually get something like "The message with ID ..... has been
delivered to .... on ...." or similar text messages.
>Does the problem comes from my SMSC ? It seems that the timestamp was
>modified and that could be the problem.
Definitively.
>Moreover, does the DLR list is saved on disk or not ? If not, what happened
>if Kannel is rebooted before the DLR arrives from SMSC ?
Then its lost in the current setup. This is something I'm going to
change. I'll probably do a version with mySQL.
>Same questions for MT not sent to SMSC due to temporary lack of access to
>SMSC ?
>Finally, is that DLR a mobile DLR or the SMSC DLR ?
Thats a Mobile DLR. A CMG can deliver the following DLR's:
a) delivery failed
b) message buffered on SMSC but not yet delivered
c) message delivered on phone
We only ask for DLR's of type a) and c) and we ignore incoming b)'s.
--
Andreas Fink
Fink-Consulting
------------------------------------------------------------------
Tel: +41-61-6932730 Fax: +41-61-6932729 Mobile: +41-79-2457333
Address: A. Fink, Schwarzwaldallee 16, 4058 Basel, Switzerland
E-Mail: [EMAIL PROTECTED] Homepage: http://www.finkconsulting.com
------------------------------------------------------------------
Something urgent? Try http://www.smsrelay.com/ Nickname afink
