Does Kannel always place the message_id from a submit_sm_resp into timestamp for a DLR using SMPP 3.4

2010-06-29 Thread brett skinner
Hi

I was checking in the SMPP 3.4 spec and came across the submit_sm_resp PDU
which specifies a message_id field. According to the spec:

This field contains the SMSC
message ID of the submitted
message. It may be used at a
later stage to query the status
of a message, cancel or
replace the message.

We are using MySql DLR. Looking at the debug output from Kannel:

2010-06-29 13:13:31 [3124] [6] DEBUG:   message_id: 50062913133840086
2010-06-29 13:13:31 [3124] [6] DEBUG: SMPP PDU dump ends.
2010-06-29 13:13:31 [3124] [6] DEBUG: DLR[mysql]: Adding DLR smsc=,
ts=50062913133840086, src=+1231234, dst=+1231234, mask=31, boxc=

It seems that it is placing the message_id into the ts field. Is this always
the case?

Regards,


Re: Does Kannel always place the message_id from a submit_sm_resp into timestamp for a DLR using SMPP 3.4

2010-06-29 Thread Alejandro Guerrieri
Yes, that's the expected behavior.

Regards,

Alex

On Tue, Jun 29, 2010 at 1:21 PM, brett skinner tatty.dishcl...@gmail.comwrote:

 Hi

 I was checking in the SMPP 3.4 spec and came across the submit_sm_resp PDU
 which specifies a message_id field. According to the spec:

 This field contains the SMSC
 message ID of the submitted
 message. It may be used at a
 later stage to query the status
 of a message, cancel or
 replace the message.

 We are using MySql DLR. Looking at the debug output from Kannel:

 2010-06-29 13:13:31 [3124] [6] DEBUG:   message_id: 50062913133840086
 2010-06-29 13:13:31 [3124] [6] DEBUG: SMPP PDU dump ends.
 2010-06-29 13:13:31 [3124] [6] DEBUG: DLR[mysql]: Adding DLR smsc=,
 ts=50062913133840086, src=+1231234, dst=+1231234, mask=31, boxc=

 It seems that it is placing the message_id into the ts field. Is this
 always the case?

 Regards,



RE: Does Kannel always place the message_id from a submit_sm_resp into timestamp for a DLR using SMPP 3.4

2010-06-29 Thread Rene Kluwen
Yes, this is always the case. But the row get deleted again after the
message reaches a final delivery state.

 

From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf
Of brett skinner
Sent: dinsdag 29 juni 2010 13:21
To: users@kannel.org
Subject: Does Kannel always place the message_id from a submit_sm_resp into
timestamp for a DLR using SMPP 3.4

 

Hi

I was checking in the SMPP 3.4 spec and came across the submit_sm_resp PDU
which specifies a message_id field. According to the spec:

This field contains the SMSC
message ID of the submitted
message. It may be used at a
later stage to query the status
of a message, cancel or
replace the message.

We are using MySql DLR. Looking at the debug output from Kannel:

2010-06-29 13:13:31 [3124] [6] DEBUG:   message_id: 50062913133840086
2010-06-29 13:13:31 [3124] [6] DEBUG: SMPP PDU dump ends.
2010-06-29 13:13:31 [3124] [6] DEBUG: DLR[mysql]: Adding DLR smsc=,
ts=50062913133840086, src=+1231234, dst=+1231234, mask=31, boxc=
 
It seems that it is placing the message_id into the ts field. Is this always
the case?

Regards,