On Jan 16, 2008 10:25 AM, Jeremy Mann <[EMAIL PROTECTED]> wrote: > Using Asterisk-1.4.17, Zaptel-1.4.8, libpri-1.4.3 > > > > Upgraded this morning, now PRI channels are unstable as hell. After about > 5 minutes all asterisk commands on the console refuse to respond, attached > is the debug log right before and after the "lock-up", IT occurred between > 9:18 and 9:20 AM at 9:20 I restarted asterisk. > > > > Box is debian w/ asterisk built from scratch. > > > > My setup is asterisk as a man-in-the-middle, Span 1 goes to Telco, Span 2 > to Nortel MICS. PRI is not the problem as it's plugged into the Nortel > directly for now and we have no problems. > > > > Nothing in dmesg indicates any errors. > > > > Any clue how I go about debugging this? > > > > ---- > > > > [Jan 16 09:18:41] DEBUG[10183] chan_zap.c: Unlinking slave 1 from 47 > > [Jan 16 09:18:41] DEBUG[10183] chan_zap.c: Removed 12 from conference 9/47 > > [Jan 16 09:18:41] DEBUG[10183] chan_zap.c: Removed 57 from conference 9/1 > > [Jan 16 09:18:41] DEBUG[10183] chan_zap.c: Set option AUDIO MODE, value: > ON(1) on Zap/1-1 > > [Jan 16 09:18:56] DEBUG[10107] chan_zap.c: Unlinking slave 26 from 3 > > [Jan 16 09:18:56] DEBUG[10107] chan_zap.c: Removed 36 from conference 9/3 > > [Jan 16 09:18:56] DEBUG[10107] chan_zap.c: Removed 14 from conference 9/26 > > [Jan 16 09:18:56] DEBUG[10107] chan_zap.c: Set option AUDIO MODE, value: > ON(1) on Zap/26-1 > > [Jan 16 09:18:56] DEBUG[10107] chan_zap.c: Not yet hungup... Calling > hangup once with icause, and clearing call > > [Jan 16 09:18:56] DEBUG[10107] chan_zap.c: Set option AUDIO MODE, value: > OFF(0) on Zap/26-1 > > [Jan 16 09:18:56] DEBUG[10107] chan_zap.c: Set option AUDIO MODE, value: > ON(1) on Zap/3-1 > > [Jan 16 09:20:24] DEBUG[8430] chan_zap.c: Ring requested on channel 0/23 > already in use or previously requested on span 2. Attempting to > renegotiating chann > > el. > > [Jan 16 09:20:24] DEBUG[8430] chan_zap.c: Found empty available channel > 0/21 > > [Jan 16 09:22:24] DEBUG[8430] chan_zap.c: Ring requested on channel 0/23 > already in use or previously requested on span 2. Attempting to > renegotiating chann > > el. > > [Jan 16 09:22:24] DEBUG[8430] chan_zap.c: Found empty available channel > 0/20 > > [Jan 16 09:22:31] DEBUG[8430] chan_zap.c: Ring requested on channel 0/23 > already in use or previously requested on span 2. Attempting to > renegotiating chann > > el. > > [Jan 16 09:22:31] DEBUG[8430] chan_zap.c: Found empty available channel > 0/19 > > [Jan 16 09:23:07] DEBUG[8430] chan_zap.c: Ring requested on channel 0/23 > already in use or previously requested on span 2. Attempting to > renegotiating chann > > el. > > [Jan 16 09:23:07] DEBUG[8430] chan_zap.c: Found empty available channel > 0/1 >
Sorry I cannot be of help with your issue since I stick with 1.2.x until I stop seeing my bugs folder filling up daily and seeing posts like this and the very long running post about "Unstable Releases". I would suggest rolling back to whatever version worked and opening an issue on bugtracker. I am curious though, why did you upgrade? Were you having problems with the version you upgraded from? Thanks, Steve Totaro
_______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
