At the moment there is no way to add the destination number of the message to the event description. But it is a good idea and I will add it to the list of new features for the next version of Diafaan SMS Server.
Got reply from Telia and operator code is correct, so I guess I will have to live with these warnings.
I will try to tune the send speed and see if this has any effect.
One last question (for now at least):
The Events log only gives the error code, example:
The GSM Modem returned +CMS ERROR: 513 (Lower layer failure (for SMS)) after the command.
Is there any way to see which receiver (mobile number) that caused the error, without having to decode the PDU string?
Diafaan SMS Server tries to re-send failed messages two times by default, but you can increase the maximum number of send-attempts in the 'Gateways' settings of each connector. A message send error means that one attempt to send the message failed but if there are no errors in the send log, one of the next send attempts for the message was successful.
I don't think that it is possible to change the operator code on the SIM card, at least not by you, but your network operator might be willing to exchange the SIM card for new ones with the most recent home network code.
There is not much that you can do in Diafaan SMS Server to solve the roaming problem or the CMS errors, the modem automatically logs on to the best network that is allowed by the SIM card. It is possible to force the modem to log on to a specific network if you know the operator code of the network. I don't think it will have much effect on the number of CMS errors but maybe it is worth a try. For instance, to force the modem to use network code '12345', you can set the 'ModemInitializationBeginning' property in the advanced settings of the GSM Modem Gateway to 'AT+COPS=1,2,"12345"'.
Another measure that sometimes works to prevent CMS errors is to slow down the send speed, you can try to set the 'SendDelayTime' in the advanced settings of the GSM Modem Gateway to 1 or 2 seconds and see how that affects the number of send errors.
Found an old Siemens TC35i modem and moved one of the SIM cards to this, and configured as a gateway.
Also roaming warnings here og CMS errors, but here i get CMS error 500 instead of 513.
I am a bit confused as to whether the SMSes that cause errors are actually sent. There are no errors in the send log, but on the "Status" pane for the modem under statistics I have "Message Part sent: 122" and "Message send errors: 50" (example from one of the modems).
Update. I spoke to my phone company (Telia in Denmark) and the roaming problem might be because Telia and another company (Telenor) have merged networks and possibly the operator codes does not match.
I do not know if it is possible to change the operator code on the SIM card?
The nice lady in support did not know the exact codes but promised to investigate.
Bought a new SMS modem pool with q24plus modems as per your recommendations. Revision code is now Q24PL001.
Modems are still roaming, and I still get CMS ERROR 513.
It is not certain that CMS ERROR 513 and the roaming problem are related but it is not unlikely either. The alert in the event log of Diafaan SMS Server is a warning that the modem is not able to log on to the home network of the SIM card and uses an alternative network instead. In itself this does not have to be a problem, it is just a warning to remind you of a situation that might be undesirable when roaming is more expensive.
There can be a couple of reasons why your modem is roaming. Perhaps the network strength of your home network is too low in the location of the modem. In that case it might help to move your modems to another location or use better antenna's.
It is also possible that the modem modules are not fully compatible with your home network, the Q2403A modules use a pretty old GSM chipset that sometimes has a problem with modern mobile networks. The Q24Plus modules that are often an option for GSM modem pools are more expensive but they are of a newer design and seem to have fewer compatibility problems.
Another problem could be that your network does not have 2G coverage in your area anymore. In some countries, the 2G network is slowly being dismantled and replaced by 3G and 4G cells. If that is the case then the only option might be to use 3G modems. This could also explain why you do not see roaming on a 3G phone.
We have an 8-port modem pool with Wavecom modems.
I am a bit unsure about the exact modem version, but in SMS server they are recognized as "WAVECOM MODEM / MULTIBAND 900E 1800" and a revision code that says Q2403A among a lot of other numbers.
Once every hour, all modems logs an event stating: "The GSM modem is not logged on to the home network but is roaming on another network."
GSM operator seems to be identified correctly (TELIA DK), Network is "Unknown".
If I put the SIM card in a normal phone, it is working fine and no roaming occurs.
Things seem to be running, SMSes are sent, but for each one send an "CMS ERROR 513" event is logged. I would very much like to get rid of these events, but I am unsure whether it is linked to the roaming events, or if it is two different problems.
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 481
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 876