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





 

Reply via email to