SMS test through RCC

MartinQS · Post by **MartinQS** » Thu Apr 10, 2008 4:30 am

When I try to test my GSM settings through RCC it says "SMS Error: Klasse is niet geregistreerd". That's dutch for "SMS Error: Class not registered".
I have to test GSM settings on the physical server where Hostmonitor is running.

Is this a bug or a missing feature?

KS-Soft Europe · Post by **KS-Soft Europe** » Thu Apr 10, 2008 4:44 am

To make it work, you should copy KSGSMXLib.ocx from HostMonitor's folder to the folder, where rcc is located and perform the following command from the command line prompt: regsvr32 KSGSMXLib.ocx

Regards,
Max

MartinQS · Post by **MartinQS** » Thu Apr 10, 2008 6:52 am

I have a Nokia 6210 to send SMS messages from HostMonitor.
I use Msg class 1, Baudrate 9600 and text mode.

The message was delivered 4 times, and all of them had the same weird characters in the first sense. What am I doing wrong? The sms log shows no errors and only one message has been send.
Another test gives an error sending the sms but it does deliver 3 times!

Code: Select all

[10-4-2008 14:45:51]	Sys	Com port open .. Ok
[10-4-2008 14:46:06]	Sys	GSM modem initialization .. Ok
[10-4-2008 14:46:37]	Sys	Error: Cannot send message to +316********. GSM modem error. No reply on AT command: AT+CMGS="+316********",145>Test message

The only abnormal thing I can see is that it takes a lot of time to initialize the GSM modem (about 15 seconds).

KS-Soft Europe · Post by **KS-Soft Europe** » Thu Apr 10, 2008 7:35 am

MartinQS wrote:I have a Nokia 6210 to send SMS messages from HostMonitor.
I use Msg class 1, Baudrate 9600 and text mode.

I would suggest you to select "19200" baud rate and the "PDU" mode. It should help.

MartinQS wrote:The message was delivered 4 times, and all of them had the same weird characters in the first sense. What am I doing wrong?

What exact "weird" characters do you mean? HosMonitor send text that is specified in Msg. template, assigned to "Send SMS (GSM)" action.

MartinQS wrote:The sms log shows no errors and only one message has been send. Another test gives an error sending the sms but it does deliver 3 times!

I would ask you to do the following:
- add registry key HKEY_LOCAL_MACHINE\SOFTWARE\KS-Soft\GSMX, set DefaultRetries DWORD value to 1
- restart HostMonitor

MartinQS wrote:The only abnormal thing I can see is that it takes a lot of time to initialize the GSM modem (about 15 seconds).

Hm. Do you have real Nokia 6210 phone connected to the machine, where HostMonitor is running, or you do use another modem, but just selected "Nokia 6210" from "Modem Type" dropdown in "Options" -> "SMS: GSM" tab?

Regards,
Max

MartinQS · Post by **MartinQS** » Thu Apr 10, 2008 7:48 am

I have a real Nokia 6210 connected to the machine where HostMonitor is running.
I have set baud rate to 19200 and PDU mode. I also added the register key as you said. The message was not send.

Code: Select all

[10-4-2008 15:40:07]	Sys	Com port open .. Ok
[10-4-2008 15:40:20]	Sys	Com port close .. Ok
[10-4-2008 15:40:20]	Sys	Error: Cannot send message to +316********. GSM modem error. No reply on AT command: ATE1

I changed the baud rate to 9600 and switched modes but every configuration now gives the same error.

The "weird" characters were there only once and it replace part of the first sense with an alpha sign.

KS-Soft Europe · Post by **KS-Soft Europe** » Thu Apr 10, 2008 7:57 am

"No reply on AT command: ATE1" means HostMonitor is unable to communicate with modem. Probably, it is used by another application?
Are you able to connect to the modem using standard windows "HyperTerminal" utility?

Are you trying to send SMS using "SMS test" window? Do you use RCC to test SMS function or do you use HostMonitor itself?

Regards,
Max

MartinQS · Post by **MartinQS** » Thu Apr 10, 2008 8:27 am

There is no other software that uses the COM port. I didn't install any software to use the phone. I connected it for the first time today and I have only used HostMonitor to connect with the phone.

I do not have hyperterminal installed on that machine. I don't even know if Windows 2003 server has hyperterminal.

I'm trying to send a test SMS using the SMS GSM option panel from HostMonitor itself. I'm not using RCC for this.

MartinQS · Post by **MartinQS** » Thu Apr 10, 2008 8:35 am

New information. I set baud rate 19200 and PDU mode.
Then when I try to test send it gives an error, but when I instanly after the error try to resend it does this:

Code: Select all

