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" DLRactually comes in the message body at the end of delivery. Am I correct ?So, when using Logica SMSC simulator there are different numbers beingreported as message ID refering to the same message:.1) After sending the message there comes Submit Response with mesage IDX (for example). This message ID is being taken by Kannel and written intoDLR database together with other data.2) Than comes Delivery notification with status 8 (this is what is meant by DLRin Kannel vocabulary, if I understood well). Problem is that this notificationcontains Message ID (lets say Y) which looks completely different from themessage ID obtained in step 1 (Y <> X). I have no clue how to relate thesetwo 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 bodywhich are given in the appendix of SMPP 3.4 specs. Among those datathere is again that number X given as message ID (the same as theone from the Submit response).QUESTIONS:Q1- Is my understanding that Kannel DLR database actualy deals with Delivery Notificationsand not "Real" DLRs, as described in SMPP 3.4 spec, correct ?Q2- did anyone managed the succesfull usage of Kannel DLR database whentesting with Logica SMSC simulatorQ3 - do you allways have the situation in Real Life (for those who are using the lifenetwork systems) that the Delivery Notification Contains Message ID exactlyappropriate 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 onlynotifications ?Q6 - is message ID the only parameter that could be used for matching Delivery Notificationsin Kannel DLR database, or something else could be used as well ?Thanks,Ilija----- Original Message -----From: Alex KinchCc: users@kannel.orgSent: Friday, May 05, 2006 5:06 PMSubject: 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!