Thanks, for the answer Ben. So in dlr part, if the sms mt takes some time I could see it in the mysql table. But how can I save the sms mt transaction id permanently for later statistics, transaction conciliations with the operators, etc ...?
Regards, Rodrigo --- Ben Suffolk <[EMAIL PROTECTED]> escribió: > > So I've read the docs but I'm not sure about: > > a) how I know mysql-dlr system is really working. > As docs indicates > > I've > > created the groups involved, dlr-storage is mysql, > but I've never > > seen any record > > in the mysql table. > > Well you could turn your phone off, then send a > message to yourself. > Then look in the table. You should see the entry. > Turn your phone > back on, receive the sms and then the entry should > no longer be in > the table. This is of course providing you have > turned on DLR when > sending the message. You need to specify a dlr-url > and a dlr-mask. If > you set the masj to 31 you will get all possible > DLRs. If things are > going well you should see 2 DLRs with status of 8 > (submitted to smsc) > and 1 (delivered to handset) > > > b) How can I manage the difference between a SMS > sent by user at > > any time and a reply from a user to a SMS our > server sent him/her > > before? > > This is down to your application, kannel can not > help you here. You > need to hold some internal state so you know if your > expecting a > reply. Of course you may want o add some > intelligence into it to make > sure you you don't still treat it as a reply in 2 > weeks time, or > maybe looking t the text to see if its a new keyword > for your app maybe. > > Ben > > __________________________________________________ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! Regístrate ya - http://correo.espanol.yahoo.com/