[10-4-2008 16:30:58]	Sys	Com port open .. Ok
[10-4-2008 16:31:11]	Sys	Com port close .. Ok
[10-4-2008 16:31:11]	Sys	Error: Cannot send message to +316********. GSM modem error. No reply on AT command: ATE1
[10-4-2008 16:31:11]	Sys	Com port open .. Ok
[10-4-2008 16:31:13]	Sys	GSM modem initialization .. Ok
[10-4-2008 16:31:20]	Sys	Error: Cannot send message to +316********. GSM modem error. No reply on AT command: AT+CMGS=126>0001000B91135690...[lots of data]...D979900E14B381DA73
[10-4-2008 16:31:20]	Sys	Com port close .. Ok
[10-4-2008 16:31:20]	Sys	GSM modem deinitialization .. Ok

Maybe the phone takes somewhat long to connect and HostMonitor cuts the connection too soon?

KS-Soft Europe · Post by **KS-Soft Europe** » Thu Apr 10, 2008 8:44 am

MartinQS wrote:I don't even know if Windows 2003 server has hyperterminal.

Yes, of course Windows 2003 has HyperTerminal.

MartinQS wrote:Maybe the phone takes somewhat long to connect and HostMonitor cuts the connection too soon?

Probably... In this case, I would ask you to download the updated KSGSMXLib.ocx library: http://www.ks-soft.net/download/test/ksgsmxlib.zip
Please, stop HostMonitor, unzip attached file into HostMonitor's folder.

After that, I would ask you to ad the following DWORD values under HKEY_LOCAL_MACHINE\SOFTWARE\KS-Soft\GSMX registry key:
RepeatTimeout 1000
DefaultRecTimeOut 15000

Please do not forget to restart HostMonitor.

Regards,
Max

MartinQS · Post by **MartinQS** » Thu Apr 10, 2008 8:56 am

I did what you asked.
Seems like the same error. The second try is right after the first one failed.

Code: Select all

[10-4-2008 16:53:34]	Sys	Com port open .. Ok
[10-4-2008 16:53:46]	Sys	Com port close .. Ok
[10-4-2008 16:53:46]	Sys	Error: Cannot send message to +316********. GSM modem error. No reply on AT command: ATE1
[10-4-2008 16:53:47]	Sys	Com port open .. Ok
[10-4-2008 16:53:49]	Sys	GSM modem initialization .. Ok
[10-4-2008 16:53:56]	Sys	Error: Cannot send message to +316********. GSM modem error. No reply on AT command: AT+CMGS=126>0001000B9....9900E14B381DA73
[10-4-2008 16:54:04]	Sys	Com port close .. Ok
[10-4-2008 16:54:04]	Sys	GSM modem deinitialization .. Ok

KS-Soft Europe · Post by **KS-Soft Europe** » Thu Apr 10, 2008 9:09 am

Hm. Strange. Could you also add "GSMLogFile" string value under HKEY_LOCAL_MACHINE\SOFTWARE\KS-Soft\GSMX and specify there some log file name(e.g. C:\HostMon\logs\at.log)? Could you send the specified log file to support@ks-soft.net after you try to send SMS?

Regards,
Max

MartinQS · Post by **MartinQS** » Thu Apr 10, 2008 9:31 am

There has been a change. After rebooting the server the phone still won't work the first time, but a quick re-send does work!

I added the GSMLogFile value in the registry, but that option only creates a log file when HostMonitor is connected to the GSM modem. The sending seems to fail only because it doesn't connect right to the GSM modem.
I still think it's some sort of timeout.

KS-Soft Europe · Post by **KS-Soft Europe** » Thu Apr 10, 2008 10:06 am

MartinQS wrote:There has been a change. After rebooting the server the phone still won't work the first time, but a quick re-send does work!

So, now it works or not?

MartinQS wrote:I added the GSMLogFile value in the registry, but that option only creates a log file when HostMonitor is connected to the GSM modem.

Correct. Only AT-commands are recorded into this log file.

MartinQS wrote:The sending seems to fail only because it doesn't connect right to the GSM modem. I still think it's some sort of timeout.

In fact it is pretty strange. You may try to increase DefaultRecTimeOut value to 30000, probably it helps. Actually, it is not normal behavior for Nokia 6210. I think, you have to reset phone to default settings, or enter certain INIT string to this phone or enter some AT-commands sequence via HyperTerminal - I do not know, I am not a GSM guru

Regards,
Max

MartinQS · Post by **MartinQS** » Fri Jun 27, 2008 4:33 am

Hello,

I would like to close this topic properly. The problems are solved. It was the COM-port that caused the problems for sending the SMS. Communication through COM1 did not work as it should.

I have one final question: is it possible that an SMS cannot be send if the message text is too long? I had some trouble sending messages but I do not know the exact lenght.

KS-Soft Europe · Post by **KS-Soft Europe** » Fri Jun 27, 2008 5:16 am

MartinQS wrote:I would like to close this topic properly. The problems are solved.

Glad to hear that.

MartinQS wrote:I have one final question: is it possible that an SMS cannot be send if the message text is too long? I had some trouble sending messages but I do not know the exact lenght.

If a message is longer than 160 characters, HostMonitor will split the message and send several SMS to the recipient. If this is not really necessary, we recommend using compact mail templates for "Send SMS (SMPP/IP)" action.

Regards,
Max