<html><head><style type="text/css"><!-- DIV {margin:0px;} P {margin:0px;} --></style></head><body><font face="times new roman, new york, times, serif" size=3><span style="font-family: times new roman,new york,times,serif;"><font size="3">Hi all,<br><br>i have updated my old asteirsk version from 1.2.x to a newer 1.4.13 (some posts did suggested that the 1.4.13 release is the most stable so far) on a brand new hardware (Dell Poweredge 2950, Digium TE420P with hardware echo canceller). Zaptel is version 1.4.7.1, libpri is 1.4.3. <br><br>Everything seems working - but from time to time i am lossing all calls on my PRI lines - after searching the logs i found one very interresting thing in the log file - as it seems my asterisk is missing some time. for normal i am getting some log entries (verbose level 3) per second - but before the line loose happens - i am missing 2 minutes of logs !!!! So it seems to me that asterisk is hanging somewhere - not able to log something - and also not able to take the data from the zaptel card...<br><br>The system is running centos 5.1 with kernel 2.6.18-53.1.4.el5.centos.plus (SMP kernel) - zaptel, libpri and asterisk self compiled. The machine does have one Quad Xeon 3 GHZ processor. <br><br>I am doing many asterisk manager queries - but also using the astmanproxy to avoid to many connections wasn't helping me - the problem still is there...<br><br><br>Here is the log, as you can see at 16:11:04 there is the last entry - the next is 2 minutes later and does indicate that asterisk has really done nothing for the last 2 minutes...<br><br>[Jan 23 16:10:56] VERBOSE[17747] logger.c: -- Executing [repark@ASPark:3] WaitMusicOnHold("Zap/38-1", "30000") in new stack<br>[Jan 23 16:10:56] VERBOSE[17747] logger.c: -- Started music on hold, class 'waitforqueue', on Zap/38-1<br>[Jan 23 16:10:59] VERBOSE[17459] logger.c: -- SIP/706-b7dcbba0 answered Zap/39-1<br>[Jan 23 16:11:04] VERBOSE[11058] logger.c: -- Remote UNIX connection<br>[Jan 23 16:13:28] NOTICE[11087] chan_sip.c: Peer '704' is now UNREACHABLE! Last qualify: 49<br>[Jan 23 16:13:38] NOTICE[11087] chan_sip.c: Peer '704' is now Reachable. (78ms / 2000ms)<br>[Jan 23 16:13:48] NOTICE[11090] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 3<br>[Jan 23 16:13:48] NOTICE[11088] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1<br>[Jan 23 16:15:42] NOTICE[11087] chan_sip.c: Peer '704' is now UNREACHABLE! Last qualify: 199<br>[Jan 23 16:15:52] NOTICE[11087] chan_sip.c: Peer '704' is now Reachable. (150ms / 2000ms)<br><br><br>The big question is - should i use an other version of asterisk - does this gets caused by the newer zaptel version than asterisk version - how can i track down the problem (i could wait watching the logs until it happens - and then attach to the process - but i don't have time to wait some hours watching logs running through....)<br><br>Hope someone here does have an idea what is happing....<br><br>regards,<br>Wolfgang Pichler<br></font></span></font></body></html>