Hi,
first of all thanks for your great job.
Second, please sorry about my english.

Let's start.....I'm using SMSd for Home Automation purpose. I installed it on a Alix Board with Debian/Voyage as OS. It works fine and through a PLC board i can control my devices by a SMS.
What miss in SMSd is the ability to placa a "CONFIRMATION" call.
I'll try to explain. When i send an SMS to turn on my Air Conditioner from my mobile, i configured SMSd to send me back confirmation Message. The Phone Operator Charge me for this SMS. A great thing can be the ability to place a call 10/15 second long and then Hang-up. This can replace the confirmation SMS with no charge of traffic on my SIM card.
I just do it, with Gnokii but sometime Gnokii hang the phone and smsd stop to work.
For example SMSd could accept a "special message" into inbox with the number to call and the duration, SMSd will palce the call and then hangup after the second specify into message.

Another thing is Blacklist.
As i understood Blacklist and Whitelist are only for outbound SMS. For home automation purpose should be great to have also an Inbound Whitelist. I this way I can permit to Enable/Disable devices only to authorized number.

Let me know if my idea are good, and if you intend to implement it in future release.

Bye
Marco

marcolino7 wrote

For example SMSd could accept a "special message" into inbox with the number to call and the duration, SMSd will palce the call and then hangup after the second specify into message.

Take a look at the SMS file format, there is Voicecall: yes message type explained. I think this fits your purposes if your modem supports it. There has been some compatibility issues with some devices, but for example good old Nokia 6210 works very well. You just need to test this with your device. Calling usually works but some devices cannot detect answering, or cannot play tones. There is also hangup option available, for example 15 seconds with this kind of message file:

marcolino7 wrote

For home automation purpose should be great to have also an Inbound Whitelist. I this way I can permit to Enable/Disable devices only to authorized number.

Inbound authority checking should be done inside the eventhandler. Smsd setup itself cannot handle inbound whitelist because it does not know what all kind of operations eventhandler is doing.

A little example of authorizing:



Do you think this kind of script can be used for your purposes?

Hi,
i'm testing the dialvoice option and work. The only thing is that SMSd don't wait the time out.
Here is the log:
2009-05-11 12:15:13,6, GSM1: IMSI: 2009-05-11 12:15:13,6, GSM1: I have to make a voice call to 39348XXXXXXX, with (2 times) DTMF # 2009-05-11 12:15:13,7, GSM1: -> ATD+39348XXXXXXX; 2009-05-11 12:15:13,7, GSM1: Command is sent 2009-05-11 12:15:13,7, GSM1: Waiting for 25 seconds 2009-05-11 12:15:16,7, GSM1: -> AT+VTS=# 2009-05-11 12:15:16,7, GSM1: Command is sent, waiting for the answer 2009-05-11 12:15:17,7, GSM1: <- ERROR 2009-05-11 12:15:20,7, GSM1: -> AT+VTS=# 2009-05-11 12:15:20,7, GSM1: Command is sent, waiting for the answer 2009-05-11 12:15:20,7, GSM1: <- ERROR 2009-05-11 12:15:21,7, GSM1: -> AT+CHUP 2009-05-11 12:15:21,7, GSM1: Command is sent, waiting for the answer 2009-05-11 12:15:21,7, GSM1: <- OK 2009-05-11 12:15:21,6, GSM1: Deleted file /var/spool/sms/checked/send_AQ4410

Seems that SMSd don't wait for 25 seconds and try immediatly to send dtmf. The call will arrive but is too short and destination phone does not start to ring, but i only got a missed call into display.

Can you help me?

Thanks

Here another test.
Seems that SMSd wait only 3 seconds before sending DTMF and not 25 second as set.

2009-05-11 12:21:13,6, GSM1: IMSI: 2009-05-11 12:21:13,6, GSM1: I have to make a voice call to 39348XXXXXXX, with (2 times) DTMF # 2009-05-11 12:21:13,7, GSM1: -> ATD+39348XXXXXXX; 2009-05-11 12:21:13,7, GSM1: Command is sent 2009-05-11 12:21:13,7, GSM1: Waiting for 25 seconds 2009-05-11 12:21:17,7, GSM1: -> AT+VTS=# 2009-05-11 12:21:17,7, GSM1: Command is sent, waiting for the answer 2009-05-11 12:21:17,7, GSM1: <- ERROR 2009-05-11 12:21:20,7, GSM1: -> AT+VTS=# 2009-05-11 12:21:20,7, GSM1: Command is sent, waiting for the answer 2009-05-11 12:21:20,7, GSM1: <- ERROR 2009-05-11 12:21:21,7, GSM1: -> AT+CHUP 2009-05-11 12:21:21,7, GSM1: Command is sent, waiting for the answer 2009-05-11 12:21:22,7, GSM1: <- OK 2009-05-11 12:21:22,6, GSM1: Deleted file /var/spool/sms/checked/send_eq4733

