Hi,
Please read User's guide about msg-id-type.
BR,
Nikos
----- Original Message -----
From: "Adam Di Blasio" <adam.dibla...@adiqglobal.com>
To: <users@kannel.org>
Sent: Thursday, July 22, 2010 7:15 PM
Subject: SMS message ids in delivery report
Hi,
I am trying to use DLR reports through SMPP but have noticed that the SMSC
returns a hex id
with submit_sm_resp and a decimal id with deliver_sm:
2010-07-22 15:42:37 [6284] [8] DEBUG: SMPP PDU 0x81af020 dump:
2010-07-22 15:42:37 [6284] [8] DEBUG: type_name: submit_sm_resp
2010-07-22 15:42:37 [6284] [8] DEBUG: command_id: 2147483652 =
0x80000004
2010-07-22 15:42:37 [6284] [8] DEBUG: command_status: 0 = 0x00000000
2010-07-22 15:42:37 [6284] [8] DEBUG: sequence_number: 3 = 0x00000003
2010-07-22 15:42:37 [6284] [8] DEBUG: message_id: "70767AFF"
2010-07-22 15:42:41 [6284] [9] DEBUG: SMPP PDU 0x81af020 dump:
2010-07-22 15:42:41 [6284] [9] DEBUG: type_name: deliver_sm
2010-07-22 15:42:41 [6284] [9] DEBUG: command_id: 5 = 0x00000005
...
2010-07-22 15:42:41 [6284] [9] DEBUG: data: 69 64 3a 31 38 38 36 38
31 32 39 32 37 20 73
75 id:1886812927
When looking at the source in gw/smsc/smsc_smpp.c lines 1365 - 1392 (cvs
version) I can see
that kannel attempts to convert the id's so that they match -
unfortunately this does not
appear to be happening.
Short of taking this up with the SMSC provider I wanted to see if anyone
else had come across
this problem and found a workaround?
Kind Regards
--
ADAM DI BLASIO
