[asterisk-dev] CLI filtering

[Justin Tunney]

This is a FANTASTIC idea!  I am in desperate need of this feature
because it is next to impossible to do anything to an Asterisk box
that's in production.

As you mentioned, there is a huge disadvantage to the fact that every
time you would need to call ast_log() and ast_verbose() you'd need a
pointer to a channel variable.

I am not very familiar with the way GCC compiles code, but is there
anyway we could have ast_log() rape the stack looking for the nearest
channel pointer and assume that it is the most relevant one?  In other
situations where the programmer knows that the wrong channel is the
nearest on the stack, they could call a wrapper for ast_log() and
specify the channel manually.

- Justin Tunney

On 1/18/07, Clod Patry <cpatry at gmail.com> wrote:
> hi guys,
> Since a couple of days i had a really big project in head, this is all about
> CLI filtering.
> The main problem is when you get pretty lot of calls, this is impossible to
> know whats going on in the CLI, the CLI just scroll down like hell.
> If you have many actives calls, there's no way to filter all the output in
> the CLI, which makes the CLI pretty hard to read for specific channel(s) and
> not to all channels.
> The main idea is to filter per channel(s) via active calls or regex to map
> your channel name(s).
> So you could filter just SIP/10 and SIP/11 for example. All the others
> ast_log and ast_verbose will be discarded.
> You could filter a specific channel, like Zap/17 for example.
>
> something like
> core filter channel SIP/1*
>
> This will be really useful for analog, sip,iax2, etc.
>
>
> Im aware that all ast_log and ast_verbose will have to receive a pointer to
> the ast_channel. That bored job is almost done at this point.
> That patch is > 24 000 lines just for ast_log and without any channel
> drivers changed for now.
>
>
> The second idea is to filter per session. When you have 2 persons in the
> CLI, if one person is doing a RTP debug, the other one will be like WTF! so
> it's to separate all that.
>
> I know a lot of person will say we could debug via log files and via
> ethereal, but that knowledge isnt given to all * users (like we all know).
> That stuff will be really simple to use
>
>
>
>
> --
> Clod Patry
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>
>
>