Last Think,
seem also that SMSd don't try to send DTMF all times as set in sms. In this case i set to send 3 times the dtmf 1, but SMSd try only 2 times:

2009-05-11 12:31:24,6, GSM1: IMSI: 2009-05-11 12:31:24,6, GSM1: I have to make a voice call to 39348XXXXXXX, with (3 times) DTMF 1 2009-05-11 12:31:24,7, GSM1: -> ATD+39348XXXXXXX; 2009-05-11 12:31:24,7, GSM1: Command is sent 2009-05-11 12:31:24,7, GSM1: Waiting for 5 seconds 2009-05-11 12:31:28,7, GSM1: -> AT+VTS=1 2009-05-11 12:31:28,7, GSM1: Command is sent, waiting for the answer 2009-05-11 12:31:28,7, GSM1: <- ERROR 2009-05-11 12:31:31,7, GSM1: -> AT+VTS=1 2009-05-11 12:31:31,7, GSM1: Command is sent, waiting for the answer 2009-05-11 12:31:31,7, GSM1: <- ERROR 2009-05-11 12:31:32,7, GSM1: -> AT+CHUP 2009-05-11 12:31:32,7, GSM1: Command is sent, waiting for the answer 2009-05-11 12:31:33,7, GSM1: <- OK 2009-05-11 12:31:33,6, GSM1: Deleted file /var/spool/sms/checked/send_PV5305

What is the smsd version you are using?

I just tried with 3.1.5beta7 and it did wait 15, 25 and 30 seconds, like:

2009-05-11 13:43:43,6, GSM1: I have to make a voice call to 35840571XXXX, with (2 times) DTMF # 2009-05-11 13:43:44,7, GSM1: -> ATD+35840571XXXX; 2009-05-11 13:43:44,7, GSM1: Command is sent 2009-05-11 13:43:44,7, GSM1: Waiting for 30 seconds 2009-05-11 13:44:14,7, GSM1: -> AT+CHUP 2009-05-11 13:44:14,7, GSM1: Command is sent, waiting for the answer 2009-05-11 13:44:14,7, GSM1: <- NO CARRIER

...and the code looks good, it should not be rushed

Hi,
I'm using version 3.1.3.
This afternoon I'm trying to download 3.1.5 beta 7. Is stable this Beta?
PS if needed phone is nokia 6310i with dlr-3p cable

Thanks

Hi,
tryed with 3.1.5 beta 7
and result is the same:

2009-05-11 13:09:30,6, GSM1: I have to make a voice call to 39348XXXXXXX, with (3 times) DTMF 1 2009-05-11 13:09:31,7, GSM1: -> ATD+39348XXXXXXX; 2009-05-11 13:09:31,7, GSM1: Command is sent 2009-05-11 13:09:31,7, GSM1: Waiting for 25 seconds 2009-05-11 13:09:34,7, GSM1: -> AT+VTS=1 2009-05-11 13:09:34,7, GSM1: Command is sent, waiting for the answer 2009-05-11 13:09:34,7, GSM1: <- ERROR 2009-05-11 13:09:38,7, GSM1: -> AT+VTS=1 2009-05-11 13:09:38,7, GSM1: Command is sent, waiting for the answer 2009-05-11 13:09:38,7, GSM1: <- ERROR 2009-05-11 13:09:39,7, GSM1: -> AT+CHUP 2009-05-11 13:09:39,7, GSM1: Command is sent, waiting for the answer 2009-05-11 13:09:40,7, GSM1: <- OK 2009-05-11 13:09:40,7, GSM1: Running eventhandler: /usr/script/check_in_sms.sh SENT /var/spool/sms/checked/send_du7363 2009-05-11 13:09:40,7, GSM1: Done: eventhandler, execution time 0 sec., status: 0 2009-05-11 13:09:40,6, GSM1: Deleted file /var/spool/sms/checked/send_du7363

