| Keywords: Mode: All keywords (AND) |
|
Sun Jun 13, 2010 12:59
|
Erik: Ok, I guess it is not feasable to add User_id to the REPORT header, though it would be really nice.
smsd could work with a map internally:
Message_id -> User_id
and then add the User_id field to the header in case of a REPORT.
However, I will solve the problem via the database.
Thanks!
Erik
|
|
Sun Jun 13, 2010 12:17
|
Erik: Thanks, I think I have to extend my current database to keep trak of the Message_id.
I do not know how difficult it is, but extending the SMS format would be nice:
To: +49123456
User_id: <varchar(255)>
This is a message
The SENT, REPORT and FAILIED message just would give this User_id in the header. This would be allow to keep track of the lifecycle without any database or filesystem tricks.
That's just an idea :-)
-Erik
|
|
Sun Jun 13, 2010 09:13
|
Erik: If I decide to use keep_filename = yes I can use my internal message ID as filename.
Hence SENT returns the filename, I can keep track of the my ID.
SENT and REPORT can be linked my Message_id.
Is there a better way to go, say by adding a header field which is given in each
successive message? Otherwise I have to keep track of the Message_id in a database.
Thanks,
Erik
|
|
Sat Jun 12, 2010 16:28
|
Erik: Operating system name and version: Debian Lenny
Version of smsd: 3.1.8
Smsd installed from: repository
Name and model of a modem / phone: TC35
Interface: serial
Hello,
I am not sure how to elegantly track the SMS from sending, receiving SENT and receiving a REPORT. Does sending an SMS allow me to set some unique identifier which re-appers in the SENT and REPORT messages?
SENT and REPORT are sharing Message_id which is fine, but how do I connect these two messages with my original SMS? I do not want to check the content of the SMS, as there will be lots of SMS, many of them with the same content and they may even be sent to the same destination, too. This makes it hard for me to track which SENT and REPORT messages concern which original SMS.
Thanks,
Erik
|
|
Mon Apr 26, 2010 15:45
|
Erik: SOLVED.
I did a complete reset of the BIOS as well as the iLo2 configuration to factory settings.
|
|
Thu Apr 22, 2010 11:24
|
Erik: Operating system name and version: HP ProLiant / Debain Lenny
Version of smsd: 3.1
Smsd installed from: debian repository
Name and model of a modem / phone: Siemens TC35
Interface: serial
Hello,
I have a problem accessing the TC35 via serial port on Debian Lenny. However, I am able to access the modem on Windows via Hyperterminal and send SMS sucessfully with the same serial cable. Hence, the problem has to be Linux configuration related.
I suspect that the serial port configuration is broken and I have to admit that I am a Linux novice and just followed several tips on the internet to solve the problem. I am aware that my question is a bit off topic, but after trying for a long time I would appreciate any help.
I tried the tips here to check if the modem is connected http://axion.physics.ubc.ca/modem-chk.html but no modems got recognized.
Also, I tried to access the modem via minicom but there is no reaction from the modem (I type some characters in but they do not appear in minicom though minicom says "connected").
The /dev/ttyS0|1 is readable and writeable.
setserial -g /dev/ttyS*
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3
\[GSM1\]
# init = ATE0+CPMS="SM"+CNMI=2,0,0,2,1 <--- tried this, too
init=AT+CNMI=2,0,0,2,1
device = /dev/ttyS0 <--- tried ttyS0 and ttyS1
incoming = yes
queues = D2
baudrate = 19200
rtscts = no <--- tried yes and no
smsd: Smsd v3.1 started.
2010-04-22 12:26:15,2, smsd: Running as smsd:dialout.
2010-04-22 12:26:15,6, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2010-04-22 12:26:15,6, smsd: Outgoing file checker has started. PID: 3447.
2010-04-22 12:26:15,6, GSM1: Modem handler 0 has started. PID: 3448.
2010-04-22 12:26:15,6, GSM1: Checking device for incoming SMS
2010-04-22 12:26:15,6, GSM1: Checking if modem is ready
2010-04-22 12:26:15,7, GSM1: -> AT
2010-04-22 12:26:15,7, GSM1: Command is sent, waiting for the answer
2010-04-22 12:26:16,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred.
2010-04-22 12:26:16,7, GSM1: <-
2010-04-22 12:26:16,7, GSM1: ->
...
Thanks!
Erik
|
