|
Hi everyone, my problem is the following. I have a SMPP-connection to send WAP-Push messages but those are falsely delivered as simple text and the SMSC-Support pointed out what I got to fix. Since then I've already spent two days of digging in the Kannel documentation and mailing-list as well as the SMPP 3.4 spec (and of course lots of trial-and-error) but still can't figure how to solve this. To make it easier for any of you to help I'll give you the following information. I hope that's sufficient? 0. kannel version and OS 1. detailed problem description 2. smpp dump of sending a wap-push from bearerbox.log 3. smsc config 4. parameters used with sendsms interface 0. kannel version and OS - Kannel 1.4.0 stable - Red Hat Enterprise Linux ES release 3 (Taroon Update 3) - Kernel 2.4.21-20.EL - SMPP 3.4 1. detailed problem description In the past I configured two other SMPP (version 3.3) connections in the exact same environment and succeded sending WAP-Push messages (unfortunately those are no longer in use and none of their logfiles exist). One thing that doesn't work is an esm_class of 67 where it should be 64 as the SMSC's support pointed out (which I could verify reading the SMPP-spec). How can I manipulate it? Another thing is a DCS of 4 where it should be 5 (information supplied by the SMSC-support). My guess would be that it corresponds to the data_coding (marked bold in section 2). The Kannel doc says I can use the sendsms-interface parameters mclass, mwi, coding and compress. After some testing by myself it seems that mclass, mwi and compress can be ruled out as they result in data_coding much higher than what I need. What I figured out is that coding has to be set to 1 (=data_coding of 4), which is done implicitly since wap-push msg's are 8-bit binary. So how do I get a 5 (setting a charset didn't change a thing)...or maybe the SMSC-Support is wrong or uses some strange implementation of SMPP? 2. debug output of sending a message from bearerbox.log (problems are marked bold): 2006-08-08 15:42:53 [2466] [7] DEBUG: SMPP PDU 0x86388e0 dump: 2006-08-08 15:42:53 [2466] [7] DEBUG: type_name: submit_sm 2006-08-08 15:42:53 [2466] [7] DEBUG: command_id: 4 = 0x00000004 2006-08-08 15:42:53 [2466] [7] DEBUG: command_status: 0 = 0x00000000 2006-08-08 15:42:53 [2466] [7] DEBUG: sequence_number: 2 = 0x00000002 2006-08-08 15:42:53 [2466] [7] DEBUG: service_type: NULL 2006-08-08 15:42:53 [2466] [7] DEBUG: source_addr_ton: 5 = 0x00000005 2006-08-08 15:42:53 [2466] [7] DEBUG: source_addr_npi: 0 = 0x00000000 2006-08-08 15:42:53 [2466] [7] DEBUG: source_addr: "SOME_STRING" 2006-08-08 15:42:53 [2466] [7] DEBUG: dest_addr_ton: 1 = 0x00000001 2006-08-08 15:42:53 [2466] [7] DEBUG: dest_addr_npi: 1 = 0x00000001 2006-08-08 15:42:53 [2466] [7] DEBUG: destination_addr: "MSISDN" 2006-08-08 15:42:53 [2466] [7] DEBUG: esm_class: 67 = 0x00000043 2006-08-08 15:42:53 [2466] [7] DEBUG: protocol_id: 0 = 0x00000000 2006-08-08 15:42:53 [2466] [7] DEBUG: priority_flag: 0 = 0x00000000 2006-08-08 15:42:53 [2466] [7] DEBUG: schedule_delivery_time: NULL 2006-08-08 15:42:53 [2466] [7] DEBUG: validity_period: NULL 2006-08-08 15:42:53 [2466] [7] DEBUG: registered_delivery: 0 = 0x00000000 2006-08-08 15:42:53 [2466] [7] DEBUG: replace_if_present_flag: 0 = 0x00000000 2006-08-08 15:42:53 [2466] [7] DEBUG: data_coding: 4 = 0x00000004 2006-08-08 15:42:53 [2466] [7] DEBUG: sm_default_msg_id: 0 = 0x00000000 2006-08-08 15:42:53 [2466] [7] DEBUG: sm_length: 69 = 0x00000045 2006-08-08 15:42:53 [2466] [7] DEBUG: short_message: 2006-08-08 15:42:53 [2466] [7] DEBUG: Octet string at 0x86385a8: 2006-08-08 15:42:53 [2466] [7] DEBUG: len: 69 2006-08-08 15:42:53 [2466] [7] DEBUG: size: 1024 2006-08-08 15:42:53 [2466] [7] DEBUG: immutable: 0 2006-08-08 15:42:53 [2466] [7] DEBUG: data: 06 05 04 0b 84 23 f0 01 06 04 03 ae 81 ea 02 05 .....#.......... 2006-08-08 15:42:53 [2466] [7] DEBUG: data: 6a 00 45 c6 0b 03 68 74 74 70 3a 2f 2f 77 77 77 j.E...http://www 2006-08-08 15:42:53 [2466] [7] DEBUG: data: 2e 62 61 72 2e 63 6f 6d 00 11 03 32 31 38 34 34 .bar.com...21844 2006-08-08 15:42:53 [2466] [7] DEBUG: data: 39 37 32 38 40 63 69 6d 6f 62 69 00 08 01 03 66 [EMAIL PROTECTED] 2006-08-08 15:42:53 [2466] [7] DEBUG: data: 6f 6f 00 01 01 oo... 2006-08-08 15:42:53 [2466] [7] DEBUG: Octet string dump ends. 2006-08-08 15:42:53 [2466] [7] DEBUG: SMPP PDU dump ends. 3. SMSC-config # SMSC CONNECTION group = smsc smsc = smpp host = 222.333.444.555 port = 1 receive-port = 0 transceiver-mode = false smsc-username = "foo" smsc-password = "bar" system-type = interface-version = 34 #default is 34 (= version 3.4) address-range = "111.222.333.444" connect-allow-ip = 127.0.0.1 source-addr-ton = 5 #alphanumeric dest-addr-ton = 1 #international #source-addr-npi = 0 #ignored by SMSC #dest-addr-npi = 0 #ignored by SMSC 4. parameters used in requests to sendsms-interface - to=URL_ENCODED_MSISDN - wbxml=_WBXML - udh=%06%05%04%0B%84%23%F0 Best regards, Christian. |