Thanks

I think it's stable, I'm using it on production. In a few week I will release the 3.1.5.

This issue is strange. The code has not changed, but in your system something breaks delay loop. However, it looks like modem did not give an answer which causes the break.

Can you edit smsd.c file, locate the following:

put_command(modem, device, command, 0, 0, 0, 0); writelogfile(LOG_DEBUG, "Waiting for %i seconds", wait_delay); answer[0] = 0; wait_time = time(0); do { read_from_modem(modem, answer, sizeof(answer), 2); // One read attempt is 200ms if (strstr(answer, "OK") || strstr(answer, "NO CARRIER") || strstr(answer, "BUSY") || strstr(answer, "NO ANSWER") || strstr(answer, "ERROR") || strstr(answer, "DELAYED")) break; } while (time(0) < wait_time +wait_delay); cut_emptylines(cutspaces(strcpy(voicecall_result, answer)));

and change:

strstr(answer, "DELAYED")) ; //break; sleep(1); } while (time(0) < wait_time +wait_delay);

After this, break is not done and modem is checked once per second only.

Hi,
great JOB!!!! it works.
I tryed to check code by myself, but i'm not C programmer, i'm a VB.net programmer.
Now work,
in this case do you plan to add a parameter or i need to edit code for each new release?

Tahnsk for your help.
Regards

Marco

I just (too late) noticed that read_from_modem() does not write anything to the log, this is why the reason for breaking was not seen...

To see what your modem actually answers, can you make one test more with the following code block:

put_command(modem, device, command, 0, 0, 0, 0); writelogfile(LOG_DEBUG, "Waiting for %i seconds", wait_delay); answer[0] = 0; wait_time = time(0); do { read_from_modem(modem, answer, sizeof(answer), 2); // One read attempt is 200ms if (strstr(answer, "OK") || strstr(answer, "NO CARRIER") || strstr(answer, "BUSY") || strstr(answer, "NO ANSWER") || strstr(answer, "ERROR") || strstr(answer, "DELAYED")) { writelogfile(LOG_DEBUG, "<- %s", answer); answer[0] = 0; } sleep(1); } while (time(0) < wait_time +wait_delay); cut_emptylines(cutspaces(strcpy(voicecall_result, answer)));

In the next release I will include some setting for this delay, is it breakable or not. You do not have to edit each new release.

This what happen with this last modification:

2009-05-11 16:12:17,6, GSM1: I have to make a voice call to 39348XXXXXXX, with (1 times) DTMF # 2009-05-11 16:12:17,7, GSM1: -> ATD+39348XXXXXXX; 2009-05-11 16:12:17,7, GSM1: Command is sent 2009-05-11 16:12:17,7, GSM1: Waiting for 15 seconds 2009-05-11 16:12:18,7, GSM1: <- OK 2009-05-11 16:12:32,7, GSM1: -> AT+CHUP 2009-05-11 16:12:32,7, GSM1: Command is sent, waiting for the answer 2009-05-11 16:12:33,7, GSM1: <- OK 2009-05-11 16:12:33,7, GSM1: Running eventhandler: /usr/script/check_in_sms.sh SENT /var/spool/sms/checked/send_Z15800 2009-05-11 16:12:33,7, GSM1: Done: eventhandler, execution time 0 sec., status: 0 2009-05-11 16:12:33,6, GSM1: Deleted file /var/spool/sms/checked/send_Z15800

Ok, it answers too fast and wrongly, because call was not yet answered. This means that device can be used for ringing purposes, but not for sending DTMF tones. However usually this is enough, and it cost's nothing.

I add voicecall_ignore_modem_response = yes to the next version.

Thank you for testing and information.

Hi,
this behaviour fit with my need. My scope is save money, so I'm not intrested to answer and Hear DTMF.
Many thank for your help. As soon Beta9 is out I'll try this new parameter.

If you need more debug info from my phone, let me know.

Bye

3.1.5 Beta9 is running on my device.
New parameter still works fine.

Thanks

Hey!

Just wanted to say, that this is a create idea!

Working fine with smsd 3.1.3 and an Nokia 6210.

Thanks for posting this!