They have all been set up completely before I started using Diafaan. The contents of the fields you mentioned ( 'SMSLogStatusText', 'SMSLogErrorCode' and 'SMSLogErrorText') are all NULL.
Issue #1: I take it that you are using the SQL Connector with MySQL or Oracle and that you are looking at the logs in the MessageLog table of the database, is that correct? After the initial set-up of the SQL Connector with MySQL or Oracle, Diafaan SMS Server only uses these 6 database fields. You can add the rest of the fields in the advanced settings of the SQL Connector settings. To be able to determine the reason why the messages could not be sent you should at least fill in the 'SMSLogStatusText', 'SMSLogErrorCode' and 'SMSLogErrorText' fields.
You can also look at the send log in the Diafaan SMS Server Console Program, this log has all the information about the message, including any error messages.
The only problem now is that when I reply through the web connector, I don't know how to set it up such that it will use the same gateway that the message came in through.
The browser application of the Web Connector does not have an option to send the reply message with a specific gateway. The HTTP API of the Web Connector can send a message to a specific gateway with the 'gateway' field in the 'send-message' HTTP API.
Thanks for replying, Henk.
My problem with issue #1 is that there is no other information why the messages failed to send. 🙁 Only the following fields -- id, sendtime, statuscode, messageto, messagetext, and (empty string) messageID -- have contents. all other fields are null.
I found a solution to my issue #2: I made the "more sensitive" gateway a backup gateway, same with the two all-network gateways.
The only problem now is that when I reply through the web connector, I don't know how to set it up such that it will use the same gateway that the message came in through. 🙂
On issue #1: Status code 300 just means that the message could not be sent. There should also be a description of the status, and usually an error code and error description, that explains the reason why the message could not be sent.
On issue #2: You can find more information about the routing options of Diafaan SMS Server in the online manual. For instance, with the 'only for to address ...' option in the 'Gateways' setting of each connector you can set or block a number range for each gateway. You can also specify a (list of) gateway(s) for each individual message with the 'Gateway' field in the MessageOut table of the SQL database.
I have set up Diafaan with four (4) modems, all with postpaid accounts, from three (3) different telecoms/networks, using an SQL Connector (and Web Connector).
All of the postpaid accounts have unlimited SMS sending, but two (2) of them are same-network only, while the other two (2) are all-networks. The all-net SIMs were set-up as Backup Gateways, while the same-net ones are Primary Gateways.
Currently, to send out SMS messages, I either just create/insert records into the MessageOut table and Diafaan sends them out. Usually I do this by copying batches of records from other tables.
My #1 issue is that sometimes, all the messages in one batch would all fail to send, getting StatusCode 300. But I can always just re-send them anyway, that's why I created other tables to store them (since Diafaan always empties out MessageOut when sending).
My #2 issue is that since majority of my recipients are on one of the telecoms with SAME-NET accounts, Diafaan INSISTS on using that network/gateway to send out the pending text messages, while the other ALL-NET sims are idle. How can I set it up so that it will use those backup gateways instantly? I can't set them up as Primary because this same issue would just make Diafaan use the first one for sending ALL messages.
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 539
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1067