Hi, this is not a kannel bug and you can do nothing to fix the problem. You can only put pressure on SMSC guys that they fix validity parsing on SMSC side.
Fourat Zouari wrote: > yes it is, how can i fix this ? > > On 2/23/07, Alexander Malysh <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> what kannel version? >> if this is 1.4.1 then it must be bug at SMSC because kannel send validity >> and deferred always in UTC and set it correctly according to SMPP spec. >> >> Fourat Zouari wrote: >> >> > anyone ? >> > >> > On 2/21/07, Fourat Zouari <[EMAIL PROTECTED]> wrote: >> >> >> >> Hello, >> >> I have Kannel connected to Telecom Operator's SMSC 'SMPP3.4'. >> >> The Operator's servers time has +2 hours on me, the correct time is >> mine >> >> and the operator wont adjust his time. >> >> The problem is when trying to send an MT, my MT is marked on the >> >> operator's SMSC with a timetoleave inferior to its time so it will not >> be >> >> delivered to mobile. >> >> As a workaround i synchronize my time on the operator's time and all's >> >> done, but after all i wont have a incorrect time. >> >> I tryed to set validityperiod to : >> >> validityperiod = 1440 >> >> But no difference, MTs will pass only when i synchronize my server >> >> time on the operator server time. >> >> >> >> -- >> Thanks, >> Alex >> >> >> -- Thanks, Alex
