This option was introduced in version 220.127.116.11 of Diafaan SMS Server.
Thank you for the quick response 🙂
I have checked the Advanced properties of some of the GSM Modems and I can't see a property called 'PermanentErrorList'. The closest I can find is 'PermitModemCommandMessages'?
We are running version 18.104.22.168, do we need to update?
CMS Error 21 means 'Short message transfer rejected'. It indicates that the mobile service does not accept the message but it does not give the exact reason why. It could be an invalid number, insufficient SMS credits or a number of other reasons. Diafaan SMS Server has no way of knowing if the message also will be rejected by another mobile service before trying it. The reason that the other modem may give a different error code for the same message is that the error is generated by the mobile operator and each operator has its own error handling procedures and might generate a different error code for the same underlying error.
Diafaan SMS Server is designed to route the messages through all designated gateways before giving up because it is also used for alarm applications where it is important that the message is sent even if there is a good chance that the message will be rejected by the next gateway as well. But you can change that behavior by adding a (list of) permanent error code(s) in the 'PermanentErrorList' property in the advanced settings of the GSM Modem Gateway. This makes sure that Diafaan SMS Server does not make further send attempts when this error is returned by the modem.
I was wondering if you could clarify something for me?
We have quite a complicated setup, so I'm going to massively simplify things to home in on the specific point.
You have two sim's, and each simm is for a different provider. Each simm is setup as a GSM Modem.
You have a scripting gateway that calls PostDispatch like so (the first 5 values are obviously variables, the last two values are hard coded)
PostDispatchMessage(recordId, toAddress, fromAddress, strMessage, messageType, "GSM1", "GSM2")
If when sending the message Diafaan recieves a CMS Error 21 (rejected) message from the network it fails over and tries to send the message via the backup gateway.
We have found that in a high percentage of cases the attempt on the backup gateway also fails (albeit with a slightly different error code).
Is this behaviour by design? Should Diafaan be trying to failover to the second gateway when confronted with a CMS 21 error?
Is there any way to change this behaviour?
If there isn't then it would be great if you could define a list of codes that will always fail over, and a list of codes that will never fail over.
Look forward to your response, hope that makes sense!
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 522
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1018