jonas kellens
2010-Mar-12 09:19 UTC
[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/4ec0cb6f/attachment.htm
Alexandru Oniciuc
2010-Mar-12 10:05 UTC
[asterisk-users] R: Can not enable sip debug because CLI flooded
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
jonas kellens
2010-Mar-12 10:25 UTC
[asterisk-users] R: Can not enable sip debug because CLI flooded
That is indeed an option, thank you. It also went away by restarting Asterisk, but this is not desirable in production environment. On Fri, 2010-03-12 at 11:05 +0100, Alexandru Oniciuc wrote:> 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-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100312/700b7dba/attachment.htm
Warren Selby
2010-Mar-12 16:51 UTC
[asterisk-users] R: Can not enable sip debug because CLI flooded
On Fri, Mar 12, 2010 at 4:25 AM, jonas kellens <jonas.kellens at telenet.be>wrote:> >Are you using SIP realtime? -- Thanks, --Warren Selby http://www.selbytech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100312/85d568c1/attachment.htm
jonas kellens
2010-Mar-12 22:30 UTC
[asterisk-users] R: Can not enable sip debug because CLI flooded
Yes I am for most of my SIP peers. On Fri, 2010-03-12 at 10:51 -0600, Warren Selby wrote:> On Fri, Mar 12, 2010 at 4:25 AM, jonas kellens > <jonas.kellens at telenet.be> wrote: > > > > > Are you using SIP realtime? > > > -- > Thanks, > --Warren Selby > http://www.selbytech.com > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100312/b9d4cea6/attachment.htm