I checked many many times, kannel is sending empty message when i type these
special characters. I traced by ethereal the smpp block and there is no text
forwarded by kannel to SMSC. Also there is no ascii configuration in SMSC
just GSM alphabet.

Strange anyway here is the debug

2009-05-06 09:29:35 [5168] [3] INFO: sendsms sender:<test1:6600>
(10.1.21.236) to:<355672006666> msg:<é>
2009-05-06 09:29:35 [5168] [3] DEBUG: Stored UUID
3b0f4d3e-fba6-4d5c-abe0-97ccab3bdf03
2009-05-06 09:29:35 [5168] [3] DEBUG: message length 2, sending 1 messages
2009-05-06 09:29:35 [5168] [3] DEBUG: Status: 202 Answer: <Sent.>
2009-05-06 09:29:35 [5168] [3] DEBUG: Delayed reply - wait for bearerbox
2009-05-06 09:29:35 [5157] [10] DEBUG: boxc_receiver: sms received
2009-05-06 09:29:35 [5157] [10] DEBUG: send_msg: sending msg to box:
<10.1.21.137>
2009-05-06 09:29:35 [5168] [0] DEBUG: Got ACK (0) of
3b0f4d3e-fba6-4d5c-abe0-97ccab3bdf03
2009-05-06 09:29:35 [5168] [0] DEBUG: HTTP: Resetting HTTPClient for
`10.1.21.236'.
2009-05-06 09:29:35 [5157] [6] DEBUG: SMPP[internal1]: Sending PDU:
2009-05-06 09:29:35 [5157] [6] DEBUG: SMPP PDU 0x8f48190 dump:
2009-05-06 09:29:35 [5157] [6] DEBUG:   type_name: submit_sm
2009-05-06 09:29:35 [5157] [6] DEBUG:   command_id: 4 = 0x00000004
2009-05-06 09:29:35 [5157] [6] DEBUG:   command_status: 0 = 0x00000000
2009-05-06 09:29:35 [5157] [6] DEBUG:   sequence_number: 2619 = 0x00000a3b
2009-05-06 09:29:35 [5157] [6] DEBUG:   service_type: NULL
2009-05-06 09:29:35 [5157] [6] DEBUG:   source_addr_ton: 2 = 0x00000002
2009-05-06 09:29:35 [5157] [6] DEBUG:   source_addr_npi: 1 = 0x00000001
2009-05-06 09:29:35 [5157] [6] DEBUG:   source_addr: "6600"
2009-05-06 09:29:35 [5157] [6] DEBUG:   dest_addr_ton: 2 = 0x00000002
2009-05-06 09:29:35 [5157] [6] DEBUG:   dest_addr_npi: 1 = 0x00000001
2009-05-06 09:29:35 [5157] [6] DEBUG:   destination_addr: "355672006666"
2009-05-06 09:29:35 [5157] [6] DEBUG:   esm_class: 3 = 0x00000003
2009-05-06 09:29:35 [5157] [6] DEBUG:   protocol_id: 0 = 0x00000000
2009-05-06 09:29:35 [5157] [6] DEBUG:   priority_flag: 0 = 0x00000000
2009-05-06 09:29:35 [5157] [6] DEBUG:   schedule_delivery_time: NULL
2009-05-06 09:29:35 [5157] [6] DEBUG:   validity_period: NULL
2009-05-06 09:29:35 [5157] [6] DEBUG:   registered_delivery: 0 = 0x00000000
2009-05-06 09:29:35 [5157] [6] DEBUG:   replace_if_present_flag: 0 =
0x00000000
2009-05-06 09:29:35 [5157] [6] DEBUG:   data_coding: 0 = 0x00000000
2009-05-06 09:29:35 [5157] [6] DEBUG:   sm_default_msg_id: 0 = 0x00000000
2009-05-06 09:29:35 [5157] [6] DEBUG:   sm_length: 1 = 0x00000001
2009-05-06 09:29:35 [5157] [6] DEBUG:   short_message:
2009-05-06 09:29:35 [5157] [6] DEBUG:    Octet string at 0x8f47a68:
2009-05-06 09:29:35 [5157] [6] DEBUG:      len:  1
2009-05-06 09:29:35 [5157] [6] DEBUG:      size: 3
2009-05-06 09:29:35 [5157] [6] DEBUG:      immutable: 0
2009-05-06 09:29:35 [5157] [6] DEBUG:      data:
05                                                .
2009-05-06 09:29:35 [5157] [6] DEBUG:    Octet string dump ends.
2009-05-06 09:29:35 [5157] [6] DEBUG: SMPP PDU dump ends.
2009-05-06 09:29:35 [5157] [6] DEBUG: SMPP[internal1]: Got PDU:
2009-05-06 09:29:35 [5157] [6] DEBUG: SMPP PDU 0x8f48190 dump:
2009-05-06 09:29:35 [5157] [6] DEBUG:   type_name: submit_sm_resp
2009-05-06 09:29:35 [5157] [6] DEBUG:   command_id: 2147483652 = 0x80000004
2009-05-06 09:29:35 [5157] [6] DEBUG:   command_status: 0 = 0x00000000
2009-05-06 09:29:35 [5157] [6] DEBUG:   sequence_number: 2619 = 0x00000a3b
2009-05-06 09:29:35 [5157] [6] DEBUG:   message_id: "2075294281"


As you can see : 2009-05-06 09:29:35 [5157] [6] DEBUG:      data: 05
Kannel converts to hexa value, but it comes empty to mobile



On Thu, May 7, 2009 at 12:38 PM, Jovan Kostovski <[email protected]> wrote:

> Hi Elton,
>
> In the past I was working for a mobile operator and we experienced the
> same problem,
> due to some particular ESME character encoding configuration on the SMSC
> side.
> For some reason the SMSC was configured to use ASCII charset so we used
> alt-dcs=1 in the Kannel's smsc-group to correct this issue and sent
> GSM7 encoded messages.
>
> I would suggest you to check the ESME logs on the SMSC side to see what
> you get on the SMSC sent from Kannel.
>
> I agree with Falko it must be some configuration issue.
>
> BR, Jovan
>

Reply via email to