Re: Problem with sqlbox and utf8
thanks for your reply spameden, but coding=2 didn't helped me. On 12.08.2013 18:55, spameden wrote: use coding=2 2013/8/12 dorin dorinafte...@mail.ru mailto:dorinafte...@mail.ru Hello! Have such trouble, I can't send utf8 data via sqlbox. Every time it spoils the data. On sent_sms and cellphone arrives question mark. Config file contains: . system-type = alt-charset = ucs-2 If needs more information data please tell me. Please help me!
Re: Problem with sqlbox and utf8
i think in addition to coding=2, you also need to change the Mysql table charset ALTER TABLE `send_sms` CHANGE `msgdata` `msgdata` TEXT CHARACTER SET utf8 COLLATE utf8_estonian_ci NULL , ROW_FORMAT=DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci ; ALTER TABLE `sent_sms` CHANGE `msgdata` `msgdata` TEXT CHARACTER SET utf8 COLLATE utf8_estonian_ci NULL , ROW_FORMAT=DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci ; in above query i have changed only `msgdata` field, i think batter you also change the following fields as well. these can also receive the unicoded data if you are getting messges from SMPP (openSMPP) `sender` `dlr_url``boxc_id` `meta_data` specially the Sender, in case of SMPP On Tue, Aug 13, 2013 at 9:22 AM, dorin dorinafte...@mail.ru wrote: thanks for your reply spameden, but coding=2 didn't helped me. On 12.08.2013 18:55, spameden wrote: use coding=2 2013/8/12 dorin dorinafte...@mail.ru Hello! Have such trouble, I can't send utf8 data via sqlbox. Every time it spoils the data. On sent_sms and cellphone arrives question mark. Config file contains: . system-type = alt-charset = ucs-2 If needs more information data please tell me. Please help me!
Re: Problem with sqlbox and utf8
Thanks a lot! Your solution helps me. Now I have another problem. When I send one SMS via sqlbox I receive good DLR from SMSC, but if I send 2 SMS via sqlbox (I made 2 inserts in the table). No DLR comes back. What can be the problem? Kannel accepts many dlr-url in a time? For ex. http://134.0.113.138/dlr.php?smsc=%ifrom=%Pto=%pdlr-mask=%dsmsID=1 http://134.0.113.138/dlr.php?smsc=%ifrom=%Pto=%pdlr-mask=%dsmsID=2 Or maybe there another solution for sending a list of SMS? On 13.08.2013 12:32, Ali Kashif wrote: i think in addition to coding=2, you also need to change the Mysql table charset ALTER TABLE `send_sms` CHANGE `msgdata` `msgdata` TEXT CHARACTER SET utf8 COLLATE utf8_estonian_ci NULL , ROW_FORMAT=DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci ; ALTER TABLE `sent_sms` CHANGE `msgdata` `msgdata` TEXT CHARACTER SET utf8 COLLATE utf8_estonian_ci NULL , ROW_FORMAT=DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci ; in above query i have changed only `msgdata` field, i think batter you also change the following fields as well. these can also receive the unicoded data if you are getting messges from SMPP (openSMPP) `sender` `dlr_url``boxc_id` `meta_data` specially the Sender, in case of SMPP On Tue, Aug 13, 2013 at 9:22 AM, dorin dorinafte...@mail.ru mailto:dorinafte...@mail.ru wrote: thanks for your reply spameden, but coding=2 didn't helped me. On 12.08.2013 18:55, spameden wrote: use coding=2 2013/8/12 dorin dorinafte...@mail.ru mailto:dorinafte...@mail.ru Hello! Have such trouble, I can't send utf8 data via sqlbox. Every time it spoils the data. On sent_sms and cellphone arrives question mark. Config file contains: . system-type = alt-charset = ucs-2 If needs more information data please tell me. Please help me!
Re: Problem with sqlbox and utf8
Want to notice that I do not properly explained the latest post, If I send 2 SMS via sqlbox then DLR comes back only for the last sent SMS. On 13.08.2013 14:17, dorin wrote: Thanks a lot! Your solution helps me. Now I have another problem. When I send one SMS via sqlbox I receive good DLR from SMSC, but if I send 2 SMS via sqlbox (I made 2 inserts in the table). No DLR comes back. What can be the problem? Kannel accepts many dlr-url in a time? For ex. http://134.0.113.138/dlr.php?smsc=%ifrom=%Pto=%pdlr-mask=%dsmsID=1 http://134.0.113.138/dlr.php?smsc=%ifrom=%Pto=%pdlr-mask=%dsmsID=2 Or maybe there another solution for sending a list of SMS? On 13.08.2013 12:32, Ali Kashif wrote: i think in addition to coding=2, you also need to change the Mysql table charset ALTER TABLE `send_sms` CHANGE `msgdata` `msgdata` TEXT CHARACTER SET utf8 COLLATE utf8_estonian_ci NULL , ROW_FORMAT=DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci ; ALTER TABLE `sent_sms` CHANGE `msgdata` `msgdata` TEXT CHARACTER SET utf8 COLLATE utf8_estonian_ci NULL , ROW_FORMAT=DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci ; in above query i have changed only `msgdata` field, i think batter you also change the following fields as well. these can also receive the unicoded data if you are getting messges from SMPP (openSMPP) `sender` `dlr_url``boxc_id` `meta_data` specially the Sender, in case of SMPP On Tue, Aug 13, 2013 at 9:22 AM, dorin dorinafte...@mail.ru mailto:dorinafte...@mail.ru wrote: thanks for your reply spameden, but coding=2 didn't helped me. On 12.08.2013 18:55, spameden wrote: use coding=2 2013/8/12 dorin dorinafte...@mail.ru mailto:dorinafte...@mail.ru Hello! Have such trouble, I can't send utf8 data via sqlbox. Every time it spoils the data. On sent_sms and cellphone arrives question mark. Config file contains: . system-type = alt-charset = ucs-2 If needs more information data please tell me. Please help me!
Message text being trimmed before going to get-url
Hello, I have a problem with a customer sending binary MOs to Kannel. Messages ending with an space (%20), or tabulation, or any whitespace character are being omitted from the %a parameter, as if a trim is being done before the message is sent. Is it the default behavior? Is there any way to make Kannel receive an MO with just one character (space, %20) and this character be forwarded to my listening web service, instead of an empty string? I'm using Kannel 1.5.0, svn-r4863. Thanks in advance, -- Rodrigo Rocco Rubim
DLR issue
Hello! who can help me? I configured: bearerbox-smsbox-sqlbox. That works fine if I send one message via sqlbox. But if I send more messages at once, I receive DLR status only for the last sent message. For example I write into send_sms table one sms - I recieve a good DLR status. If I write into send_sms table 10 sms (10 rows) - I recieve a good DLR only for 10th. Unfortunately my SMSC don't support submit_sm_multi. At the moment I see only one solution: to send next SMS after previous returned DRL, but this is not a deal. I write a lot of posts but I can't get the solution of this problem.
Re: DLR issue
Also, are you sending to the same phone number? Many carriers have velocity check that would just ignore multiple messages to the same phone number if sent close together. Regards, Alex On Tue, Aug 13, 2013 at 11:18 AM, Rene Kluwen rene.klu...@chimit.nl wrote: Check your sent_sms logs. Do you get DLR rows for each of the sent sms? And smsbox doesn't forward them to your webserver? Or do you _not_ get any dlr entries, not even in sent_sms? == Rene -Original Message- From: users [mailto:users-boun...@kannel.org] On Behalf Of dorin Sent: dinsdag 13 augustus 2013 17:10 To: users@kannel.org Subject: DLR issue Hello! who can help me? I configured: bearerbox-smsbox-sqlbox. That works fine if I send one message via sqlbox. But if I send more messages at once, I receive DLR status only for the last sent message. For example I write into send_sms table one sms - I recieve a good DLR status. If I write into send_sms table 10 sms (10 rows) - I recieve a good DLR only for 10th. Unfortunately my SMSC don't support submit_sm_multi. At the moment I see only one solution: to send next SMS after previous returned DRL, but this is not a deal. I write a lot of posts but I can't get the solution of this problem.
Re: Message text being trimmed before going to get-url
Nevermind...I was using %a, and the desired behavior is achieved using %b, as seen in the User Guide: http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN3887 Maybe the description for the %a parameter could include the information of the trim being done (not just whitespaces being squeezed to one, but also whitespaces at both ends being completely removed). Greetings, -- Rodrigo Rocco Rubim On Tue, Aug 13, 2013 at 11:03 AM, Rodrigo Rocco rodri...@gmail.com wrote: Hello, I have a problem with a customer sending binary MOs to Kannel. Messages ending with an space (%20), or tabulation, or any whitespace character are being omitted from the %a parameter, as if a trim is being done before the message is sent. Is it the default behavior? Is there any way to make Kannel receive an MO with just one character (space, %20) and this character be forwarded to my listening web service, instead of an empty string? I'm using Kannel 1.5.0, svn-r4863. Thanks in advance, -- Rodrigo Rocco Rubim
RE: DLR issue
It could be because Kannel is load balancing between your boxes. Give both sqlbox and your smsbox a different smsbox-id. Then, when inserting a message, set the boxc_id field to your smsbox-id. == Rene From: Alejandro Guerrieri [mailto:alejandro.guerri...@gmail.com] Sent: dinsdag 13 augustus 2013 18:23 To: Rene Kluwen Cc: dorin; users@kannel.org Subject: Re: DLR issue Also, are you sending to the same phone number? Many carriers have velocity check that would just ignore multiple messages to the same phone number if sent close together. Regards, Alex On Tue, Aug 13, 2013 at 11:18 AM, Rene Kluwen rene.klu...@chimit.nl wrote: Check your sent_sms logs. Do you get DLR rows for each of the sent sms? And smsbox doesn't forward them to your webserver? Or do you _not_ get any dlr entries, not even in sent_sms? == Rene -Original Message- From: users [mailto:users-boun...@kannel.org] On Behalf Of dorin Sent: dinsdag 13 augustus 2013 17:10 To: users@kannel.org Subject: DLR issue Hello! who can help me? I configured: bearerbox-smsbox-sqlbox. That works fine if I send one message via sqlbox. But if I send more messages at once, I receive DLR status only for the last sent message. For example I write into send_sms table one sms - I recieve a good DLR status. If I write into send_sms table 10 sms (10 rows) - I recieve a good DLR only for 10th. Unfortunately my SMSC don't support submit_sm_multi. At the moment I see only one solution: to send next SMS after previous returned DRL, but this is not a deal. I write a lot of posts but I can't get the solution of this problem.
