Thanx, but that would mean
that the system can't use NTP for timesync.
M
Paradise Dove wrote:
this is a new bug which is submitted: http://bugs.digium.com/view.php?id=6349
change your system date to an older value. everything will work again.
paradise dove
On 1/25/06, Marnus van Niekerk
Yep, I just got stung by this too - an hour of extreme pain, multiple *
boxen all failed at precisely the same moment, and they're in different
timezones, so must be a calc on epoch or UTC.
Anyone shed any light on this? I'm hacking our CDRs currently to work
around the difference in year,
yes, it's a bad pain.
btw, i've submitted a bug.
On 1/25/06, Peter Fern [EMAIL PROTECTED] wrote:
Yep, I just got stung by this too - an hour of extreme pain, multiple *
boxen all failed at precisely the same moment, and they're in different
timezones, so must be a calc on epoch or UTC.
you will have to desable NTP or downgrade to an older version of
asterisk to fix this, untill there is an official bugfix.
i believe the first one is easier...
A
Marnus van Niekerk schrieb:
Thanx, but that would mean that the system can't use NTP for timesync.
M
Paradise Dove wrote:
this
problem with disabling ntp is
that the time will drift which will influence time based dialplan
extensions (office closed etc...)
M
Adrian Raez wrote:
you will
have to desable NTP or downgrade to an older version of asterisk to fix
this, untill there is an official bugfix.
i believe the
yes but i think its worse to have * down then to have a slightly wrong
date - i hope there is a patch for this soon, so the drift should be
acceptable.
A
Marnus van Niekerk schrieb:
problem with disabling ntp is that the time will drift which will
influence time based dialplan extensions
Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] Suddenly No audio
this is a new bug which is submitted:
http://bugs.digium.com/view.php?id=6349
change your system date to an older value. everything will work again.
paradise dove
On 1/25/06, Marnus van Niekerk [EMAIL
Hi,
I set up a small system over the last couple of days and all was fine.
(* 1.2.2 - Fedora Core 1
System has 2xTDM400P with 7xFXO and 1xFXS, a couple of SIP phones
(snom320 and IP300), fax machine on the FXS channel and an IAX2 trunk
through a local provider.
All worked fine until this
this is a new bug which is submitted: http://bugs.digium.com/view.php?id=6349
change your system date to an older value. everything will work again.
paradise dove
On 1/25/06, Marnus van Niekerk [EMAIL PROTECTED] wrote:
Hi,
I set up a small system over the last couple of days and all was
