Hello Alejandro and all, i have come across this before, the same problem, strings terminating after a NULL character. From what i have found out, the strings are handled correctly as octstr in the code, but the actual mysql insert does not encode the payload to a binary insert and hence the 00 clipping occurs within the mysql driver.
There is no easy fix because the representation of data needs to be converted to a binary safe syntax for the mysql insert. That's where i stopped, cause i am not that firm in c, and used the method of repeating the port in the UDH sequence like described earlier. a pointer for fixing this in sqlbox would be http://dev.mysql.com/doc/refman/5.0/en/hexadecimal-values.html Thursday, May 29, 2008, 4:38:48 PM, you wrote: The hex values as a string? Could you paste a sample query of what you're doing? Regards, Alejandro On Thu, May 29, 2008 at 6:42 AM, Tushar <[EMAIL PROTECTED]> wrote: I tried with sqlbox-standalone also but the same thing happened again. Can u tell me in what form I should submit the udhdata and msgdata into database. Currently I am inserting the hex values only. Thanks and regards, Tushar Chauhan From: Alejandro Guerrieri [mailto:[EMAIL PROTECTED] Sent: Thursday, May 29, 2008 10:52 AM To: users@kannel.org Subject: Re: problem with sqlbox Well, looks a lot like a bug. Maybe the string is treated as a null terminated C string instead of an Octstr somewhere on sqlbox code. That would explain that behaviour, but more testings are needed to confirm that. Furthermore, the sqlbox patch is quite outdated and deprecated, you should try running the sqlbox-standalone package along with latest stable kannel (the cvs branch is quite stable as well). sqlbox-standalone works independently from kannel, so no patching is necessary on kannel's tree. Maybe the problem was fixed on newer releases, try updating and if the problem persists then let us know. Regards, Alejandro On Thu, May 29, 2008 at 2:15 AM, Tushar <[EMAIL PROTECTED]> wrote: I have already done that …. After putting 1581 instead of 0000 I got the UDH right but the message data part was still trimmed after "00" as I have shown below. I need to send the full message. Please help me with this/ Thanks and regards, Tushar Chauhan From: Alejandro Guerrieri [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2008 8:46 PM To: users@kannel.org Subject: Re: problem with sqlbox Try putting 1581, instead of 0000, should work... Regards, Alejandro On Wed, May 28, 2008 at 11:34 AM, Tushar <[EMAIL PROTECTED]> wrote: No my sms is not exceeding 160 chars. The size of the message pasted below is also 91. so I don't think there is any problem with the size of the message. Moreover the same message is getting delivered when I send it thru' the http url of kannel. Tushar Chauhan From: Kashif Ali Bukhari [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2008 6:41 PM To: Tushar Cc: users@kannel.org Subject: Re: problem with sqlbox may be you sms is exceeding 160 characters and telco doesn't support concatenation . Tushar wrote: Hello all, I am running kannel version 1.4.1 with sqlbox patch and TLV patch. I am having following problem with sqlbox : Whenever I am trying to submit monotone or any other binary message with UDH, e.g, let us consider a monotone with UDH = 06050415810000 And DATA= 024A3A515195C9940400791CC512495412424E314492550490938C512495412424E314488498498518520552560520498498498518520552560520498939039038C512612814494812824E20E4144985205D855A51A55849854A00 Now whenever I am trying to send this message through sqlbox. I am getting nothing on my phone when I checked the logs I found out that Sqlbox sent the message with following details: UDH= 0605041581 And DATA = 024A3A515195C99404 I don't know what's happening but I think sqlbox is removing everything after it gets "00" in UDH or data part. If somebody got the same problem, Please help me to fix this. Thanks and regards, Tushar Chauhan -- Best regards, Thomas mailto:[EMAIL PROTECTED]
