[Migrated from old forumParticipant April 11, 2015 at 3:02 am Post count: 327]

#5907 |

as someone new to vdp, shockingly my first attempt at a script/context didn’t work as i had planned.

can someone experienced post a short list of tips and techniques for debugging my script? are there asterisk log files for example that would be particularly helpful?

here are two such ideas i’ve stumbled upon already. 1) put in debugging points in the script with a letter/a, letter/b where the script talks to you as it goes through. 2) putting log entries within the script to write out info.

i’m sure an experienced person would have many more good ideas that would be helpful to us newbe’s. anyone?

[Migrated from old forumParticipant April 11, 2015 at 3:03 am Post count: 327]

#5908 |

Skyrun,

The NoOp component could be used for dial plan debugging purposes. Please note that you should specify verbose level to 3 or higher in order to get some useful results from this component.

Also, you may check “How to log debug messages in Asterisk dial plan” short movie available at:
http://www.apstel.com/forums/topic/educational-movies-about-visual-dialplan-for-asterisk/

Raman

• This reply was modified 10 years, 6 months ago by  admin.

[Migrated from old forumParticipant April 11, 2015 at 3:03 am Post count: 327]

#5909 |

thanks raman,

in case it’s not obvious to others, to view the asterisk console in realtime after adding these log entries, logon to the server via SSH and type ‘asterisk -r’.

[Migrated from old forumParticipant April 11, 2015 at 3:03 am Post count: 327]

#5910 |

Skyrun,
You may want to increase the verbosity level on the CLI when you invoke the asterisk monitor to give you more information, ie: asterisk -vvvvr each ‘v’ increases the level, and if i remember correctly the ‘default’ is 3, so if you need to get more info you need to go higher than that. HTH

Kevin