On Wed, 2006-01-25 at 14:10 -0600, Kevin P. Fleming wrote: > Aaron Daniel wrote: > > We had the bug on 1.2.2, but when I rolled back to 1.2.1 to fix the > > problem, everything started working. Doesn't seem like it's a bug in > > 1.2.1 :) > > It is not. The bug was introduced during the 1.2.1->1.2.2 transition.
Observation ... Had a problem with asterisk 1.2 trunk from approx 10 Dec, (from memory), when the problem occurred, a restart of asterisk did not fix it, and a reboot of the machine still did not fix it. A svn update and restart of asterisk still did not fix it. I wonder, was it really only 2^22 seconds, or how exactly did that work?? I really was quite stumped when it happened, since nobody had changed anything for ages... Anyway, thankfully it broke at 4:30pm, and everyone went home at 5pm (the after hours announce only and hangup was working), so I left it until the next day. A few debug attempts, and a login to IRC, and suddenly the solution was shouting at me (in the subject/title of the IRC channel to svn update). Mainly was confused as to why a asterisk + zaptel restart and a reboot didn't fix the problem (even just temporarily)? Regards, Adam _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
