DLRs for concatenated messages
Hi all, I'm seeing some strangeness with DLR handling of concatenated messages sent via SMPP in Kannel 1.5.0. I'm using MySQL for DLR storage and only the first message of the set generates a DLR in the database. My provider, however, follows the specs and returns a DLR for each part. Kannel recognizes the first DLR and updates the database. When the DLRs for the remaining parts arrive, Kannel tries to find them in the database and fails, spitting out an error (see below). Specifically: 1. When the submit_sm_resp PDU for the first message part arrives, Kannel happily creates the DLR in the database: 2011-03-25 02:03:37 [5106] [10] DEBUG: SMPP PDU 0xc8ad960 dump: 2011-03-25 02:03:37 [5106] [10] DEBUG: type_name: submit_sm_resp 2011-03-25 02:03:37 [5106] [10] DEBUG: command_id: 2147483652 = 0x8004 2011-03-25 02:03:37 [5106] [10] DEBUG: command_status: 0 = 0x 2011-03-25 02:03:37 [5106] [10] DEBUG: sequence_number: 17 = 0x0011 2011-03-25 02:03:37 [5106] [10] DEBUG: message_id: 2011-03-25 02:03:37 [5106] [10] DEBUG:Octet string at 0xc8cbc50: 2011-03-25 02:03:37 [5106] [10] DEBUG: len: 20 2011-03-25 02:03:37 [5106] [10] DEBUG: size: 21 2011-03-25 02:03:37 [5106] [10] DEBUG: immutable: 0 2011-03-25 02:03:37 [5106] [10] DEBUG: data: 31 33 30 30 39 38 39 38 31 37 36 36 36 31 38 33 1300989817666183 2011-03-25 02:03:37 [5106] [10] DEBUG: data: 30 34 30 32 0402 2011-03-25 02:03:37 [5106] [10] DEBUG:Octet string dump ends. 2011-03-25 02:03:37 [5106] [10] DEBUG: SMPP PDU dump ends. 2011-03-25 02:03:37 [5106] [10] DEBUG: DLR[mysql]: Adding DLR smsc=MY-SMPP-CONNECTION, ts=13009898176661830402, src=test, dst=9, mask=31, boxc=smsbox 2011-03-25 02:03:37 [5106] [10] DEBUG: adding DLR entry into database 2011-03-25 02:03:37 [5106] [10] DEBUG: sql: INSERT INTO `smsgw_kannel_sms_dlr` (`smsc`, `timestamp`, `source`, `destination`, `service`, `url`, `mask`, `boxc_id`, `status`) VALUES (?, ?, ?, ?, ?, ?, ?, ?, 0) 2. When the submit_sm_resp PDU for the subsequent message parts arrive, Kannel doesn't create a database DLR but instead appears to create one in memory (note the missing SQL): 2011-03-25 02:03:38 [5106] [10] DEBUG: SMPP PDU 0xc8ad960 dump: 2011-03-25 02:03:38 [5106] [10] DEBUG: type_name: submit_sm_resp 2011-03-25 02:03:38 [5106] [10] DEBUG: command_id: 2147483652 = 0x8004 2011-03-25 02:03:38 [5106] [10] DEBUG: command_status: 0 = 0x 2011-03-25 02:03:38 [5106] [10] DEBUG: sequence_number: 18 = 0x0012 2011-03-25 02:03:38 [5106] [10] DEBUG: message_id: 2011-03-25 02:03:38 [5106] [10] DEBUG:Octet string at 0xc8d1d80: 2011-03-25 02:03:38 [5106] [10] DEBUG: len: 20 2011-03-25 02:03:38 [5106] [10] DEBUG: size: 21 2011-03-25 02:03:38 [5106] [10] DEBUG: immutable: 0 2011-03-25 02:03:38 [5106] [10] DEBUG: data: 31 33 30 30 39 38 39 38 31 37 39 33 34 31 38 34 1300989817934184 2011-03-25 02:03:38 [5106] [10] DEBUG: data: 30 34 30 32 0402 2011-03-25 02:03:38 [5106] [10] DEBUG:Octet string dump ends. 2011-03-25 02:03:38 [5106] [10] DEBUG: SMPP PDU dump ends. 2011-03-25 02:03:38 [5106] [10] DEBUG: SMSC[MY-SMPP-CONNECTION]: creating DLR message 2011-03-25 02:03:38 [5106] [10] DEBUG: SMSC[MY-SMPP-CONNECTION]: DLR = 3. When the deliver_sm PDU arrives for the first message part, it's correctly matched against the database, processed and deleted: 2011-03-25 02:03:48 [5106] [10] DEBUG: SMPP PDU 0xc8ad960 dump: 2011-03-25 02:03:48 [5106] [10] DEBUG: type_name: deliver_sm 2011-03-25 02:03:48 [5106] [10] DEBUG: command_id: 5 = 0x0005 2011-03-25 02:03:48 [5106] [10] DEBUG: command_status: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: sequence_number: 8 = 0x0008 2011-03-25 02:03:48 [5106] [10] DEBUG: service_type: NULL 2011-03-25 02:03:48 [5106] [10] DEBUG: source_addr_ton: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: source_addr_npi: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: source_addr: 9 2011-03-25 02:03:48 [5106] [10] DEBUG: dest_addr_ton: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: dest_addr_npi: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: destination_addr: test 2011-03-25 02:03:48 [5106] [10] DEBUG: esm_class: 4 = 0x0004 2011-03-25 02:03:48 [5106] [10] DEBUG: protocol_id: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: priority_flag: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: schedule_delivery_time: NULL 2011-03-25 02:03:48 [5106] [10] DEBUG: validity_period: NULL 2011-03-25 02:03:48 [5106] [10] DEBUG: registered_delivery: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: replace_if_present_flag: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: data_coding: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: sm_default_msg_id: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: sm_length: 165 = 0x00a5 2011-03-25 02:03:48 [5106] [10] DEBUG: short_message
Re: DLRs for concatenated messages
Hi That is the way kannel handles dlr for concatenated messages. There has been several threads regarding how to improve this but nothing has been done. |-| 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.NET www.smsglobal.com.mx y www.pravcom.com On Thu, Mar 24, 2011 at 1:29 PM, Toby Phipps toby.phi...@nexmedia.com.sg wrote: Hi all, I'm seeing some strangeness with DLR handling of concatenated messages sent via SMPP in Kannel 1.5.0. I'm using MySQL for DLR storage and only the first message of the set generates a DLR in the database. My provider, however, follows the specs and returns a DLR for each part. Kannel recognizes the first DLR and updates the database. When the DLRs for the remaining parts arrive, Kannel tries to find them in the database and fails, spitting out an error (see below). Specifically: 1. When the submit_sm_resp PDU for the first message part arrives, Kannel happily creates the DLR in the database: 2011-03-25 02:03:37 [5106] [10] DEBUG: SMPP PDU 0xc8ad960 dump: 2011-03-25 02:03:37 [5106] [10] DEBUG: type_name: submit_sm_resp 2011-03-25 02:03:37 [5106] [10] DEBUG: command_id: 2147483652 = 0x8004 2011-03-25 02:03:37 [5106] [10] DEBUG: command_status: 0 = 0x 2011-03-25 02:03:37 [5106] [10] DEBUG: sequence_number: 17 = 0x0011 2011-03-25 02:03:37 [5106] [10] DEBUG: message_id: 2011-03-25 02:03:37 [5106] [10] DEBUG: Octet string at 0xc8cbc50: 2011-03-25 02:03:37 [5106] [10] DEBUG: len: 20 2011-03-25 02:03:37 [5106] [10] DEBUG: size: 21 2011-03-25 02:03:37 [5106] [10] DEBUG: immutable: 0 2011-03-25 02:03:37 [5106] [10] DEBUG: data: 31 33 30 30 39 38 39 38 31 37 36 36 36 31 38 33 1300989817666183 2011-03-25 02:03:37 [5106] [10] DEBUG: data: 30 34 30 32 0402 2011-03-25 02:03:37 [5106] [10] DEBUG: Octet string dump ends. 2011-03-25 02:03:37 [5106] [10] DEBUG: SMPP PDU dump ends. 2011-03-25 02:03:37 [5106] [10] DEBUG: DLR[mysql]: Adding DLR smsc=MY-SMPP-CONNECTION, ts=13009898176661830402, src=test, dst=9, mask=31, boxc=smsbox 2011-03-25 02:03:37 [5106] [10] DEBUG: adding DLR entry into database 2011-03-25 02:03:37 [5106] [10] DEBUG: sql: INSERT INTO `smsgw_kannel_sms_dlr` (`smsc`, `timestamp`, `source`, `destination`, `service`, `url`, `mask`, `boxc_id`, `status`) VALUES (?, ?, ?, ?, ?, ?, ?, ?, 0) 2. When the submit_sm_resp PDU for the subsequent message parts arrive, Kannel doesn't create a database DLR but instead appears to create one in memory (note the missing SQL): 2011-03-25 02:03:38 [5106] [10] DEBUG: SMPP PDU 0xc8ad960 dump: 2011-03-25 02:03:38 [5106] [10] DEBUG: type_name: submit_sm_resp 2011-03-25 02:03:38 [5106] [10] DEBUG: command_id: 2147483652 = 0x8004 2011-03-25 02:03:38 [5106] [10] DEBUG: command_status: 0 = 0x 2011-03-25 02:03:38 [5106] [10] DEBUG: sequence_number: 18 = 0x0012 2011-03-25 02:03:38 [5106] [10] DEBUG: message_id: 2011-03-25 02:03:38 [5106] [10] DEBUG: Octet string at 0xc8d1d80: 2011-03-25 02:03:38 [5106] [10] DEBUG: len: 20 2011-03-25 02:03:38 [5106] [10] DEBUG: size: 21 2011-03-25 02:03:38 [5106] [10] DEBUG: immutable: 0 2011-03-25 02:03:38 [5106] [10] DEBUG: data: 31 33 30 30 39 38 39 38 31 37 39 33 34 31 38 34 1300989817934184 2011-03-25 02:03:38 [5106] [10] DEBUG: data: 30 34 30 32 0402 2011-03-25 02:03:38 [5106] [10] DEBUG: Octet string dump ends. 2011-03-25 02:03:38 [5106] [10] DEBUG: SMPP PDU dump ends. 2011-03-25 02:03:38 [5106] [10] DEBUG: SMSC[MY-SMPP-CONNECTION]: creating DLR message 2011-03-25 02:03:38 [5106] [10] DEBUG: SMSC[MY-SMPP-CONNECTION]: DLR = 3. When the deliver_sm PDU arrives for the first message part, it's correctly matched against the database, processed and deleted: 2011-03-25 02:03:48 [5106] [10] DEBUG: SMPP PDU 0xc8ad960 dump: 2011-03-25 02:03:48 [5106] [10] DEBUG: type_name: deliver_sm 2011-03-25 02:03:48 [5106] [10] DEBUG: command_id: 5 = 0x0005 2011-03-25 02:03:48 [5106] [10] DEBUG: command_status: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: sequence_number: 8 = 0x0008 2011-03-25 02:03:48 [5106] [10] DEBUG: service_type: NULL 2011-03-25 02:03:48 [5106] [10] DEBUG: source_addr_ton: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: source_addr_npi: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: source_addr: 9 2011-03-25 02:03:48 [5106] [10] DEBUG: dest_addr_ton: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: dest_addr_npi: 0 = 0x 2011-03-25 02:03:48 [5106] [10] DEBUG: destination_addr: test 2011-03-25 02:03:48 [5106] [10] DEBUG: esm_class: 4 = 0x0004 2011-03-25 02
RE: DLRs for concatenated messages
Hi Alvaro, Thanks for the feedback. Any insight into why it was implemented this way? i.e. is there reason why each of the submit_sm_resp PDUs shouldn't generate a separate DLR in the DB? The only reason I can come up with offhand is that the current way probably handles misbehaving SMPP servers better - servers that send one DLR per concatenated message rather than per part. However, the current (broken, IMHO) behaviour could easily be maintained with a config parameter. Before I scope a patch to address this, any comments or disagreements? Also, I haven't tried this with memory-only DLRs - is this an issue limited to SQL DLR storage? From looking at my logs, it seems that a DLR is indeed created in memory for the second and subsequent message parts, just not written to the DB. Thanks, Toby -Original Message- From: Alvaro Cornejo [mailto:cornejo.alv...@gmail.com] Sent: Friday, March 25, 2011 1:47 AM To: Toby Phipps Cc: users@kannel.org Subject: Re: DLRs for concatenated messages Hi That is the way kannel handles dlr for concatenated messages. There has been several threads regarding how to improve this but nothing has been done. |--- --| 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.NET www.smsglobal.com.mx y www.pravcom.com On Thu, Mar 24, 2011 at 1:29 PM, Toby Phipps toby.phi...@nexmedia.com.sg wrote: Hi all, I'm seeing some strangeness with DLR handling of concatenated messages sent via SMPP in Kannel 1.5.0. I'm using MySQL for DLR storage and only the first message of the set generates a DLR in the database. My provider, however, follows the specs and returns a DLR for each part. Kannel recognizes the first DLR and updates the database. When the DLRs for the remaining parts arrive, Kannel tries to find them in the database and fails, spitting out an error (see below). Specifically: 1. When the submit_sm_resp PDU for the first message part arrives, Kannel happily creates the DLR in the database: 2011-03-25 02:03:37 [5106] [10] DEBUG: SMPP PDU 0xc8ad960 dump: 2011-03-25 02:03:37 [5106] [10] DEBUG: type_name: submit_sm_resp 2011-03-25 02:03:37 [5106] [10] DEBUG: command_id: 2147483652 = 0x8004 2011-03-25 02:03:37 [5106] [10] DEBUG: command_status: 0 = 0x 2011-03-25 02:03:37 [5106] [10] DEBUG: sequence_number: 17 = 0x0011 2011-03-25 02:03:37 [5106] [10] DEBUG: message_id: 2011-03-25 02:03:37 [5106] [10] DEBUG: Octet string at 0xc8cbc50: 2011-03-25 02:03:37 [5106] [10] DEBUG: len: 20 2011-03-25 02:03:37 [5106] [10] DEBUG: size: 21 2011-03-25 02:03:37 [5106] [10] DEBUG: immutable: 0 2011-03-25 02:03:37 [5106] [10] DEBUG: data: 31 33 30 30 39 38 39 38 31 37 36 36 36 31 38 33 1300989817666183 2011-03-25 02:03:37 [5106] [10] DEBUG: data: 30 34 30 32 0402 2011-03-25 02:03:37 [5106] [10] DEBUG: Octet string dump ends. 2011-03-25 02:03:37 [5106] [10] DEBUG: SMPP PDU dump ends. 2011-03-25 02:03:37 [5106] [10] DEBUG: DLR[mysql]: Adding DLR smsc=MY-SMPP-CONNECTION, ts=13009898176661830402, src=test, dst=9, mask=31, boxc=smsbox 2011-03-25 02:03:37 [5106] [10] DEBUG: adding DLR entry into database 2011-03-25 02:03:37 [5106] [10] DEBUG: sql: INSERT INTO `smsgw_kannel_sms_dlr` (`smsc`, `timestamp`, `source`, `destination`, `service`, `url`, `mask`, `boxc_id`, `status`) VALUES (?, ?, ?, ?, ?, ?, ?, ?, 0) 2. When the submit_sm_resp PDU for the subsequent message parts arrive, Kannel doesn't create a database DLR but instead appears to create one in memory (note the missing SQL): 2011-03-25 02:03:38 [5106] [10] DEBUG: SMPP PDU 0xc8ad960 dump: 2011-03-25 02:03:38 [5106] [10] DEBUG: type_name: submit_sm_resp 2011-03-25 02:03:38 [5106] [10] DEBUG: command_id: 2147483652 = 0x8004 2011-03-25 02:03:38 [5106] [10] DEBUG: command_status: 0 = 0x 2011-03-25 02:03:38 [5106] [10] DEBUG: sequence_number: 18 = 0x0012 2011-03-25 02:03:38 [5106] [10] DEBUG: message_id: 2011-03-25 02:03:38 [5106] [10] DEBUG: Octet string at 0xc8d1d80: 2011-03-25 02:03:38 [5106] [10] DEBUG: len: 20 2011-03-25 02:03:38 [5106] [10] DEBUG: size: 21 2011-03-25 02:03:38 [5106] [10] DEBUG: immutable: 0 2011-03-25 02:03:38 [5106] [10] DEBUG: data: 31 33 30 30 39 38 39 38 31 37 39 33 34 31 38 34 1300989817934184 2011-03-25 02:03:38 [5106] [10] DEBUG: data: 30 34 30 32 0402 2011-03-25 02:03:38 [5106] [10] DEBUG: Octet string dump ends. 2011-03-25 02:03:38 [5106] [10] DEBUG: SMPP PDU dump ends. 2011-03-25 02:03:38 [5106] [10] DEBUG: SMSC[MY-SMPP-CONNECTION]: creating DLR message 2011-03-25 02:03:38 [5106] [10] DEBUG: SMSC[MY-SMPP-CONNECTION]: DLR = 3
Re: DLRs for concatenated messages
Hi From my understanting - I'm not a developper- the issue is what to do when only one part of the concatenated fails -resend the whole/failed part- and how/when to validate the original full initial message. it seems that type of messafe handling will require to have a separate queue/buffer for concatenated messages in order to be able to track the whole message. Maybe you can do a search on the mailing list for concatenated messages and will find the threads between devs people. 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.NET www.smsglobal.com.mx y www.pravcom.com On Thu, Mar 24, 2011 at 2:00 PM, Toby Phipps toby.phi...@nexmedia.com.sg wrote: Hi Alvaro, Thanks for the feedback. Any insight into why it was implemented this way? i.e. is there reason why each of the submit_sm_resp PDUs shouldn't generate a separate DLR in the DB? The only reason I can come up with offhand is that the current way probably handles misbehaving SMPP servers better - servers that send one DLR per concatenated message rather than per part. However, the current (broken, IMHO) behaviour could easily be maintained with a config parameter. Before I scope a patch to address this, any comments or disagreements? Also, I haven't tried this with memory-only DLRs - is this an issue limited to SQL DLR storage? From looking at my logs, it seems that a DLR is indeed created in memory for the second and subsequent message parts, just not written to the DB. Thanks, Toby -Original Message- From: Alvaro Cornejo [mailto:cornejo.alv...@gmail.com] Sent: Friday, March 25, 2011 1:47 AM To: Toby Phipps Cc: users@kannel.org Subject: Re: DLRs for concatenated messages Hi That is the way kannel handles dlr for concatenated messages. There has been several threads regarding how to improve this but nothing has been done. |--- --| 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.NET www.smsglobal.com.mx y www.pravcom.com On Thu, Mar 24, 2011 at 1:29 PM, Toby Phipps toby.phi...@nexmedia.com.sg wrote: Hi all, I'm seeing some strangeness with DLR handling of concatenated messages sent via SMPP in Kannel 1.5.0. I'm using MySQL for DLR storage and only the first message of the set generates a DLR in the database. My provider, however, follows the specs and returns a DLR for each part. Kannel recognizes the first DLR and updates the database. When the DLRs for the remaining parts arrive, Kannel tries to find them in the database and fails, spitting out an error (see below). Specifically: 1. When the submit_sm_resp PDU for the first message part arrives, Kannel happily creates the DLR in the database: 2011-03-25 02:03:37 [5106] [10] DEBUG: SMPP PDU 0xc8ad960 dump: 2011-03-25 02:03:37 [5106] [10] DEBUG: type_name: submit_sm_resp 2011-03-25 02:03:37 [5106] [10] DEBUG: command_id: 2147483652 = 0x8004 2011-03-25 02:03:37 [5106] [10] DEBUG: command_status: 0 = 0x 2011-03-25 02:03:37 [5106] [10] DEBUG: sequence_number: 17 = 0x0011 2011-03-25 02:03:37 [5106] [10] DEBUG: message_id: 2011-03-25 02:03:37 [5106] [10] DEBUG: Octet string at 0xc8cbc50: 2011-03-25 02:03:37 [5106] [10] DEBUG: len: 20 2011-03-25 02:03:37 [5106] [10] DEBUG: size: 21 2011-03-25 02:03:37 [5106] [10] DEBUG: immutable: 0 2011-03-25 02:03:37 [5106] [10] DEBUG: data: 31 33 30 30 39 38 39 38 31 37 36 36 36 31 38 33 1300989817666183 2011-03-25 02:03:37 [5106] [10] DEBUG: data: 30 34 30 32 0402 2011-03-25 02:03:37 [5106] [10] DEBUG: Octet string dump ends. 2011-03-25 02:03:37 [5106] [10] DEBUG: SMPP PDU dump ends. 2011-03-25 02:03:37 [5106] [10] DEBUG: DLR[mysql]: Adding DLR smsc=MY-SMPP-CONNECTION, ts=13009898176661830402, src=test, dst=9, mask=31, boxc=smsbox 2011-03-25 02:03:37 [5106] [10] DEBUG: adding DLR entry into database 2011-03-25 02:03:37 [5106] [10] DEBUG: sql: INSERT INTO `smsgw_kannel_sms_dlr` (`smsc`, `timestamp`, `source`, `destination`, `service`, `url`, `mask`, `boxc_id`, `status`) VALUES (?, ?, ?, ?, ?, ?, ?, ?, 0) 2. When the submit_sm_resp PDU for the subsequent message parts arrive, Kannel doesn't create a database DLR but instead appears to create one in memory (note the missing SQL): 2011-03-25 02:03:38 [5106] [10] DEBUG: SMPP PDU 0xc8ad960 dump: 2011-03-25 02:03:38 [5106] [10] DEBUG: type_name: submit_sm_resp 2011-03-25 02:03:38
Issue with concatenated messages and load balancing over SMPP
I'm currently using Kannel from last SVN in such configuration: CGI PUSH -- SMSBOX 1 -- BEARERBOX 1 -- SMPP LINK -- Open SMPPBOX --- BEARERBOX 2 To BEARERBOX 2 I have connected 3 SMSC via AT2. Each SMSC have the same smsc-id to make load balancing available. When I push a MT Message to CGI interface of SMSBOX 1 which is longer than 160 chars, it is concatenated and BEARERBOX 1 sends two submit_sm PDUs to BEARERBOX 2 via SMPPBOX. But BEARERBOX 2 sends each part of concatenated message via different SMSC (make load balancing for each part of concatenated msg) which makes the message unavailable to read on mobile. I think that BEARERBOX 2 doesn't know that these two messages are parts of one message and should be sent via the same SMSC. I can attach some logs if they are needed. If you could please help me to fix this issue. Thank you. Regarards, Tomasz
Re: Issue with concatenated messages and load balancing over SMPP
Hi, You are not using correct configuration for load-balancing. Use different smsc-id for each smsc and simply do not specify smsc in your sendsms url. Kannel will load-balance SMS using rand() and load on each smsc. This will allow finer control (load) over your smscs, since when you want to use a specific SMSc (termination issues?) you can still direct to a specific SMSc from your sendsms URL. For that you will want to specify preferred-smsc-id as itself in each smsc definition. However, I suspect that this will not fix your problem. For a fix, SMPPbox needs to reassemble SMS to 1 before sending it to bearerbox 2. Any takers on that? BR, Nikos - Original Message - From: Tomasz ad...@impexrur.pl To: users@kannel.org Sent: Tuesday, June 15, 2010 11:25 AM Subject: Issue with concatenated messages and load balancing over SMPP I'm currently using Kannel from last SVN in such configuration: CGI PUSH -- SMSBOX 1 -- BEARERBOX 1 -- SMPP LINK -- Open SMPPBOX --- BEARERBOX 2 To BEARERBOX 2 I have connected 3 SMSC via AT2. Each SMSC have the same smsc-id to make load balancing available. When I push a MT Message to CGI interface of SMSBOX 1 which is longer than 160 chars, it is concatenated and BEARERBOX 1 sends two submit_sm PDUs to BEARERBOX 2 via SMPPBOX. But BEARERBOX 2 sends each part of concatenated message via different SMSC (make load balancing for each part of concatenated msg) which makes the message unavailable to read on mobile. I think that BEARERBOX 2 doesn't know that these two messages are parts of one message and should be sent via the same SMSC. I can attach some logs if they are needed. If you could please help me to fix this issue. Thank you. Regarards, Tomasz
Re: Issue with concatenated messages and load balancing over SMPP
Hi Nikos, Sorry, I didn't make it so clear in my first post. I use other smsc-id for each SMSC but I use also some virtual smsc-id at allowed-smsc-id which is identical for several SMSC. It allows me to make several SMSC groups with load balancing - each group has several modems. Then I specify this virtual smsc-id in SMPPBOX config (route-to-smsc) and kannel makes load-balancing :) Everything works great with non-concatenated messages. I've also found that issue is caused by SMPPBOX as it pass to bearerbox two messages (received from BB 1) instead of 1. It makes that each part of concatenated is being sent via different smsc, due to load balancing. Regards, Tomasz Hi, You are not using correct configuration for load-balancing. Use different smsc-id for each smsc and simply do not specify smsc in your sendsms url. Kannel will load-balance SMS using rand() and load on each smsc. This will allow finer control (load) over your smscs, since when you want to use a specific SMSc (termination issues?) you can still direct to a specific SMSc from your sendsms URL. For that you will want to specify preferred-smsc-id as itself in each smsc definition. However, I suspect that this will not fix your problem. For a fix, SMPPbox needs to reassemble SMS to 1 before sending it to bearerbox 2. Any takers on that? BR, Nikos
Re: Issue with concatenated messages and load balancing over SMPP
Yes. That is pretty much what I said (concerning concatenation). SMPPbox seems to need a patch for that. @Rene: Have you come across this issue in production? BR, Nikos - Original Message - From: Tomasz ad...@impexrur.pl To: users@kannel.org Sent: Tuesday, June 15, 2010 3:31 PM Subject: Re: Issue with concatenated messages and load balancing over SMPP Hi Nikos, Sorry, I didn't make it so clear in my first post. I use other smsc-id for each SMSC but I use also some virtual smsc-id at allowed-smsc-id which is identical for several SMSC. It allows me to make several SMSC groups with load balancing - each group has several modems. Then I specify this virtual smsc-id in SMPPBOX config (route-to-smsc) and kannel makes load-balancing :) Everything works great with non-concatenated messages. I've also found that issue is caused by SMPPBOX as it pass to bearerbox two messages (received from BB 1) instead of 1. It makes that each part of concatenated is being sent via different smsc, due to load balancing. Regards, Tomasz Hi, You are not using correct configuration for load-balancing. Use different smsc-id for each smsc and simply do not specify smsc in your sendsms url. Kannel will load-balance SMS using rand() and load on each smsc. This will allow finer control (load) over your smscs, since when you want to use a specific SMSc (termination issues?) you can still direct to a specific SMSc from your sendsms URL. For that you will want to specify preferred-smsc-id as itself in each smsc definition. However, I suspect that this will not fix your problem. For a fix, SMPPbox needs to reassemble SMS to 1 before sending it to bearerbox 2. Any takers on that? BR, Nikos
RE: Issue with concatenated messages and load balancing over SMPP
Yes, it seems to be a bug in the current version. -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: dinsdag 15 juni 2010 15:35 To: Tomasz; rene.klu...@chimit.nl Cc: users@kannel.org Subject: Re: Issue with concatenated messages and load balancing over SMPP Yes. That is pretty much what I said (concerning concatenation). SMPPbox seems to need a patch for that. @Rene: Have you come across this issue in production? BR, Nikos - Original Message - From: Tomasz ad...@impexrur.pl To: users@kannel.org Sent: Tuesday, June 15, 2010 3:31 PM Subject: Re: Issue with concatenated messages and load balancing over SMPP Hi Nikos, Sorry, I didn't make it so clear in my first post. I use other smsc-id for each SMSC but I use also some virtual smsc-id at allowed-smsc-id which is identical for several SMSC. It allows me to make several SMSC groups with load balancing - each group has several modems. Then I specify this virtual smsc-id in SMPPBOX config (route-to-smsc) and kannel makes load-balancing :) Everything works great with non-concatenated messages. I've also found that issue is caused by SMPPBOX as it pass to bearerbox two messages (received from BB 1) instead of 1. It makes that each part of concatenated is being sent via different smsc, due to load balancing. Regards, Tomasz Hi, You are not using correct configuration for load-balancing. Use different smsc-id for each smsc and simply do not specify smsc in your sendsms url. Kannel will load-balance SMS using rand() and load on each smsc. This will allow finer control (load) over your smscs, since when you want to use a specific SMSc (termination issues?) you can still direct to a specific SMSc from your sendsms URL. For that you will want to specify preferred-smsc-id as itself in each smsc definition. However, I suspect that this will not fix your problem. For a fix, SMPPbox needs to reassemble SMS to 1 before sending it to bearerbox 2. Any takers on that? BR, Nikos
Problem with Concatenated Messages
Hello Group, I'm having trouble when I submit concatenated messages. Seems like they are not acknowledged properly from the upstream. Most of the messages are retrying and are getting delivered multiple times. My log has the following warning. 2009-08-25 05:11:09 [5575] [10] WARNING: SMPP[SMPP1]: Not ACKED message found, will retransmit. SENT63sec. ago, SEQ47554, DST 2009-08-25 05:11:09 [5575] [11] WARNING: SMPP[SMPP1]: Not ACKED message found, will retransmit. SENT64sec. ago, SEQ46527, DST 2009-08-25 05:11:09 [5575] [11] WARNING: SMPP[SMPP1]: Not ACKED message found, will retransmit. SENT64sec. ago, SEQ46528, DST 2009-08-25 05:11:09 [5575] [11] WARNING: SMPP[SMPP1]: Not ACKED message found, will retransmit. SENT63sec. ago, SEQ46529, DST 2009-08-25 05:11:09 [5575] [11] WARNING: SMPP[SMPP1]: Not ACKED message found, will retransmit. SENT63sec. ago, SEQ46530, DST Is there anything to configure at my end to solve this? Thanks Jinson Abraham
Re: Reply: Regular and concatenated messages
Piyush 1) Sure, if the message is of more that 160chars, kanel will split it into n parts automatically. I think there is a patch on CVS that allows kannel to report the number of parts the message was splitted into. Note that if the message is splited, each chunk will be of no more that 154chars since splitting need some overhead in order to allow recipients to reconstruct the original message. Also take not that this char limit depend ond the coding you use (ie 7 or 8 bits) 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.NET www.smsglobal.com.mx y www.pravcom.com On Tue, Jun 16, 2009 at 11:39 PM, Piyushpiy...@ibibo.com wrote: Thanks Alvaro. 1.) Yes, I need it on the basis of billing. I can use only one account i.e. group = sendsms-user username = XX password = XX max-messages = 3 concatenation = true But message of 160 characters will consume 2 messages. Thats why I used two accounts. I just wanted to confirm... is this is the right approach? 2.) When I use first account i.e. group = sendsms-user username = abcdef password = abcdef I do get foreign message id in both DLR (8 1). But when I use second account and message length crosses 160 characters i.e group = sendsms-user username = pqrst password = pqrst max-messages = 3 concatenation = true I don't get foreign message id in first DLR when status=8, but I do get message id in second DLR(1). I want to know, how to resolve this issue? Thanks regards, Piyush Khandelwal -- Original Message -- From: Alvaro Cornejocornejo.alv...@gmail.com; Date: Jun 16, 2009 06:54 PM To: Piyushpiy...@ibibo.com; Cc: usersusers@kannel.org; Subject: Re: Regular and concatenated messages 1) You can use the same useraccount for both types of messages. You might want to separate them for easily billing or stat, but for kannel is not important. 2) Kannel can not privide you the foreing_id in the first dlr since its connection to smsc is asyncronous. When you receive an dlr=8 means KANNEL received the message, not the telco smsc. 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.NET www.smsglobal.com.mx y www.pravcom.com On Tue, Jun 16, 2009 at 4:14 AM, Piyushpiy...@ibibo.com wrote: Hi, I have two sendsms-user accounts. One for sending regular(160 characters) and another for long messages(more then 160). group = sendsms-user username = XX password = XX group = sendsms-user username = XX password = XX max-messages = 3 concatenation = true I can able to send messages correctly from both the accounts. Now I want to know... 1.) Is this the right way to send both regular and concatenated messages? 2.) I am not getting foreign message id, in the first delivery report(when statusis being set to 8). What can be the reason for this? Thanks in advance, Piyush ibibo Mail :: Get your mail box with Music, Skins, Greetings and Stationery now! ibibo Mail :: Get your FREE mail box with Music, Skins, Greetings and Stationery now!
problem and solution sending concatenated messages by inserting into send_sms (sqlbox, smpp)
Hi all when I tried to send long message (over 160 chars) by inserting into send_sms table, message was corrupted or wasn't delivered. The same message sent by http call was delivered. Problem was in coding value. While I send message by http request without coding value set, kannel set it by default to 0. The same data inserted into send_sms, without coding value set (no default value for coding field in table set, so null value set), after insert was message processed by sqlbox/kannel and coding was set to 4 (value from log files). So solution is to set default value in send_sms table or while inserting into send_sms table fill coding field too. May be it will help to someone. Sincerely, Stefan
Regular and concatenated messages
Hi, I have two sendsms-user accounts. One for sending regular(160 characters) and another for long messages(more then 160). group = sendsms-user username = XX password = XX group = sendsms-user username = XX password = XX max-messages = 3 concatenation = true I can able to send messages correctly from both the accounts. Now I want to know... 1.) Is this the right way to send both regular and concatenated messages? 2.) I am not getting foreign message id, in the first delivery report(when statusis being set to 8). What can be the reason for this? Thanks in advance, Piyush ibibo Mail :: Get your mail box with Music, Skins, Greetings and Stationery now!
Re: Regular and concatenated messages
1) You can use the same useraccount for both types of messages. You might want to separate them for easily billing or stat, but for kannel is not important. 2) Kannel can not privide you the foreing_id in the first dlr since its connection to smsc is asyncronous. When you receive an dlr=8 means KANNEL received the message, not the telco smsc. 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.NET www.smsglobal.com.mx y www.pravcom.com On Tue, Jun 16, 2009 at 4:14 AM, Piyushpiy...@ibibo.com wrote: Hi, I have two sendsms-user accounts. One for sending regular(160 characters) and another for long messages(more then 160). group = sendsms-user username = XX password = XX group = sendsms-user username = XX password = XX max-messages = 3 concatenation = true I can able to send messages correctly from both the accounts. Now I want to know... 1.) Is this the right way to send both regular and concatenated messages? 2.) I am not getting foreign message id, in the first delivery report(when statusis being set to 8). What can be the reason for this? Thanks in advance, Piyush ibibo Mail :: Get your mail box with Music, Skins, Greetings and Stationery now!
Re: problem and solution sending concatenated messages by inserting into send_sms (sqlbox, smpp)
Hi Stefan, very cool, thanks for the hint. To which coding value have you set the sms in the send_sms table ? text sms should be most of the time as coding=0, while binary sms (like concatenated) should go as coding=1 Which one were you using ? I suppose coding=0 (as it could be by default using the smsbox) Julien 2009/6/16 Stefan Mada m...@beesoft.sk: Hi all when I tried to send long message (over 160 chars) by inserting into send_sms table, message was corrupted or wasn't delivered. The same message sent by http call was delivered. Problem was in coding value. While I send message by http request without coding value set, kannel set it by default to 0. The same data inserted into send_sms, without coding value set (no default value for coding field in table set, so null value set), after insert was message processed by sqlbox/kannel and coding was set to 4 (value from log files). So solution is to set default value in send_sms table or while inserting into send_sms table fill coding field too. May be it will help to someone. Sincerely, Stefan -- Julien Buratto
Reply: Regular and concatenated messages
Thanks Alvaro. 1.) Yes, I need it on the basis of billing. I can use only one account i.e. group = sendsms-user username = XX password = XX max-messages = 3 concatenation = true But message of 160 characters will consume 2 messages. Thats why I used two accounts. I just wanted to confirm... is this is the right approach? 2.) When I use first account i.e. group = sendsms-user username = abcdef password = abcdef I do get foreign message id in both DLR (8 1). But when I use second account and message length crosses 160 characters i.e group = sendsms-user username = pqrst password = pqrst max-messages = 3 concatenation = true I don't get foreign message id in first DLR when status=8, but I do get message id in second DLR(1). I want to know, how to resolve this issue? Thanks regards, Piyush Khandelwal -- Original Message -- From: Alvaro Cornejocornejo.alv...@gmail.com; Date: Jun 16, 2009 06:54 PM To: Piyushpiy...@ibibo.com; Cc: usersusers@kannel.org; Subject: Re: Regular and concatenated messages 1) You can use the same useraccount for both types of messages. You might want to separate them for easily billing or stat, but for kannel is not important. 2) Kannel can not privide you the foreing_id in the first dlr since its connection to smsc is asyncronous. When you receive an dlr=8 means KANNEL received the message, not the telco smsc. 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.NET www.smsglobal.com.mx y www.pravcom.com On Tue, Jun 16, 2009 at 4:14 AM, Piyushpiy...@ibibo.com wrote: Hi, I have two sendsms-user accounts. One for sending regular(160 characters) and another for long messages(more then 160). group = sendsms-user username = XX password = XX group = sendsms-user username = XX password = XX max-messages = 3 concatenation = true I can able to send messages correctly from both the accounts. Now I want to know... 1.) Is this the right way to send both regular and concatenated messages? 2.) I am not getting foreign message id, in the first delivery report(when statusis being set to 8). What can be the reason for this? Thanks in advance, Piyush ibibo Mail :: Get your mail box with Music, Skins, Greetings and Stationery now! ibibo Mail :: Get your FREE mail box with Music, Skins, Greetings and Stationery now!
Re: Reply: Regular and concatenated messages
Hi, Using coding=0 (7-bit ASCII SMS) in your send URL, you should be able to get 160 chars in one shot. Other coding schemes (1, 8-bit; 2, UTF-8) have lower limits. A clarification: DLR 8 means message has been accepted by SMSc. You don't get a forreign ID unless SMSc attempts to send it. BR, Nikos - Original Message - From: Piyush To: Alvaro Cornejo Cc: users Sent: Wednesday, June 17, 2009 7:39 AM Subject: Reply: Regular and concatenated messages Thanks Alvaro. 1.) Yes, I need it on the basis of billing. I can use only one account i.e. group = sendsms-user username = XX password = XX max-messages = 3 concatenation = true But message of 160 characters will consume 2 messages. Thats why I used two accounts. I just wanted to confirm... is this is the right approach? 2.) When I use first account i.e. group = sendsms-user username = abcdef password = abcdef I do get foreign message id in both DLR (8 1). But when I use second account and message length crosses 160 characters i.e group = sendsms-user username = pqrst password = pqrst max-messages = 3 concatenation = true I don't get foreign message id in first DLR when status=8, but I do get message id in second DLR(1). I want to know, how to resolve this issue? Thanks regards, Piyush Khandelwal -- Original Message -- From: Alvaro Cornejocornejo.alv...@gmail.com; Date: Jun 16, 2009 06:54 PM To: Piyushpiy...@ibibo.com; Cc: usersusers@kannel.org; Subject: Re: Regular and concatenated messages 1) You can use the same useraccount for both types of messages. You might want to separate them for easily billing or stat, but for kannel is not important. 2) Kannel can not privide you the foreing_id in the first dlr since its connection to smsc is asyncronous. When you receive an dlr=8 means KANNEL received the message, not the telco smsc. 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.NET www.smsglobal.com.mx y www.pravcom.com On Tue, Jun 16, 2009 at 4:14 AM, Piyushpiy...@ibibo.com wrote: Hi, I have two sendsms-user accounts. One for sending regular(160 characters) and another for long messages(more then 160). group = sendsms-user username = XX password = XX group = sendsms-user username = XX password = XX max-messages = 3 concatenation = true I can able to send messages correctly from both the accounts. Now I want to know... 1.) Is this the right way to send both regular and concatenated messages? 2.) I am not getting foreign message id, in the first delivery report(when statusis being set to 8). What can be the reason for this? Thanks in advance, Piyush ibibo Mail :: Get your mail box with Music, Skins, Greetings and Stationery now! ibibo Mail :: Get your FREE mail box with Music, Skins, Greetings and Stationery now!
concatenated messages
hi list :) how i can receive concatenated messages (MO) as a one part in the mohandler table . thanes for your help. regard.
Wierd errors (CMS 38) when sending long (concatenated) messages...
I'm at a loss as to what to troubleshoot next, so perhaps somebody has run into this in the past. I'm running Fedora Core 3, and Kannel 1.4.0. The modem is a MultiModem GSM/GPRS modem . I have set it up so that the received messages are forwarded to a web server, which processes them, and returns a reply. Everything works great when the message returned is not getting split up. However, when the response is a long message, things don't work very well at all. I have turned on the concatenation in the configuration, applicable section is like so: group = sms-service keyword = default concatenation = true max-messages = 3 #split-chars= ,.!? send-sender = true catch-all = true strip-keyword = false get-url = http://localhost:8080/smssender/servlet/kannel?sender=%ptext=%a; omit-empty = true Here's an entry from the bearerbox logs showing a _single_ message that works aok and looks great on the phone: 2005-09-03 23:11:26 [7867] [6] DEBUG: AT2[mobile]: -- AT+CMGS=119^M 2005-09-03 23:11:26 [7867] [6] DEBUG: AT2[mobile]: -- 2005-09-03 23:11:26 [7867] [6] DEBUG: AT2[mobile]: send command status: 1 2005-09-03 23:11:26 [7867] [6] DEBUG: AT2[mobile]: -- 0011000B912160247745F0A778D437E81EA68FD120F35B0E7297C372711E7496BFEB7050BBDC1697E573D05B0E82CBDFE634BB0C6A87E96374790E9297E1EC3CE89EA6A341F0B09C0E7A9B417474197496BFEB70903BDC2E83DE72105CFE36A7D965903BDC2E83D8E9751924BA87E96334C8196C1645 2005-09-03 23:11:27 [7867] [6] DEBUG: AT2[mobile]: -- ^Z 2005-09-03 23:11:27 [7867] [8] DEBUG: boxc_receiver: heartbeat with load value 0 received 2005-09-03 23:11:30 [7867] [6] DEBUG: AT2[mobile]: -- 2005-09-03 23:11:30 [7867] [6] DEBUG: AT2[mobile]: -- +CMGS: 17 2005-09-03 23:11:30 [7867] [6] DEBUG: AT2[mobile]: -- OK Now, I do a message that is longer and is split into two messages (smsbox says: 2005-09-03 23:12:28 [7875] [5] DEBUG: message length 273, sending 2 messages And then the bearerbox logs say: 2005-09-03 23:12:30 [7867] [6] DEBUG: AT2[mobile]: -- AT+CMGS=125^M 2005-09-03 23:12:30 [7867] [6] DEBUG: AT2[mobile]: -- 2005-09-03 23:12:30 [7867] [6] DEBUG: AT2[mobile]: send command status: 1 2005-09-03 23:12:30 [7867] [6] DEBUG: AT2[mobile]: -- 0051000B912160247745F0A77F050003020202C479503B4C1FA3CB731728FBAE83C6613728CC9EBF41F3B29B0CAACF752011BD1C9E97E5A0E6F42802D1DFA079D94D06854173F45B4E0735A74710FD0D3A97E9A0FCBB2E07B9CB61B9380F6A87E96374790E4ABBE96579794E2F9341693748FD4EBBD3EE3328FFAE87 2005-09-03 23:12:30 [7867] [6] DEBUG: AT2[mobile]: -- ^Z 2005-09-03 23:12:33 [7867] [6] DEBUG: AT2[mobile]: -- 2005-09-03 23:12:33 [7867] [6] DEBUG: AT2[mobile]: -- +CMS ERROR: 38 2005-09-03 23:12:33 [7867] [6] ERROR: AT2[mobile]: CMS ERROR: +CMS ERROR: 38 (Network out of order) 2005-09-03 23:12:33 [7867] [6] DEBUG: AT2[mobile]: send command status: 1 2005-09-03 23:12:33 [7867] [6] DEBUG: AT2[mobile]: -- AT+CMGS=125^M 2005-09-03 23:12:34 [7867] [6] DEBUG: AT2[mobile]: -- 2005-09-03 23:12:34 [7867] [6] DEBUG: AT2[mobile]: send command status: 1 2005-09-03 23:12:34 [7867] [6] DEBUG: AT2[mobile]: -- 0051000B912160247745F0A77F050003020202C479503B4C1FA3CB731728FBAE83C6613728CC9EBF41F3B29B0CAACF752011BD1C9E97E5A0E6F42802D1DFA079D94D06854173F45B4E0735A74710FD0D3A97E9A0FCBB2E07B9CB61B9380F6A87E96374790E4ABBE96579794E2F9341693748FD4EBBD3EE3328FFAE87 2005-09-03 23:12:34 [7867] [6] DEBUG: AT2[mobile]: -- ^Z 2005-09-03 23:12:37 [7867] [6] DEBUG: AT2[mobile]: -- 2005-09-03 23:12:37 [7867] [6] DEBUG: AT2[mobile]: -- +CMS ERROR: 38 2005-09-03 23:12:37 [7867] [6] ERROR: AT2[mobile]: CMS ERROR: +CMS ERROR: 38 (Network out of order) 2005-09-03 23:12:37 [7867] [6] DEBUG: AT2[mobile]: send command status: 1 2005-09-03 23:12:37 [7867] [6] DEBUG: AT2[mobile]: -- AT+CMGS=125^M 2005-09-03 23:12:37 [7867] [6] DEBUG: AT2[mobile]: -- 2005-09-03 23:12:37 [7867] [6] DEBUG: AT2[mobile]: send command status: 1 2005-09-03 23:12:37 [7867] [6] DEBUG: AT2[mobile]: -- 0051000B912160247745F0A77F050003020202C479503B4C1FA3CB731728FBAE83C6613728CC9EBF41F3B29B0CAACF752011BD1C9E97E5A0E6F42802D1DFA079D94D06854173F45B4E0735A74710FD0D3A97E9A0FCBB2E07B9CB61B9380F6A87E96374790E4ABBE96579794E2F9341693748FD4EBBD3EE3328FFAE87 2005-09-03 23:12:38 [7867] [6] DEBUG: AT2[mobile]: -- ^Z 2005-09-03 23:12:41 [7867] [6] DEBUG: AT2[mobile]: -- 2005-09-03 23:12:41 [7867] [6] DEBUG: AT2[mobile]: -- +CMS ERROR: 38 2005-09-03 23:12:41 [7867] [6] ERROR: AT2[mobile]: CMS ERROR: +CMS ERROR: 38 (Network out of order) 2005-09-03 23:12:41 [7867] [6] DEBUG: AT2[mobile]: send command status: 1 2005-09-03 23:12:41 [7867] [6] DEBUG: Set split msg status to 3 2005-09-03 23:12:41 [7867] [6] DEBUG: AT2[mobile]: TP-Validity-Period: 24.0 hours 2005-09-03 23:12:41 [7867] [6] DEBUG: AT2[mobile]: -- AT+CMGS=154^M 2005-09-03 23:12:41 [7867] [6] DEBUG: AT2[mobile]: -- 2005-09-03 23:12:41 [7867] [6] DEBUG: AT2[mobile]: send command status: 1 2005-09-03 23:12:41 [7867] [6] DEBUG: AT2[mobile]: --
concatenated messages with SAR_ parameters
Does anybody have any experience with handling concatenated messages using the sar_ parameters (sar_msg_ref_num, sar_total_segments, sar_segment_seqnum)? Is it possible to pass UDH parameters, but the carrier I am working with doesn't pass those to SME's, but does SAR_'s instead. Thanks for any hints. Regards, Peter
Re: receiving concatenated messages
On Wed, Jul 06, 2005 at 02:15:00PM +0100, Ismail Adebayo wrote: Hi You need to store and reassemble the received concatenated message parts based on the UDH. What makes this worse yet is that some mobile carriers (all of the carriers in my country do this) actually set their SMSC's to discard any UDH in messages that they send back to content providers. This makes the entire task of reassembling received concat messages automatically totally impossible. -- ...avoid the necessity of those overgrown Military establishments, which, under any form of government, are inauspicious to liberty, and which are to be regarded as particularly hostile to Republican Liberty. http://stormwyrm.blogspot.com/
RE: receiving concatenated messages
I've been working on the same issue recently, and what I found in the list archives was that as of now Kannel can only handle concatenated messages as single messages (it does not do temporary storage of messages with special UDH). I guess you will have too prepare some workaround for this yourself -search the archives, there was a patch that could do something that could help you on the way. Peter -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sasko Celakovski Sent: Tuesday, July 05, 2005 5:15 PM To: users@kannel.org Subject: receiving concatenated messages Hi All, I have a problem receiving (SMPP) long concatenated messages (like picutres) with Kannel (versions 1.2, 1.3.1 and 1.4)... Is this implemented? Kannel behavies strange when receiving picture in a message, bearerbox reports error in its log stating that the connection to SMSC was lost (i.e connection lost, could not connect to smsc etc...) ... Has anyone else experienced this behaviour? Is there any soution for this.. Thanks, Sasko Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com
Re: receiving concatenated messages
Hi You need to store and reassemble the received concatenated message parts based on the UDH. Ismail - Original Message - From: Peter Tatischev [EMAIL PROTECTED] To: users@kannel.org Sent: Wednesday, July 06, 2005 2:00 PM Subject: RE: receiving concatenated messages I've been working on the same issue recently, and what I found in the list archives was that as of now Kannel can only handle concatenated messages as single messages (it does not do temporary storage of messages with special UDH). I guess you will have too prepare some workaround for this yourself -search the archives, there was a patch that could do something that could help you on the way. Peter -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sasko Celakovski Sent: Tuesday, July 05, 2005 5:15 PM To: users@kannel.org Subject: receiving concatenated messages Hi All, I have a problem receiving (SMPP) long concatenated messages (like picutres) with Kannel (versions 1.2, 1.3.1 and 1.4)... Is this implemented? Kannel behavies strange when receiving picture in a message, bearerbox reports error in its log stating that the connection to SMSC was lost (i.e connection lost, could not connect to smsc etc...) ... Has anyone else experienced this behaviour? Is there any soution for this.. Thanks, Sasko Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com
receiving concatenated messages
Hi All, I have a problem receiving (SMPP) long concatenated messages (like picutres) with Kannel (versions 1.2, 1.3.1 and 1.4)... Is this implemented? Kannel behavies strange when receiving picture in a message, bearerbox reports error in its log stating that the connection to SMSC was lost (i.e connection lost, could not connect to smsc etc...) ... Has anyone else experienced this behaviour? Is there any soution for this.. Thanks, Sasko Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com
concatenated messages over same modem (smsc = at)
Hi List, i am using Kannel stable and cvs version using Wavecom modems. If i send concatenated messages Kannel sends them over different smsc's (modem devices). Is there a way to stick them together that they will be sent using the same smsc? Thanks in advance -oliver __ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201
receiving concatenated messages
Hello Sasko! Ive read your postings at [EMAIL PROTECTED] regarding receiving concatenated MO messages. We also have a service to get comments from the public and we route that to corresponding web application based on the keyword sent. Unfortunately, we are also experiencing the same problem as yours, wherein our Kannel does not recognize the more than 160 characters long MO message but as multiple messages. Were you able to solve this one? Kannel says in my smsbox log: Starting to service ? from sender-number to recipients-number Formatted text reply No service specified My configuration for the sms-service is as follows ( I also have service for default and nop keyword) # SERVICESgroup = sms-servicekeyword = mykeywordaccepted-smsc = suncelget-url = http://XXX.XXX.XX.X/receivemsg2.asp?from=%pto=%Ptext=%amax-messages = 3concatenation = true catch-all = true Thanks, Jane
Re: Sending concatenated messages
On Thu, Aug 19, 2004 at 06:07:56PM +0300, Enver ALTIN wrote: BTW, it would be great to have SMS concatenation built-in with Kannel, so messages with text longer than 160 chars would be automatically concatenated using needed UDH parameter. I've actually looked at the code (because I had to hack it so that Kannel should not attach binfo stuff to every concatenated message), and as far as I can tell, Kannel already has this support. Maybe you should try sending a message with more than 160 characters...? I'm primarily using Kannel with SMSC's but it does seem to work for me. -- dido Sans les mathematiques on ne penetre point au fond de la philosophie. Sans la philosophie on ne penetre point au fond des mathematiques. Sans les deux on ne penetre au fond de rien.
RE: Sending concatenated messages
Hi, I was using kannel 1.3.2 this week and I was definitely able to do this, without using UDH. All you need to do is add the following lines to your smskannel.conf, in the sendsms-user section. In your case, you'd have to add it to the sendsms-user for user blah max-messages = 3 concatenation = true Obviously, adjust the maximum number of split messages to your liking... You are then able to just send regular text messages, without using udh=x , they'll get split automatically... It did work on my nokia 3310 for instance Kind regards, Renaat -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Enver ALTIN Sent: Thursday, August 19, 2004 17:08 To: [EMAIL PROTECTED] Subject: Sending concatenated messages Hi, I'm trying to send concatenated messages using the UDH parameter using: http://localhost:13002/cgi-bin/sendsms?username=blahpassword=blahfrom=$fro mto=$totext=ONE$outudh=%05%00%03%01%02%01 http://localhost:13002/cgi-bin/sendsms?username=blahpassword=blahfrom=$fro mto=$totext=TWO$outudh=%05%00%03%01%02%02 It works very well for recipients with decent handsets, but seems to be broken older handsets like Nokia 6210 (it definitely supports this, because it can send and receive messages longer than 160 chars itself), which says Can't display message or something. Is there anything I can do about this? BTW, it would be great to have SMS concatenation built-in with Kannel, so messages with text longer than 160 chars would be automatically concatenated using needed UDH parameter. -HAND -- Enver ALTIN |http://skyblue.gen.tr/ Software developer @ Parkyeri | http://www.parkyeri.com/
Re: Sending concatenated messages
Yes it works! I fact, if you look at the logfiles, Kannel actually do the UDH stuff for you and split the message in as many parts as necessary and adds the right UDH to each message. Regards, - Original Message - From: Renaat Dumon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, August 20, 2004 12:19 PM Subject: RE: Sending concatenated messages Hi, I was using kannel 1.3.2 this week and I was definitely able to do this, without using UDH. All you need to do is add the following lines to your smskannel.conf, in the sendsms-user section. In your case, you'd have to add it to the sendsms-user for user blah max-messages = 3 concatenation = true Obviously, adjust the maximum number of split messages to your liking... You are then able to just send regular text messages, without using udh=x , they'll get split automatically... It did work on my nokia 3310 for instance Kind regards, Renaat -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Enver ALTIN Sent: Thursday, August 19, 2004 17:08 To: [EMAIL PROTECTED] Subject: Sending concatenated messages Hi, I'm trying to send concatenated messages using the UDH parameter using: http://localhost:13002/cgi-bin/sendsms?username=blahpassword=blahfrom=$fro mto=$totext=ONE$outudh=%05%00%03%01%02%01 http://localhost:13002/cgi-bin/sendsms?username=blahpassword=blahfrom=$fro mto=$totext=TWO$outudh=%05%00%03%01%02%02 It works very well for recipients with decent handsets, but seems to be broken older handsets like Nokia 6210 (it definitely supports this, because it can send and receive messages longer than 160 chars itself), which says Can't display message or something. Is there anything I can do about this? BTW, it would be great to have SMS concatenation built-in with Kannel, so messages with text longer than 160 chars would be automatically concatenated using needed UDH parameter. -HAND -- Enver ALTIN |http://skyblue.gen.tr/ Software developer @ Parkyeri | http://www.parkyeri.com/
Sending concatenated messages
Hi, I'm trying to send concatenated messages using the UDH parameter using: http://localhost:13002/cgi-bin/sendsms?username=blahpassword=blahfrom=$fromto=$totext=ONE$outudh=%05%00%03%01%02%01 http://localhost:13002/cgi-bin/sendsms?username=blahpassword=blahfrom=$fromto=$totext=TWO$outudh=%05%00%03%01%02%02 It works very well for recipients with decent handsets, but seems to be broken older handsets like Nokia 6210 (it definitely supports this, because it can send and receive messages longer than 160 chars itself), which says Can't display message or something. Is there anything I can do about this? BTW, it would be great to have SMS concatenation built-in with Kannel, so messages with text longer than 160 chars would be automatically concatenated using needed UDH parameter. -HAND -- Enver ALTIN |http://skyblue.gen.tr/ Software developer @ Parkyeri | http://www.parkyeri.com/ signature.asc Description: This is a digitally signed message part
receiving concatenated messages
Hi, How is the receiving of concatenated messages solved in Kannel? Im using 1.3.1 version and when a MO concatenated message is sent Kannel does not recognize it as one message but as multiple messages. Only the first message can be served by the service since it is in the only message that contains the keyword (but with incomplete data since the rest of it is packed in other messages). Furthermore, the providers default coding when sending/receiving concatenated messages is 7-bit and the message can not be decoded properly when it is divided in multiple messages. Is there a solution to this problem? Regards, Sasko COSMOFON - Mobile Telecommunications Services - A.D. Skopje This e-mail (including any attachments) is confidential and may be protected by legal privilege. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. COSMOFON A.D. Skopje shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system.
receiving concatenated messages
We have one service whose job is simply to obtain subscriber comments and store them in a database for later human consumption. Trouble is, a lot of subscribers happen to have newfangled phones that generate concatenated SMS, and it is becoming difficult to manually reassemble these many concatenated SMS messages. Is there a way to make Kannel automatically stitch these messages when they're received by our service, or at least some information available that will facilitate automatically reassembling message fragments? We're using a recent version of Kannel-CVS and are connecting to both CIMD2 and UCP SMSC's. -- dido The only thing of value passing through a politician's brain is a bullet.
