I noted that
CIMD2 driver does not timestamp MOs (neither with local time nor with param 060
timestamp).
EMI2 driver
for example does take the MO timestamp, and only if it doesn't have one, it
takes local time.
I'd like to
do two things:
First and
obvious, add param 060 support to CIMD2 driver.
Second, add
a generic smsc config directive to have some flexibility for MO timestamps:
take the MO timestamp (if there's one) or force local time. Maybe even
a timezone correction could be possible.
How about
that second feature?
One more
(silly) question: what is %t url pattern supposed to give? GMT or local
time?
Angel Fradejas
Mediafusi�n Espa�a, S.A.
[EMAIL PROTECTED]
www.mediafusion.es
Tel. +34 91 252 32 00
Fax +34 91 572 27 08
Mediafusi�n Espa�a, S.A.
[EMAIL PROTECTED]
www.mediafusion.es
Tel. +34 91 252 32 00
Fax +34 91 572 27 08
