On Nov 8, 2008, at 1:30 PM, Atis Lezdins wrote:
Asterisk offers very much the same flexibility. You can disable
specific log levels (for example warnings) in logger.conf or you can
log everything to syslog, where filter out this specific message.
Of course, there is always this method, which
Russell Bryant wrote:
On Nov 8, 2008, at 1:30 PM, Atis Lezdins wrote:
Asterisk offers very much the same flexibility. You can disable
specific log levels (for example warnings) in logger.conf or you can
log everything to syslog, where filter out this specific message.
Of course,
On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote:
Tzafrir Cohen wrote:
On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
I'd take this warning seriously. It means that your monitoring app isn't
monitoring what you think it is.
I always want to know when I get
Tzafrir Cohen wrote:
On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote:
Maybe it's me, but I think that warning should be regarding a problem
I can fix. Malformed network content does not neceserily fall under that
definition. notice?
Absolutely it does. Warnings of
On Sat, Nov 8, 2008 at 9:20 AM, Louis-David Mitterrand
[EMAIL PROTECTED] wrote:
On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote:
Tzafrir Cohen wrote:
On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
I'd take this warning seriously. It means that your monitoring app
On Sat, Nov 08, 2008 at 09:30:59PM +0200, Atis Lezdins wrote:
On Sat, Nov 8, 2008 at 9:20 AM, Louis-David Mitterrand
[EMAIL PROTECTED] wrote:
On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote:
Tzafrir Cohen wrote:
On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote:
Louis-David Mitterrand wrote:
When monitoring an asterisk through its iax2 port I get these warnings
at the console:
[Nov 6 13:15:15] WARNING[2209]: chan_iax2.c:7000 socket_process:
midget packet received (1 of 4
Louis-David Mitterrand wrote:
On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote:
Your monitoring app is not sending valid IAX2 packets to the server. If
it was sending a true IAX2 POKE, it would be a valid packet and wouldn't
generate this warning.
Could asterisk at
On 7 Nov 2008, at 08:49, Louis-David Mitterrand wrote:
On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote:
Louis-David Mitterrand wrote:
When monitoring an asterisk through its iax2 port I get these
warnings
at the console:
[Nov 6 13:15:15] WARNING[2209]:
On 7 Nov 2008, at 09:57, Louis-David Mitterrand wrote:
On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
Your monitoring app is not sending valid IAX2 packets to the
server. If
it was sending a true IAX2 POKE, it would be a valid packet and
wouldn't
generate this warning.
On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
Your monitoring app is not sending valid IAX2 packets to the
server. If
it was sending a true IAX2 POKE, it would be a valid packet and
wouldn't
generate this warning.
Could asterisk at least _not_ report this harmless,
Tim Panton [EMAIL PROTECTED] writes:
I always want to know when I get malformed protocol packets in.
It's easy for an attacker to fill your log drive then.
/Benny
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
I'd take this warning seriously. It means that your monitoring app isn't
monitoring what you think it is.
I always want to know when I get malformed protocol packets in. It is
always bad news, mostly either a misconfiguration (your
Rob Hillis wrote:
Louis-David Mitterrand wrote:
On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote:
Your monitoring app is not sending valid IAX2 packets to the server. If
it was sending a true IAX2 POKE, it would be a valid packet and wouldn't
generate this
Tzafrir Cohen wrote:
On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
I'd take this warning seriously. It means that your monitoring app isn't
monitoring what you think it is.
I always want to know when I get malformed protocol packets in. It is
always bad news, mostly either
On Sat, Nov 08, 2008 at 02:33:18PM +1100, Rob Hillis wrote:
Tzafrir Cohen wrote:
On Fri, Nov 07, 2008 at 09:29:20AM +, Tim Panton wrote:
I'd take this warning seriously. It means that your monitoring app isn't
monitoring what you think it is.
I always want to know when I get
Louis-David Mitterrand wrote:
When monitoring an asterisk through its iax2 port I get these warnings
at the console:
[Nov 6 13:15:15] WARNING[2209]: chan_iax2.c:7000 socket_process:
midget packet received (1 of 4 min)
This is triggered by the monitoring app sending a POKE to the
On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote:
Louis-David Mitterrand wrote:
When monitoring an asterisk through its iax2 port I get these warnings
at the console:
[Nov 6 13:15:15] WARNING[2209]: chan_iax2.c:7000 socket_process:
midget packet received (1 of 4
On Thursday 06 November 2008 08:53:40 Louis-David Mitterrand wrote:
On Thu, Nov 06, 2008 at 08:42:52AM -0600, Kevin P. Fleming wrote:
Louis-David Mitterrand wrote:
When monitoring an asterisk through its iax2 port I get these warnings
at the console:
[Nov 6 13:15:15]
19 matches
Mail list logo
