Re: Kannel ignoring sms-resend-retry
Hi, Thanks guys for help, Konstantin your right I note that this problem happend with concatenated SMS only, I tried to send 1 sms to the same users and I did not get the connection stuck. I will provide the logs today for the bug report. but is there temporary solution for this issue? Regards, Hafez 2010/1/18 Nikos Balkanas nbalka...@gmail.com Hi, Actually 2 SMS keep looping. The one to xxx6855 is standalone, the other to xxx4220 has 3 parts. The log size is not sufficient to show if it exceeds the sms-resend-retry = 5 limit (5x for xxx6855, 4.3 for xxx4220), but certainly the sms-resend-freq = 1200 is violated. Since it is a reported bug, it needs to be looked after in the code. @Hafez: Could you please supplement the bug report by Konstantin, making sure your logs are longer than sms-resend-retry = 5 if you want to demonstrate infinite looping (or reduce your retry limit). BR, Nikos - Original Message - *From:* Konstantin Vayner konstan...@appcell.net *To:* Nikos Balkanas nbalka...@gmail.com ; hafez ahmadhafezad...@gmail.com *Cc:* users users@kannel.org *Sent:* Monday, January 18, 2010 2:59 AM *Subject:* Re: Kannel ignoring sms-resend-retry Hi guys, Actually, this thing looks a lot like the problem i had recently. The brief is like the following: 1) a *concatenated* message is being sent (am i right here, Hafez? i think yours are concatenated because i see pdu size 140 in all the samples i've seen in your log...) 2) one or more parts of the message fail with *temporary* error 3) the link is still alive (e.g. remote smsc throws temporary error - in your case Message Queue Full, in mine it was System Error) these 3 together lead to *infinite* retry without delay at all, disobeying both sms-resend-freq and sms-resend-retry (tested on 1.4.1 , 1.4.3 and cvs) see this bugreport: http://redmine.kannel.org/issues/show/529 Regards, Β Konstantin 2010/1/18 Nikos Balkanas nbalka...@gmail.com Hi, Β Actually, kannel obeys strictly the sms-resend-retry = 5 you specified. It will retry 5 times to resend the SMS before aborting. You seem to confuse throttling with max-pending-submits. Please read user guide on that. Β I imagineΒ that your problem is with sms-resend-freq = 1200, and why it resends the SMS every 1 instead of waiting 1200. I would have to check the code for that. Β Meanwhile, comment out the wait-ack = 1, it doesn't make sense in your setup and the default value is better. Β BR, NikosΒ - Original Message - *From:* hafez ahmad hafezad...@gmail.com *To:* Nikos Balkanas nbalka...@gmail.com *Cc:* users@kannel.org *Sent:* Sunday, January 17, 2010 4:22 PM *Subject:* Re: Kannel ignoring sms-resend-retry Dear Nikos, Thanks for your kind feedback. please find the attached log and the config below: group = core admin-port = 14000 smsbox-port = 14005 admin-password = status-password = admin-allow-ip = localhost log-file = /logs/kannel.log log-level = 0 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 dlr-storage = internal sms-resend-freq = 1200 sms-resend-retry = 5 group = smsc smsc = smpp smsc-id = MYSMPP host = XXX.XXX.XXX.XXX port = x transceiver-mode = 1 smsc-username = *** smsc-password = system-type = *** allowed-smsc-id = MYSMPP interface-version = 34 address-range = 808080 max-pending-submits = 1 reconnect-delay = 30 source-addr-ton = 5 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 bind-addr-ton = 1 bind-addr-npi = 1 wait-ack = 1 wait-ack-expire = 0x02 msg-id-type = 0x00 log-file = /logs/808080.log log-level = 0 thanks and Regards, Hafez 2010/1/17 Nikos Balkanas nbalka...@gmail.com Hi, Β Please post detailed BB logs showing the problem and configuration. Β BR, Nikos - Original Message - *From:* hafez ahmad hafezad...@gmail.com *To:* users@kannel.org *Sent:* Sunday, January 17, 2010 10:55 AM *Subject:* Kannel ignoring sms-resend-retry Dears, I the following error: Β SMSC returned error code 0x0014 (Message Queue Full) in response to submit_sm As I know that errorΒ happenedΒ eitherΒ I am sending SMS more than the operator allowed me Β - (Β alreadyΒ I am using max-pending-submit = 1) ORΒ there are some users have full sms queue in the SMSC. I contact my operator and he found the some users haveΒ Β full sms queue , I set the followingΒ sms-resend-freq = 1200 sms-resend-retry = 5 wait-ack = 1Β wait-ack-expire = 0x02 but the kannelΒ ignoringΒ theΒ sms-resend-retry and stillΒ tryingΒ to send it again. Please Any Ideas, how can I solve this problem. Regards, Hafez -- Hafez A.Ahmad Amman-Jordan mobile: 962-795708728 http://blog.hafezadnan.com -- Hafez A.Ahmad Amman-Jordan mobile: 962-795708728 http://blog.hafezadnan.com
Re: Kannel ignoring sms-resend-retry
Hi Hafez, You have several options for workaround: 1) disable concatenation (its the most simple, and most clean solution, though of course it limits you very much) 2) make all temporary errors permanent. to do that you will need to modify function smpp_status_to_smscconn_failure_reason in gw/smsc/smsc_smpp.c This will make Kannel consider any error as permanent and drop a message without retrying. However, chances are you will lose messages with this so your application will have to deal with it... 3) modify functions handle_split and bb_smscconn_send_failed in gw/bb_smscconn.c - there (in handle_split) is the reason of this behavior. I have a simple patch for this (attaching), however you should know that this patch might result in some of the messages (among those concatenated messages that originally fail) be broken when delivered to target - depending on your configuration. It works for me with my configuration because (a) all smscs in my setup have explicit smsc-id's (which apparently isnt required by kannel), and (b) all of smscs in my config allow only themselves (allow-smsc-id = value of smsc-id) What the patch actually does is throws a *part* that failed back into main kannel queue - so if your gateway can do rerouting of messages between different smscs, this may result in parts of same message be routed via different smscs , in which case the message will not be reconstructed by the handset... We had a brief discussion in devel list about what is needed for the real solution, but i still had no time to look deeper into it, neither had any of the developers i guess (my bugreport is still open ;) ) Regards, Konstantin 2010/1/18 hafez ahmad hafezad...@gmail.com Hi, Thanks guys for help, Konstantin your right I note that this problem happend with concatenated SMS only, I tried to send 1 sms to the same users and I did not get the connection stuck. I will provide the logs today for the bug report. but is there temporary solution for this issue? Regards, Hafez 2010/1/18 Nikos Balkanas nbalka...@gmail.com Hi, Actually 2 SMS keep looping. The one to xxx6855 is standalone, the other to xxx4220 has 3 parts. The log size is not sufficient to show if it exceeds the sms-resend-retry = 5 limit (5x for xxx6855, 4.3 for xxx4220), but certainly the sms-resend-freq = 1200 is violated. Since it is a reported bug, it needs to be looked after in the code. @Hafez: Could you please supplement the bug report by Konstantin, making sure your logs are longer than sms-resend-retry = 5 if you want to demonstrate infinite looping (or reduce your retry limit). BR, Nikos - Original Message - *From:* Konstantin Vayner konstan...@appcell.net *To:* Nikos Balkanas nbalka...@gmail.com ; hafez ahmadhafezad...@gmail.com *Cc:* users users@kannel.org *Sent:* Monday, January 18, 2010 2:59 AM *Subject:* Re: Kannel ignoring sms-resend-retry Hi guys, Actually, this thing looks a lot like the problem i had recently. The brief is like the following: 1) a *concatenated* message is being sent (am i right here, Hafez? i think yours are concatenated because i see pdu size 140 in all the samples i've seen in your log...) 2) one or more parts of the message fail with *temporary* error 3) the link is still alive (e.g. remote smsc throws temporary error - in your case Message Queue Full, in mine it was System Error) these 3 together lead to *infinite* retry without delay at all, disobeying both sms-resend-freq and sms-resend-retry (tested on 1.4.1 , 1.4.3 and cvs) see this bugreport: http://redmine.kannel.org/issues/show/529 Regards, Β Konstantin 2010/1/18 Nikos Balkanas nbalka...@gmail.com Hi, Β Actually, kannel obeys strictly the sms-resend-retry = 5 you specified. It will retry 5 times to resend the SMS before aborting. You seem to confuse throttling with max-pending-submits. Please read user guide on that. Β I imagineΒ that your problem is with sms-resend-freq = 1200, and why it resends the SMS every 1 instead of waiting 1200. I would have to check the code for that. Β Meanwhile, comment out the wait-ack = 1, it doesn't make sense in your setup and the default value is better. Β BR, NikosΒ - Original Message - *From:* hafez ahmad hafezad...@gmail.com *To:* Nikos Balkanas nbalka...@gmail.com *Cc:* users@kannel.org *Sent:* Sunday, January 17, 2010 4:22 PM *Subject:* Re: Kannel ignoring sms-resend-retry Dear Nikos, Thanks for your kind feedback. please find the attached log and the config below: group = core admin-port = 14000 smsbox-port = 14005 admin-password = status-password = admin-allow-ip = localhost log-file = /logs/kannel.log log-level = 0 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 dlr-storage = internal sms-resend-freq = 1200 sms-resend-retry = 5 group = smsc smsc = smpp smsc-id = MYSMPP host = XXX.XXX.XXX.XXX port = x transceiver-mode = 1
RE: MO Concatenation problem
Hi Alex, I am still confuse with MO kannel depending in sar* values , i have configured all parameters and as you can seen below I am still getting the messages divided, attached log file on how I am receiving the message from operator , please take a look and advise if I am doing anything in wrong way ? 2010-01-18 23:02:25 SMS HTTP-request sender:+966569567406 request: '-- 113771' url: 'http://192.168.00.00:9876/store.asp?msisdn=%2B966569567406sms=%E2%80%8B%E2%80%8B%E2%80%8B%E2%80%8B%D8%AE%D8%B7%D9%8A%D8%A8+%D8%AC%D9%85%D8%B9%D9%87+%D8%AA%D8%A8%D8%AE%D8%B1+%D8%A8%D8%AD%D8%B4%D9%8A%D8%B4+%D8%A8%D8%A7%D9%84%D8%BA%D9%84%D8%B7+%D9%88%D8%A8%D8%B9%D8%AF+%D8%A7%D9%84%D8%B5%D9%84%D8%A7%D8%A9+%D8%B1%D8%A7%D8%AD%D9%88+%D9%84%D9%87+%D8%A7%D9%84%D9%86%D8%A7%D8%B3+%D8%A8%D9%8A%D8%AA%D9%87%D9%85+%D9%82%D8%A7%D9%84sc=6423bin=%E2%80%8B%E2%80%8B%E2%80%8B%E2%80%8B%D8%AE%D8%B7%D9%8A%D8%A8+%D8%AC%D9%85%D8%B9%D9%87+%D8%AA%D8%A8%D8%AE%D8%B1+%D8%A8%D8%AD%D8%B4%D9%8A%D8%B4+%D8%A8%D8%A7%D9%84%D8%BA%D9%84%D8%B7+%D9%88%D8%A8%D8%B9%D8%AF+%D8%A7%D9%84%D8%B5%D9%84%D8%A7%D8%A9+%D8%B1%D8%A7%D8%AD%D9%88+%D9%84%D9%87+%D8%A7%D9%84%D9%86%D8%A7%D8%B3+%D8%A8%D9%8A%D8%AA%D9%87%D9%85+%D9%82%D8%A7%D9%84enc=UTF-8enc2=0meta-data=%3Fsmpp%3Fsource_network_type%3D%2501%26sar_msg_ref_num%3D193%26dest_network_type%3D%2501%26sar_total_segments%3D3%26sar_segment_seqnum%3D1%26' reply: 200 ' successful ' 2010-01-18 23:02:25 SMS HTTP-request sender:+966569567406 request: '-- 113772' url: 'http://192.168.00.00:9876/store.asp?msisdn=%2B966569567406sms=%D9%88+%D9%84%D9%87+%D9%82%D9%84%D8%AA+%D8%BA%D8%B2%D9%88%D9%87+%D8%A8%D8%AF%D8%B1+%D8%A8%D8%A7%D9%84%D8%B7%D9%8A%D8%A7%D8%B1%D8%A7%D8%AA+%D9%82%D9%84%D9%86%D8%A7+%D8%B9%D8%A7%D8%AF%D9%8A+%D9%82%D9%84%D8%AA+%D8%B5%D9%84%D8%A7%D8%AD+%D8%A7%D9%84%D8%AF%D9%8A%D9%86+%D9%81%D8%AA%D8%AD+%D8%A7%D9%84%D9%82%D8%AF%D8%B3+%D8%A8%D8%A7%D9%84%D9%83sc=6423bin=%D9%88+%D9%84%D9%87+%D9%82%D9%84%D8%AA+%D8%BA%D8%B2%D9%88%D9%87+%D8%A8%D8%AF%D8%B1+%D8%A8%D8%A7%D9%84%D8%B7%D9%8A%D8%A7%D8%B1%D8%A7%D8%AA+%D9%82%D9%84%D9%86%D8%A7+%D8%B9%D8%A7%D8%AF%D9%8A+%D9%82%D9%84%D8%AA+%D8%B5%D9%84%D8%A7%D8%AD+%D8%A7%D9%84%D8%AF%D9%8A%D9%86+%D9%81%D8%AA%D8%AD+%D8%A7%D9%84%D9%82%D8%AF%D8%B3+%D8%A8%D8%A7%D9%84%D9%83enc=UTF-8enc2=0meta-data=%3Fsmpp%3Fsource_network_type%3D%2501%26sar_msg_ref_num%3D193%26dest_network_type%3D%2501%26sar_total_segments%3D3%26sar_segment_seqnum%3D2%26' reply: 200 ' successful ' 2010-01-18 23:02:26 SMS HTTP-request sender:+966569567406 request: '-- 113773' url: 'http://192.168.00.00:9876/store.asp?msisdn=%2B966569567406sms=%D9%8A%D9%85%D8%A7%D9%88%D9%8A+%D9%82%D9%84%D9%86%D8%A7+%D9%85%D8%A7%D8%B4%D9%8A+%D8%A7%D9%85%D8%A7+%D9%82%D8%B1%D9%8A%D8%B4+%D8%A8%D8%A7%D8%B9%D8%AA+%D8%A7%D8%A8%D9%88%D8%B3%D9%81%D9%8A%D8%A7%D9%86+%D8%A850+%D9%85%D9%84%D9%8A%D9%88%D9%86+%D9%84%D8%A8%D8%B1%D8%B4%D9%84%D9%88%D9%86%D9%87+%D9%82%D9%88%D9%8A%D9%87sc=6423bin=%D9%8A%D9%85%D8%A7%D9%88%D9%8A+%D9%82%D9%84%D9%86%D8%A7+%D9%85%D8%A7%D8%B4%D9%8A+%D8%A7%D9%85%D8%A7+%D9%82%D8%B1%D9%8A%D8%B4+%D8%A8%D8%A7%D8%B9%D8%AA+%D8%A7%D8%A8%D9%88%D8%B3%D9%81%D9%8A%D8%A7%D9%86+%D8%A850+%D9%85%D9%84%D9%8A%D9%88%D9%86+%D9%84%D8%A8%D8%B1%D8%B4%D9%84%D9%88%D9%86%D9%87+%D9%82%D9%88%D9%8A%D9%87enc=UTF-8enc2=0meta-data=%3Fsmpp%3Fsource_network_type%3D%2501%26sar_msg_ref_num%3D193%26dest_network_type%3D%2501%26sar_total_segments%3D3%26sar_segment_seqnum%3D3%26' reply: 200 ' successful ' Here are TLV Parameters : group = smpp-tlv name = sar_msg_ref_num tag=0x020C #type= octetstring type= integer length = 2 smsc-id = AXIOM3 group = smpp-tlv name = sar_total_segments tag=0x020E #type= octetstring type= integer length = 2 smsc-id = AXIOM3 group = smpp-tlv name = sar_segment_seqnum tag=0x020F #type= octetstring type= integer length = 2 smsc-id = AXIOM3 group = smpp-tlv name = dest_network_type tag=0x0006 type= octetstring length = 2 smsc-id = AXIOM3 group = smpp-tlv name = source_network_type tag=0x000e type= octetstring length = 2 smsc-id = AXIOM3 Appreiate your help. ... Best Regards Date: Sun, 10 Jan 2010 20:41:31 +0100 Subject: Re: MO Concatenation problem From: alejandro.guerri...@gmail.com To: aopa...@hotmail.com CC: users@kannel.org Afaik Kannel cannot handle concatenation based on sar parameters, only UDH-based concatenation. Regards, Alex On Sun, Jan 10, 2010 at 7:48 PM, Abdulraheem Obaisi aopa...@hotmail.com wrote: Hi, I have configured TLV optional parameters like what mention in latest manual and depending on operator instructions but my problem still exist.Kannel still deliver MO concatenate as divided parts, does kannel handle the MO concatenated with sar parameters ? Did MO concatenation work with sar* values so far? ... Best Regards Abdulraheem Ali Obaisi From: aopa...@hotmail.com To: cornejo.alv...@gmail.com Subject: RE: MO Concatenation problem Date: Wed, 6 Jan 2010 18:13:22
Re: MO Concatenation problem
I'm afraid Kannel does't know how to re-assemble based on SAR-* values. Even if you define the TLV's, the logic to re-assemble is missing. Kannel can only re-assemble based on UDH values. Regards, Alex On Mon, Jan 18, 2010 at 8:20 PM, Abdulraheem Obaisi aopa...@hotmail.comwrote: Hi Alex, I am still confuse with MO kannel depending in sar* values , i have configured all parameters and as you can seen below I am still getting the messages divided, attached log file on how I am receiving the message from operator , please take a look and advise if I am doing anything in wrong way ? 2010-01-18 23:02:25 SMS HTTP-request sender:+966569567406 request: '-- 113771' url: ' http://192.168.00.00:9876/store.asp?msisdn=%2B966569567406sms=%E2%80%8B%E2%80%8B%E2%80%8B%E2%80%8B%D8%AE%D8%B7%D9%8A%D8%A8+%D8%AC%D9%85%D8%B9%D9%87+%D8%AA%D8%A8%D8%AE%D8%B1+%D8%A8%D8%AD%D8%B4%D9%8A%D8%B4+%D8%A8%D8%A7%D9%84%D8%BA%D9%84%D8%B7+%D9%88%D8%A8%D8%B9%D8%AF+%D8%A7%D9%84%D8%B5%D9%84%D8%A7%D8%A9+%D8%B1%D8%A7%D8%AD%D9%88+%D9%84%D9%87+%D8%A7%D9%84%D9%86%D8%A7%D8%B3+%D8%A8%D9%8A%D8%AA%D9%87%D9%85+%D9%82%D8%A7%D9%84sc=6423bin=%E2%80%8B%E2%80%8B%E2%80%8B%E2%80%8B%D8%AE%D8%B7%D9%8A%D8%A8+%D8%AC%D9%85%D8%B9%D9%87+%D8%AA%D8%A8%D8%AE%D8%B1+%D8%A8%D8%AD%D8%B4%D9%8A%D8%B4+%D8%A8%D8%A7%D9%84%D8%BA%D9%84%D8%B7+%D9%88%D8%A8%D8%B9%D8%AF+%D8%A7%D9%84%D8%B5%D9%84%D8%A7%D8%A9+%D8%B1%D8%A7%D8%AD%D9%88+%D9%84%D9%87+%D8%A7%D9%84%D9%86%D8%A7%D8%B3+%D8%A8%D9%8A%D8%AA%D9%87%D9%85+%D9%82%D8%A7%D9%84enc=UTF-8enc2=0meta-data=%3Fsmpp%3Fsource_network_type%3D%2501%26sar_msg_ref_num%3D193%26dest_network_type%3D%2501%26sar_total_segments%3D3%26sar_segment_seqnum%3D1%26' reply: 200 ' successful ' 2010-01-18 23:02:25 SMS HTTP-request sender:+966569567406 request: '-- 113772' url: ' http://192.168.00.00:9876/store.asp?msisdn=%2B966569567406sms=%D9%88+%D9%84%D9%87+%D9%82%D9%84%D8%AA+%D8%BA%D8%B2%D9%88%D9%87+%D8%A8%D8%AF%D8%B1+%D8%A8%D8%A7%D9%84%D8%B7%D9%8A%D8%A7%D8%B1%D8%A7%D8%AA+%D9%82%D9%84%D9%86%D8%A7+%D8%B9%D8%A7%D8%AF%D9%8A+%D9%82%D9%84%D8%AA+%D8%B5%D9%84%D8%A7%D8%AD+%D8%A7%D9%84%D8%AF%D9%8A%D9%86+%D9%81%D8%AA%D8%AD+%D8%A7%D9%84%D9%82%D8%AF%D8%B3+%D8%A8%D8%A7%D9%84%D9%83sc=6423bin=%D9%88+%D9%84%D9%87+%D9%82%D9%84%D8%AA+%D8%BA%D8%B2%D9%88%D9%87+%D8%A8%D8%AF%D8%B1+%D8%A8%D8%A7%D9%84%D8%B7%D9%8A%D8%A7%D8%B1%D8%A7%D8%AA+%D9%82%D9%84%D9%86%D8%A7+%D8%B9%D8%A7%D8%AF%D9%8A+%D9%82%D9%84%D8%AA+%D8%B5%D9%84%D8%A7%D8%AD+%D8%A7%D9%84%D8%AF%D9%8A%D9%86+%D9%81%D8%AA%D8%AD+%D8%A7%D9%84%D9%82%D8%AF%D8%B3+%D8%A8%D8%A7%D9%84%D9%83enc=UTF-8enc2=0meta-data=%3Fsmpp%3Fsource_network_type%3D%2501%26sar_msg_ref_num%3D193%26dest_network_type%3D%2501%26sar_total_segments%3D3%26sar_segment_seqnum%3D2%26' reply: 200 ' successful ' 2010-01-18 23:02:26 SMS HTTP-request sender:+966569567406 request: '-- 113773' url: ' http://192.168.00.00:9876/store.asp?msisdn=%2B966569567406sms=%D9%8A%D9%85%D8%A7%D9%88%D9%8A+%D9%82%D9%84%D9%86%D8%A7+%D9%85%D8%A7%D8%B4%D9%8A+%D8%A7%D9%85%D8%A7+%D9%82%D8%B1%D9%8A%D8%B4+%D8%A8%D8%A7%D8%B9%D8%AA+%D8%A7%D8%A8%D9%88%D8%B3%D9%81%D9%8A%D8%A7%D9%86+%D8%A850+%D9%85%D9%84%D9%8A%D9%88%D9%86+%D9%84%D8%A8%D8%B1%D8%B4%D9%84%D9%88%D9%86%D9%87+%D9%82%D9%88%D9%8A%D9%87sc=6423bin=%D9%8A%D9%85%D8%A7%D9%88%D9%8A+%D9%82%D9%84%D9%86%D8%A7+%D9%85%D8%A7%D8%B4%D9%8A+%D8%A7%D9%85%D8%A7+%D9%82%D8%B1%D9%8A%D8%B4+%D8%A8%D8%A7%D8%B9%D8%AA+%D8%A7%D8%A8%D9%88%D8%B3%D9%81%D9%8A%D8%A7%D9%86+%D8%A850+%D9%85%D9%84%D9%8A%D9%88%D9%86+%D9%84%D8%A8%D8%B1%D8%B4%D9%84%D9%88%D9%86%D9%87+%D9%82%D9%88%D9%8A%D9%87enc=UTF-8enc2=0meta-data=%3Fsmpp%3Fsource_network_type%3D%2501%26sar_msg_ref_num%3D193%26dest_network_type%3D%2501%26sar_total_segments%3D3%26sar_segment_seqnum%3D3%26' reply: 200 ' successful ' Here are TLV Parameters : group = smpp-tlv name = sar_msg_ref_num tag=0x020C #type= octetstring type= integer length = 2 smsc-id = AXIOM3 group = smpp-tlv name = sar_total_segments tag=0x020E #type= octetstring type= integer length = 2 smsc-id = AXIOM3 group = smpp-tlv name = sar_segment_seqnum tag=0x020F #type= octetstring type= integer length = 2 smsc-id = AXIOM3 group = smpp-tlv name = dest_network_type tag=0x0006 type= octetstring length = 2 smsc-id = AXIOM3 group = smpp-tlv name = source_network_type tag=0x000e type= octetstring length = 2 smsc-id = AXIOM3 Appreiate your help. ... Best Regards -- Date: Sun, 10 Jan 2010 20:41:31 +0100 Subject: Re: MO Concatenation problem From: alejandro.guerri...@gmail.com To: aopa...@hotmail.com CC: users@kannel.org Afaik Kannel cannot handle concatenation based on sar parameters, only UDH-based concatenation. Regards, Alex On Sun, Jan 10, 2010 at 7:48 PM, Abdulraheem Obaisi aopa...@hotmail.comwrote: Hi, I have configured TLV optional parameters like what mention in latest manual and depending on operator instructions but my problem still exist. Kannel still deliver MO concatenate as divided
BinarySMS as post
Really confused here. Can someone show me an example of how can I send binary data as post to a custom client port through Kannel? -Quintin
Count SMS units for Unicode Messages
Hello Group, How do we count SMS units for a unicode message? Suppose I want to submit Hindi Messages from a PHP script, how do I calculate the number for characters and units consumed? Thanks Jinson Abraham
Re: Count SMS units for Unicode Messages
Hi, Each unicode character counts as 2 regular chars. That is, unicode chars above the regular ASCII (hindu chars for example). BR, Nikos - Original Message - From: Jinson To: users Sent: Tuesday, January 19, 2010 8:39 AM Subject: Count SMS units for Unicode Messages Hello Group, How do we count SMS units for a unicode message? Suppose I want to submit Hindi Messages from a PHP script, how do I calculate the number for characters and units consumed? Thanks Jinson Abraham
Re: Count SMS units for Unicode Messages
So just counting the chars in my incoming hindi text * 2 will get the number characters for sending sms? Im doing the conversion like this in php. 1. get the numeric ascii value of the letter 2. convert it to hex and add a percent (%) Thanks Jinson Abraham MobME Wireless Solutions Pvt. Ltd Cochin +91 4846492646 MobME storms into Emerging 50 Companies in India by Nasscom 2010/1/19 Nikos Balkanas n...@amdtelecom.net Hi, Each unicode character counts as 2 regular chars. That is, unicode chars above the regular ASCII (hindu chars for example). BR, Nikos - Original Message - *From:* Jinson jin...@mobme.in *To:* users users@kannel.org *Sent:* Tuesday, January 19, 2010 8:39 AM *Subject:* Count SMS units for Unicode Messages Hello Group, How do we count SMS units for a unicode message? Suppose I want to submit Hindi Messages from a PHP script, how do I calculate the number for characters and units consumed? Thanks Jinson Abraham
Re: Count SMS units for Unicode Messages
I don't know how you make your php script. But if you convert everything to binary (i.e. hex) just read off the bytes. PS: There is no ASCII value for hindi chars! BR, Nikos - Original Message - From: Jinson To: Nikos Balkanas Cc: users Sent: Tuesday, January 19, 2010 9:10 AM Subject: Re: Count SMS units for Unicode Messages So just counting the chars in my incoming hindi text * 2 will get the number characters for sending sms? Im doing the conversion like this in php. 1. get the numeric ascii value of the letter 2. convert it to hex and add a percent (%) Thanks Jinson Abraham MobME Wireless Solutions Pvt. Ltd Cochin +91 4846492646 MobME storms into Emerging 50 Companies in India by Nasscom 2010/1/19 Nikos Balkanas n...@amdtelecom.net Hi, Each unicode character counts as 2 regular chars. That is, unicode chars above the regular ASCII (hindu chars for example). BR, Nikos - Original Message - From: Jinson To: users Sent: Tuesday, January 19, 2010 8:39 AM Subject: Count SMS units for Unicode Messages Hello Group, How do we count SMS units for a unicode message? Suppose I want to submit Hindi Messages from a PHP script, how do I calculate the number for characters and units consumed? Thanks Jinson Abraham
