Re: SMPP getting stuck

> 2002-12-05 06:57:53 [10] DEBUG: SMPP[link5]: Got PDU:
> 2002-12-05 06:57:53 [10] DEBUG: SMPP PDU 0x814fdc8 dump:
> 2002-12-05 06:57:53 [10] DEBUG: type_name: generic_nack_resp
> 2002-12-05 06:57:53 [10] DEBUG: command_id: 2147483648 = 0x80000000
> 2002-12-05 06:57:53 [10] DEBUG: command_status: 88 = 0x00000058
> 2002-12-05 06:57:53 [10] DEBUG: sequence_number: 31 = 0x0000001f
> 2002-12-05 06:57:53 [10] DEBUG: SMPP PDU dump ends.
> 2002-12-05 06:57:53 [10] ERROR: SMPP[link5]: Unknown PDU type 0x80000000, ignored.

hmm, ok, it's at least an "official" PDU for generic_nack.

from the 3.4 spec:

4.3 “GENERIC_NACK” PDU
This is a generic negative acknowledgement to an SMPP PDU submitted
with an invalid
message header. A generic_nack response is returned in the following
cases:
• Invalid command_length
If the receiving SMPP entity, on decoding an SMPP PDU, detects an
invalid
command_length (either too short or too long), it should assume that
the data is corrupt. In
such cases a generic_nack PDU must be returned to the message
originator.
• Unknown command_id
If an unknown or invalid command_id is received, a generic_nack PDU
must also be
returned to the originator.

Stipe

[email protected]
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [email protected]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are