| CMS Error 517 follow with hard reset of GSM modem |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Lite Support ⬆ Archive through September 20, 2012 ⬆ |
◄ ► |
| Author | Message | ||||
| Pavel Lipanov New member Username: Sloyt Post Number: 1 Registered: 02-2012 |
Hi guys! Our customer recently purchased NowSMS Lite and GSM modem. We followed all instructions and all become working. But suddenly we're receiving error CMS 517 always when we try to send sms. We tried to reset modem, restart server, change SIM-card, but nothing helps to us. And also we found dangerous that NowSMS resets modem after receiving CMS 517 error! Please, help us! What we're doing wrong way? Where to look for problem? P.S. There is NowSMS Lite log file in attachment with errors...
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3815 Registered: 08-2008 |
Hi Pavel, By default, NowSMS resets a modem after errors in order to try to recover it. Unfortunately, it is somewhat common for modems to get stuck in an unstable state. If you want to disable that behaviour, you can edit SMSGW.INI, and add ModemHardResetAfterError=No under the [SMSGW] header. There is also another recovery setting that is in the configuration dialog of NowSMS, but is not displayed in NowSMS Lite (but is still supported). This is RebootOnModemError=Yes, which goes under the [Modem - driver name] section header. (Not under the [SMSGW] header like the first setting.) That said, if you are getting this error even after a complete reboot (remove/reinsert modem), and with different SIMs, it sounds like something has failed internal to the modem. I am concerned that one of the early errors that appears in response to another init command might be more telling ... +CME ERROR: 769 These values are both manufacturer specific ... does that manufacturer have any documentation on their error codes? I've done some web searching, and I see CME Error 769 being referenced as meaning "unable to get control of required module". As it is a manufacturer specific value, there is no guarantee that this is what it actually means on your modem.. However, from one of the posts I saw relating to this error, I saw that the modem in question needed between 30 and 40 seconds after first access before it would actually start working properly. NowSMS is "jumping the gun" in reseting the modem so early. This logic should only be triggered after more consecutive errors. So try adding the ModemHardResetAfterError=No to avoid this reset. Perhaps the modem will wake up itself after 30 to 40 seconds. -- Des NowSMS Support | ||||
SMS log file
