Re: gsm7 send messages 140 =160 chars length
Thx for all the help, I wrote a simple PHP script to convert the chars into GSM percent-encoded chars, and now it's working like a charm. Thx! Andreas 2011/5/23 Nikos Balkanas nbalka...@gmail.com Interesting no one has requested for it... BR, Nikos - Original Message - From: Rene Kluwen rene.klu...@chimit.nl To: 'Nikos Balkanas' nbalka...@gmail.com; 'Nicolas de Bari Embriz Garcia Rojas' nb...@backup.sh; us...@vm1.kannel.org Sent: Monday, May 23, 2011 1:54 AM Subject: RE: gsm7 send messages 140 =160 chars length Afaik, gsm was last supported in Kannel 1.4.1. That's why I know some people are still using that version. == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Nikos Balkanas Sent: Sunday, 22 May, 2011 23:28 To: Nicolas de Bari Embriz Garcia Rojas; us...@vm1.kannel.org Subject: Re: gsm7 send messages 140 =160 chars length Hi, Actually I just had a look at the smsbox.c code. It doesn't support gsm in cgi-bin/sendsms. That's why (2) comes out garbled. You should provide iso or utf-8 text urlencoded. Why your mobile doesn't display it correctly, it is a question of either your mobile's settings, or your SMScs. BR, Nikos - Original Message - From: Nikos Balkanas nbalka...@gmail.com To: Nicolas de Bari Embriz Garcia Rojas nb...@backup.sh; us...@vm1.kannel.org Sent: Sunday, May 22, 2011 11:19 PM Subject: Re: gsm7 send messages 140 =160 chars length Hi, 1) Output is correct GSM and kannel sends it out correctly. You should contact your SMSc to see if they support GSM and if they do, why it is not displaying correctly on the mobile. Try also text==%00%7D%05coding=0. Should work and it is fewer characters to type. 2) data_coding 241 is for GSM. Kannel is trying to send GSM 03.38 but it doesn't look right. It actually sends in GSM: ?{?. Anyway just skip it. 3) Indeed UTF-8 will take up twice as many characters (other than latin-1) and maximum size is 80 = size = 160 BR, Nikos - Original Message - From: Nicolas de Bari Embriz Garcia Rojas nb...@backup.sh To: Nikos Balkanas nbalka...@gmail.com; users@kannel.org Sent: Sunday, May 22, 2011 9:17 PM Subject: Re: gsm7 send messages 140 =160 chars length Hi, please find bellow the 3 different outputs of the SMPP PDU log This one is using urlencode('@ΞΒ±ΞΒ(c)'); (message are not properly displayed on the phone but kannel send 3 chars as supposed based on the GSM charset: (smsc has NO alt-charset = UTF-8) and seems text=%40%C3%B1%C3%A9coding=0 -- DEBUG: SMPP PDU 0x801febe80 dump: DEBUG: type_name: submit_sm DEBUG: command_id: 4 = 0x0004 DEBUG: command_status: 0 = 0x DEBUG: sequence_number: 7 = 0x0007 DEBUG: service_type: NULL DEBUG: source_addr_ton: 0 = 0x DEBUG: source_addr_npi: 1 = 0x0001 DEBUG: source_addr: 42865 DEBUG: dest_addr_ton: 2 = 0x0002 DEBUG: dest_addr_npi: 1 = 0x0001 DEBUG: destination_addr: 9988776655 DEBUG: esm_class: 3 = 0x0003 DEBUG: protocol_id: 0 = 0x DEBUG: priority_flag: 0 = 0x DEBUG: schedule_delivery_time: NULL DEBUG: validity_period: NULL DEBUG: registered_delivery: 0 = 0x DEBUG: replace_if_present_flag: 0 = 0x DEBUG: data_coding: 0 = 0x DEBUG: sm_default_msg_id: 0 = 0x DEBUG: sm_length: 3 = 0x0003 DEBUG: short_message: DEBUG:Octet string at 0x80220fca0: DEBUG: len: 3 DEBUG: size: 6 DEBUG: immutable: 0 DEBUG: data: 00 7d 05 .}. DEBUG:Octet string dump ends. DEBUG: SMPP PDU dump ends. -- This one is using:%00 %7D %05 (message are not properly displayed on the phone but kannel send 3 chars as supposed based on the GSM charset: (smsc has alt-charset = UTF-8) text=%00%7D%05coding=0alt-dcs=1 (here i think kannel recodes the sms and does not recognize the alt-dsc) -- DEBUG: SMPP PDU 0x801fe1040 dump: DEBUG: type_name: submit_sm DEBUG: command_id: 4 = 0x0004 DEBUG: command_status: 0 = 0x DEBUG: sequence_number: 4974 = 0x136e DEBUG: service_type: NULL DEBUG: source_addr_ton: 0 = 0x DEBUG: source_addr_npi: 1 = 0x0001 DEBUG: source_addr: 42865 DEBUG: dest_addr_ton: 2 = 0x0002 DEBUG: dest_addr_npi: 1 = 0x0001 DEBUG: destination_addr: 9988776655 DEBUG: esm_class: 3 = 0x0003 DEBUG: protocol_id: 0 = 0x DEBUG: priority_flag: 0 = 0x DEBUG: schedule_delivery_time: NULL DEBUG: validity_period: NULL DEBUG: registered_delivery: 0 = 0x DEBUG: replace_if_present_flag: 0 = 0x DEBUG: data_coding: 241 = 0x00f1 DEBUG: sm_default_msg_id: 0 = 0x DEBUG: sm_length: 4 = 0x0004 DEBUG: short_message: DEBUG:Octet string at 0x801f836a0: DEBUG: len: 4 DEBUG: size: 1024 DEBUG: immutable: 0 DEBUG:
Re: gsm7 send messages 140 =160 chars length
Hi, same results, could it be something on 1.5 dev version ? regards. 2011/5/23 Nikos Balkanas nbalka...@gmail.com: Hi, 1) Test sending it from your browser directly, without php. 2) To send iso, you just type in regular text and specify coding and charset. You don't need to sent binary. I.e. for Greek: text=abcdΑΒΓΔΕΖcoding=0charset=iso-8859-7alt-dcs=1 and comment out alt-charset in your configuration. BR, Nikos - Original Message - From: Nicolas de Bari Embriz Garcia Rojas nb...@backup.sh To: Nikos Balkanas nbalka...@gmail.com Cc: us...@vm1.kannel.org Sent: Monday, May 23, 2011 3:41 AM Subject: Re: gsm7 send messages 140 =160 chars length Currently I am using php urlencode or url utf8_decode and coding=0 but can not make it work I get the following also testing with out using alt-charset = UTF-8 on the smsc text=%40%F1%E9 (ISO) using utf8_decode DEBUG: data_coding: 0 = 0x DEBUG: sm_default_msg_id: 0 = 0x DEBUG: sm_length: 2 = 0x0002 DEBUG: short_message: DEBUG: Octet string at 0x80240d600: DEBUG: len: 2 DEBUG: size: 4 DEBUG: immutable: 0 DEBUG: data: 00 7d .} DEBUG: Octet string dump ends. and text=%40%C3%B1%C3%A9 (UTF-8) using urlencode DEBUG: data_coding: 0 = 0x DEBUG: sm_default_msg_id: 0 = 0x DEBUG: sm_length: 3 = 0x0003 DEBUG: short_message: DEBUG: Octet string at 0x802077280: DEBUG: len: 3 DEBUG: size: 6 DEBUG: immutable: 0 DEBUG: data: 00 7d 05 .}. DEBUG: Octet string dump ends. DEBUG: SMPP PDU dump ends. for making the chars to appear correctly I just had to set alt-charset = UTF-8 on the smsc otherwise networking. and use urlencode('@Γ±Γ©); text=%40%C3%B1%C3%A9coding=0. that outputs: DEBUG: data_coding: 0 = 0x DEBUG: sm_default_msg_id: 0 = 0x DEBUG: sm_length: 5 = 0x0005 DEBUG: short_message: DEBUG: Octet string at 0x80220f100: DEBUG: len: 5 DEBUG: size: 6 DEBUG: immutable: 0 DEBUG: data: 40 c3 b1 c3 a9 @ DEBUG: Octet string dump ends. regards. [..snip..]
Re: gsm7 send messages 140 =160 chars length
Absolutely not. According to your logs, kannel sends gsm fine. It is not a kannel problem. It is a matter of your smsc or your mobile's settings. BR, Nikos - Original Message - From: Nicolas de Bari Embriz Garcia Rojas nb...@backup.sh To: Nikos Balkanas nbalka...@gmail.com Cc: us...@vm1.kannel.org Sent: Monday, May 23, 2011 8:40 PM Subject: Re: gsm7 send messages 140 =160 chars length Hi, same results, could it be something on 1.5 dev version ? regards. 2011/5/23 Nikos Balkanas nbalka...@gmail.com: Hi, 1) Test sending it from your browser directly, without php. 2) To send iso, you just type in regular text and specify coding and charset. You don't need to sent binary. I.e. for Greek: text=abcdΑΒΓΔΕΖcoding=0charset=iso-8859-7alt-dcs=1 and comment out alt-charset in your configuration. BR, Nikos - Original Message - From: Nicolas de Bari Embriz Garcia Rojas nb...@backup.sh To: Nikos Balkanas nbalka...@gmail.com Cc: us...@vm1.kannel.org Sent: Monday, May 23, 2011 3:41 AM Subject: Re: gsm7 send messages 140 =160 chars length Currently I am using php urlencode or url utf8_decode and coding=0 but can not make it work I get the following also testing with out using alt-charset = UTF-8 on the smsc text=%40%F1%E9 (ISO) using utf8_decode DEBUG: data_coding: 0 = 0x DEBUG: sm_default_msg_id: 0 = 0x DEBUG: sm_length: 2 = 0x0002 DEBUG: short_message: DEBUG: Octet string at 0x80240d600: DEBUG: len: 2 DEBUG: size: 4 DEBUG: immutable: 0 DEBUG: data: 00 7d .} DEBUG: Octet string dump ends. and text=%40%C3%B1%C3%A9 (UTF-8) using urlencode DEBUG: data_coding: 0 = 0x DEBUG: sm_default_msg_id: 0 = 0x DEBUG: sm_length: 3 = 0x0003 DEBUG: short_message: DEBUG: Octet string at 0x802077280: DEBUG: len: 3 DEBUG: size: 6 DEBUG: immutable: 0 DEBUG: data: 00 7d 05 .}. DEBUG: Octet string dump ends. DEBUG: SMPP PDU dump ends. for making the chars to appear correctly I just had to set alt-charset = UTF-8 on the smsc otherwise networking. and use urlencode('@Γ±Γ©); text=%40%C3%B1%C3%A9coding=0. that outputs: DEBUG: data_coding: 0 = 0x DEBUG: sm_default_msg_id: 0 = 0x DEBUG: sm_length: 5 = 0x0005 DEBUG: short_message: DEBUG: Octet string at 0x80220f100: DEBUG: len: 5 DEBUG: size: 6 DEBUG: immutable: 0 DEBUG: data: 40 c3 b1 c3 a9 @ DEBUG: Octet string dump ends. regards. [..snip..]
Delay return of deliver_sm_resp
Hello, I am attempting to set-up kannel to mimic a customer who is geographically located across the country from the SMSC. What I would like bearerbox to do is to wait a configurable amount of time (for example, 100ms) before sending back the deliver_sm_resp. This would mimic the delay. I have read that there is a throughput command, but I believe this only throttles the outbound submit_sm messages as a way to not flood the SMSC. My testing confirmed this. I am actually attempting to flood the SMSC by decreasing the number of messages kannel takes out of the message queue. Is there any configuration parameter that will allow me to do this? Thanks, Kent
Re: Delay return of deliver_sm_resp
Throughput won't cut it, it won't prevent the _sm_resp PDU response from going out. If this is only for testing and you're not concerned about performance, you could make the thread sleep right before sending the _sm_resp. Regards, Alex On Mon, May 23, 2011 at 6:11 PM, Kent Walker kent.wal...@jasperwireless.com wrote: Hello, I am attempting to set-up kannel to mimic a customer who is geographically located across the country from the SMSC. What I would like bearerbox to do is to wait a configurable amount of time (for example, 100ms) before sending back the deliver_sm_resp. This would mimic the delay. I have read that there is a throughput command, but I believe this only throttles the outbound submit_sm messages as a way to not flood the SMSC. My testing confirmed this. I am actually attempting to flood the SMSC by decreasing the number of messages kannel takes out of the message queue. Is there any configuration parameter that will allow me to do this? Thanks, Kent