It has been a long time since I have posted something on my blog, so here we go to start off 2008 correctly.

As many of you already know, I've returned to university to complete my software engineering degree. This is a long road, but Asterisk will benefit from it one day, I'm sure.

Enough about me, what's new with Asterisk? I will continue working on CLI filtering to allow an Asterisk administrator to easily debug calls. Basically, this will let you to apply filters to the CLI for specific channels.

The main problem is when you have something like 50 active channels:

-- Playing 'multi/A151' (escape_digits=1234567890) (sample_offset 0)
-- Playing 'digits/6.ulaw' (language 'fr')
-- Playing 'multi/confs/A31' (escape_digits=1234567890#) (sample_offset 0)
-- Playing 'multi/A125.slin' (language 'fr')
-- AGI Script ma/bar10.agi completed, returning -1
-- Executing [h@prodosec-inbound:1] Set("SIPi [0]/64.15.69.138-b6b02e78", "deleted=1") in new stack

We could ask ourselves, "Okay, which customers heard the prompt called "multi/A151"? At this time, there is no easy way to do it.

The main job to make this possible is to pass the ast_channel structure to these functions:
ast_log()
ast_verb()
ast_verbose()
ast_debug()

Also, this first long job will help another cool project:
CLI filtering per session user.

Right now, for example: if 2 admins(A and B) are logged in and admin A is doing an "iax2 set debug", admin B will see all of the iax2 messages, as well. Also, if admin B does: core set verbose 0, admin A will drop his verbose to 0, too. So, this project is to have per-session output and preferences. But, it requires that the work for CLI filtering be completed first.

I've started the main idea 1 year ago, and I'd like to complete this for the next major release.

For more information, you can visit: http://bugs.digium.com/view.php?id=8849 [1]