Re: Kannel Bug in SMPP handling

Falko Ziemann Tue, 03 Mar 2009 10:11:27 -0800

Your guess is right...

you're now in the area of sms-service again. I guess you have erasedthe sms-service with "keyword = default", which I sent to you a coupleof hours earlier, from your kannel-config.


Put it back in place and there you go...

Regards
Falko

Am 03.03.2009 um 18:49 schrieb Elton Hoxha:

Hi Falko,

Thanks for orientating me to the right path :)
I configured another 6 octets smpp client and from smsbox we have:
2009-03-02 22:47:23 [12517] [4] WARNING: No translation found for<Tl> from <+355672509006> to <15106>
2009-03-02 22:47:23 [12517] [4] ERROR: request failed
2009-03-02 22:47:23 [12517] [4] DEBUG: message length 14, sending 1messages2009-03-02 22:47:23 [12517] [0] DEBUG: Got ACK (0) of 4ab79d17-dc50-43de-bea3-22badbb0e6322009-03-02 22:47:23 [12517] [0] DEBUG: No client - multi-send or ACKto pull-reply
No translation for TI (TI is the content of sms I typed), does itmean I`m not calling any API to process that incoming SMS???
from the bearebox:

2009-03-02 22:47:23 [12509] [6] DEBUG: SMPP PDU 0x9e9b338 dump:
2009-03-02 22:47:23 [12509] [6] DEBUG:   type_name: deliver_sm
2009-03-02 22:47:23 [12509] [6] DEBUG:   command_id: 5 = 0x00000005
2009-03-02 22:47:23 [12509] [6] DEBUG: command_status: 0 =0x000000002009-03-02 22:47:23 [12509] [6] DEBUG: sequence_number: 302 =0x0000012e
2009-03-02 22:47:23 [12509] [6] DEBUG:   service_type: "cca106"
2009-03-02 22:47:23 [12509] [6] DEBUG: source_addr_ton: 1 =0x000000012009-03-02 22:47:23 [12509] [6] DEBUG: source_addr_npi: 1 =0x00000001
2009-03-02 22:47:23 [12509] [6] DEBUG:   source_addr: "355672509006"
2009-03-02 22:47:23 [12509] [6] DEBUG:   dest_addr_ton: 0 = 0x00000000
2009-03-02 22:47:23 [12509] [6] DEBUG:   dest_addr_npi: 1 = 0x00000001
2009-03-02 22:47:23 [12509] [6] DEBUG:   destination_addr: "15106"
2009-03-02 22:47:23 [12509] [6] DEBUG:   esm_class: 0 = 0x00000000
2009-03-02 22:47:23 [12509] [6] DEBUG:   protocol_id: 0 = 0x00000000
2009-03-02 22:47:23 [12509] [6] DEBUG:   priority_flag: 0 = 0x00000000
2009-03-02 22:47:23 [12509] [6] DEBUG:   schedule_delivery_time: NULL
2009-03-02 22:47:23 [12509] [6] DEBUG:   validity_period: NULL
2009-03-02 22:47:23 [12509] [6] DEBUG: registered_delivery: 1 =0x000000012009-03-02 22:47:23 [12509] [6] DEBUG: replace_if_present_flag: 0= 0x00000000
2009-03-02 22:47:23 [12509] [6] DEBUG:   data_coding: 0 = 0x00000000
2009-03-02 22:47:23 [12509] [6] DEBUG: sm_default_msg_id: 0 =0x00000000
2009-03-02 22:47:23 [12509] [6] DEBUG:   sm_length: 2 = 0x00000002
2009-03-02 22:47:23 [12509] [6] DEBUG:   short_message: "Tl"
2009-03-02 22:47:23 [12509] [6] DEBUG: SMPP PDU dump ends.
2009-03-02 22:47:23 [12509] [9] DEBUG: send_msg: sending msg to box:<127.0.0.1>2009-03-02 22:47:23 [12509] [9] DEBUG: boxc_sender: sent message to<127.0.0.1>
2009-03-02 22:47:23 [12509] [6] DEBUG: SMPP[internal]: Sending PDU:
2009-03-02 22:47:23 [12509] [6] DEBUG: SMPP PDU 0x9e9fd30 dump:
2009-03-02 22:47:23 [12509] [6] DEBUG:   type_name: deliver_sm_resp
2009-03-02 22:47:23 [12509] [6] DEBUG: command_id: 2147483653 =0x800000052009-03-02 22:47:23 [12509] [6] DEBUG: command_status: 0 =0x000000002009-03-02 22:47:23 [12509] [6] DEBUG: sequence_number: 302 =0x0000012e
2009-03-02 22:47:23 [12509] [6] DEBUG:   message_id: NULL
2009-03-02 22:47:23 [12509] [6] DEBUG: SMPP PDU dump ends.
2009-03-02 22:47:23 [12509] [8] DEBUG: boxc_receiver: sms received
2009-03-02 22:47:23 [12509] [8] DEBUG: send_msg: sending msg to box:<127.0.0.1>
2009-03-02 22:47:23 [12509] [6] DEBUG: SMPP[internal]: Sending PDU:
2009-03-02 22:47:23 [12509] [6] DEBUG: SMPP PDU 0x9e9b2f8 dump:
2009-03-02 22:47:23 [12509] [6] DEBUG:   type_name: submit_sm
2009-03-02 22:47:23 [12509] [6] DEBUG:   command_id: 4 = 0x00000004
2009-03-02 22:47:23 [12509] [6] DEBUG: command_status: 0 =0x000000002009-03-02 22:47:23 [12509] [6] DEBUG: sequence_number: 2 =0x00000002
2009-03-02 22:47:23 [12509] [6] DEBUG:   service_type: NULL
2009-03-02 22:47:23 [12509] [6] DEBUG: source_addr_ton: 2 =0x000000022009-03-02 22:47:23 [12509] [6] DEBUG: source_addr_npi: 1 =0x00000001
2009-03-02 22:47:23 [12509] [6] DEBUG:   source_addr: "15106"
2009-03-02 22:47:23 [12509] [6] DEBUG:   dest_addr_ton: 1 = 0x00000001
2009-03-02 22:47:23 [12509] [6] DEBUG:   dest_addr_npi: 1 = 0x00000001
2009-03-02 22:47:23 [12509] [6] DEBUG: destination_addr:"355672509006"
2009-03-02 22:47:23 [12509] [6] DEBUG:   esm_class: 3 = 0x00000003
2009-03-02 22:47:23 [12509] [6] DEBUG:   protocol_id: 0 = 0x00000000
2009-03-02 22:47:23 [12509] [6] DEBUG:   priority_flag: 0 = 0x00000000
2009-03-02 22:47:23 [12509] [6] DEBUG:   schedule_delivery_time: NULL
2009-03-02 22:47:23 [12509] [6] DEBUG:   validity_period: NULL
2009-03-02 22:47:23 [12509] [6] DEBUG: registered_delivery: 0 =0x000000002009-03-02 22:47:23 [12509] [6] DEBUG: replace_if_present_flag: 0= 0x00000000
2009-03-02 22:47:23 [12509] [6] DEBUG:   data_coding: 0 = 0x00000000
2009-03-02 22:47:23 [12509] [6] DEBUG: sm_default_msg_id: 0 =0x00000000
2009-03-02 22:47:23 [12509] [6] DEBUG:   sm_length: 14 = 0x0000000e
2009-03-02 22:47:23 [12509] [6] DEBUG: short_message: "RequestFailed"
2009-03-02 22:47:23 [12509] [6] DEBUG: SMPP PDU dump ends.

I marked some bold lines as below;

Why the service type is null in the submit_sm block?
what does short_message: "Request Failed" means?
Thanks a lot for your patience after this looooooooooooooooooooongdiscussion :)
On Tue, Mar 3, 2009 at 6:29 PM, Falko Ziemann <fal...@gmail.com>wrote:
Hi,
During the looooooong discussion with Elton it turned out thatkannel has a bug in his smpp 3.4 implementation (which didn't causeEltons problem, but anyway...)
It refuses the too long service-type in the deliver_sm (which is okwith the spec) but sets it for itself in the submit_sm command...
Is there a developer who wants to touch the smpp area of kannel?
submit_sm sets a service_type with more then 6 chars in smpp 3.4...This must be refused by kannel even configured according to chapter4.4.1 of smpp spec 3.4
Regards
Falko

Re: Kannel Bug in SMPP handling

Reply via email to