My impression is that the problem is caused by the the number format of some of the messages. I am not sure what happens but some mobile networks do not handle numbers that are not in international number format very well. The '#' (national) or '*' (unknown) characters before the number tells Diafaan SMS Server what the format of the number is and how it should be presented to the modem. You can also use the 'DefaultAddressType' option of the GSM Modem Gateway to specify what the default format of the numbers are for numbers without a leading '+', '#' or '*'.
The simplest solution might be to make sure that all numbers are in international number format. Diafaan SMS Server can convert numbers to different formats with the Number template option. But since you send the messages from a C# script it might be even easier to convert the numbers to the international number format in the script itself.
If you enable the communication log for the GSM Modem Gateway(s) you can see what happens in the communication between Diafaan SMS Server and the modem(s). There might be clues in the log about the cause of the blocking situation. For instance that the modem goes offline after an invalid number or that one of the messages is sent repeatedly, blocking other messages.
The default 'Max. send attempts' in Diafaan SMS Server is 3 attempts per gateway. This can be changed in the 'Gateways' settings of each connector.
The Scripting Connector does not have the functionality to remove a message from the send queue with the script.
We have a new installation DIAFAAN SMS Server with a GSM Modem Gateway and a scripting connector C# since a couple of weeks.
To send an SMS message, a file, containing phonenumber and message, is saved in a folder on the pc and the file is processed by a basic C# script in the Scripting Connector.
When a message is processed with a wrong phonenumber, the message stays in the Send Queue and it looks like new messages that are processed afterwards are disapearing without sending the SMS message.
The bat-file which is used to save the input files for the scripting connector script, saves an extra copy of the input file as a kind of backup. These backup files exist which normally means that the script should have processed the input file but I cannot find any logging about it.
The problem occurs when the phonenumber of a message does not have an international format (+32xxxxxxxxx).
I have found that an '#' or '*' can be used in front of the phonenumber to avoid the wrong phonenumber problem.
If the problem happens I have to remove the message from the Send queue to release the blocking situation.
I have already decreased the default value of 100 in the Max Send Attempts field to 2. Also the other fields on the screen concerning Send Attempts are decreased to 2. But it does not help.
Can I add something in the script to avoid the blocking issue ?
As far as I have found info about it in the Manual, it is not possible to delete a message from the Send Queue from withing the script.
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 583
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1204