Re: Gammu-smsd issues

hi.
please what is your gammu version?
see at your dmesg / syslog if has any message that helps understand what is
going on?
your hw is real or you using virtualization (virtualbox, vmware, etc)?
please post your on receive script.
regards.

2015-02-20 7:45 GMT-02:00 IT Manager <[email protected]>:

>  L.S.,
>
> I am having some issues with gammu.
>
> After setting up gammu-smsd on my Ubuntu 12.04 server with a Cinterion
> (Siemens) MC55iT GSM/GPRS serial kit and writing a RunOnReceive script to
> perform some actions (including sending an SMS) on the received messages I
> started testing the setup. I noticed that gammu-smsd takes more than 15
> minutes to notice the received message and run the post-processing script.
>
> My /etc/gammu-smsdrc is as follows:
> [gammu]
> device = /dev/ttyS0
> connection = at115200
>
> [smsd]
> Service = files
> debuglevel = 2
> LogFile = /var/log/gammu.log
> CheckSecurity = 0
> CheckBattery = 0
> CommTimeout = 30
> ReceiveFrequency = 30
> InboxPath = */var/lib/samba/gammu/inbox/*
> OutboxPath = */var/lib/samba/gammu/outbox/*
> SentSMSPath = */var/lib/samba/gammu/sent/*
> ErrorSMSPath = */var/lib/samba/gammu/error/*
> RunOnReceive = /usr/local/bin/gt_scripts/SMS_server.py
>
> When I start gammu-smsd, the log gives the following lines:
> Tue 2014/12/23 13:28:38 gammu-smsd[20206]: Warning: No PIN code in
> /etc/gammu-smsdrc file
> Tue 2014/12/23 13:28:38 gammu-smsd[20207]: Created POSIX RW shared memory
> at
> 0x7fbae9870000
> Tue 2014/12/23 13:28:38 gammu-smsd[20207]: Starting phone communication...
>
> It seems that the options (CheckSecurity, CheckBattery, CommTimeout and
> ReceiveFrequency) are not passed to the program, I read in this mailing
> list
> that it should at least show these options in the log file.
>
> My first question is if the options are passed to the program although
> they
> are not shown in the log file.
> My second question is how can I set the check frequency lower, for example
> every 30 seconds (if the ReceiveFrequency = 30 is not correctly passed to
> the progam).
>
> Thirdly, when the SMS is received eventually it sends out an SMS to some
> other number, which is received correctly, however in the log I see an
> SMSC
> warning:
> Tue 2014/12/23 13:52:18 python-gammu[20343]: Created outbox message
> OUTC20141223_135218_00_############_sms0.smsbackup
> Tue 2014/12/23 13:52:18 gammu-smsd[20207]: Process finished successfully
> Tue 2014/12/23 13:52:18 gammu-smsd[20207]: Message without SMSC, assuming
> you want to use the one from phone
> Tue 2014/12/23 13:53:12 gammu-smsd[20207]: Transmitted
> OUTC20141223_135218_00_############_sms0.smsbackup (total: 1) to
> ############, message reference 0x1e
>
> The message that is sent by gammu-smsd-inject is in the format:
> smsd.InjectSMS({'Text': smstext, 'SMSC': {'Location': 1}, 'Number':
> number})
> which specifies the SMSC, is that option not passed to gammu-smsd-inject?
>
> Lastly, I noticed that the log also shows some timeout and emtpy errors:
> Tue 2014/12/23 04:03:23 gammu-smsd[11582]: Starting phone communication...
> Tue 2014/12/23 04:03:26 gammu-smsd[11582]: Error at init connection: No
> response in specified timeout. Probably phone not connected. (TIMEOUT[14])
> Tue 2014/12/23 04:03:26 gammu-smsd[11582]: Already hit 250 errors
> Tue 2014/12/23 04:03:26 gammu-smsd[11582]: Terminating communication: No
> response in specified timeout. Probably phone not connected. (TIMEOUT[14])
> Tue 2014/12/23 04:03:26 gammu-smsd[11582]: Starting phone communication...
> Tue 2014/12/23 05:45:49 gammu-smsd[11582]: Error getting SMS status: No
> response in specified timeout. Probably phone not connected. (TIMEOUT[14])
> Tue 2014/12/23 05:46:38 gammu-smsd[11582]: Error getting SMS status: No
> response in specified timeout. Probably phone not connected. (TIMEOUT[14])
> Tue 2014/12/23 05:47:27 gammu-smsd[11582]: Error getting SMS status: No
> response in specified timeout. Probably phone not connected. (TIMEOUT[14])
> Tue 2014/12/23 05:47:27 gammu-smsd[11582]: Already hit 3 errors
> Tue 2014/12/23 05:47:27 gammu-smsd[11582]: Terminating communication:
> Entry
> is empty. (EMPTY[22])
> Tue 2014/12/23 05:47:27 gammu-smsd[11582]: Starting phone communication...
>
> Although it seems that in the end the communication with the phone is
> resumed and it can process messages again.
> Is this normal behavior?
>
> Thanks in advance for any help you can provide.
>
> Regards,
> Gertjan
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> _______________________________________________
> Gammu-users mailing list -
> https://lists.sourceforge.net/lists/listinfo/gammu-users
>
>


-- 
gilberto dos santos alves
+55(11)9-8646-5049
sao paulo - sp - brasil

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk

_______________________________________________
Gammu-users mailing list - https://lists.sourceforge.net/lists/listinfo/gammu-users