Re: SMS lifetime
I called SMSC support they have such time. I have read SMPP documentation there expects absolute and relative time format YYMMDDhhmmsstnnp I write validity parameter like it's write in the documentation / ...it should only try to send the message for this many *minutes*.../ validity = 5; (I mean sqlbox parameter that's written in send_sms table) then I try smpp absolute format to send: validity = 140408123011000 and relative format: validity = 050 As result, all time I get +30, +40 years later. I think there you have bugs. some suspicions In code you use time stamp, but year 14 in timestamp is 1914 and not 2014. On 2 aprilie 2014 19:41, Milan P. Stanic wrote: On Wed, 2014-04-02 at 19:01, dorin wrote: I would appreciate any help or maybe some ideas. Or my problem is unsolvable? On 2014-03-31 18:16, dorin wrote: Hello all! I want to configure SMS validity under sqlbox. As I read in documentation I must set parameter validity with desired minutes. in my case I have validity = 5 but on the SMSC arives 1032139564 minutes insted of 5. what I missed? It is absolute time in UTC, IIRC. Read the specification about SMPP and Kannel documentation.
Re: SMS lifetime
On Tue, 2014-04-08 at 10:29, Dorin wrote: I called SMSC support they have such time. I have read SMPP documentation there expects absolute and relative time format YYMMDDhhmmsstnnp I write validity parameter like it's write in the documentation / ...it should only try to send the message for this many *minutes*.../ validity = 5; (I mean sqlbox parameter that's written in send_sms table) then I try smpp absolute format to send: validity = 140408123011000 and relative format: validity = 050 As result, all time I get +30, +40 years later. I don't know how sqlbox handles validity parameter (never used or tested sqlbox) but Kannel use minutes as the parameter to validity option in HTTP interface (cgi-bin/sendsms) at least. Kannel then calculates these minutes to the SMPP valid format (I can't remember is it absolute or relative) and set it packet for the SMSC. I think there you have bugs. Well, could be. But you should tell which version of Kannel and sqlbox you use, how they are built. IIRC validity calculation is changed somewhat at the beginning of the 2013. some suspicions In code you use time stamp, but year 14 in timestamp is 1914 and not 2014. I think this is a bug in SMPP specification because year is defined as two number (0 - 99). But, if relative time used then the problem is mitigated (though not solved). On 2 aprilie 2014 19:41, Milan P. Stanic wrote: On Wed, 2014-04-02 at 19:01, dorin wrote: I would appreciate any help or maybe some ideas. Or my problem is unsolvable? On 2014-03-31 18:16, dorin wrote: Hello all! I want to configure SMS validity under sqlbox. As I read in documentation I must set parameter validity with desired minutes. in my case I have validity = 5 but on the SMSC arives 1032139564 minutes insted of 5. what I missed? It is absolute time in UTC, IIRC. Read the specification about SMPP and Kannel documentation. -- Kind regards, Milan -- Arvanta,http://www.arvanta.net Please do not send me e-mail containing HTML code or documents in proprietary format (word, excel, pps and so on)
Re: SMS lifetime
2014-04-08 11:29 GMT+04:00 Dorin dorinafte...@mail.ru: I called SMSC support they have such time. I have read SMPP documentation there expects absolute and relative time format YYMMDDhhmmsstnnp I write validity parameter like it's write in the documentation * ...it should only try to send the message for this many minutes...* validity = 5; (I mean sqlbox parameter that's written in send_sms table) then I try smpp absolute format to send: validity = 140408123011000 and relative format: validity = 050 As result, all time I get +30, +40 years later. I think there you have bugs. some suspicions In code you use time stamp, but year 14 in timestamp is 1914 and not 2014. Post detailed bugreport on http://redmine.kannel.org with logs included and version of the kannel you've used. Or send bugreport to de...@kannel.org. On 2 aprilie 2014 19:41, Milan P. Stanic wrote: On Wed, 2014-04-02 at 19:01, dorin wrote: I would appreciate any help or maybe some ideas. Or my problem is unsolvable? On 2014-03-31 18:16, dorin wrote: Hello all! I want to configure SMS validity under sqlbox. As I read in documentation I must set parameter validity with desired minutes. in my case I have validity = 5 but on the SMSC arives 1032139564 minutes insted of 5. what I missed? It is absolute time in UTC, IIRC. Read the specification about SMPP and Kannel documentation.
Re: SMS lifetime
I would appreciate any help or maybe some ideas. Or my problem is unsolvable? On 2014-03-31 18:16, dorin wrote: Hello all! I want to configure SMS validity under sqlbox. As I read in documentation I must set parameter validity with desired minutes. in my case I have validity = 5 but on the SMSC arives 1032139564 minutes insted of 5. what I missed? p.s. SMSC support told me the same time zone as my server.
Re: SMS lifetime
Sent from Yahoo Mail on Android
Re: SMS lifetime
On Wed, 2014-04-02 at 19:01, dorin wrote: I would appreciate any help or maybe some ideas. Or my problem is unsolvable? On 2014-03-31 18:16, dorin wrote: Hello all! I want to configure SMS validity under sqlbox. As I read in documentation I must set parameter validity with desired minutes. in my case I have validity = 5 but on the SMSC arives 1032139564 minutes insted of 5. what I missed? It is absolute time in UTC, IIRC. Read the specification about SMPP and Kannel documentation. -- Kind regards, Milan -- Arvanta,http://www.arvanta.net Please do not send me e-mail containing HTML code or documents in proprietary format (word, excel, pps and so on)
Re: SMS lifetime
2014-03-31 19:16 GMT+04:00 dorin dorinafte...@mail.ru: Hello all! I want to configure SMS validity under sqlbox. As I read in documentation I must set parameter validity with desired minutes. in my case I have validity = 5 but on the SMSC arives 1032139564 minutes insted of 5. hello. check user-guide, there is a column called validity, you can specify in minutes how much time MT should be valid for. most likely you've got time out of sync with your SMPP provider, contact them and try to resolve this. it works fine. what I missed? p.s. SMSC support told me the same time zone as my server.
