asterisk cli improvement
Command Line Interface for asterisk pbx is usefull to debug and track what is happening or happenned
on you asterisk server.
However, this can become a whole mess if you have multiple calls going to different sections of your dialplan. Multiple clis cannot do differents and separate things. If you set debug level to 0, every connected client will be set to 0 then.
Back in 2007, a discussion on digium board about cli filtering that will allow users to follow one specific channel or extension.
http://lists.digium.com/pipermail/asterisk-dev/2007-January/025792.html
They were a patch but I don’t think this feature has been released.
Here are cool and usefull stuff asterisk cli needs to include :
- a connected cli informations should be specific to that connection. Multiple different clis should have different verbose and debug levels, sip debug …
- an asterisk command should allow us to filter what we want to see. Filter can be on:
* channel name (eg : core cli filter SIP/testuser*)
* on module. Only show logs from that module (eg: core cli filter app_dial.so chan_iax2.so)
* on a section or context or extension of the dialplan (eg: core cli filter 5050@default). So, if you want to see all the channels going through a specific critical path of your dialplan, you will start seeing debug informations as soon as a channel reach that extension in the dialplan.
* on a specific caller id or caller id pattern
Comments
Leave a Reply