Operating system name and version: suse linux 10.2
Version of smsd: 3.1.14
Smsd installed from: sources (all standard by installscript)
Name and model of a modem / phone: modem PSI-GSM
Interface: serial


sent messages are garbled after approx 80 signs at destination-phone.
(tested with various phones)
is this a setup problem ?

This sounds like an alphabet problem. What kind of message file you have sent?

hi
just a normal text message

file:
To: 0043...........
Flash: yes
Alphabet: GSM

das ist eine testsms. weitere koennen noch folgen.
aber keine anderen mehr.
l.g.
hs

end file:

The alphabet is not GSM. Remove that line.

hi
done.
problem still exists.

received result at mobile:

das ist eine testsms. weitere koennen noch folgen.
aber keine anderen kAJc&N4bA0rf"


the smsd.log just says: SMS sent, Message_id: 26,.........


do you hafe any testmobile ?
if yes i can try to send this message to youi from our system directlly.

Ok, actually your text can be sent with alphabet GSM, because it contains latin letters only.

Have you disabled handshaking (rtscts = no)?

You may have a communication problem with your modem. You could use the modem setting verify_pdu = yes and try again after restarting smsd. With this setting smsd checks if the PDU string is echoed back correctly from the modem. If there is no error, but received message is still garbled, you could show the PDU so I can check if it's correct or not.

hi
this is /etc/smsd.conf:
devices = GSM1
logfile = /var/log/smsd.log
loglevel = 7

[GSM1]
device = /dev/ttyS0
incoming = yes
rtscts = yes
verify_pdu = yes
#pin = 1111


this is log-output after restart:

2010-11-29 14:39:00,6, GSM1: Checking if modem is ready 2010-11-29 14:39:00,7, GSM1: -> AT 2010-11-29 14:39:00,7, GSM1: Command is sent, waiting for the answer 2010-11-29 14:39:01,7, GSM1: <- OK 2010-11-29 14:39:01,6, GSM1: Pre-initializing modem 2010-11-29 14:39:01,7, GSM1: -> ATE0+CMEE=1;+CREG=2 2010-11-29 14:39:01,7, GSM1: Command is sent, waiting for the answer 2010-11-29 14:39:01,7, GSM1: <- OK 2010-11-29 14:39:01,7, GSM1: -> AT+CSQ 2010-11-29 14:39:01,7, GSM1: Command is sent, waiting for the answer 2010-11-29 14:39:02,7, GSM1: <- +CSQ: 20,0 OK 2010-11-29 14:39:02,6, GSM1: Signal Strength Indicator: (20,0) -73 dBm (Excellent), Bit Error Rate: less than 0.2 % 2010-11-29 14:39:02,6, GSM1: Checking if Modem is registered to the network 2010-11-29 14:39:02,7, GSM1: -> AT+CREG? 2010-11-29 14:39:02,7, GSM1: Command is sent, waiting for the answer 2010-11-29 14:39:03,7, GSM1: <- +CREG: 2,1,"38A6","F942" OK 2010-11-29 14:39:03,6, GSM1: Modem is registered to the network 2010-11-29 14:39:03,6, GSM1: Selecting PDU mode 2010-11-29 14:39:03,7, GSM1: -> AT+CMGF=0 2010-11-29 14:39:03,7, GSM1: Command is sent, waiting for the answer 2010-11-29 14:39:03,7, GSM1: <- OK 2010-11-29 14:39:03,7, GSM1: -> ATE1+CMGS=92 2010-11-29 14:39:03,7, GSM1: Command is sent, waiting for the answer 2010-11-29 14:39:04,7, GSM1: <- > 2010-11-29 14:39:04,7, GSM1: -> 0011000D91349619777071F70010FF58E4F01C949ED341E5B4BB0CA297E7F4797BEE023514F7729A5E969741EB77D9ED2EBB41EEF7180D32BFD9E7B2DBD55084C56539685D4EBBCBA0B09B5C9697DDA076192D7735146CD7D9D550A0E7 2010-11-29 14:39:04,7, GSM1: Command is sent, waiting for the answer 2010-11-29 14:39:08,7, GSM1: <- 0011000D91349619777071F70010FF58E4F01C949ED341E5B4BB0CA297E7F4797BEE023514F7729A5E969741EB77D9ED2EBB41EEF7180D32BFD9E7B2DBD55084C56539685D4EBBCBA0B09B5C9697DDA0 +CMGS: 31 OK

The PDU is broken. Perhaps you should try with a lower baudrate, for example 9600. If it does not help, try the setting send_handshake_select = no.

Is this problem still active?