0x40 (64 in decimal) is used when the message has an UDH payload.

Messages over 160 characters use an UDH (to allow for later reasembly).

You only need to change the default from store and forward to default smsc,
and it should be fine, kannel will automagically use 0 for regular sms and
64 for concatenated messages (if you don't change the default, it will use 3
and 67 instead).

Regards,

Alex

On Fri, May 28, 2010 at 8:47 PM, Anderson Schmidt <alsn...@yahoo.com.br>wrote:

> Hi all,
>
> I have a SMSC documentation saying that for short SMS,
> the esm_class needs to be "0" and for long SMS, over than 159 chars,
> I have to use the value "64".
>
> Currently my Kannel instance sends for long SMS:
> esm_class: 67 = 0x00000043
> and for short SMS:
> esm_class: 3 = 0x00000003
>
> So, long SMSs are being splitted, not contatenated. And arriving on cell
> phones with some
> weird chars on each message beginning. Short SMS are OK.
>
>  I read about smsc.smpp.c hard-coded changing on esm_class default value,
> but even so, I probably will get some other problem using this
> new fixed value for all SMS.
>
> Any idea of what can I do to solve this problem?
>
> below the complete submit_sm command log:
>
> [6] DEBUG: SMPP PDU 0x783390 dump:
> [6] DEBUG:   type_name: submit_sm
> [6] DEBUG:   command_id: 4 = 0x00000004
> [6] DEBUG:   command_status: 0 = 0x00000000
> [6] DEBUG:   sequence_number: 5 = 0x00000005
> [6] DEBUG:   service_type: "CMT"
> [6] DEBUG:   source_addr_ton: 5 = 0x00000005
> [6] DEBUG:   source_addr_npi: 0 = 0x00000000
> [6] DEBUG:   source_addr: "xxx"
> [6] DEBUG:   dest_addr_ton: 1 = 0x00000001
> [6] DEBUG:   dest_addr_npi: 0 = 0x00000000
> [6] DEBUG:   destination_addr: "910000000000"
> [6] DEBUG:   esm_class: 67 = 0x00000043
> [6] DEBUG:   protocol_id: 0 = 0x00000000
> [6] DEBUG:   priority_flag: 0 = 0x00000000
> [6] DEBUG:   schedule_delivery_time: NULL
> [6] DEBUG:   validity_period: NULL
> [6] DEBUG:   registered_delivery: 0 = 0x00000000
> [6] DEBUG:   replace_if_present_flag: 0 = 0x00000000
> [6] DEBUG:   data_coding: 0 = 0x00000000
> [6] DEBUG:   sm_default_msg_id: 0 = 0x00000000
> [6] DEBUG:   sm_length: 159 = 0x0000009f
> [6] DEBUG:   short_message:
> [6] DEBUG:    Octet string at 0x780a50:
> [6] DEBUG:      len:  159
> [6] DEBUG:      size: 1024
> [6] DEBUG:      immutable: 0
> [6] DEBUG:      data: 05 00 03 00 02 01 54 65 73 74 20 75 73 69 6e 67
> ......Test using
> [6] DEBUG:      data: 20 6c 6f 6e 67 20 53 4d 53 20 6c 65 6e 67 68 74
> long SMS lenght
> [6] DEBUG:      data: 20 77 69 74 68 20 6d 6f 72 65 20 74 68 61 6e 20
> with more than
> [6] DEBUG:      data: 31 36 30 20 63 68 61 72 73 20 6f 66 20 63 6f 6e   160
> chars of con
> [6] DEBUG:      data: 74 65 6e 74 20 54 65 73 74 20 75 73 69 6e 67 20
> tent Test using
> [6] DEBUG:      data: 6c 6f 6e 67 20 53 4d 53 20 6c 65 6e 67 68 74 20
> long SMS lenght
> [6] DEBUG:      data: 77 69 74 68 20 6d 6f 72 65 20 74 68 61 6e 20 31
> with more than 1
> [6] DEBUG:      data: 36 30 20 63 68 61 72 73 20 6f 66 20 63 6f 6e 74   60
> chars of cont
> [6] DEBUG:      data: 65 6e 74 20 54 65 73 74 20 75 73 69 6e 67 20 6c   ent
> Test using l
> [6] DEBUG:      data: 6f 6e 67 20 53 4d 53 20 6c 65 6e 67 68 74 20      ong
> SMS lenght
> [6] DEBUG:    Octet string dump ends.
>
> Thanks a lot,
> Anderson
>
>
>
>

Reply via email to