Incorrect Date/Time Bug?

Got no response from the users list so reposting here:

I have a Siemens TC35 and the current stable 1.2.0 version of Kannel.  When
I receive text messages from the device (being used as a virtual SMSC) the
date stamp of the SMS is corrupted.  It is reporting dates such as:

1902-02-01 21:02:28

When I send a text message to the device at around 4:30 pm in the afternoon.
My initial thought was that this might have been confusing the timestamp
with a Unix epoch time as opposed to the YYYY-MM-DD HH:MM:SS format, as
specified in the manual, but the times are roughly correct.  My second
thought was that the internal clock on the TC35 was incorrect, but the date
stamp on the text message is set at the receiving SMSC, not by the GSM
device.

I've run out of ideas on this one.  Do I need to set the clock on the TC35?
Is there a patch to fix this in the current version?

Also, I'd like to directly store all incoming messages on any SMSC into a
MySQL database.  I can't find any information in the documentation about
this other then DLR storage, which is not what I'm after.  I need to keep
track of all incoming messages, including sender, date, and body.  Are they
any add-ons that do this or will I have to use a manual solution (as I
currently do)?

Currently it calls an exec command on the default sms-service which executes
a script, passing the relevant parameters to it.  However this is still
subject to the date bug.

Gaby

-- 
Gaby Vanhegan, Web Developer
[email protected]
----------------------------------------------------------
MediaWorks
Telephone +44(0)113 234 5600   Fax +44(0)113 234 5601
http://www.mediaworksccl.com/

This e-mail contains information that is confidential and may be
Legally privileged. If this e-mail has been addressed to you in
error and you are not the person intended or authorized to receive
it or a copy of it, please notify the sender as soon as possible.