|
|
SMS Server Tools 3 Community |
Welcome, Guest. Please login or register. |
Sun Apr 28, 2024 21:07 |
This topic is locked
Page: 1 2 Next
Author |
Post |
|
#1 Fri May 22, 2009 08:12, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
|
Hi there First of all sorry for my bad english i got the following problem: Receiving messages is no problem, only sending is the problem. i always get +CMS ERROR: 500. i checked the commands with minicom and they where all OK the log file looks like this: my config file: # AUTOMATICALLY CREATED CONFIGURATION FILE -- DO NOT EDIT BY HAND! # # Description: Main configuration file for the smsd # Last changed: Mit Mai 20 11:34:46 CEST 2009 # Please note that this is _not_ a dpkg-conffile. It has been created because # you have choosen to manage smsd configuration with debconf. This file is not meant # to be and should not be editted directly. # Instead # Run: dpkg-reconfigure <-plow> smstools # # If you want to manage your configuration file by hand at a later time # you may run the above command, too and say that you don't want to manage # smsd configuration with debconf.
# Global configuration devices = 6310i logfile = /var/log/smstools/smsd.log infofile = /var/run/smstools/smsd.working pidfile = /var/run/smstools/smsd.pid outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked failed = /var/spool/sms/failed incoming = /var/spool/sms/incoming sent = /var/spool/sms/sent stats = /var/log/smstools/smsd_stats # You can specify here an external program that is started whenever an alarm occurs. # alarmhandler = /path/to/an/alarmhandler/script # Specifies what levels start an alarmhandler. You can use value between 2 and 5. # alarmlevel = 4 #eventhandler = /usr/local/bin/sendsms #blacklist = /etc/smstools/blacklist #whitelist = /etc/smstools/whitelist #autosplit = 3 loglevel = 7
# Modem configuration [6310i] device = /dev/ttyS0 incoming = yes mode = new smsc = 43664xxxxxxx rtscts = no cs_convert = yes #pin = baudrate = 19200 'smsdconf' Syntax Highlight powered by GeSHi it's the first time for me configuring this so i'm pretty nooby hope the config looks fine if anybody may help me this would be great regards luke « Last edit by keke on Fri May 22, 2009 08:33, 181 months ago. »
|
|
#2 Fri May 22, 2009 08:19, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
oh i forgot: using a nokia 6310i (plugged in with serial) and Ubuntu 8.04
|
|
#3 Fri May 22, 2009 08:32, 181 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
CMS 500 is problematic because it's "Unknown error".
In your case it was caused because you wrote destination number using national format. With a smsd version you are using, destination number must always be written using international format (without a plus sign), Try To: 43676xxxxx and I think your message will be sent.
|
|
#4 Fri May 22, 2009 08:38, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
thanks for the fast answear i tried it with 43676... but same problem any other suggestions ? thanks luke « Last edit by luke on Fri May 22, 2009 08:41, 181 months ago. »
|
|
#5 Fri May 22, 2009 08:46, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
after the PDU there is always a
^Z
is this the ctrl+Z or is this a command from the mobil phone? or is this maybe the problem?
|
|
#6 Fri May 22, 2009 08:52, 181 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
^Z is a PDU termination character and it should be there.
Perhaps you could try without smsc setting, in most cases this setting is not necessary. After commenting this setting out restart is necessary for smstools.
|
|
#7 Fri May 22, 2009 08:56, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
after restart i found another error: well i think i first have to fix this problem
|
|
#8 Fri May 22, 2009 09:04, 181 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
CIMI error is not a problem, your device just does not support this query. In this case smsd tries to get identity string using CGSN.
What is a version of smsd you are using?
|
|
#9 Fri May 22, 2009 09:07, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
Version 3.0.10, Copyright (c) Keijo Kasvi, authors email, http://smstools3.kekekasvi.com Based on SMS Server Tools 2 from Stefan Frings, email of version 2 author, http://www.meinemullemaus.de
|
|
#10 Fri May 22, 2009 09:16, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
and heres the command i'm using trying to send sms: maybe just my command is broken i copied the sendsms script from the examples/script folder to /usr/local/bin/ do i have to edit it? sendsms: with my pretty bad knowledge of shell-scripts (i hope it is a shell-script ) i would say no « Last edit by luke on Fri May 22, 2009 09:19, 181 months ago. »
|
|
#11 Fri May 22, 2009 09:38, 181 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
The sendsms script is ok, even when it's old and there is a better version available. You smsd also is very old, it could be good if you can move to the latest 3.1.5beta9 which is very stable but it's still beta because I have not had a time to release an official 3.1.5. However it's coming soon. After it is released, it takes a time until it's available in package repositories of Linux distributions. I therefore recommend to compile from sources anyway. You have used this SIM and phone to send similar SMS and it has worked, right? luke wrote i checked the commands with minicom and they where all OK
Do you mean that you checked sending using the same commands and PDU, and it worked?
|
|
#12 Fri May 22, 2009 09:41, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
hmmmm well i tried if the PUD gives me a OK back so i not realy tried to send it... but i will upgrade to the 3.1.5 beta.
|
|
#13 Fri May 22, 2009 10:14, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
well... installed 3.1.5 beta9.... same problem that means the problem is in the config or the mobile phone... am i right?
|
|
#14 Fri May 22, 2009 10:27, 181 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
This might be hopeless, but try with mode = old. Is the error message same?
|
|
#15 Fri May 22, 2009 10:35, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
with mode=old: with mode=new:
|
|
#16 Fri May 22, 2009 10:47, 181 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
Ok, this is going difficult... Next try sending using Minicom. First try using ASCII mode: ATE1 to see that device answers and to turn echo on OKAT+CMGF=1 to select ASCII mode OKAT+CMGS="+43676xxxxx" to initialize sending > Type a text here. and end it with Ctrl-Z+CMGS: (number) OKDoes this work?
|
|
#17 Fri May 22, 2009 10:55, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
hmmmm the answer is: maybe i have to end it with 2 ctrl-Z's and there is no +CMGS: and the message is not delivered
|
|
#18 Fri May 22, 2009 11:29, 181 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
Message was not delivered, but device still said OK. Are you sure that a destination number is correct?
Your phone is from year 2002 and 2006 it got a firmware version which was broken. Because of this, it does not return message reference number as expected. Before 2006 it was working. Probably current firmware is broken and this device cannot be used for sending (which sounds strange, but anything is possible).
You have rtscts = no, why handshaking is disabled? Was there some troubles with receiving messages when handshaking was on?
Perhaps you could make one more try with Minicom and ASCII mode, give a number in national format, AT+CMGS="0676xxxxx". Does this make any difference?
|
|
#19 Fri May 22, 2009 11:59, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
handshake was off because of the old config (other tool) i tried it with yes and no (no difference) i also tried with national format (no difference) now i will try it with a nokia 6280 maybe that will help
|
|
#20 Fri May 22, 2009 12:58, 181 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
Yes, it's a good idea to test with another device. If you have not already seen, view this post. Board member marcolino7 also uses 6310i device. The question was not about sending messages, but he also did not say that sending does not work...
|
|
#21 Fri May 22, 2009 13:27, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
thx keke i will look at this post... and for today it's enough for me... may i bother you again at monday ?
|
|
#22 Fri May 22, 2009 13:32, 181 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
You're welcome...
|
|
#23 Mon May 25, 2009 08:40, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
hope you had a nice weekend back to some nice problems tested it with nokia 6280: new problem: and if i try sending, old problem : phone is now connected with usb
|
|
#24 Mon May 25, 2009 09:03, 181 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
Thank's, the weekend was nice and it looks like this newly started week is going to be interesting too... Now you have a S40 "smart phone" with at least 3rd edition of firmware. Those devices do not show incoming messages thru the external AT command interface and typically can be used for sending only. You could try ASCII mode sending using Minicom with this 6280. What is the result and is the message delivered? Are you sure that the SIM is not broken? Have you tried to send SMS using ordinary phone and with success?
|
|
#25 Mon May 25, 2009 09:10, 181 months ago.
|
Member
Registered: May 2009
Location: Austria
Topic owner
|
Minicom: Quote Are you sure that the SIM is not broken?
pretty sure Quote Have you tried to send SMS using ordinary phone and with success?
yes
|
This topic is locked
Page: 1 2 Next
Time in this board is UTC.
|
|
|
|
|
|
|