Yes, there is, it is documented in the user-guide - I'll resist the
temptation to say RTFM by now ;-)
Right from the user-guide:
msg-id-type
Optional, specifies which number base the SMSC is using for the message ID
numbers in the corresponding submit_sm_resp and deliver_sm PDUs. This is
required to make delivery reports (DLR) work on SMSC that behave
differently. The number is a combined set of bit 1 and bit 2 that indicate
as follows: bit 1: type for submit_sm_resp, bit 2: type for deliver_sm. If
the bit is set then the value is in hex otherwise in decimal number base.
Which means the following combinations are possible and valid: 0x00
deliver_sm decimal, submit_sm_resp decimal; 0x01 deliver_sm decimal,
submit_sm_resp hex; 0x02 deliver_sm hex, submit_sm_resp decimal; 0x03
deliver_sm hex, submit_sm_resp hex. In accordance to the SMPP v3.4 specs the
default will be a C string literal if no of the above values is explicitly
indicated using the config directive.
Angel FRADEJAS
Mediafusión España, S.A.
[EMAIL PROTECTED]
www.mediafusion.es
Tel. +34 91 252 3200
Fax +34 91 252 5969
-----Mensaje original-----
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de
Arnar Gestsson
Enviado el: martes, 09 de marzo de 2004 12:39
Para: [EMAIL PROTECTED]
Asunto: dlr issue
Hi guys,
we are using Kannel 1.3.1 and connected to an SMPP SMSC, the funny thing
is when we issue dlr request, the message id is stored in Kannel in hex
format, but when the DLR arrives from the SMSC it comes on decimal
format. Do you guys know about this and if there is a simple solution
for it?
BR. Arnar
--
Arnar Gestsson <[EMAIL PROTECTED]>
