Here you go:
 DEBUG: SMPP PDU 0x7f6554000a10 dump:
 DEBUG:   type_name: submit_sm
 DEBUG:   command_id: 4 = 0x00000004
 DEBUG:   command_status: 0 = 0x00000000
 DEBUG:   sequence_number: 20068 = 0x00004e64
 DEBUG:   service_type: NULL
 DEBUG:   source_addr_ton: 5 = 0x00000005
 DEBUG:   source_addr_npi: 0 = 0x00000000
 DEBUG:   source_addr: "+123456789"
 DEBUG:   dest_addr_ton: 2 = 0x00000002
 DEBUG:   dest_addr_npi: 1 = 0x00000001
 DEBUG:   destination_addr: "+1987654321"
 DEBUG:   esm_class: 3 = 0x00000003
 DEBUG:   protocol_id: 0 = 0x00000000
 DEBUG:   priority_flag: 0 = 0x00000000
 DEBUG:   schedule_delivery_time: NULL
 DEBUG:   validity_period: "140000110005000+"
 DEBUG:   registered_delivery: 0 = 0x00000000
 DEBUG:   replace_if_present_flag: 0 = 0x00000000
 DEBUG:   data_coding: 0 = 0x00000000
 DEBUG:   sm_default_msg_id: 0 = 0x00000000
 DEBUG:   sm_length: 158 = 0x0000009e
 DEBUG:   short_message:
 DEBUG:    Octet string at 0x7f65540065c0:
 DEBUG:      len:  158
 DEBUG:      size: 159
 DEBUG:      immutable: 0

--data--


 DEBUG:    Octet string dump ends.
 DEBUG: SMPP PDU dump ends.
 DEBUG: SMPP[XXXXXXXXXX]: throughput (6.00,19.00)
 DEBUG: SMPP[XXXXXXXXXX]: throughput (6.00,19.00)
 WARNING: SMPP: PDU NULL terminated string (message_id) has no NULL.
 DEBUG: SMPP[XXXXXXXXXX]: Got PDU:
 DEBUG: SMPP PDU 0x7f6554000a10 dump:
 DEBUG:   type_name: submit_sm_resp
 DEBUG:   command_id: 2147483652 = 0x80000004
 DEBUG:   command_status: 88 = 0x00000058
 DEBUG:   sequence_number: 20067 = 0x00004e63
 DEBUG:   message_id: NULL
 DEBUG: SMPP PDU dump ends.

There is no throttling issue as I am operating well below the defined tps
of this link.





On Fri, Mar 7, 2014 at 5:31 PM, Stipe Tolj <[email protected]> wrote:

> Am 07.03.2014 07:34, schrieb [Digital^Dude] Ž:
>
>  Is there any possibility that kannel would send command_status != 0x00 ?
>> and the sms would get failed? Does this happen in case of link
>> throttling? How can throttling be handled at the ESME end?
>>
>
> not on the submit_sm_resp side, this is a PDU coming from the SMSC side.
> You will need to share your bearerbox.log in DEBUG log-level to the list to
> review exactly what is going on.
>
>
> Stipe
>
> --
> -------------------------------------------------------------------
> Kölner Landstrasse 419
> 40589 Düsseldorf, NRW, Germany
>
> tolj.org system architecture      Kannel Software Foundation (KSF)
> http://www.tolj.org/              http://www.kannel.org/
>
> mailto:st_{at}_tolj.org           mailto:stolj_{at}_kannel.org
> -------------------------------------------------------------------
>
>

Reply via email to