Confuse smpp with tlv

Dear list

After configure smpp with tlv (using cvs version "Kannel/cvs-20090520")


This is my configuration

group = smsc
smsc = smpp
host = xxx.xxx.xxx.xxx
port = 10293
smsc-username = a
smsc-password = b
system-type = tcp
smsc-id = new
allowed-smsc-id = new
transceiver-mode = yes
source-addr-ton = 0
source-addr-npi = 1
source-addr-autodetect = no
address-range = ""
dest-addr-ton = 0
dest-addr-npi = 1
msg-id-type = 0x01
throughput = 1

/etc/kannel/smpp-tlv.conf
group = smpp-tlv
name = short_name
tag = 0x5120
type = octetstring
length = 8

group = smpp-tlv
name = txid
tag = 0x5121
type = integer
length = 20

group = smpp-tlv
name = conttype
tag = 0x5123
type = octetstring
length = 20


 lynx "
http://127.0.0.1:13013/cgi-bin/sendsms?user=new&smsc=new&pass=new&to=234355058673&from=123404&text=testing+push&meta-data=%3Fsmpp%3Fshort_name%3Dcr9trial
"

In /var/log/kannel/access.log
2009-10-08 11:14:56 FAILED Send SMS [SMSC:new] [SVC:abc] [ACT:] [BINF:]
[FID:] [META:?smpp?short_name=cr9trial] [from:123404] [to:234355058673]
[flags:-1:0:-1:-1:-1] [msg:12:testing push] [udh:0:]

In /var/log/kannel/kannel.log
2009-10-08 11:14:55 [10888] [32] DEBUG: boxc_receiver: sms received
2009-10-08 11:14:55 [10888] [32] DEBUG: send_msg: sending msg to box:
<127.0.0.1>
2009-10-08 11:14:55 [10888] [9] DEBUG: SMPP[new]: Manually forced source
addr ton = 0, source add npi = 1
2009-10-08 11:14:55 [10888] [9] DEBUG: SMPP[new]: Manually forced dest addr
ton = 0, dest add npi = 1
2009-10-08 11:14:55 [10888] [9] DEBUG: new group created `smpp'
2009-10-08 11:14:55 [10888] [9] DEBUG: group=`smpp' key=`short_name'
value=`cr9trial'
2009-10-08 11:14:55 [10888] [9] DEBUG: SMPP[new]: Sending PDU:
2009-10-08 11:14:55 [10888] [9] DEBUG: SMPP PDU 0xc7c0ef0 dump:
2009-10-08 11:14:55 [10888] [9] DEBUG:   type_name: submit_sm
2009-10-08 11:14:55 [10888] [9] DEBUG:   command_id: 4 = 0x00000004
2009-10-08 11:14:55 [10888] [9] DEBUG:   command_status: 0 = 0x00000000
2009-10-08 11:14:55 [10888] [9] DEBUG:   sequence_number: 25577 = 0x000063e9
2009-10-08 11:14:55 [10888] [9] DEBUG:   service_type: NULL
2009-10-08 11:14:55 [10888] [9] DEBUG:   source_addr_ton: 0 = 0x00000000
2009-10-08 11:14:55 [10888] [9] DEBUG:   source_addr_npi: 1 = 0x00000001
2009-10-08 11:14:55 [10888] [9] DEBUG:   source_addr: "123404"
2009-10-08 11:14:55 [10888] [9] DEBUG:   dest_addr_ton: 0 = 0x00000000
2009-10-08 11:14:55 [10888] [9] DEBUG:   dest_addr_npi: 1 = 0x00000001
2009-10-08 11:14:55 [10888] [9] DEBUG:   destination_addr: "234355058673"
2009-10-08 11:14:55 [10888] [9] DEBUG:   esm_class: 3 = 0x00000003
2009-10-08 11:14:55 [10888] [9] DEBUG:   protocol_id: 0 = 0x00000000
2009-10-08 11:14:55 [10888] [9] DEBUG:   priority_flag: 0 = 0x00000000
2009-10-08 11:14:55 [10888] [9] DEBUG:   schedule_delivery_time: NULL
2009-10-08 11:14:55 [10888] [9] DEBUG:   validity_period: NULL
2009-10-08 11:14:55 [10888] [9] DEBUG:   registered_delivery: 0 = 0x00000000
2009-10-08 11:14:55 [10888] [9] DEBUG:   replace_if_present_flag: 0 =
0x00000000
2009-10-08 11:14:55 [10888] [9] DEBUG:   data_coding: 0 = 0x00000000
2009-10-08 11:14:55 [10888] [9] DEBUG:   sm_default_msg_id: 0 = 0x00000000
2009-10-08 11:14:55 [10888] [9] DEBUG:   sm_length: 15 = 0x0000000f
2009-10-08 11:14:55 [10888] [9] DEBUG:   short_message: "testing push"
2009-10-08 11:14:55 [10888] [9] DEBUG:   short_name: "cr9trial"
2009-10-08 11:14:55 [10888] [9] DEBUG: SMPP PDU dump ends.
2009-10-08 11:14:56 [10888] [9] DEBUG: SMPP[new]: Got PDU:
2009-10-08 11:14:56 [10888] [9] DEBUG: SMPP PDU 0xc7a0fb8 dump:
2009-10-08 11:14:56 [10888] [9] DEBUG:   type_name: submit_sm_resp
2009-10-08 11:14:56 [10888] [9] DEBUG:   command_id: 2147483652 = 0x80000004
2009-10-08 11:14:56 [10888] [9] DEBUG:   command_status: 1031 = 0x00000407
2009-10-08 11:14:56 [10888] [9] DEBUG:   sequence_number: 25577 = 0x000063e9
2009-10-08 11:14:56 [10888] [9] DEBUG:   message_id: NULL
2009-10-08 11:14:56 [10888] [9] DEBUG: SMPP PDU dump ends.
2009-10-08 11:14:56 [10888] [9] ERROR: SMPP[new]: SMSC returned error code
0x00000407 (Vendor-specific error, please refer to your SMPP provider) in
response to submit_sm.
[I edit some data]

The situation is my telco doing migration system with optional parameter.
and they need wireshark data from us
From that there is submit_sm (kannel log above), but i can't see submit_sm
in wireshark, why this could happen.  i have another connection to other
port for the same ip and that connection not using any meta data and it work
give submit_sm in wireshark.

Regards
Benjamin