Situation such. There is an asterisk working as office pbx. 6 fxo - 18 fxs ports. All works perfectly, but some times in a week something occurs. Could not catch what exactly yet. But symptoms such. The asterisk infinitely writes the message of a type to broad gullies: WARNING [20757] chan_zap.c: We're Zap/8-1, not ... <ZOMBIE>. Numbers of channels can change. Because of that that broad gullies get littered fairly promptly, I have not time to see that occured in an instant of the beginning of this event. When the asterisk is in such condition, the appropriating channel does not work, in this case 8. What can it be? asterisk version 1.2.14-BRIstuffed-0.3.0-PRE-1x
Hi, Vitaly: Vitaly Oborsky wrote:> Situation such. There is an asterisk working as office pbx. 6 fxo - 18 > fxs ports. All works perfectly, but some times in a week something > occurs. Could not catch what exactly yet. But symptoms such. The > asterisk infinitely writes the message of a type to broad gullies: > WARNING [20757] chan_zap.c: We're Zap/8-1, not ... <ZOMBIE>. Numbers > of channels can change. Because of that that broad gullies get > littered fairly promptly, I have not time to see that occured in an > instant of the beginning of this event. When the asterisk is in such > condition, the appropriating channel does not work, in this case 8. > What can it be? > > asterisk version 1.2.14-BRIstuffed-0.3.0-PRE-1xThis looks suspiciously like a Babelfish translation... and I have to admit it's a bit confusing. Can you try rewording it? :\ -Stephen-
On Fri, May 11, 2007 at 05:32:33PM +0300, Vitaly Oborsky wrote:> Situation such. There is an asterisk working as office pbx. 6 fxo - 18 > fxs ports. All works perfectly, but some times in a week something > occurs. Could not catch what exactly yet. But symptoms such. The > asterisk infinitely writes the message of a type to broad gullies: > WARNING [20757] chan_zap.c: We're Zap/8-1, not ... <ZOMBIE>. Numbers > of channels can change. Because of that that broad gullies get > littered fairly promptly, I have not time to see that occured in an > instant of the beginning of this event. When the asterisk is in such > condition, the appropriating channel does not work, in this case 8. > What can it be? > > asterisk version 1.2.14-BRIstuffed-0.3.0-PRE-1xCould you try a later verssion of bristuff? I seem to recall a bug report for chan_zap (or is it Zaptel) with exactly those symptoms. I cannot find it right now. Anybody? -- Tzafrir Cohen icq#16849755 jabber:tzafrir@jabber.org +972-50-7952406 mailto:tzafrir.cohen@xorcom.com http://www.xorcom.com iax:guest@local.xorcom.com/tzafrir