Thanks for the clarification Alex, much appreciated.
Andrew _____ From: Alejandro Guerrieri [mailto:alejandro.guerri...@gmail.com] Sent: Wednesday, 21 April 2010 2:15 AM To: Andrew Toth Cc: users@kannel.org Subject: Re: receipted_msg_id in dlr? kannel calls dlr-url on: * submit_sm_resp, this is why I call "fake dlr". Kannel hits the dlr-url with an "ACK/" or "NACK/<error string>" payload. * when receiving a "real" DLR from a carrier (which is a deliver_sm, but not an MO but a special case where the payload is the delivery receipt string). Regards, Alex On Tue, Apr 20, 2010 at 10:02 AM, Andrew Toth <at...@mobiledatagroup.com> wrote: Hi Alex, I was under the impression that kannel only calls dlr-url for deliver_sm events, and not for submit_sm_resp. Please let me know if I'm wrong on this point. Thanks, Andrew _____ From: Alejandro Guerrieri [mailto:alejandro.guerri...@gmail.com] Sent: Tuesday, 20 April 2010 4:29 PM To: Andrew Toth Cc: Juan Nin; users@kannel.org Subject: Re: receipted_msg_id in dlr? Andrew, Sorry I don't get the question. If the message_id is on the submit_sm_resp, it will be made available as the "foreign id" so you can use it on dlr's. If you're NOT getting the submit_sm_resp, where do you expect the message_id to come from? Btw, kannel will handle a missing submit_sm_resp and you can configure what to do when that happens. Check the user guide for more details. Regards, Alex On Tue, Apr 20, 2010 at 3:22 AM, Andrew Toth <at...@mobiledatagroup.com> wrote: Thanks for the response Alex that certainly solved the issue. I was switching between protocol version 3.3 and 3.4 for testing and it was needed for 3.3. I've noticed that kannel will only pass this message id through to our application on the deliver_sm event. Is there any way to get the message id from submit_sm_resp? The reason this would be useful is that there have been incidents in the past where kannel has messages stuck in its internal queue infinitely, as it tries to submit the message but does not get a submit_sm_resp. I have not been able to figure out why this is happening as at the same time it can submit messages successfully, just not some messages. I could trigger a kannel restart and message resubmit in our application if some time has elapsed since the message was passed on to kannel but we did not receive a submit_sm_resp. Thanks, Andrew _____ From: Alejandro Guerrieri [mailto:alejandro.guerri...@gmail.com] Sent: Friday, 16 April 2010 9:13 PM To: Andrew Toth Cc: Juan Nin; users@kannel.org Subject: Re: receipted_msg_id in dlr? Oh, you're not setting msg-id-type right? That would explain the problem... If you do, try removing that line from your conf. Regards, Alex On Fri, Apr 16, 2010 at 8:49 AM, Andrew Toth <at...@mobiledatagroup.com> wrote: Hi, Is kannel treating message id as an integer, and doing some kind of conversion on the string? We need to be able to capture whatever is passed back as the message id, integer or string. If it makes any difference we are connecting protocol version 3.4 I noticed that the aggregator sends message id in a different format over 3.3 (integer), but we need to connect with 3.4 now. _____ From: Alejandro Guerrieri [mailto:alejandro.guerri...@gmail.com] Sent: Friday, 16 April 2010 4:25 PM To: Andrew Toth Cc: Juan Nin; users@kannel.org Subject: Re: receipted_msg_id in dlr? Weird, that's exactly what %F should do. Maybe those dashes are causing the trouble? Regards, Alex On Fri, Apr 16, 2010 at 3:22 AM, Andrew Toth <at...@mobiledatagroup.com> wrote: Hi, Thanks for the response, unfortunately that is not what we're after. See example below. 2010-04-15 18:11:09 [16689] [8] DEBUG: SMPP PDU 0x2aaaac000ee0 dump: 2010-04-15 18:11:09 [16689] [8] DEBUG: type_name: submit_sm_resp 2010-04-15 18:11:09 [16689] [8] DEBUG: command_id: 2147483652 = 0x80000004 2010-04-15 18:11:09 [16689] [8] DEBUG: command_status: 0 = 0x00000000 2010-04-15 18:11:09 [16689] [8] DEBUG: sequence_number: 10 = 0x0000000a 2010-04-15 18:11:09 [16689] [8] DEBUG: message_id: 2010-04-15 18:11:09 [16689] [8] DEBUG: Octet string at 0x2aaaac0010a0: 2010-04-15 18:11:09 [16689] [8] DEBUG: len: 23 2010-04-15 18:11:09 [16689] [8] DEBUG: size: 24 2010-04-15 18:11:09 [16689] [8] DEBUG: immutable: 0 2010-04-15 18:11:09 [16689] [8] DEBUG: data: 38 34 31 30 32 2d 30 34 31 35 38 2d 32 31 31 31 84102-04158-2111 2010-04-15 18:11:09 [16689] [8] DEBUG: data: 4b 2d 30 39 42 52 54 K-09BRT 2010-04-15 18:11:09 [16689] [8] DEBUG: Octet string dump ends. 2010-04-15 18:11:09 [16689] [8] DEBUG: SMPP PDU dump ends. 2010-04-15 18:11:09 [16689] [8] DEBUG: DLR[mysql]: Adding DLR smsc=xxxxxxx, ts=540930, src=77447, dst=13109776776, mask=31, boxc= I need to capture message id 84102-04158-21K-09BRT. This same message id is included in deliver_sm (dlr for this message) in the receipted_msg_id field. Kannel, in the %F parameter passes through 540930 (where does that number come from anyway?). Further, this number is different for each dlr received for this message. The first dlr had message id 540930, the second had 33808. Andrew -----Original Message----- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Juan Nin Sent: Friday, 16 April 2010 10:58 AM To: users@kannel.org Subject: Re: receipted_msg_id in dlr? %F the foreign (smsc-provided) message ID. Only relevant on DLR url's. On Thu, Apr 15, 2010 at 9:32 PM, Andrew Toth <at...@mobiledatagroup.com> wrote: > Hi all, > > > > We are looking to get the msg id from kannel that is sent by the smsc in > submit_sm_resp as well as deliver_sm. > > > > I found a discussion from 2008 > (http://www.mail-archive.com/de...@kannel.org/msg07999.html) that refers to > a patch to add support for this and my impression was that this feature has > been incorporated into the main kannel version. I've done a quick test and > %w in the dlr-url is not being replaced by the message id. > > > > We are using Kannel version cvs-20090525 (which supports TLVs) and the patch > seems to be for an older version. > > > > I also checked the source code (in dlr.c) for kannel 1.4.3 and it did not > have this feature. > > > > We would like to avoid patching and recompiling kannel in our live > environment as it would be a risky operation and affect many services. > > > > Do we have any other options? Is there a later cvs version which has this > feature? Is it going to be included in the next stable release? > > > > Thanks, > > Andrew > > > > > > -- Juan Nin 3Cinteractive / Mobilizing Great Brands http://www.3cinteractive.com
