Re: Kannel concatenated SMS and DLR
Hi That is the expected behavior from kannel architecture side. As is now, kannel uses the first final successful/failed dlr (not necessarily from 1st part) in order to validate the whole message. Following dlrs just fails to update as shown in your log. There are some old threads discussing the issue and how to handle concatenated dlrs when some of the parts are delivered and some doesn't. Regards Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com On Tue, Dec 16, 2014 at 5:46 PM, Laurent Charlois laurent.charl...@smsmode.com wrote: Hi, We use Kannel to send SMS to our provider using SMPP. Everything going well except for one thing : when we send concatenated SMS for some reasons our provider can only return one DLR to us. When this DLR concerns the first part of the message it's ok but when the DLR do not concerns the first part of the message kannel cannot handle the DLR. In this case we get error message like that : 2014-12-16 23:36:22 [29635] [21] ERROR: SMPP[mySMSC]: got DLR but could not find message or was not interested in it id566686393 dst33601020304, type1 Is it somebody that have a workaround for this case? Is it a way to tell Kannel to consider any DLR from the SMSC as the (one) DLR kannel waits for? Thanks to all folk that read this email and try to give us a solution :) Best regards, Laurent Charlois.
Re: Kannel concatenated SMS and DLR
Hi Alvaro, Thanks for your answer. I do some search in old threads and didn't find any solution for our issue. The point is that it seems that when we receive DLR for the first part kannel forward the DLR to our server. But when the DLR (the only one that we receive for the concatenated SMS) doesn't concern the first part then kannel never forwerd the DLR to our server. My goal is not to ask change in kannel process : Kannel works very well. My goal is only to find a workaround to get DLRs (first part DLR or not) to be forwarded to our server. Best regards, On 12/17/2014 04:06 PM, Alvaro Cornejo wrote: Hi That is the expected behavior from kannel architecture side. As is now, kannel uses the first final successful/failed dlr (not necessarily from 1st part) in order to validate the whole message. Following dlrs just fails to update as shown in your log. There are some old threads discussing the issue and how to handle concatenated dlrs when some of the parts are delivered and some doesn't. Regards Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com http://www.perusms.com On Tue, Dec 16, 2014 at 5:46 PM, Laurent Charlois laurent.charl...@smsmode.com mailto:laurent.charl...@smsmode.com wrote: Hi, We use Kannel to send SMS to our provider using SMPP. Everything going well except for one thing : when we send concatenated SMS for some reasons our provider can only return one DLR to us. When this DLR concerns the first part of the message it's ok but when the DLR do not concerns the first part of the message kannel cannot handle the DLR. In this case we get error message like that : 2014-12-16 23:36:22 [29635] [21] ERROR: SMPP[mySMSC]: got DLR but could not find message or was not interested in it id566686393 dst33601020304, type1 Is it somebody that have a workaround for this case? Is it a way to tell Kannel to consider any DLR from the SMSC as the (one) DLR kannel waits for? Thanks to all folk that read this email and try to give us a solution :) Best regards, Laurent Charlois. -- Laurent Charlois +33 4 91 05 64 62 smsMode.com
Kannel concatenated SMS and DLR
Hi, We use Kannel to send SMS to our provider using SMPP. Everything going well except for one thing : when we send concatenated SMS for some reasons our provider can only return one DLR to us. When this DLR concerns the first part of the message it's ok but when the DLR do not concerns the first part of the message kannel cannot handle the DLR. In this case we get error message like that : 2014-12-16 23:36:22 [29635] [21] ERROR: SMPP[mySMSC]: got DLR but could not find message or was not interested in it id566686393 dst33601020304, type1 Is it somebody that have a workaround for this case? Is it a way to tell Kannel to consider any DLR from the SMSC as the (one) DLR kannel waits for? Thanks to all folk that read this email and try to give us a solution :) Best regards, Laurent Charlois.
Concatenated SMS (Loyc Cossou)
Hi Loyc, set the params in group = sendsms-user setting for the short code, restart, retest. Faith Date: Wed, 28 May 2014 09:00:28 +0100 From: Loyc Cossou loycos...@gmail.com To: users@kannel.org Subject: Concatenated SMS Message-ID: CAAuJUSyY= ynuxqsalw_-jks4q2ke7tkj+fp3ev1xxlzx--x...@mail.gmail.com Content-Type: text/plain; charset=utf-8 Hi, Hope you are all doing good. I am facing a issue related to the lenght of the SMS. Whe trying to send a SMS that has the lenght of 3 messages (459 characters), the SMS is tranmitted with only the 2 first messages, then is truncated. In my sms-service group I have written: max-messages = 5 concatenation = true ?Please advice.? -- loyc Cossou -- next part -- An HTML attachment was scrubbed... URL: http://www.kannel.org/pipermail/users/attachments/20140528/00e726a6/attachment.html -- Subject: Digest Footer ___ users mailing list users@kannel.org http://www.kannel.org/mailman/listinfo/users -- End of users Digest, Vol 93, Issue 56 *
Re: Concatenated SMS (Loyc Cossou)
Hi Faith, Thank you for your mail. It worked!! Cool! I am now able to send the whole message. Thanks again. -- loyc Cossou On 29 May 2014 08:22, me moraa.lovetak...@gmail.com wrote: Hi Loyc, set the params in group = sendsms-user setting for the short code, restart, retest. Faith Date: Wed, 28 May 2014 09:00:28 +0100 From: Loyc Cossou loycos...@gmail.com To: users@kannel.org Subject: Concatenated SMS Message-ID: CAAuJUSyY= ynuxqsalw_-jks4q2ke7tkj+fp3ev1xxlzx--x...@mail.gmail.com Content-Type: text/plain; charset=utf-8 Hi, Hope you are all doing good. I am facing a issue related to the lenght of the SMS. Whe trying to send a SMS that has the lenght of 3 messages (459 characters), the SMS is tranmitted with only the 2 first messages, then is truncated. In my sms-service group I have written: max-messages = 5 concatenation = true ?Please advice.? -- loyc Cossou -- next part -- An HTML attachment was scrubbed... URL: http://www.kannel.org/pipermail/users/attachments/20140528/00e726a6/attachment.html -- Subject: Digest Footer ___ users mailing list users@kannel.org http://www.kannel.org/mailman/listinfo/users -- End of users Digest, Vol 93, Issue 56 *
Concatenated SMS
Hi, Hope you are all doing good. I am facing a issue related to the lenght of the SMS. Whe trying to send a SMS that has the lenght of 3 messages (459 characters), the SMS is tranmitted with only the 2 first messages, then is truncated. In my sms-service group I have written: max-messages = 5 concatenation = true Please advice. -- loyc Cossou
Re: concatenated sms
Hi John, I have already configured with those parameters. Best On Fri, Dec 13, 2013 at 2:13 AM, John alero johnale...@gmail.com wrote: Hi, Kindly use below parameters in sendsms-user group. group = sendsms-user [Group name to send SMS] max-messages = 5 [max SMS length is 5] concatenation=true On Thu, Dec 12, 2013 at 4:43 AM, Alejandro Mussi alemu...@gmail.comwrote: Hi, I have one smsc operator that does not concatenate a long sms. I send an MT and the phone only receives the first part. The operator said that the smsc support UDH and TLVs for this propose. What kannel use for default and how should i make it work with UDH ? If i use *concatenation = false*, the message is delivered into X parts. But with true value i only get the first part. Other smsc operators work fine. Here is my log of a message sent: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP[personal]: Sending PDU: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP PDU 0x7f4fb80008c0 dump: 2013-12-11 13:47:37 [8691] [8] DEBUG: type_name: submit_sm 2013-12-11 13:47:37 [8691] [8] DEBUG: command_id: 4 = 0x0004 2013-12-11 13:47:37 [8691] [8] DEBUG: command_status: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sequence_number: 14097 = 0x3711 2013-12-11 13:47:37 [8691] [8] DEBUG: service_type: CCHUR 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr: 1244 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: destination_addr: 0981591407 2013-12-11 13:47:37 [8691] [8] DEBUG: esm_class: 67 = 0x0043 2013-12-11 13:47:37 [8691] [8] DEBUG: protocol_id: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: priority_flag: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: schedule_delivery_time: NULL 2013-12-11 13:47:37 [8691] [8] DEBUG: validity_period: NULL 2013-12-11 13:47:37 [8691] [8] DEBUG: registered_delivery: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: replace_if_present_flag: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: data_coding: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sm_default_msg_id: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sm_length: 159 = 0x009f 2013-12-11 13:47:37 [8691] [8] DEBUG: short_message: 2013-12-11 13:47:37 [8691] [8] DEBUG:Octet string at 0x7f4fb8000aa0: 2013-12-11 13:47:37 [8691] [8] DEBUG: len: 159 2013-12-11 13:47:37 [8691] [8] DEBUG: size: 1024 2013-12-11 13:47:37 [8691] [8] DEBUG: immutable: 0 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 05 00 03 00 02 01 42 69 65 6e 76 65 6e 69 64 6f ..Bienvenido 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 61 6c 20 53 65 72 76 69 63 69 6f 20 43 68 75al Servicio Chu 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 72 65 72 6f 2e 20 52 65 63 69 62 69 72 61 73 20 rero. Recibiras 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 68 61 73 74 61 20 33 20 6e 6f 76 65 64 61 64 65 hasta 3 novedade 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 73 20 70 6f 72 20 64 69 61 20 64 65 20 22 45 6c s por dia de El 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 43 68 75 72 65 72 6f 22 2e 20 43 6f 73 74 6fChurero. Costo 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 64 65 6c 20 73 65 72 76 69 63 69 6f 20 31 2edel servicio 1. 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 31 30 30 20 47 73 20 70 6f 72 20 64 69 61 2e 20 100 Gs por dia. 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 50 61 72 61 20 63 61 6e 63 65 6c 61 72 20 65 6c Para cancelar el 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 73 65 72 76 69 63 69 6f 20 65 6e 76 69 65 servicio envie 2013-12-11 13:47:37 [8691] [8] DEBUG:Octet string dump ends. 2013-12-11 13:47:37 [8691] [8] DEBUG: more_messages_to_send: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP PDU dump ends. 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP[personal]: Sending PDU: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP PDU 0x7f4fb80008c0 dump: 2013-12-11 13:47:37 [8691] [8] DEBUG: type_name: submit_sm 2013-12-11 13:47:37 [8691] [8] DEBUG: command_id: 4 = 0x0004 2013-12-11 13:47:37 [8691] [8] DEBUG: command_status: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sequence_number: 14098 = 0x3712 2013-12-11 13:47:37 [8691] [8] DEBUG: service_type: CCHUR 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr: 1244 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG:
Re: concatenated sms
Hi If your operator said you need to use udh tlv, that is what you need to do. This means you need to do the split the message by your own and send each part independently. Ask your priovider which values you need to use for the tlv or better give you an example or a dump to get details. About udh values, you need to calculate it as well as the sequence numbers. Search the mailing list for more details on how to manually build concatenated messages. There was a couple of conversations about a couple of years ago. Hope helps Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com On Fri, Dec 13, 2013 at 7:46 AM, Alejandro Mussi alemu...@gmail.com wrote: Hi John, I have already configured with those parameters. Best On Fri, Dec 13, 2013 at 2:13 AM, John alero johnale...@gmail.com wrote: Hi, Kindly use below parameters in sendsms-user group. group = sendsms-user [Group name to send SMS] max-messages = 5 [max SMS length is 5] concatenation=true On Thu, Dec 12, 2013 at 4:43 AM, Alejandro Mussi alemu...@gmail.com wrote: Hi, I have one smsc operator that does not concatenate a long sms. I send an MT and the phone only receives the first part. The operator said that the smsc support UDH and TLVs for this propose. What kannel use for default and how should i make it work with UDH ? If i use concatenation = false, the message is delivered into X parts. But with true value i only get the first part. Other smsc operators work fine. Here is my log of a message sent: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP[personal]: Sending PDU: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP PDU 0x7f4fb80008c0 dump: 2013-12-11 13:47:37 [8691] [8] DEBUG: type_name: submit_sm 2013-12-11 13:47:37 [8691] [8] DEBUG: command_id: 4 = 0x0004 2013-12-11 13:47:37 [8691] [8] DEBUG: command_status: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sequence_number: 14097 = 0x3711 2013-12-11 13:47:37 [8691] [8] DEBUG: service_type: CCHUR 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr: 1244 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: destination_addr: 0981591407 2013-12-11 13:47:37 [8691] [8] DEBUG: esm_class: 67 = 0x0043 2013-12-11 13:47:37 [8691] [8] DEBUG: protocol_id: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: priority_flag: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: schedule_delivery_time: NULL 2013-12-11 13:47:37 [8691] [8] DEBUG: validity_period: NULL 2013-12-11 13:47:37 [8691] [8] DEBUG: registered_delivery: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: replace_if_present_flag: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: data_coding: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sm_default_msg_id: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sm_length: 159 = 0x009f 2013-12-11 13:47:37 [8691] [8] DEBUG: short_message: 2013-12-11 13:47:37 [8691] [8] DEBUG:Octet string at 0x7f4fb8000aa0: 2013-12-11 13:47:37 [8691] [8] DEBUG: len: 159 2013-12-11 13:47:37 [8691] [8] DEBUG: size: 1024 2013-12-11 13:47:37 [8691] [8] DEBUG: immutable: 0 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 05 00 03 00 02 01 42 69 65 6e 76 65 6e 69 64 6f ..Bienvenido 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 61 6c 20 53 65 72 76 69 63 69 6f 20 43 68 75al Servicio Chu 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 72 65 72 6f 2e 20 52 65 63 69 62 69 72 61 73 20 rero. Recibiras 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 68 61 73 74 61 20 33 20 6e 6f 76 65 64 61 64 65 hasta 3 novedade 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 73 20 70 6f 72 20 64 69 61 20 64 65 20 22 45 6c s por dia de El 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 43 68 75 72 65 72 6f 22 2e 20 43 6f 73 74 6fChurero. Costo 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 64 65 6c 20 73 65 72 76 69 63 69 6f 20 31 2edel servicio 1. 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 31 30 30 20 47 73 20 70 6f 72 20 64 69 61 2e 20 100 Gs por dia. 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 50 61 72 61 20 63 61 6e 63 65 6c 61 72 20 65 6c Para cancelar el 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 73 65 72 76 69 63 69 6f 20 65 6e 76 69 65 servicio envie 2013-12-11 13:47:37 [8691] [8] DEBUG:Octet string dump ends.
Re: concatenated sms
Thanks Alvaro, Is it possible to use *concatenated = false* for some smsc and *true* for others? Best On Fri, Dec 13, 2013 at 10:51 AM, Alvaro Cornejo cornejo.alv...@gmail.comwrote: Hi If your operator said you need to use udh tlv, that is what you need to do. This means you need to do the split the message by your own and send each part independently. Ask your priovider which values you need to use for the tlv or better give you an example or a dump to get details. About udh values, you need to calculate it as well as the sequence numbers. Search the mailing list for more details on how to manually build concatenated messages. There was a couple of conversations about a couple of years ago. Hope helps Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com On Fri, Dec 13, 2013 at 7:46 AM, Alejandro Mussi alemu...@gmail.com wrote: Hi John, I have already configured with those parameters. Best On Fri, Dec 13, 2013 at 2:13 AM, John alero johnale...@gmail.com wrote: Hi, Kindly use below parameters in sendsms-user group. group = sendsms-user [Group name to send SMS] max-messages = 5 [max SMS length is 5] concatenation=true On Thu, Dec 12, 2013 at 4:43 AM, Alejandro Mussi alemu...@gmail.com wrote: Hi, I have one smsc operator that does not concatenate a long sms. I send an MT and the phone only receives the first part. The operator said that the smsc support UDH and TLVs for this propose. What kannel use for default and how should i make it work with UDH ? If i use concatenation = false, the message is delivered into X parts. But with true value i only get the first part. Other smsc operators work fine. Here is my log of a message sent: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP[personal]: Sending PDU: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP PDU 0x7f4fb80008c0 dump: 2013-12-11 13:47:37 [8691] [8] DEBUG: type_name: submit_sm 2013-12-11 13:47:37 [8691] [8] DEBUG: command_id: 4 = 0x0004 2013-12-11 13:47:37 [8691] [8] DEBUG: command_status: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sequence_number: 14097 = 0x3711 2013-12-11 13:47:37 [8691] [8] DEBUG: service_type: CCHUR 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr: 1244 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: destination_addr: 0981591407 2013-12-11 13:47:37 [8691] [8] DEBUG: esm_class: 67 = 0x0043 2013-12-11 13:47:37 [8691] [8] DEBUG: protocol_id: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: priority_flag: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: schedule_delivery_time: NULL 2013-12-11 13:47:37 [8691] [8] DEBUG: validity_period: NULL 2013-12-11 13:47:37 [8691] [8] DEBUG: registered_delivery: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: replace_if_present_flag: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: data_coding: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sm_default_msg_id: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sm_length: 159 = 0x009f 2013-12-11 13:47:37 [8691] [8] DEBUG: short_message: 2013-12-11 13:47:37 [8691] [8] DEBUG:Octet string at 0x7f4fb8000aa0: 2013-12-11 13:47:37 [8691] [8] DEBUG: len: 159 2013-12-11 13:47:37 [8691] [8] DEBUG: size: 1024 2013-12-11 13:47:37 [8691] [8] DEBUG: immutable: 0 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 05 00 03 00 02 01 42 69 65 6e 76 65 6e 69 64 6f ..Bienvenido 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 61 6c 20 53 65 72 76 69 63 69 6f 20 43 68 75al Servicio Chu 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 72 65 72 6f 2e 20 52 65 63 69 62 69 72 61 73 20 rero. Recibiras 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 68 61 73 74 61 20 33 20 6e 6f 76 65 64 61 64 65 hasta 3 novedade 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 73 20 70 6f 72 20 64 69 61 20 64 65 20 22 45 6c s por dia de El 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 43 68 75 72 65 72 6f 22 2e 20 43 6f 73 74 6fChurero. Costo 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 64 65 6c 20 73 65 72 76 69 63 69 6f 20 31 2edel servicio 1. 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 31 30 30 20 47 73 20 70 6f
Re: concatenated sms
Hi Yes, but you need to use a different group sendsms-user since concatenated= is a characteristic from that group. Regards Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com On Fri, Dec 13, 2013 at 9:03 AM, Alejandro Mussi alemu...@gmail.com wrote: Thanks Alvaro, Is it possible to use concatenated = false for some smsc and true for others? Best On Fri, Dec 13, 2013 at 10:51 AM, Alvaro Cornejo cornejo.alv...@gmail.com wrote: Hi If your operator said you need to use udh tlv, that is what you need to do. This means you need to do the split the message by your own and send each part independently. Ask your priovider which values you need to use for the tlv or better give you an example or a dump to get details. About udh values, you need to calculate it as well as the sequence numbers. Search the mailing list for more details on how to manually build concatenated messages. There was a couple of conversations about a couple of years ago. Hope helps Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com On Fri, Dec 13, 2013 at 7:46 AM, Alejandro Mussi alemu...@gmail.com wrote: Hi John, I have already configured with those parameters. Best On Fri, Dec 13, 2013 at 2:13 AM, John alero johnale...@gmail.com wrote: Hi, Kindly use below parameters in sendsms-user group. group = sendsms-user [Group name to send SMS] max-messages = 5 [max SMS length is 5] concatenation=true On Thu, Dec 12, 2013 at 4:43 AM, Alejandro Mussi alemu...@gmail.com wrote: Hi, I have one smsc operator that does not concatenate a long sms. I send an MT and the phone only receives the first part. The operator said that the smsc support UDH and TLVs for this propose. What kannel use for default and how should i make it work with UDH ? If i use concatenation = false, the message is delivered into X parts. But with true value i only get the first part. Other smsc operators work fine. Here is my log of a message sent: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP[personal]: Sending PDU: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP PDU 0x7f4fb80008c0 dump: 2013-12-11 13:47:37 [8691] [8] DEBUG: type_name: submit_sm 2013-12-11 13:47:37 [8691] [8] DEBUG: command_id: 4 = 0x0004 2013-12-11 13:47:37 [8691] [8] DEBUG: command_status: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sequence_number: 14097 = 0x3711 2013-12-11 13:47:37 [8691] [8] DEBUG: service_type: CCHUR 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr: 1244 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: destination_addr: 0981591407 2013-12-11 13:47:37 [8691] [8] DEBUG: esm_class: 67 = 0x0043 2013-12-11 13:47:37 [8691] [8] DEBUG: protocol_id: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: priority_flag: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: schedule_delivery_time: NULL 2013-12-11 13:47:37 [8691] [8] DEBUG: validity_period: NULL 2013-12-11 13:47:37 [8691] [8] DEBUG: registered_delivery: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: replace_if_present_flag: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: data_coding: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sm_default_msg_id: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sm_length: 159 = 0x009f 2013-12-11 13:47:37 [8691] [8] DEBUG: short_message: 2013-12-11 13:47:37 [8691] [8] DEBUG:Octet string at 0x7f4fb8000aa0: 2013-12-11 13:47:37 [8691] [8] DEBUG: len: 159 2013-12-11 13:47:37 [8691] [8] DEBUG: size: 1024 2013-12-11 13:47:37 [8691] [8] DEBUG: immutable: 0 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 05 00 03 00 02 01 42 69 65 6e 76 65 6e 69 64 6f ..Bienvenido 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 61 6c 20 53 65 72 76 69 63 69 6f 20 43 68 75al Servicio Chu 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 72 65 72 6f 2e 20 52 65 63 69 62 69 72 61 73 20 rero. Recibiras
Re: concatenated sms
Hi, Kindly use below parameters in sendsms-user group. group = sendsms-user [Group name to send SMS] max-messages = 5 [max SMS length is 5] concatenation=true On Thu, Dec 12, 2013 at 4:43 AM, Alejandro Mussi alemu...@gmail.com wrote: Hi, I have one smsc operator that does not concatenate a long sms. I send an MT and the phone only receives the first part. The operator said that the smsc support UDH and TLVs for this propose. What kannel use for default and how should i make it work with UDH ? If i use *concatenation = false*, the message is delivered into X parts. But with true value i only get the first part. Other smsc operators work fine. Here is my log of a message sent: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP[personal]: Sending PDU: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP PDU 0x7f4fb80008c0 dump: 2013-12-11 13:47:37 [8691] [8] DEBUG: type_name: submit_sm 2013-12-11 13:47:37 [8691] [8] DEBUG: command_id: 4 = 0x0004 2013-12-11 13:47:37 [8691] [8] DEBUG: command_status: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sequence_number: 14097 = 0x3711 2013-12-11 13:47:37 [8691] [8] DEBUG: service_type: CCHUR 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr: 1244 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: destination_addr: 0981591407 2013-12-11 13:47:37 [8691] [8] DEBUG: esm_class: 67 = 0x0043 2013-12-11 13:47:37 [8691] [8] DEBUG: protocol_id: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: priority_flag: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: schedule_delivery_time: NULL 2013-12-11 13:47:37 [8691] [8] DEBUG: validity_period: NULL 2013-12-11 13:47:37 [8691] [8] DEBUG: registered_delivery: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: replace_if_present_flag: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: data_coding: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sm_default_msg_id: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sm_length: 159 = 0x009f 2013-12-11 13:47:37 [8691] [8] DEBUG: short_message: 2013-12-11 13:47:37 [8691] [8] DEBUG:Octet string at 0x7f4fb8000aa0: 2013-12-11 13:47:37 [8691] [8] DEBUG: len: 159 2013-12-11 13:47:37 [8691] [8] DEBUG: size: 1024 2013-12-11 13:47:37 [8691] [8] DEBUG: immutable: 0 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 05 00 03 00 02 01 42 69 65 6e 76 65 6e 69 64 6f ..Bienvenido 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 61 6c 20 53 65 72 76 69 63 69 6f 20 43 68 75al Servicio Chu 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 72 65 72 6f 2e 20 52 65 63 69 62 69 72 61 73 20 rero. Recibiras 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 68 61 73 74 61 20 33 20 6e 6f 76 65 64 61 64 65 hasta 3 novedade 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 73 20 70 6f 72 20 64 69 61 20 64 65 20 22 45 6c s por dia de El 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 43 68 75 72 65 72 6f 22 2e 20 43 6f 73 74 6fChurero. Costo 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 64 65 6c 20 73 65 72 76 69 63 69 6f 20 31 2edel servicio 1. 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 31 30 30 20 47 73 20 70 6f 72 20 64 69 61 2e 20 100 Gs por dia. 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 50 61 72 61 20 63 61 6e 63 65 6c 61 72 20 65 6c Para cancelar el 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 73 65 72 76 69 63 69 6f 20 65 6e 76 69 65 servicio envie 2013-12-11 13:47:37 [8691] [8] DEBUG:Octet string dump ends. 2013-12-11 13:47:37 [8691] [8] DEBUG: more_messages_to_send: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP PDU dump ends. 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP[personal]: Sending PDU: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP PDU 0x7f4fb80008c0 dump: 2013-12-11 13:47:37 [8691] [8] DEBUG: type_name: submit_sm 2013-12-11 13:47:37 [8691] [8] DEBUG: command_id: 4 = 0x0004 2013-12-11 13:47:37 [8691] [8] DEBUG: command_status: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sequence_number: 14098 = 0x3712 2013-12-11 13:47:37 [8691] [8] DEBUG: service_type: CCHUR 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr: 1244 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: destination_addr: 0981591407 2013-12-11 13:47:37 [8691] [8] DEBUG: esm_class: 67 =
Length of Concatenated SMS
Hello, I'm using the native kannel concatenated sms. Just question for the length of each part. In theory, each part should has 153 characters long (134 octet), but i always observe 2nd part has 151 characters only ( in case my message is spitted to 3 or 4 parts). Why? Brs, Tuan. -- ((=o-( ',_,' )-o=))= Bản chất tốt nhưng cuộc đời xô đẩy!
concatenated sms
Hi, I have one smsc operator that does not concatenate a long sms. I send an MT and the phone only receives the first part. The operator said that the smsc support UDH and TLVs for this propose. What kannel use for default and how should i make it work with UDH ? If i use *concatenation = false*, the message is delivered into X parts. But with true value i only get the first part. Other smsc operators work fine. Here is my log of a message sent: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP[personal]: Sending PDU: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP PDU 0x7f4fb80008c0 dump: 2013-12-11 13:47:37 [8691] [8] DEBUG: type_name: submit_sm 2013-12-11 13:47:37 [8691] [8] DEBUG: command_id: 4 = 0x0004 2013-12-11 13:47:37 [8691] [8] DEBUG: command_status: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sequence_number: 14097 = 0x3711 2013-12-11 13:47:37 [8691] [8] DEBUG: service_type: CCHUR 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr: 1244 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: destination_addr: 0981591407 2013-12-11 13:47:37 [8691] [8] DEBUG: esm_class: 67 = 0x0043 2013-12-11 13:47:37 [8691] [8] DEBUG: protocol_id: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: priority_flag: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: schedule_delivery_time: NULL 2013-12-11 13:47:37 [8691] [8] DEBUG: validity_period: NULL 2013-12-11 13:47:37 [8691] [8] DEBUG: registered_delivery: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: replace_if_present_flag: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: data_coding: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sm_default_msg_id: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sm_length: 159 = 0x009f 2013-12-11 13:47:37 [8691] [8] DEBUG: short_message: 2013-12-11 13:47:37 [8691] [8] DEBUG:Octet string at 0x7f4fb8000aa0: 2013-12-11 13:47:37 [8691] [8] DEBUG: len: 159 2013-12-11 13:47:37 [8691] [8] DEBUG: size: 1024 2013-12-11 13:47:37 [8691] [8] DEBUG: immutable: 0 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 05 00 03 00 02 01 42 69 65 6e 76 65 6e 69 64 6f ..Bienvenido 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 61 6c 20 53 65 72 76 69 63 69 6f 20 43 68 75al Servicio Chu 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 72 65 72 6f 2e 20 52 65 63 69 62 69 72 61 73 20 rero. Recibiras 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 68 61 73 74 61 20 33 20 6e 6f 76 65 64 61 64 65 hasta 3 novedade 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 73 20 70 6f 72 20 64 69 61 20 64 65 20 22 45 6c s por dia de El 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 43 68 75 72 65 72 6f 22 2e 20 43 6f 73 74 6fChurero. Costo 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 64 65 6c 20 73 65 72 76 69 63 69 6f 20 31 2edel servicio 1. 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 31 30 30 20 47 73 20 70 6f 72 20 64 69 61 2e 20 100 Gs por dia. 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 50 61 72 61 20 63 61 6e 63 65 6c 61 72 20 65 6c Para cancelar el 2013-12-11 13:47:37 [8691] [8] DEBUG: data: 20 73 65 72 76 69 63 69 6f 20 65 6e 76 69 65 servicio envie 2013-12-11 13:47:37 [8691] [8] DEBUG:Octet string dump ends. 2013-12-11 13:47:37 [8691] [8] DEBUG: more_messages_to_send: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP PDU dump ends. 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP[personal]: Sending PDU: 2013-12-11 13:47:37 [8691] [8] DEBUG: SMPP PDU 0x7f4fb80008c0 dump: 2013-12-11 13:47:37 [8691] [8] DEBUG: type_name: submit_sm 2013-12-11 13:47:37 [8691] [8] DEBUG: command_id: 4 = 0x0004 2013-12-11 13:47:37 [8691] [8] DEBUG: command_status: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: sequence_number: 14098 = 0x3712 2013-12-11 13:47:37 [8691] [8] DEBUG: service_type: CCHUR 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: source_addr: 1244 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_ton: 2 = 0x0002 2013-12-11 13:47:37 [8691] [8] DEBUG: dest_addr_npi: 1 = 0x0001 2013-12-11 13:47:37 [8691] [8] DEBUG: destination_addr: 0981591407 2013-12-11 13:47:37 [8691] [8] DEBUG: esm_class: 67 = 0x0043 2013-12-11 13:47:37 [8691] [8] DEBUG: protocol_id: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: priority_flag: 0 = 0x 2013-12-11 13:47:37 [8691] [8] DEBUG: schedule_delivery_time: NULL 2013-12-11 13:47:37 [8691] [8] DEBUG: validity_period: NULL 2013-12-11 13:47:37 [8691] [8]
concatenated SMS delay period ?
Hello, Is there a way for me to add a delay option between each part of concatenated message, since I can add delay at my application level while calling sendsms page, but I can't add a delay there in the case of long concatenated messages, I am looking for a way of doing it inside kannel. So far I've been getting Message Queue Full Error 2012-07-16 08:13:24 [7604] [18] ERROR: SMPP[x]: SMSC returned error code 0x0014 (Message Queue Full) in response to submit_sm. 2012-07-16 08:13:25 [7604] [18] ERROR: SMPP[x]: SMSC returned error code 0x0014 (Message Queue Full) in response to submit_sm. 2012-07-16 08:13:26 [7604] [18] ERROR: SMPP[x]: SMSC returned error code 0x0014 (Message Queue Full) in response to submit_sm. 2012-07-16 08:13:26 [7604] [18] ERROR: SMPP[x]: SMSC returned error code 0x0014 (Message Queue Full) in response to submit_sm. Thanks
Concatenated SMS MO have corrupt UDH when sms-combine-concatenated-mo is set to false
Hi, By default, Kannel concatenates fragmented MOs into one long SMS MO, by setting sms-combine-concatenated-mo to false, it delivers every fragment as is with an UDH indicating it is a long sms fragment, so for a long sms fragment i get this UDH in access-log: [udh:6:0500031D6332] So, this udh: 0500031D0302 means: - 05 UDH length - 00 IEI, concatenated short messages - 03 IE Data length - 1D reference number (29) - 03 number of short messages in the concatenated short message (3) - 02 sequence number of the current short message, that means this is the second fragment of 3 fragments I use PHP scripts to make one message from such messages, but in my PHP application I do not get this UDH, instead I get something like this: 0500031Dc2 In my smsbox access-log I see: 2007-08-08 20:51:18 SMS HTTP-request sender:26392390208295477 request: '' url: 'http://test.dev/receive.php?text=enaidnieki+513)+automashinas%3 B+514)+kugji+515)+traktori+516)+zobenzivis+517)+buldozeri+518)+sanitaari+519)+draugi+520)+ienaidnieki+521)+automashinas%3B+522)keyword=enaidniekikeyword2=51 3)from=26392390208295477to=1827smsc=5time=2007-08-08+17:51:18drv=-1coding=0charset=ISO-8859-1udh=%05%00%03%1Dc2' reply: 200 ' successful ' What is it? %05%00%03%1Dc2 is not HEX anymore. I use Kannel 1.4.3. My kannel SMS service: # SMS SERVICE Default group = sms-service keyword = default accept-x-kannel-headers = true get-url = http://test.dev/receive.php?text=%akeyword=%kkeyword2=%sfrom=%pto=%Psmsc=%itime=%tdrv=%dcoding=%ccharset=%Cudh=%u max-messages = 0 omit-empty = true How can I stop kannel to make such conversations? Binary SMS text sometimes also is converted to something meaningless. For information, using a tcpdump i see that i get correct udh for every fragmented SMS-MO delivered to bearerbox, but once received from smsbox, the udh gets corrupted.
Re: Why does Kannel not use sar_total_segments and sar_segment_seqnum when sending concatenated sms?
Hi guys. Does anyone have an ideas to my question below? Thanks, On Thu, Jan 13, 2011 at 11:35 AM, brett skinner tatty.dishcl...@gmail.comwrote: Hi I was looking through the logs and saw that Kannel sends concatenated SMSs using UDH in the Short Message fields. From reading the SMPP spec I was under the impression that the same thing could be achieved by using sar_total_segments and sar_segment_seqnum. Did I misinterpret the spec or does Kannel not use these fields for another reason such as unreliable implementation on the receiving SMSC. Regards,
Re: Why does Kannel not use sar_total_segments and sar_segment_seqnum when sending concatenated sms?
It's not implemented afaik. Only the UDH method is supported. Regards, Alex On Tue, Jan 18, 2011 at 10:47 AM, brett skinner tatty.dishcl...@gmail.comwrote: Hi guys. Does anyone have an ideas to my question below? Thanks, On Thu, Jan 13, 2011 at 11:35 AM, brett skinner tatty.dishcl...@gmail.com wrote: Hi I was looking through the logs and saw that Kannel sends concatenated SMSs using UDH in the Short Message fields. From reading the SMPP spec I was under the impression that the same thing could be achieved by using sar_total_segments and sar_segment_seqnum. Did I misinterpret the spec or does Kannel not use these fields for another reason such as unreliable implementation on the receiving SMSC. Regards,
Re: Why does Kannel not use sar_total_segments and sar_segment_seqnum when sending concatenated sms?
It means that Kannel doesn't have the ability to re-assemble messages using the sar method. I'm not sure about how extensively used is this method among the carriers, I so far only encountered one case. Regards, Alex On Tue, Jan 18, 2011 at 11:08 AM, brett skinner tatty.dishcl...@gmail.comwrote: Do you mean as far as Kannel is concerned or that most SMSC don't use this method? So I did understand the spec correctly. It is just that everyone chooses to use the UDH method rather? On Tue, Jan 18, 2011 at 11:51 AM, Alejandro Guerrieri alejandro.guerri...@gmail.com wrote: It's not implemented afaik. Only the UDH method is supported. Regards, Alex On Tue, Jan 18, 2011 at 10:47 AM, brett skinner tatty.dishcl...@gmail.com wrote: Hi guys. Does anyone have an ideas to my question below? Thanks, On Thu, Jan 13, 2011 at 11:35 AM, brett skinner tatty.dishcl...@gmail.com wrote: Hi I was looking through the logs and saw that Kannel sends concatenated SMSs using UDH in the Short Message fields. From reading the SMPP spec I was under the impression that the same thing could be achieved by using sar_total_segments and sar_segment_seqnum. Did I misinterpret the spec or does Kannel not use these fields for another reason such as unreliable implementation on the receiving SMSC. Regards,
RE: Why does Kannel not use sar_total_segments and sar_segment_seqnum when sending concatenated sms?
I do have an existing patch for that, somewhere along the mailinglist. == Rene From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Alejandro Guerrieri Sent: Tuesday, 18 January, 2011 11:11 To: brett skinner Cc: users@kannel.org Subject: Re: Why does Kannel not use sar_total_segments and sar_segment_seqnum when sending concatenated sms? It means that Kannel doesn't have the ability to re-assemble messages using the sar method. I'm not sure about how extensively used is this method among the carriers, I so far only encountered one case. Regards, Alex On Tue, Jan 18, 2011 at 11:08 AM, brett skinner tatty.dishcl...@gmail.com wrote: Do you mean as far as Kannel is concerned or that most SMSC don't use this method? So I did understand the spec correctly. It is just that everyone chooses to use the UDH method rather? On Tue, Jan 18, 2011 at 11:51 AM, Alejandro Guerrieri alejandro.guerri...@gmail.com wrote: It's not implemented afaik. Only the UDH method is supported. Regards, Alex On Tue, Jan 18, 2011 at 10:47 AM, brett skinner tatty.dishcl...@gmail.com wrote: Hi guys. Does anyone have an ideas to my question below? Thanks, On Thu, Jan 13, 2011 at 11:35 AM, brett skinner tatty.dishcl...@gmail.com wrote: Hi I was looking through the logs and saw that Kannel sends concatenated SMSs using UDH in the Short Message fields. From reading the SMPP spec I was under the impression that the same thing could be achieved by using sar_total_segments and sar_segment_seqnum. Did I misinterpret the spec or does Kannel not use these fields for another reason such as unreliable implementation on the receiving SMSC. Regards,
Why does Kannel not use sar_total_segments and sar_segment_seqnum when sending concatenated sms?
Hi I was looking through the logs and saw that Kannel sends concatenated SMSs using UDH in the Short Message fields. From reading the SMPP spec I was under the impression that the same thing could be achieved by using sar_total_segments and sar_segment_seqnum. Did I misinterpret the spec or does Kannel not use these fields for another reason such as unreliable implementation on the receiving SMSC. Regards,
How does Kannel handle DLR for concatenated sms
Hi I have sent through a couple of long messages. Looking through the logs I can see multiple messages submitted to the SMSC via submit_sm PDUs. However these is only one deliver_sm coming back from the SMSC (at least according to the logs). Is the number of deliver_sm PDUs implementation specific and differ between SMSCs? Is this expected behavior? Or has Kannel done some behind the scenes magic because I have the concatenated flag set to true? Regards,
Concatenated SMS sending
Hello! Please help me to find an answer on the question about concatenated SMS (long messages) sending. Does it possible to send concatenated SMS (long messages) via SMPP connection using Kannel software? If yes, then please tell me, Kannel software send long SMS message attribute using UDH header or SAR optional parameter? Thank you in advance! -- Best regards Sergii Dryga OM Engineer LLC Global Message Services Ukraine Tel.: +380 (44) 284-03-03 (ext.337) Mob.: +380 (50) 465-49-67 E-mail: s.dr...@gmsu.ua ICQ:343-867-653 MSN:s.dr...@gmsu.ua
Re: Concatenated SMS sending
Hi, yes with udh. check the option in the sendsms-user group. 2010/3/12 Sergii Dryga s.dr...@gmsu.ua Hello! Please help me to find an answer on the question about concatenated SMS (long messages) sending. Does it possible to send concatenated SMS (long messages) via SMPP connection using Kannel software? If yes, then please tell me, Kannel software send long SMS message attribute using UDH header or SAR optional parameter? Thank you in advance! -- Best regards Sergii Dryga OM Engineer LLC Global Message Services Ukraine Tel.: +380 (44) 284-03-03 (ext.337) Mob.: +380 (50) 465-49-67 E-mail: s.dr...@gmsu.ua ICQ:343-867-653 MSN:s.dr...@gmsu.ua
Re: Concatenated SMS sending
Hello, Sergii. Yes, it's possible to send concatenated SM using Kannel. Kannel itself uses UDH for concatenation and it's enough to set the following parameters: group = sendsms-user name = user username = user password = topsecret max-messages = 3 concatenation = true Also it's possible to use SAR based concatenation using meta-data functionality (optional TLV). Below you can find part of Kannel configuration. group = smpp-tlv name = sar_msg_ref_num tag=0x020C type= integer length = 2 group = smpp-tlv name = sar_total_segments tag=0x020E type= integer length = 2 group = smpp-tlv name = sar_segment_seqnum tag=0x020F type= integer length = 2 -- Regards, Michael Bochkaryov www.rattler.kiev.ua On Fri, Mar 12, 2010 at 10:55 AM, Sergii Dryga s.dr...@gmsu.ua wrote: Hello! Please help me to find an answer on the question about concatenated SMS (long messages) sending. Does it possible to send concatenated SMS (long messages) via SMPP connection using Kannel software? If yes, then please tell me, Kannel software send long SMS message attribute using UDH header or SAR optional parameter? Thank you in advance! -- Best regards Sergii Dryga OM Engineer LLC Global Message Services Ukraine Tel.: +380 (44) 284-03-03 (ext.337) Mob.: +380 (50) 465-49-67 E-mail: s.dr...@gmsu.ua ICQ:343-867-653 MSN:s.dr...@gmsu.ua
Re: Concatenated SMS sending
Hello Michael, thank you a lot for helping :) Best regards Sergii Dryga OM Engineer LLC Global Message Services Ukraine Tel.: +380 (44) 284-03-03 (ext.337) Mob.: +380 (50) 465-49-67 E-mail: s.dr...@gmsu.ua ICQ:343-867-653 MSN:s.dr...@gmsu.ua On 12.03.2010 12:44, Michael Bochkaryov wrote: Hello, Sergii. Yes, it's possible to send concatenated SM using Kannel. Kannel itself uses UDH for concatenation and it's enough to set the following parameters: group = sendsms-user name = user username = user password = topsecret max-messages = 3 concatenation = true Also it's possible to use SAR based concatenation using meta-data functionality (optional TLV). Below you can find part of Kannel configuration. group = smpp-tlv name = sar_msg_ref_num tag=0x020C type= integer length = 2 group = smpp-tlv name = sar_total_segments tag=0x020E type= integer length = 2 group = smpp-tlv name = sar_segment_seqnum tag=0x020F type= integer length = 2 -- Regards, Michael Bochkaryov www.rattler.kiev.ua http://www.rattler.kiev.ua On Fri, Mar 12, 2010 at 10:55 AM, Sergii Dryga s.dr...@gmsu.ua mailto:s.dr...@gmsu.ua wrote: Hello! Please help me to find an answer on the question about concatenated SMS (long messages) sending. Does it possible to send concatenated SMS (long messages) via SMPP connection using Kannel software? If yes, then please tell me, Kannel software send long SMS message attribute using UDH header or SAR optional parameter? Thank you in advance! -- Best regards Sergii Dryga OM Engineer LLC Global Message Services Ukraine Tel.: +380 (44) 284-03-03 (ext.337) Mob.: +380 (50) 465-49-67 E-mail: s.dr...@gmsu.ua mailto:s.dr...@gmsu.ua ICQ:343-867-653 MSN: s.dr...@gmsu.ua mailto:s.dr...@gmsu.ua
Re: receive concatenated SMS
Dear iain, Thanks for reply, can you please tell me how can I get the patch. thanks. On Sat, Mar 29, 2008 at 3:42 PM, Iain Dooley [EMAIL PROTECTED] wrote: hi hafez, How can I receive concatenated SMS as one hit, not many hits, i have the following confugration for my sms-service: there's a patch on the CVS version that allows this, but if you want to run the release version, i wrote this script which does concatenation in PHP: http://www.workingsoftware.com.au/concatenate_mo.php.txt in order to do this you have to filter all messages through that single URL. i needed to also get the destination phone number to route messages to different applications, so i developed a method of parsing the error logs to find out what number a message was sent *to* instead of what number it was sent from. let me know if you need this snippet. cheers iain group = sms-service keyword = default get-url = http://localhost/scripts/myscript.php?sms_txt_binary=%bsender_number=%preceiver_number=%Psmsc_id=%imessage_coding=%cudh=%uoriginating_smsc=%fmessage_charset=%Cfirst_word=%ksecond_word_encoded=%ssecond_word_uncoded=%Srest_sms_txt=%rsms_txt_spaces_squeezed=%asent_datetime=%tsent_timestamp=%Tsender_number_no_zeros=%qreciver_number_no_zeros=%Qsmsc_id_internal=%Idelivery_report=%ddelivery_report_reply=%Asendsms_user_service=%nmessage_class=%mmwi=%Mbilling_identifier=%Baccount_identifier=%o omit-empty = true max-messages = 10 concatenation = true Any Ideas, Thanks, Hafez -- Hafez A.Ahmad Amman-Jordan mobile:962-785259011 962-795708728 http://blog.hafezadnan.com
Re: receive concatenated SMS
Thanks for reply, can you please tell me how can I get the patch. thanks. i have no idea. i think you just need to check kannel out of CVS. there's instructions on the site. cheers iain On Sat, Mar 29, 2008 at 3:42 PM, Iain Dooley [EMAIL PROTECTED] wrote: hi hafez, How can I receive concatenated SMS as one hit, not many hits, i have the following confugration for my sms-service: there's a patch on the CVS version that allows this, but if you want to run the release version, i wrote this script which does concatenation in PHP: http://www.workingsoftware.com.au/concatenate_mo.php.txt in order to do this you have to filter all messages through that single URL. i needed to also get the destination phone number to route messages to different applications, so i developed a method of parsing the error logs to find out what number a message was sent *to* instead of what number it was sent from. let me know if you need this snippet. cheers iain group = sms-service keyword = default get-url = http://localhost/scripts/myscript.php?sms_txt_binary=%bsender_number=%preceiver_number=%Psmsc_id=%imessage_coding=%cudh=%uoriginating_smsc=%fmessage_charset=%Cfirst_word=%ksecond_word_encoded=%ssecond_word_uncoded=%Srest_sms_txt=%rsms_txt_spaces_squeezed=%asent_datetime=%tsent_timestamp=%Tsender_number_no_zeros=%qreciver_number_no_zeros=%Qsmsc_id_internal=%Idelivery_report=%ddelivery_report_reply=%Asendsms_user_service=%nmessage_class=%mmwi=%Mbilling_identifier=%Baccount_identifier=%o omit-empty = true max-messages = 10 concatenation = true Any Ideas, Thanks, Hafez -- Hafez A.Ahmad Amman-Jordan mobile:962-785259011 962-795708728 http://blog.hafezadnan.com
receive concatenated SMS
Hi All, How can I receive concatenated SMS as one hit, not many hits, i have the following confugration for my sms-service: group = sms-service keyword = default get-url = http://localhost/scripts/myscript.php?sms_txt_binary=%bsender_number=%preceiver_number=%Psmsc_id=%imessage_coding=%cudh=%uoriginating_smsc=%fmessage_charset=%Cfirst_word=%ksecond_word_encoded=%ssecond_word_uncoded=%Srest_sms_txt=%rsms_txt_spaces_squeezed=%asent_datetime=%tsent_timestamp=%Tsender_number_no_zeros=%qreciver_number_no_zeros=%Qsmsc_id_internal=%Idelivery_report=%ddelivery_report_reply=%Asendsms_user_service=%nmessage_class=%mmwi=%Mbilling_identifier=%Baccount_identifier=%o omit-empty = true max-messages = 10 concatenation = true Any Ideas, Thanks, Hafez
Re: receive concatenated SMS
hi hafez, How can I receive concatenated SMS as one hit, not many hits, i have the following confugration for my sms-service: there's a patch on the CVS version that allows this, but if you want to run the release version, i wrote this script which does concatenation in PHP: http://www.workingsoftware.com.au/concatenate_mo.php.txt in order to do this you have to filter all messages through that single URL. i needed to also get the destination phone number to route messages to different applications, so i developed a method of parsing the error logs to find out what number a message was sent *to* instead of what number it was sent from. let me know if you need this snippet. cheers iain group = sms-service keyword = default get-url = http://localhost/scripts/myscript.php?sms_txt_binary=%bsender_number=%preceiver_number=%Psmsc_id=%imessage_coding=%cudh=%uoriginating_smsc=%fmessage_charset=%Cfirst_word=%ksecond_word_encoded=%ssecond_word_uncoded=%Srest_sms_txt=%rsms_txt_spaces_squeezed=%asent_datetime=%tsent_timestamp=%Tsender_number_no_zeros=%qreciver_number_no_zeros=%Qsmsc_id_internal=%Idelivery_report=%ddelivery_report_reply=%Asendsms_user_service=%nmessage_class=%mmwi=%Mbilling_identifier=%Baccount_identifier=%o omit-empty = true max-messages = 10 concatenation = true Any Ideas, Thanks, Hafez
problems with udh (concatenated SMS)
Hi, I try to send concatenated SMS, 15000 characters long, 99 SMSs. With smaller messages, I have no problems, but with this, I get UDH corrupted by kannel. In core group access-log everything is OK: 2007-08-08 20:51:18 Receive SMS [SMSC:5] [SVC:] [ACT:] [BINF:] [from:26392390208295477] [to:1827] [flags:-1:0:-1:0:-1] [msg:153:enaidnieki 513) automashinas; 514) kugji 515) traktori 516) zobenzivis 517) buldozeri 518) sanitaari 519) draugi 520) ienaidnieki 521) automashinas; 522)] [udh:6:0500031D6332] So, this udh: 0500031D6332 means: 05 UDH length 00 IEI, concatenated short messages 03 IE Data length 1D reference number (29) 63 number of short messages in the concatenated short message (99) 32 sequence number of the current short message (50) I use PHP scripts to make one message from such messages, but in my PHP application I do not get this UDH, instead I get something like this: 0500031Dc2 In my smsbox access-log I see: 2007-08-08 20:51:18 SMS HTTP-request sender:26392390208295477 request: '' url: 'http://kannel.mpakalpojumi.lv/writesms.php?text=enaidnieki+513)+automashinas%3 B+514)+kugji+515)+traktori+516)+zobenzivis+517)+buldozeri+518)+sanitaari+519)+draugi+520)+ienaidnieki+521)+automashinas%3B+522)keyword=enaidniekikeyword2=51 3)from=26392390208295477to=1827smsc=5time=2007-08-08+17:51:18drv=-1coding=0charset=ISO-8859-1udh=%05%00%03%1Dc2' reply: 200 ' successful ' What is it? %05%00%03%1Dc2 is not HEX anymore. I use Kannel 1.4.1. My kannel SMS service: # SMS SERVICE Default group = sms-service keyword = default accept-x-kannel-headers = true get-url = http://kannel.mpakalpojumi.lv/writesms.php?text=%akeyword=%kkeyword2=%sfrom=%pto=%Psmsc=%itime=%tdrv=%dcoding=%ccharset=%Cudh=%u; max-messages = 0 omit-empty = true How can I stop kannel to make such conversations? Binary SMS text sometimes also is converted to something meaningless. Ivars
Re: Problem sending concatenated sms (siemens mc35i)
Kavuri Prasad schrieb: Hmm, I used Siemens MC35i, it works fine is handling multiple messages (more Hi Prasad! Thanks for your answer, this is good news! than 160 chars). I guess, you have some configuration problem. If possible post confuguration and OS details, Kannel version etc ... Ok, here we go: This is kannel 1.4.1 on FreeBSD 6.0. Our config looks like this: group = core admin-port = 13000 smsbox-port = 13001 admin-password = nothing admin-deny-ip = *.*.*.* admin-allow-ip = aaa.bbb.ccc.195 log-file = /var/log/kannel.log log-level = 0 box-deny-ip = *.*.*.* box-allow-ip = aaa.bbb.ccc.195 store-file = kannel.store group = smsc smsc = at smsc-id = MC35 modemtype = mc35 speed = 0 #0=automatic device = /dev/cuad0 pin = 1234 preferred-smsc-id = MC35 keepalive = 10 alt-dcs = 1 group = modems id = mc35 name = mc35 detect-string = SIEMENS detect-string2 = MC35 #init-string = AT+CNMI=1,2,0,9,1 #init-string = AT+CSMS=1 init-string = AT+CNMI=3,2,0,1,1 enable-hwhs = AT\\Q3 need-sleep = true speed = 57600 group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 global-sender = 123456 sendsms-chars = 0123456789 +- group = sendsms-user username = user password = password user-deny-ip = *.*.*.* user-allow-ip = aaa.bbb.ccc.23 concatenation = true max-messages = 3 group = sms-service keyword = default omit-empty = true max-messages = 3 concatenation = true get-url = http://foobar...; Thanks, Christian
Re: Problem sending concatenated sms (siemens mc35i)
Hmm, I used Siemens MC35i, it works fine is handling multiple messages (more than 160 chars). I guess, you have some configuration problem. If possible post confuguration and OS details, Kannel version etc ... Regards, Prasad On 11/27/06, Christian Lox [EMAIL PROTECTED] wrote: Hi all! I am experiencing problems when trying to send SMS larger than 160 characters. The log file says: 2006-11-27 15:09:58 [23767] [6] ERROR: AT2[MC35]: Generic error: ERROR 2006-11-27 15:09:58 [23767] [6] DEBUG: AT2[MC35]: send command status: -1 [...] 2006-11-27 15:09:59 [23767] [6] DEBUG: AT2[MC35]: send command status: 1 [...] 2006-11-27 15:10:04 [23767] [6] DEBUG: AT2[MC35]: send command status: 0 [...] 2006-11-27 15:09:58 [23767] [6] DEBUG: Set split msg status to 3 [...] 2006-11-27 15:10:04 [23767] [6] DEBUG: Parts of concatenated message failed. Is it not possible to send concatenated messages with the Siemens MC35i? Or ist this a problem with our configuration? group = sms-service keyword = default omit-empty = true max-messages = 3 concatenation = true Same behaviour with 'concatenation = false'! Thanks for any help, Christian
Problem sending concatenated sms (siemens mc35i)
Hi all! I am experiencing problems when trying to send SMS larger than 160 characters. The log file says: 2006-11-27 15:09:58 [23767] [6] ERROR: AT2[MC35]: Generic error: ERROR 2006-11-27 15:09:58 [23767] [6] DEBUG: AT2[MC35]: send command status: -1 [...] 2006-11-27 15:09:59 [23767] [6] DEBUG: AT2[MC35]: send command status: 1 [...] 2006-11-27 15:10:04 [23767] [6] DEBUG: AT2[MC35]: send command status: 0 [...] 2006-11-27 15:09:58 [23767] [6] DEBUG: Set split msg status to 3 [...] 2006-11-27 15:10:04 [23767] [6] DEBUG: Parts of concatenated message failed. Is it not possible to send concatenated messages with the Siemens MC35i? Or ist this a problem with our configuration? group = sms-service keyword = default omit-empty = true max-messages = 3 concatenation = true Same behaviour with 'concatenation = false'! Thanks for any help, Christian
concatenated SMS
Hi I need to send SMS 160 characters as told in manual i set concatentation = true and max-messages =2 and send the sms via web interface but teh receving phone receives 2 messages and not a contacentated message. If i set concatenation = truethe phonereceives 2 messages but both messages are empty ! and if i set concatenation = false and max-messages = 2the phonereceives 2 messages but it is not concatenated as a single message.. I tried to send these 2 : http://localhost:13131/cgi-bin/sendsms?username=xxxpassword=xxxto=xxxtext=%62%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%udh=%05%00%03%01%02%01% http://localhost:13131/cgi-bin/sendsms?username=xxxpassword=xxxto=xtext=%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%31%udh=%05%00%03%01%02%02% but it doesnt go thru..kannel log shows SMSC returned error code 0X000ff unknown error in response to submit_sm Pls help Thanks Regards Sriram
Concatenated SMS over TDMA/CDMA
Hi, Anyone knows if it is possible to concatenate SMS messages over TDMA/CDMA networks? The main problem I have is that my provider has the UDH filtered, so any message with the udhi_indicator field not being zero gets rejected (or worse, it is accepted but not delivered, or the mobile receives an empty message for each concatenated part). With the //SCKL encoding, it is possible to send many parts, because that encoding has special codes to indicate each part. The parts get reassembled on the phone after the last one is received. The problem is, I am trying to send an iMELODY message that is about 300-400 bytes long. Imelody does not have any way to do that, so I must find a way to spawn the message over 2 o 3 segments. Without the UDH, I didn´t find any way to do that. I´ve tried configuring sendsms to allow concatenation, etc. but it uses the UDH also. Any hints? Thank you in advance,
Concatenated sms
Can anybody help me how to send concatenated sms? Do I have to configure my .conf file?
RE: Concatenated sms
somewhere in conf file, you need to set *max-messages*. This is probably under sendsms-user group. Look into the docs you will get it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Friday, January 09, 2004 10:49 AM To: [EMAIL PROTECTED] Subject: Concatenated sms Can anybody help me how to send concatenated sms? Do I have to configure my .conf file?
