Hello, In case of CIMD2 & Oracle the timestamp received from SMSC is stored in the database. Is it possible to send this timestamp as %t or %T parameter? >From the documentation: %t the time the message was sent, formatted as "YYYY-MM-DD HH:MM", e.g., "1999-09-21 14:18" %T the time the message was sent, in UNIX epoch timestamp format
Against this, in the URL the delivery time is sent. >From the bearerbox log (field 060 is the timestamp): 2005-02-23 13:24:17 [5827] [6] DEBUG: CIMD2[oncall]: sending <03:069 021:36709809882 023:36709809882 056:14 044:0 033:Hello A> 2005-02-23 13:24:17 [5827] [6] DEBUG: CIMD2[oncall]: received: <53:069 021:36709809882 060:050223132417 A5> [...] 2005-02-23 13:28:02 [5827] [6] DEBUG: CIMD2[oncall]: received: <23:004 021:36709809882 060:050223132417 061:4 063:050223132801 > 2005-02-23 13:28:02 [5827] [6] DEBUG: DLR[oracle]: Looking for DLR smsc=CIMD2:172.16.4.162:9971:oncall, ts=050223132417, dst=36709809882,1 In the database: SQL> select source,destination,ts from kannel_dlr ; SOURCE DESTINATION TS 36709809882 36709809882 050223132417 In the report.log: Received request with status 8, timestamp 1109161457 (050223132417), to 36709809882, from 36709809882 Could not connect to database! Received request with status 1, timestamp 1109161682 (050223132802), to 36709809882, from 36709809882 Could not connect to database! As - at least in Nokia SMSCs - the timestamp and the destination must be unique, this could identify a message unequivocally. Again, I must highlight that this is the case of CIMD2 protocol, I am not aware of the other protocols. Thanks for the attention :-) Peter
