SMS Server Tools 3
 Menu
Basic information:
Additional information:
Support:
Get SMS Server Tools 3:
Additional Options

 Sponsored links

 Search
Custom Search

 Visitor locations
 
 SMS Server Tools 3 Community
Welcome, Guest. The forum is currently read-only, but will open soon. Sat Dec 21, 2024 17:08
SMSTools3 Community » Help and support Bottom

[answered] CMS ERROR: 33570

  This topic is locked

Page:  1

Author Post
Member
Registered:
Mar 2011
Location: Roma, Italy
Operating system name and version: Linux Debian 5
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: Benq M32 (DealExtreme)
Interface: USB


Hi and thanks for smsd!! :)

I have bought the DealExtreme Benq M32 modem, and it works flawlessly in Windows (urgh!)
when I send an SMS thru sendsms, it cannot send it and in the smsd.log a weird error appears: +CMS ERROR: 33570

Here's the log file:



and here is the smsd.conf:

devices = GSM1
logfile = /var/log/smsd.log
loglevel = 7

[GSM1]
device = /dev/ttyUSB0
init = AT+CNMI=0,0,0,1,0
incoming = yes
check_memory_method = 31
phonecalls = clip
voicecall_hangup_ath = yes
voicecall_cpas = yes
needs_wakeup_at = yes
using_routed_status_report = yes
routed_status_report_cnma = no
eventhandler = /usr/local/bin/smsevent
 
'smsdconf' Syntax Highlight powered by GeSHi


I cannot even find the meaning of that error code.. did this happen to anybody else?
moving the modem to another usb port doesn't help. a reboot sometimes helps, but it works only for a minute and then.. here's the 33570 again
Please help.. I'm completely stuck :(
Thanks a lot in advance!

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
I do not know about this error number, it's not a general CMS error, it's a modem specific and undocumented.

So, your system works for a minute, and then errors start to happen? Within this minute, on Debian, have you ever sent messages successfully?

Also, that message which failed, do you know if it still was received (probably three times) or not?

As the modem worked in Windows, what program did you use for testing, and what was the communication speed (baudrate)? I think that the communication speed may be a clue, at the same time when it seems that your Linux is under very heavy load ("Took 2.0 seconds to get a file...", but there was only one file).

If there is some problem with a communication between smsd and modem, you could use a modem setting verify_pdu = yes to detect it. With this setting PDU is echoed back, and smsd will check if it's returned correctly.

Member
Registered:
Mar 2011
Location: Roma, Italy
Topic owner
Keke, thank you very much for your reply.
The machine is a laptop with a solid state HD that sometimes is slower than expected, but I don't think that its performance is tied to this issue.
I added verify_pdu = yes, and I just rebooted.
I sent another sms, but the message was not sent (I verified that it was not received) and here's the new log:



..so I discovered that the pdu was echoed correctly and the first error is 33571. But I'm still stuck.. any ideas? what else could I try?
thanks!!

Member
Registered:
Mar 2011
Location: Roma, Italy
Topic owner
I forgot to write that I quickly tried the modem with windows, using default settings and the awful software that came with it, so I don't picked a particular baud rate..

Member
Registered:
Mar 2011
Location: Roma, Italy
Topic owner
please read "I don't picked" as "I don't think I picked" ;)

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Is that Windows machine the same laptop, or is it a desktop hardware?

In this forum here is one almost similar problem presented, in it's case the error code was 33825 which is undocumented too. In topic [solved] CMS ERROR: 33825, PA-HHCS wrote:

Quote
I moved the GSM Modem to another UBS Port just to see if that made any difference - which I did
we are now able to send and receive sms messages.

Not sure why moving the usb port - changed things - because we have done that once before, also when we first tested SMS Server tools using an old Samsung G600 we used that port for about 3 weeks with out a problem.

However, there is a difference (another than error code): Answer to the PDU is received within one second, while in your case the time is about 10 seconds. And, as you said, moving the modem to another port had not helped.

In your case the modem reported "+CREG: 1, 7535, 7672" once, but in that time the cell id was not changed. A modem should report this only when it is asked, or when the cell id is changed. Perhaps the modem has problem with the GSM network. Signal quality is very good, so it's not a problem. When communicating with the network, modem draws more power. Assuming that you had a different machine running Windows, you could try to use a hub with external power supply.

Member
Registered:
Mar 2011
Location: Roma, Italy
Topic owner
Hi Keke, thanks for your suggestions.
I now think I have a defective unit. I tried it on several PCs, with and without USB hubs with external power, using different SIMs of different operators.. it works during the first minute after I plug it in, then it stops working and gives the dreaded CMS ERROR: 33570 when I try to send SMSs.
I'll try it again on windows when I'll have it at hand. In the meantime I bought another modem and it worked almost immediately (I already posted its working configuration). Thanks again!

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Hi Frank,
thank you for your donation!

DealExtreme has some kind of guarantee or return policy for those devices, have you checked if they are willing to replace it?

  This topic is locked

Page:  1

SMSTools3 Community » Help and support Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.