Whatever you do, you do at your own risk. I can only recommend and do not claim 100% of the solution much depends on your environment and other settings. I can not guess. Addition of materials and fixing bugs is welcomed

Debug SIP Protocol in Asterisk

If you need to see SIP messages coming from the peer, and what messages your server sends to it, then on the server you need to run the following command: "asterisk -rx "sip set debug peer SIPuserID"" SIPuserID, respectively, change the name of the SIP user account. It is important to take into account that the Asterisk server must know the user's IP, in other words, the user must be registered or have an IP registered in its settings.

If you know the user's IP, but do not know the user name, you can use the command "asterisk-rx "sip set debug ip 192.168.1.1"". For viewing of all sent/received SIP messages, run "asterisk -rx "sip set debug on"".

You can view the result of the execution in two ways:

Console version. Go to the CLI console command: "asterisk-r". This method is fast, but in my opinion is not very convenient, because the log runs fast and there is no search. This method is suitable for determining whether messages are coming at all.
File log. Open the log file "asterisk/var/log/asterisk/messages" and look at it all that we need. If necessary, we can copy the file and part of the file.
When you have finished viewing the SIP messages do not forget to turn debugging off with the command: "asterisk -rx "sip set debug off"". If you can not execute any command due to lack of rights, before the command write "sudo".

Debugging a dial plan (DialPlan) in Asterisk

To start debugging a dial plan or DialPlan, run the command: "asterisk-rx "core set verbose 3"" verbose level tells asterisk how much detail to report its actions, level 3 is enough to analyze the call. After debugging, make a call and all the information about it will be in the log file /var/log/asterisk/messages. In the file, search for the number, we are interested in a string that starts with Executing. This period will describe the actions from the extensions file.conf. Continue the search until you reach the last instruction, it is likely that there is an error.

Just after debugging do not forget to turn it off. "asterisk-rx" core set verbose off"" or "asterisk-rx"core set verbose 0"".

Here is perhaps all actions that will help you solve the problem with calls.

If you helped the article or information was useful. Gratitude should not know borders

Popular tags