Diego Iastrubni
2007-Aug-08 09:56 UTC
[asterisk-users] Monitor doohicky got event Event 160 on channel..
Hi all, I am seeing on my logs this message: Jun 13 09:14:51 DEBUG[4944] chan_zap.c: Monitor doohicky got event Event 160 on channel 3 Jun 13 09:14:51 DEBUG[4944] chan_zap.c: Monitor doohicky got event Event 160 on channel 3 (repeated much more then what I will show here). I see that it comes from static void* do_monitor(void *data) in chan_zap.c, but I do not understand what does it mean, and now why is it spamming my logs. Can anyone give me a hint...? - diego
Philipp Kempgen
2007-Aug-09 06:40 UTC
[asterisk-users] Monitor doohicky got event Event 160 on channel..
Diego Iastrubni wrote:> I am seeing on my logs this message: > > Jun 13 09:14:51 DEBUG[4944] chan_zap.c: Monitor doohicky got event Event 160 > on channel 3 > Jun 13 09:14:51 DEBUG[4944] chan_zap.c: Monitor doohicky got event Event 160 > on channel 3 > > (repeated much more then what I will show here). > > I see that it comes from static void* do_monitor(void *data) in chan_zap.c, > but I do not understand what does it mean, and now why is it spamming my > logs.Because you are logging debug messages :-P ---cut--- ; Debug mode turns on a LOT of extra messages, ; most of which you are unlikely to understand without an understanding of ; the underlying code. Do NOT report debug messages as code issues, unless ; you have a specific issue that you are attempting to debug. They are ; messages for just that -- debugging -- and do not rise to the level of ; something that merit your attention as an Asterisk administrator. Debug ; messages are also very verbose and can and do fill up logfiles quickly; ; this is another reason not to have debug mode on a production system unless ; you are in the process of debugging a specific issue. ---cut--- So if there is no problem with your system just don't enable debug mode. Regards, Philipp Kempgen -- amooma GmbH - Bachstr. 126 - 56566 Neuwied - amooma.de Let's use IT to solve problems and not to create new ones. Asterisk? -> das-asterisk-buch.de My pick of the month: rfc 2822 3.6.5 Gesch?ftsf?hrer: Stefan Wintermeyer Handelsregister: Neuwied B 14998
Tzafrir Cohen
2007-Aug-09 07:14 UTC
[asterisk-users] Monitor doohicky got event Event 160 on channel..
On Wed, Aug 08, 2007 at 12:56:33PM +0300, Diego Iastrubni wrote:> Hi all, > > I am seeing on my logs this message: > > Jun 13 09:14:51 DEBUG[4944] chan_zap.c: Monitor doohicky got event Event 160 > on channel 3 > Jun 13 09:14:51 DEBUG[4944] chan_zap.c: Monitor doohicky got event Event 160 > on channel 3It means that either: * Asterisk is drunk * Asterisk is getting strange events from the zaptel channels. The trigger here is an even from Zaptel. But what are those events? But where does Zaptel send those events? I don't see any similar ZT_EVENT_* value in zaptel.h and I don't see any value sent through zt_qevent_lock that is not a ZT_EVENT_* . Hmmm... leftovers in the events buffer? Time for a bug report, I guess. -- Tzafrir Cohen icq#16849755 jabber:tzafrir at jabber.org +972-50-7952406 mailto:tzafrir.cohen at xorcom.com xorcom.com iax:guest at local.xorcom.com/tzafrir