Re: SMPP getting stuck
Andreas Fink <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <[email protected]> |
On Donnerstag, Dezember 5, 2002, at 10:56 Uhr, Stipe Tolj wrote: >> 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. > I've fixed the problem in CVS. the implementation didnt expect to see an error as generic_err_resp but only as sms_submit_resp the error was a THROTTLING. Andreas Fink Global Networks Switzerland AG ------------------------------------------------------------------ Tel: +41-61-6666333 Fax: +41-61-6666334 Mobile: +41-79-2457333 Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland Web: http://www.global-networks.ch/ [email protected] ------------------------------------------------------------------ Member of the GSM Association