Support forum

Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_TopicIcon
Error 24, Undeliverable, but message was sent and receipt received by Diafaan
sp_NewPost Add Reply sp_NewTopic Add Topic
July 5, 2018
11:31 am
Henk Helmantel
Admin
Forum Posts: 897
Member Since:
May 28, 2013
sp_UserOfflineSmall Offline

If error code 24 does not come from iQsim then it probably comes from the mobile operator. Unfortunately, error code 24 is not a standard SMS error code. It is a 'reserved' status code value and it could be an error code that is specific to the mobile operator.

It is clear however that Diafaan SMS Server receives a negative delivery report from the iQsim with an 'UNDELIV' status which means that the message could not be delivered. Diafaan SMS Server just shows the status that it receives from the iQsim gateway.

The information in the 'ErrorText' field in database is truncated because the field length is too small for the information. We will increase the field length for newly created databases in future versions of Diafaan SMS Server.

Regards, Henk

July 4, 2018
6:41 pm
Udo
Guest
Guests

Hello Henk,

After some more research I've found that:
a) Error 24 is not known to iQsim
b) Messages with error 24 were probably NOT delivered to handset, as far as we know (really not sure)
c) The message that Diafaan writes to the SQL DB in case of an error 24 is: "301, Error: Status error 'Undeliverable' received after the message was accepted by the SMPP gateway."
*Note: Diafaan can't write the full text to the DB, it is truncated. Should it be this way? In the database (MS SQL Express) I have the text 'Error: Status error 'Undeliverable' received after the message was accepted by t'

How exactly shall I interpret this error 24/301?
It seems to be a 'negative' DLR, but what causes it? Sometimes it are large numbers when compared to 200/201.

BR

Udo

June 16, 2018
10:39 am
Henk Helmantel
Admin
Forum Posts: 897
Member Since:
May 28, 2013
sp_UserOfflineSmall Offline

Hello Udo,

If I understand the problem correctly the iQsim device accepts the messages from Diafaan SMS server (status code 200) and then sends an UNDELIV delivery report (DLR) back to Diafaan SMS Server (status code 301) with error code 24 even when the message is sent by the iQsim device and received on the mobile phone. Is that correct?

If this is what happens then the problem can't be solved by anything in Diafaan SMS Server because as far as I can determine Diafaan SMS Server receives and processes the UNDELIV DLR from the iQsim correctly.

I don't recognize error code 24 in the delivery report. It is not a GSM or SMPP error. It could be a custom error code from iQsim but I can't find any reference to the iQsim SMPP DLR error codes on the internet. Perhaps you can find information about the error codes in the manuals of the iQsim device.

Regards, Henk

June 15, 2018
10:53 pm
Udo
Guest
Guests

Hello,

I'm getting many errors 24, Undeliverable, but they aren't correct.
The messages have actually been sent.

Example:
2018/06/15 17:30:28.711 - command:submit_sm status:ok sequence:14882 source:10003 dest:+5511992595641 short_message:CAIXA ...
2018/06/15 17:30:54.171 - command:submit_sm status:ok sequence:14917 source:10003 dest:+5511992595641 short_message:CAIXA ...
2018/06/15 17:30:59.475 - command:deliver_sm status:ok sequence:3586 source:5511992595641 dest: receipt:id:2129987801 sub:001 dlvrd:000 submit date:1806152230 done date:1806152231 stat:UNDELIV err:024 Text:....................

1520303194 CTI : App 0 (200) - SMS - Calling() Called(+5511992595641) - Flags 0x06000010h
1520303194 ODBC : Session ODBC 491 SWITCH REQUEST CTI: App MSG Server / CalledNumber 005511992595641
1520303195 GK : Session GK 491 Fill CTI SEND SMS REQUEST to (Slot: 0 - Port :3)
1520304396 ODBCDR : send 1.41;314444;3;MSG Server;-1;-1;0;HUP-GSM02;0;3;111;17;20180615;203043;0;;005511992595641;0;264;1;1F;0;0;724051225142983;;724;0;;0;358268035972687;;isc01;38;;1;4211;3761
1520305740 CTI : App 0 (200) - SMS - Calling() Called(+5511992595641) - Flags 0x06000010h
1520305740 ODBC : Session ODBC 557 SWITCH REQUEST CTI: App MSG Server / CalledNumber 005511992595641
1520305740 GK : Session GK 557 Fill CTI SEND SMS REQUEST to (Slot: 0 - Port :5)
1520305959 ODBCDR : send 1.41;314496;3;MSG Server;-1;-1;0;HUP-3G02;0;5;111;17;20180615;203059;1;;005511992595641;0;264;0;10;0;0;724102294170562;;724;0;;0;358268032452816;;isc01;0;;1;40511;33536021
1520310268 CTI : SMS Delivery Report (724102294170562 : 5511992595641 : 113 : 1)
Date format: ddhhmmsscc, where cc is 1/100 s. In the hour field there is a 5 hour difference due to time zones.
The traces below are from an iQsim system.

Two attempts, on the first we had an operator failure (1F), but the second was ok (10). And the receipt was delivered less than 10 seconds after sending the SMS, so there should be no timeout.
More than 50% of the messages were sent and Diafaan received a delivery receipt, so it isn't a format issue.
About 25% of the messages have the "Undelivered" problem. The SMPP server shows a failure rate of only 3-4%

What can it be?

BR

Udo

Forum Timezone: Europe/Amsterdam

Most Users Ever Online: 494

Currently Online:
6 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Member Stats:

Guest Posters: 485

Members: 0

Moderators: 0

Admins: 1

Forum Stats:

Groups: 2

Forums: 3

Topics: 748

Posts: 2586

Newest Members:

, Henk Helmantel

Administrators: Henk Helmantel: 897