Re: SMPP submit_sm resp reserved error.

Stipe Tolj <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Organization Kannel Software Foundation (KSF)
Message-ID <[email protected]>
Am 07.03.2014 13:41, schrieb [Digital^Dude] ®:
> 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.

the command_status 0x58 is defined in the spec as throttling error. If 
you are way below your defined TPS, then you need to ask your SMSC 
provider what the purpose of the value is.

The submit_sm PDU has at least one "flaw", the dest_addr_ton = 0x02 
defines "national" numbering scheme, which is NOT what the 
destination_addr looks like.

Generally in SMPP there is no usage of the + prefix for the exit code.

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
-------------------------------------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.