Re: DLR : why I got this log on smsclogfile?

[Ilija Cutura google]

Hi Alex,   thanx for your promt response. I tested this now, but I had the problem with it.   Namely, in submit_sm_resp which I get from Logica SMSC msgID is interpreted in Kannels SMSClog as text (for example SMSC2149). When I was NOT using msg-id-type in SMSC config than i had that message id written in "ts" column of DLR table.   When I implemented message-id-type than I got allways 0 in the "ts" column for every message regardles of which value I was ussing for msg-id-type.   Do you have an idea what am I doing wrong here ? Thanks Ilija ----- Original Message ----- From: Alex Kinch To: Ilija Cutura google Cc: users@kannel.org Sent: Friday, May 05, 2006 7:07 PM Subject: Re: DLR : why I got this log on smsclogfile? Hello,   I've connected to Logica SMSCs without a problem. Use:   msg-id-type = 0x01   which will make Kannel expect the submit_sm_resp in hex and the deliver_sm in decimal.   Alex   On 5/5/06, Ilija Cutura google <[EMAIL PROTECTED]> wrote: Hi All,   Does anyone have expirience with DLR handling using Logica SMSC simulator?   Just to get a common understanding. This, what is in Kannel context called DLR, is actually Delivery Notification according to SMPP 3.4 spec. "Real" DLR actually comes in the message body at the end of delivery. Am I correct ?   So, when using Logica SMSC simulator there are different numbers being reported as message ID refering to the same message:.   1) After sending the message there comes Submit Response with mesage ID X (for example). This message ID is being taken by Kannel and written into DLR database together with other data.   2) Than comes Delivery notification with status 8 (this is what is meant by DLR in Kannel vocabulary, if I understood well). Problem is that this notification contains Message ID (lets say Y) which looks completely different from the message ID obtained in step 1  (Y <> X). I have no clue how to relate these two numbers, although I am 100% sure they refer to the same message.   3) At the end comes "Real" DLR having all those data in the message body which are given in the appendix of SMPP 3.4 specs. Among those data there is again that number X given as message ID (the same as the one from the Submit response).     QUESTIONS:   Q1- Is my understanding that Kannel DLR database actualy deals with Delivery Notifications and not "Real" DLRs, as described in SMPP 3.4 spec, correct ?   Q2- did anyone managed the succesfull usage of Kannel DLR database when testing with Logica SMSC simulator   Q3 - do you allways have the situation in Real Life (for those who are using the life network systems) that the Delivery Notification Contains Message ID exactly appropriate to the one obtained in Sumbit Response when sending original message ?   Q4 - Could msg-id-type parameter be helpfull to test with Logica SMSC as well ?   Q5 - is there any way of automatic handling of "real" DLRs with Kannel, and not only notifications ?   Q6 - is message ID the only parameter that could be used for matching Delivery Notifications in Kannel DLR database, or something else could be used as well  ?   Thanks, Ilija           ----- Original Message ----- From: Alex Kinch To: [EMAIL PROTECTED] Cc: users@kannel.org Sent: Friday, May 05, 2006 5:06 PM Subject: Re: DLR : why I got this log on smsclogfile?   It's because you have received a delivery report that doesn't match up to anything in Kannel's DLR table. Try sending a message, noting down the message id that Kannel logs to the DLR table, then see what DLR it is looking for when the report comes back. It's possible that you'll need to use the msg-id-type option in your SMPP configuration.   Alex   On 5/5/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: 2006-05-05 16:53:05 [4326] [7] DEBUG: DLR[internal]: Looking for DLR smsc=my_route, ts=9093560, dst=393386776419, type=1 2006-05-05 16:53:05 [4326] [7] WARNING: DLR[internal]: DLR for DST<393386776419> not found. 2006-05-05 16:53:05 [4326] [7] ERROR: SMPP[my_route]: got DLR but could not find message or was not interested in it id<9093560> dst<sergio>, type<1> Was NOT interested?? Who?? I hope not me, i'm trying to get them from a lot of time! Could anybody explain how to fix this? Thank you!