| NowSMS fails with "CMS Error: 535" |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Lee Whalen New member Username: Law Post Number: 6 Registered: 12-2006 |
Hello all, unfortunately I'm having further trouble with NowSMS. Just today, my users are reporting that they are no longer able to send out SMS messages. I took a look at the event log, and found this error message: "Message could not be sent to $phonenumber. CMS Error: 535". To try and rectify the problem, I performed the following actions: Stopped the NowSMS gateway Removed the Falcom USB Modem from the SMSC Connections Went to Windows Device Manager, verified the modem was still there, and that I was able to successfully query it Returned to NowSMS and re-added the modem, making sure that it was able to be tested successfully several times Restarted NowSMS with debug logs. Unfortunately, I'm still getting the same error, but I now have a debug log available. I've set it up on a pastebin, could someone in Support please take a look and let me know what I need to do in order to make this start working again? If you need any more information, please don't hesitate to let me know! Many thanks! --Lee Whalen Debug log can be found here: http://paste.lisp.org/display/34512 | |||
| Malcolm - Now Support Moderator Username: Malcolm Post Number: 74 Registered: 12-2006 |
Hi Lee, First, I want to clarify a point. The "CMS ERROR 535" error is being generated by your modem. In order to send an SMS message, NowSMS has to ask your modem to send it. The modem is indicating that it cannot, and returning this "CMS ERROR 535" to indicate the reason for the error. There is a great list of CMS error codes in the following thread: http://support.nowsms.com/discus/messages/1/829.html However, codes 512 and above are modem manufacturer specific. So in those cases, we need to find if your modem manufacturer has any information on their error codes. When we can't find the code, our first suggestion is usually to put the SIM card into a phone, and make sure that the phone can send SMS using the SIM. This can determine whether the problem might be a problem with your account with the mobile operator. Assuming the phone can send SMS ok with the SIM, then try changing the "SMS Access" parameter, trying both the "GSM" and "GPRS" settings to see if one of those settings works. Of course, it's also a good idea to try to find documentation from the modem manufacturer to see what the error code means. I have a manual for the Falcom Samba 75 USB modem, but it doesn't mention 535. Nor does the manual for the Falcom Samba 55/56. But I did find some documentation from both Siemens and Multitech, where both define error 535 as "Protocol Stack Busy". What you might want to do is edit SMSGW.INI, and under the [Modem - driver name] section header, add CommandPostInit1=AT+CMEE=2 For some modems, this command will cause them to return a text string for the error code, instead of a number. So this might tell us what error "535" means for that particular modem. If it does mean "Protocol Stack Busy", then this sounds like something has gone wrong in the modem's internal software. I'd suggest powering off the modem, give it a minute or so to reset itself, and then power it back up. I believe that particular modem draws its power off of the USB port, so remove it from the USB port to reset it. -- Malcolm Now Wireless Support | |||
| Lee Whalen New member Username: Law Post Number: 7 Registered: 12-2006 |
Malcom, thank you for the tip! I popped the SIM card into a handset, and lo, it didn't work. We replaced the SIM with a known-good one, and the gateway is cranking once again! Thanks so much for your help! --Lee | |||
