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

in reply to: recommended way to transfer to an extension #5918 |

yes, i realize it works and why the error message appears, but it’s a huge pain to have all of your queues lit up in orange and that message every time you deploy. the goto block doesn’t behave that way, only queue and dial seem to generate the unnecessary(imho) warning.

anyway, here is a workaround i found for what it’s worth to anyone reading this…

1) create a global variable (something like queuename) to store the variable
2) use a SET block to set the global variable.
3) then use the global variable in your queue or dial block instead of the ${SPEECH_TEXT(0)} type variable and then you don’t get the error message. this has the added benefit of having the variable in the dropdown select list for you. (the downside is that you longer code that’s harder to maintain since it takes 2 blocks with 2 variables to do what could(imho) be done in one)

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

in reply to: recommended way to transfer to an extension #5917 |

This message is given because at design time Visual Dialplan can not recognize resource Queue ${SPEECH_TEXT(0)} but at run time it will replace ${SPEECH_TEXT(0)} with valid resource (registered queue number).

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

in reply to: recommended way to transfer to an extension #5916 |

mmm… same question but for queues… when i use the queue block, i can set the queue number to ${SPEECH_TEXT(0)} but i get a warning from VDP that ${SPEECH_TEXT(0)} is not a known resource. seems to work though…

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

in reply to: recommended way to transfer to an extension #5915 |

solved my own problem. don’t know if this is the recommended approach, but if you use a ‘goto’ block and set the context to ‘from-did-direct’ and the extension to a variable like ${SPEECH_TEXT(0)} or just a number like ‘101’. it works for me. The ‘ext-did’ context suggested in the tutorials didn’t work for me for some reason.

i use elastix, perhaps that’s why.

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

in reply to: copy context from one .vdp file to another? #5913 |

yes! that worked perfectly, thanks!

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

in reply to: copy context from one .vdp file to another? #5912 |

You may try with the following steps:

1. ‘copy’ context (go to main window and select one or more contexts or macros you wont to copy, there is no need to go to design window)
2. check dial plan version
3. close the current dial plan (not Visual Dialplan)
4. open or create new dial plan
5. check dial plan version and make sure it is the same as in 2. step
6. go to main window and then ‘paste’ it.

This should do the trick

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

in reply to: debugging vdp contexts #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

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

in reply to: debugging vdp contexts #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]

in reply to: debugging vdp contexts #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:01 am Post count: 327]

in reply to: Reverse Engineer Dialplan #5905 |

Paolo,

Nope, it’s not possible.

Raman

• This reply was modified 10 years, 6 months ago by  Migrated from old forum.

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

in reply to: Counter #5903 |

Hi Raoul,

I’m not clear with your question.
Can you explain it in more detail?

BTW if you click on Math block you will be able to see code under Build tab (in the lower left corner).

Set(counter=${MATH(1+${counter})}) represents the following: counter=counter+1;

Raman

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

in reply to: Counter #5902 |

I’m having a problem with Math but i dont know what here is the code for my Math
Quote:
Set(counter=${MATH(1+${counter})})

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

in reply to: Counter #5901 |

ahh ok thanks alot

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

in reply to: Counter #5900 |

Raoul,

You can set variable named counter=0 and than later in dial plan (or in loop) use math block to increase value of variable counter for 1.

Raman

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

in reply to: Dialplan Reload Not Working #5898 |

Hello Paolo,

I guess the best approach would be doing a clean install of Visual Dialplan. Please backup your work and then uninstall and delete all files before you install Visual Dialplan again.

Also, please note that Visual Dialplan is not tested in Mac OSX environment. We do not support Mac OSX.

I hope this answer your questions.
Please do not hesitate to let us know if you have any further question.

Michael Denich
Apstel support team