Ok, are you sure that the carrier has enabled DLR's for your account? Regards,
Alejandro On 8/15/07, Ady Wicaksono <[EMAIL PROTECTED]> wrote: > Kannel don't even recognized this MO SMS as DLR, so kannel hit my default > SMS handler > not dlr-url :) > > dlr-url is urlencoded > > > On 8/15/07, Alejandro Guerrieri <[EMAIL PROTECTED]> wrote: > > Ady, > > > > >From what I understand, you send a message and gets loaded on the dlr > > table, but when the dlr comes back (it comes back, right) kannel does > > not recognize it and the dlr stays forever on the table? > > > > Or, kannel recognizes it but doesn't hit dlr-url? > > > > First of all, check the logs and make sure wich case is yours, maybe > > something's wrong on the conf files (there's a setting for the format > > on the message_id, for example, some SMSC return in hex, some in > > decimal and that could be confusing the dlr engine). > > > > Also make sure that you are sending the dlr-url urlencoded. > > > > If you want to paste some relevant log entries we could take a look at it. > > > > Regards, > > > > Alejandro > > > > On 8/12/07, Ady Wicaksono <[EMAIL PROTECTED]> wrote: > > > I think we have a little missunderstanding :) > > > the problem is dlr-url is not working :) > > > > > > if when DLR comes and kannel could detect it then it should be hit > dlr-url > > > right? > > > the problem is, kannel never hit dlr-url I defined when doing submit SMS > > > > > > > > > > > > On 8/13/07, Alejandro Guerrieri < [EMAIL PROTECTED]> wrote: > > > > Ady, > > > > > > > > Have you really _read_ the docs? Think about a little, what purpose > > > > could have a dlr engine if you cannot have a mean to identify each > > > > particular message? > > > > > > > > The %d parameter carries the message id, so you can identify the > > > > delivery when it gets back. > > > > > > > > Pass the %d parameter on the dlr-url, and it will get back with the > > > > message id when the dlr is updated. > > > > > > > > Regards, > > > > > > > > Alejandro > > > > > > > > > > > > > > > > On 8/12/07, Ady Wicaksono < [EMAIL PROTECTED]> wrote: > > > > > Hi Alejandro > > > > > > > > > > The problem is not on delivery report value itself. The problem is, > I > > > need > > > > > to know which message is delivered, or undelivered > > > > > > > > > > I send SMS A (submit_sm) --> to kannel HTTP Service only got status > > > > > "Accepted for delivery". > > > > > > > > > > By common case, kannel will maintain SMSC, one kannel found DLR it > will > > > > > generate HTTP request > > > > > as defined by me when doing submit_sm. But it's not happening, SMSC > send > > > > > standard incoming SMS > > > > > without informing that this SMS is delivery report, but I know the > > > format is > > > > > DLR. Kannel NEVER > > > > > generate HTTP request to my delivery report handler. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 8/12/07, Alejandro Guerrieri < [EMAIL PROTECTED] > > wrote: > > > > > > Ady, > > > > > > > > > > > > Check the user guide for the "%d" parameter, it's what you're > looking > > > for. > > > > > > > > > > > > Regards, > > > > > > > > > > > > Alejandro > > > > > > > > > > > > On 8/12/07, Ady Wicaksono < [EMAIL PROTECTED]> wrote: > > > > > > > I have one SMSC connection and already setup DLR for kannel. > > > > > > > > > > > > > > I use DLR-MySQL with configuration like this > > > > > > > > > > > > > > ----------- cut here ------------- > > > > > > > group = dlr-db > > > > > > > id = mydlr > > > > > > > table = t_kannel_dlr > > > > > > > field-smsc = smsc > > > > > > > field-timestamp = timestamp > > > > > > > field-destination = destination > > > > > > > field-source = source > > > > > > > field-service = service > > > > > > > field-url = url > > > > > > > field-mask = mask > > > > > > > field-status = status > > > > > > > field-boxc-id = boxc > > > > > > > ----------- cut here ------------- > > > > > > > > > > > > > > Anytime I send SMS I use HTTP Request like this: > > > > > > > > > > > > > > GET > > > > > > > > > > > > > > > > /sendsms?dlr-mask=31&username=kakek01&password=xxxxx&to=<somenumber>&text=<sometext>&from=<sender>&dlr-url=<somedlr-url> > > > > > > > HTTP/1.0 > > > > > > > > > > > > > > However, delivery report comes to me as standard incoming SMS > and > > > hit my > > > > > > > default SMS handler like this like this > > > > > > > > > > > > > > GET > > > > > > > > > > > > > > > > /smshandler/reg_sms_bulksms.php?msisdn=0&sms=id%3A1267572+sub%3A000+dlvrd%3A0 > > > > > > > > > > > > > > > > 00+submit+date%3A0708110516+done+date%3A0708110516+stat%3ADELIVRD+err%3A00+text%3AGW290+MCC%3D505+MNC%3D3+BillingMNC%3D3&trx_ > > > > > > > date=2007-08-11+18:02:34&dest=<someMSISDN> > HTTP/1.1 > > > > > > > > > > > > > > or > > > > > > > > > > > > > > something like this in kannel access > > > > > > > msg:134: id:1322900 sub:000 dlvrd:000 submit date:0708110218 > done > > > > > > > date:0708110218 stat:DELIVRD err:00 text:GW290 MCC=505 MNC=11 > > > > > BillingMNC=11 > > > > > > > > > > > > > > My Question is, can I save id 1322900 while doing submit_sm so > one > > > day > > > > > SMSC > > > > > > > give me DLR using standard incoming sms > > > > > > > I could detect this DLR and process to update my SMS data? > > > > > > > > > > > > > > Or any other way for this case? > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Regards, > > > > > > > > > > > > > > Ady Wicaksono > > > > > > > Email: > > > > > > > ady.wicaksono at gmail.com > > > > > > > http://adywicaksono.wordpress.com/ > > > > > > > > > > > > > > > > > > -- > > > > > > Alejandro Guerrieri > > > > > > Magicom > > > > > > http://www.magicom-bcn.net/ > > > > > > LinkedIn: http://www.linkedin.com/in/aguerrieri > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Regards, > > > > > > > > > > Ady Wicaksono > > > > > Email: > > > > > ady.wicaksono at gmail.com > > > > > http://adywicaksono.wordpress.com/ > > > > > > > > > > > > -- > > > > Alejandro Guerrieri > > > > Magicom > > > > http://www.magicom-bcn.net/ > > > > LinkedIn: http://www.linkedin.com/in/aguerrieri > > > > > > > > > > > > > > > > > > > > -- > > > > > > Regards, > > > > > > Ady Wicaksono > > > Email: > > > ady.wicaksono at gmail.com > > > http://adywicaksono.wordpress.com/ > > > > > > -- > > Alejandro Guerrieri > > Magicom > > http://www.magicom-bcn.net/ > > LinkedIn: http://www.linkedin.com/in/aguerrieri > > > > > > > > -- > > Regards, > > Ady Wicaksono > Email: > ady.wicaksono at gmail.com > http://adywicaksono.wordpress.com/ -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri
