Hi!

I'm using kannel 1.4.0 to connect by smpp to a partner, I've done this a few times with no further problems... however this time I'm getting the following error when our partner sends a sms to kannel:

Unknown PDU type 0x00000004, ignored.

I checked the PDU and it looks ok.. I even compare it octet by octed with other pdu's and it looks ok as well...

any idea of why this may be happening?

this is the log I get from tshark and kannel:

-- tcp dump
0000  00 0d 9d 4e 29 6b 00 0f 3d 59 ac 66 08 00 45 00   ...N)k..=Y.f..E.
0010  00 68 a8 98 00 00 6c 06 46 a7 45 14 0e cb 0a 18   .h....l.F.E.....
0020  01 5a 26 fa 9f f2 28 7c e1 10 e9 37 d0 f1 80 18   .Z&...(|...7....
0030  fc 1b 06 bd 00 00 01 01 08 0a 00 6d 28 04 3d 07   ...........m(.=.
0040  c3 46 00 00 00 34 00 00 00 04 00 00 00 00 00 00   .F...4..........
0050  09 31 00 00 00 32 32 39 39 39 00 00 00 35 35 33   .1...22999...553
0060  33 33 33 34 32 39 36 00 00 00 00 00 00 01 00 00   3334296.........
0070  00 04 74 65 73 74                                 ..test

-- kannel log
2006-12-07 18:05:50 [9797] [15] DEBUG: SMPP PDU 0x81d7a70 dump:
2006-12-07 18:05:50 [9797] [15] DEBUG:   type_name: submit_sm
2006-12-07 18:05:50 [9797] [15] DEBUG:   command_id: 4 = 0x00000004
2006-12-07 18:05:50 [9797] [15] DEBUG:   command_status: 0 = 0x00000000
2006-12-07 18:05:50 [9797] [15] DEBUG: sequence_number: 2353 = 0x00000931
2006-12-07 18:05:50 [9797] [15] DEBUG:   service_type: NULL
2006-12-07 18:05:50 [9797] [15] DEBUG:   source_addr_ton: 0 = 0x00000000
2006-12-07 18:05:50 [9797] [15] DEBUG:   source_addr_npi: 0 = 0x00000000
2006-12-07 18:05:50 [9797] [15] DEBUG:   source_addr: "22999"
2006-12-07 18:05:50 [9797] [15] DEBUG:   dest_addr_ton: 0 = 0x00000000
2006-12-07 18:05:50 [9797] [15] DEBUG:   dest_addr_npi: 0 = 0x00000000
2006-12-07 18:05:50 [9797] [15] DEBUG:   destination_addr: "5533334296"
2006-12-07 18:05:50 [9797] [15] DEBUG:   esm_class: 0 = 0x00000000
2006-12-07 18:05:50 [9797] [15] DEBUG:   protocol_id: 0 = 0x00000000
2006-12-07 18:05:50 [9797] [15] DEBUG:   priority_flag: 0 = 0x00000000
2006-12-07 18:05:50 [9797] [15] DEBUG:   schedule_delivery_time: NULL
2006-12-07 18:05:50 [9797] [15] DEBUG:   validity_period: NULL
2006-12-07 18:05:50 [9797] [15] DEBUG: registered_delivery: 1 = 0x00000001 2006-12-07 18:05:50 [9797] [15] DEBUG: replace_if_present_flag: 0 = 0x00000000
2006-12-07 18:05:50 [9797] [15] DEBUG:   data_coding: 0 = 0x00000000
2006-12-07 18:05:50 [9797] [15] DEBUG: sm_default_msg_id: 0 = 0x00000000
2006-12-07 18:05:50 [9797] [15] DEBUG:   sm_length: 4 = 0x00000004
2006-12-07 18:05:50 [9797] [15] DEBUG:   short_message: "test"
2006-12-07 18:05:50 [9797] [15] DEBUG: SMPP PDU dump ends.
2006-12-07 18:05:50 [9797] [15] ERROR: SMPP[mi_wo_1111]: Unknown PDU type 0x00000004, ignored.

as you can see it reads correctly the PDU and then it throws the 0x00000004 error...

does the ton & npi values may have something to do with it?

we've play around a little with the configuration of registered_delivery (0/1) and esm_class (0/3) with no success....

other thing I notice is that the system-type they provide me is not VMA, does this has something to do with this issue???

my configuration is as follows:

host = xx.xx.xx.xx
port = xxxx
transceiver-mode = true
smsc-username = xxxx
smsc-password = xxxx
system-type = WOLrcv
interface-version = 0x34
enquire-link-interval = 30
max-pending-submits = 10
reconnect-delay = 30
source-addr-ton = 0
source-addr-npi = 0
source-addr-autodetect = true
dest-addr-ton = 0
dest-addr-npi = 0
alt-charset = "UTF-8"
log-level = 0
log-file = "/xxxxx/xxxxx/xxxx.log"

thanx in advance,

regards,
Enrique


Reply via email to