[asterisk-users] R: Can not enable sip debug because CLI flooded

[Alexandru Oniciuc]

Edit logger.conf and set the desired log level.

To disable the messages below just remove the severity notice from console.

console => notice,warning,error,debug

Alex


Da: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] Per conto di jonas kellens
Inviato: venerdì 12 marzo 2010 10:20
A: Asterisk Mailing
Oggetto: [asterisk-users] Can not enable sip debug because CLI flooded

Hello list,

I have nat=no and qualify=no in my sip peer definition and still my CLI is flooded with :

[Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (30ms / 2000ms)
[Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (24ms / 2000ms)
[Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (25ms / 2000ms)
[Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (29ms / 2000ms)
[Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (21ms / 2000ms)
[Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (23ms / 2000ms)
[Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (21ms / 2000ms)
[Mar 12 10:17:27] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (29ms / 2000ms)
[Mar 12 10:17:27] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (22ms / 2000ms)
[Mar 12 10:17:27] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (27ms / 2000ms)
[Mar 12 10:17:27] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (30ms / 2000ms)
[Mar 12 10:17:27] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (31ms / 2000ms)
[Mar 12 10:17:27] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (22ms / 2000ms)
[Mar 12 10:17:27] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (21ms / 2000ms)
[Mar 12 10:17:27] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (23ms / 2000ms)
[Mar 12 10:17:27] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (25ms / 2000ms)
[Mar 12 10:17:27] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (27ms / 2000ms)
[Mar 12 10:17:28] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (23ms / 2000ms)
[Mar 12 10:17:28] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (22ms / 2000ms)
[Mar 12 10:17:28] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (22ms / 2000ms)
[Mar 12 10:17:28] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (39ms / 2000ms)
[Mar 12 10:17:28] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (37ms / 2000ms)
[Mar 12 10:17:28] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (37ms / 2000ms)

I want to enable sip debugging but then my CLI is even more flooded with al the SIP OPTION packets...

What can I do ??

Jonas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100312/e088ff8e/attachment.htm