Incorrect date/time

Gaby Vanhegan <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <B9BA3463.2A33%[email protected]>
Continuing a conversation I was having (since corrected my email address so
the mailing list manager will accept my posts... :-)

> when SENDING an SMS, you have no control over SCTS as it is not part of the
> PDU. while RECEIVING an SMS, kannel doesnt do anything with the SCTS as far as
> I remember. If it does, then that's the spot to look at. The service center
> timestamp has only 2 digits for the year.

I've run some tests.  Here's the appropriate line from kannel.conf:

# The default service
group = sms-service
keyword = default
exec = "/usr/local/kannel/send_squeezy_sms.pl '%q' '%t' '%a'"
omit-empty = true

The script puts the data into a database and uses an external provider to
issue the response SMS.  What ends up in the database is this:

The date off the SMS:     1902-02-05 17:41:40
The actual received date: 2002-09-27 13:13:13

The times are correct as I send the message myself and it arrives a few
seconds later, but that shouldn¹t account for the massive difference.  Next,
I tried this:

group = sms-service
keyword = datetest
text = "%t"

And I get the response text message from the gateway:

1902-02-05+20:20:37

The message was sent at 3:59pm local time today.  I can only assume that
kannel is misinterpreting the date on the message.  I've got a similar
response from three different models of phone on three different networks.

Any clues?

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.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.