not on metadata.. i mean adding a new table `field` to both send_sms and sent_sms
-- Regards Kenny On Mon, Nov 29, 2010 at 8:08 PM, Alejandro Guerrieri < alejandro.guerri...@gmail.com> wrote: > on meta-data? Yes indeed. > > Regards, > > Alex > > > On Mon, Nov 29, 2010 at 8:07 PM, Kenny <ken.bell...@gmail.com> wrote: > >> Hi Alex, >> >> If a custom field is included send_sms, would the value be moved to >> sent_sms ? >> >> -- >> Regards >> Kenny >> >> >> >> >> On Thu, Nov 18, 2010 at 1:52 PM, Alejandro Guerrieri < >> alejandro.guerri...@gmail.com> wrote: >> >>> You should add an arbitrary id to your dlr-url, that's the usual way to >>> do it. >>> >>> Hope it helps. >>> >>> Alex >>> >>> >>> On Thu, Nov 18, 2010 at 11:43 AM, James E <jam...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> Thanks for your replies. >>>> >>>> Is there a way when inserting into the Send_sms table, to match it to >>>> the DLR in the sent_sms? >>>> >>>> At the moment, I see no linking between the MT and DLR in the sent_sms >>>> table. >>>> >>>> Regards, >>>> J >>>> >>>> >>>> On Thu, Nov 18, 2010 at 5:14 PM, Alejandro Guerrieri < >>>> alejandro.guerri...@gmail.com> wrote: >>>> >>>>> James, >>>>> >>>>> No, it doesn't work like that. The DLR message actually comes from the >>>>> carrier, so it'll insert only the information from that message. You'll >>>>> get >>>>> your BINFO on the sent_sms copy of the message you've sent, but not on the >>>>> DLR's coming from the carrier. You could, however, pass the value you're >>>>> storing on the BINFO as a parameter on the dlr-url, and that way you'll be >>>>> able to get it when kannel hits the dlr-url. >>>>> >>>>> Hope it helps, >>>>> >>>>> Alex >>>>> >>>>> >>>>> On Thu, Nov 18, 2010 at 7:10 AM, James E <jam...@gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I am just wondering, if I enter BINFO into the send_sms table, >>>>>> shouldnt it be carried and inserted into the sent_sms table as well in >>>>>> the >>>>>> DLR info? >>>>>> >>>>>> In my attempts it isnt doing this. >>>>>> >>>>>> Regards, >>>>>> J >>>>>> >>>>> >>>>> >>>> >>> >> >
