Call Filter

When troubleshooting a call process we always go to the Asterisk CLI first to see if we are receiving the calls and trace the call to see what is the outcome that we get. We use the following command to get to the Asterisk CLI.

root@debian:~# asterisk -rvvvvvvvvv

Or simply

root@debian:~# a

However, monitoring the Asterisk CLI with high verbosity while the system is under production can show us a lot of information at a very fast pace. For this, we can filter out the Full log for Asterisk to trace actions that affect a particular call only.

We start by running the following command.

root@debian:~# tail -f /var/log/asterisk/full | grep {PHONE_NUMBER}

Where {PHONE_NUMBER} is a particular phone number you want to trace within the full log. Remember that you don’t have to include the curly braces. For example, you will enter something like this.

root@debian:~# tail -f /var/log/asterisk/full | grep 15554846868

In the beginning, you may see nothing if information including this number has not been set. Once any activity starts that includes this phone number you will start to see anything related to it.

This phone number you monitor can be an external number calling into your VitalPBX and you want to see the route it uses. Or it can be a DID on your system and you want to see that it is used appropriately for your inbound routes. This can help you monitor how your VoIP provider sends your DID information so you can enter it correctly on your Inbound Routes. It can also be a specific Extension Number you want to monitor their current call. Use this option to make your call troubleshooting easier during active hours on your VitalPBX.