**>From: "Hillel Bilman" <[EMAIL PROTECTED]> **>To: "Davy Chan" <[EMAIL PROTECTED]> **>Subject: RE: receiving the messageid - another approach until a DLR parameter is introduced. **>Date: Sun, 13 Feb 2005 11:06:25 +0200 **> **>Dear Davy, **> **>This is great, it will help many of us. **> **>How do you envisage the statusbox working: **>It would be beter if it called the drl-url with the messageid for the smsid, **>rather than we would have to call it. We can then do a simple update on the **>database using the smsid as the unique key and fill in the messageid.
Ah hah! Didn't read too closely in to my reply ;-)! [ ... lines deleted ... ] **>I've got 30% of it done (hacking all the dlr_xxx.[hc] to add another **>field for the sms.id, updating the urltrans_get_pattern() to support **>%II for the 'ts' field content expansion, designing the interface **>and protcol for the statusbox...still looking for a better name). **>I've still got to finish coding my statusbox. And, the statusbox **>will be very preliminary. I'll add in support for allow/deny-ip **>and username/password later. I am planning to add another Kannel escape code (%II) that will force the smsbox to contact my statusbox to get the sms.id<->ts (or message-id for SMPP) mapping. See ya... d.c.
