Hi,

SMPP Spec on submit_sm:
"This operation is used by an ESME to submit a short message to the SMSC"

SMPP Spec on deliver_sm:
"The deliver_sm is issued by the SMSC to send a message to an ESME. "

submit_sm is only used when a client sends data to a server. When the server wants to send data to the client you have to use deliver_sm (0x00000005) So a client doesn't need to know what a submit_sm is, when it _receives_ it. And kannel is client only (without smppbox)

Regards
Falko

Am 08.05.2009 um 15:31 schrieb Nikos Balkanas:

Hi,

According to SMPP v 5, 0x00000004 is the submit_sm. Very essential and recognized by kannel as seen from the logs. Strange thing is that a few lines below, it doesn't recognize it, which can only mean that it is not expecting it at the state it is in.

This looks hairy. Can you provide a tcpdump?

BR,
Nikos
----- Original Message -----
From: SYARIFL
To: [email protected]
Sent: Friday, May 08, 2009 5:42 AM
Subject: SMSC.SMPP: Unknown PDU type 0x00000004

I make labs to learn how SMPP works, I used Mobile Message Tester (MMT) Application to rcvd and send message to kannel. Testing from kannel via SMPP to MMT is successful, but when i tried to send message from MMT to kannel via SMPP, kannel, ignore it and generate "Unknown PDU type 0x00000004", here the configuration and log:

configuration:

group = smsc
smsc-id = danu_smsc
smsc = smpp
host = aaa.bbb.ccc.ddd <----- (MMT IP ADDRESS)
port = 3000
smsc-username = "tester"
smsc-password = "tester"
system-type = "VMA"
address-range = ""
transceiver-mode = 1

kannel.log:

2009-05-07 12:00:21 [17176] [8] DEBUG: SMPP[danu_smsc]: Got PDU:
2009-05-07 12:00:21 [17176] [8] DEBUG: SMPP PDU 0x814c100 dump:
2009-05-07 12:00:21 [17176] [8] DEBUG:   type_name: submit_sm
2009-05-07 12:00:21 [17176] [8] DEBUG:   command_id: 4 = 0x00000004
2009-05-07 12:00:21 [17176] [8] DEBUG: command_status: 0 = 0x00000000 2009-05-07 12:00:21 [17176] [8] DEBUG: sequence_number: 1 = 0x00000001
2009-05-07 12:00:21 [17176] [8] DEBUG:   service_type: "SMSDS"
2009-05-07 12:00:21 [17176] [8] DEBUG: source_addr_ton: 3 = 0x00000003 2009-05-07 12:00:21 [17176] [8] DEBUG: source_addr_npi: 14 = 0x0000000e
2009-05-07 12:00:21 [17176] [8] DEBUG:   source_addr: "21474046"
2009-05-07 12:00:21 [17176] [8] DEBUG:   dest_addr_ton: 3 = 0x00000003
2009-05-07 12:00:21 [17176] [8] DEBUG: dest_addr_npi: 14 = 0x0000000e
2009-05-07 12:00:21 [17176] [8] DEBUG:   destination_addr: "9999"
2009-05-07 12:00:21 [17176] [8] DEBUG:   esm_class: 0 = 0x00000000
2009-05-07 12:00:21 [17176] [8] DEBUG:   protocol_id: 0 = 0x00000000
2009-05-07 12:00:21 [17176] [8] DEBUG:   priority_flag: 0 = 0x00000000
2009-05-07 12:00:21 [17176] [8] DEBUG:   schedule_delivery_time: NULL
2009-05-07 12:00:21 [17176] [8] DEBUG:   validity_period: NULL
2009-05-07 12:00:21 [17176] [8] DEBUG: registered_delivery: 1 = 0x00000001 2009-05-07 12:00:21 [17176] [8] DEBUG: replace_if_present_flag: 0 = 0x00000000
2009-05-07 12:00:21 [17176] [8] DEBUG:   data_coding: 0 = 0x00000000
2009-05-07 12:00:21 [17176] [8] DEBUG: sm_default_msg_id: 0 = 0x00000000
2009-05-07 12:00:21 [17176] [8] DEBUG:   sm_length: 20 = 0x00000014
2009-05-07 12:00:21 [17176] [8] DEBUG:   short_message:
2009-05-07 12:00:21 [17176] [8] DEBUG:    Octet string at 0x81498b0:
2009-05-07 12:00:21 [17176] [8] DEBUG:      len:  20
2009-05-07 12:00:21 [17176] [8] DEBUG:      size: 21
2009-05-07 12:00:21 [17176] [8] DEBUG:      immutable: 0
2009-05-07 12:00:21 [17176] [8] DEBUG: data: 6d 61 73 69 68 20 74 65 73 74 2e 2e 2e 20 68 75 masih test... hu 2009-05-07 12:00:21 [17176] [8] DEBUG: data: 68 75 68 75 huhu
2009-05-07 12:00:21 [17176] [8] DEBUG:    Octet string dump ends.
2009-05-07 12:00:21 [17176] [8] DEBUG: SMPP PDU dump ends.
2009-05-07 12:00:21 [17176] [8] ERROR: SMPP[danu_smsc]: Unknown PDU type 0x00000004, ignored.

--
// syarifl.com

Reply via email to