Hi Adrian,
Try setting the same time on both servers - this will do the job, even if it is a dirty trick.
Regards, Bogdan
Adrian A wrote:
Also, changing the expires to TIMESTAMP from DATETIME causes location lookups to fail, even though the value for expires seems to be in the same format. I changed it back to DATETIME for now to get calls to work again.
Any help with this is appreciated.
On Mon, Mar 17, 2008 at 11:57 AM, Adrian A <adrianvoip@gmail.com mailto:adrianvoip@gmail.com> wrote:
Hello, I changed the type to timestamp but the problem is still there. E.g. Client registers to proxy located in PST, expires is set to: 2008-03-17 12:50:55 but time on EST server is 14:55:13 EDT 2008 so within a minute the entry is deleted. The MySQL timezone is set to the system timezone for these servers. Thanks. On Mon, Mar 17, 2008 at 2:26 AM, Alex Hermann <alex@speakup.nl <mailto:alex@speakup.nl>> wrote: On Monday 17 March 2008, Adrian A wrote: > The issue is that when clients register to the proxy located in the PST > zone, the 'expires' time is much earlier than the current time in EST. As a > result, the proxy in EST deletes the entry from the location table since it > thinks it is stale. > > Is there any way around this, other than setting both proxy servers to the > same timezone? Make the 'expires' column a TIMESTAMP type and make sure the MySQL server timezone is also correctly configured. -- Greetings, Alex Hermann _______________________________________________ Users mailing list Users@lists.openser.org <mailto:Users@lists.openser.org> http://lists.openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users