But in my VDP software this component is absent (There only GotoIf, GoToIfTime, GoTo, Random, GoSub, Return, StackPop, Redirect).
It is very critical point for me. I need this component.
I will be very grateful, if someone will tell what to make that it there would appear.
Thanks ahead.
mt,
From the main dialog you will see a button on the left hand side that says “Macros”, which will display all macros in your dialplan.To create a new one, simply click on “New” from the top menu and you will get a dialog box that pops up and asks the name you want to call the macro. If you look at the title of that dialog you will see it says “Macro”. Create a new one and then move on from there. Hope this helps.
It supposed to do some routine jobs first example – language selection menu in different contexs. It is similiar for every action.
Plus, i wrote IVR navigation macro, which receives ivr file as argument and some parameters and controls IVR flow (main menu announce, step back, repeat announce, go to top and calls corresponding to user’s selection context)
this context can call the same macro with another parameters.
Ok, if I remember correctly VDP itself will not read in and “run” an outside macro directly. I think you need to recreate the workflow in a new macro created in VDP itself if you want to be able to manage it there. You may be able to have a VDP dialplan call outside code manually depending on how the diaplan is coded within VDP itself, but I’m not 100% sure. However, VDP will not just read in the code and make it appear in your dialplan design flow, etc. It will have to be manually done within your dialplan.
Kevin, i know it.
I started to create my macro in VDP.
An i see in User’s Manual in Context Editing Window in tab ‘CALLFLOW’ a box (component) called “Macro”
According to description this is what i need.
But there is no such component in MY callflow tab.
I understand, but I dont know if its just a mistake in the docs and that the macro area I explained about is actually what needs to be used or not. Apstel support can answer better, and the monitor the forums so you should get an answer.
You should probably use Gosub instead of Macro component.
Basically it’s the same component, Gosub is the preferred component as off Asterisk 1.6 as opposed to Macro.
Your dial plan version is probably Asterisk 1.6 or greater and that’s the reason why you don’t see Macro component under the Callflow tab. If you revert to Asterisk 1.4 you will see Macro component.
Raman, thank you.
Is there any comparsion: in which dialplan version what is available, what is not?
What will i lose in 1.4. dialplan version?
I use Asterisk 1.8.11-certified.
If you are using Asterisk 1.8 version then you should choose Asterisk 1.8 dialplan version in VDP.
If you don’t synchronize these two parameters there is a possibility that some components won’t work as they should.
Also, there is no way you can use macros in VDP for Asterisk 1.6 and 1.8 dialplan version, for these versions macros are automatically transformed to Gosub components.
In case you have some hand (code) made Macro you wish to call then you may find useful CustomCode component.
I see.
Why Macro component was removed from VDP dialplan version 1.8 ?
It is not deprecated in Asterisk 1.8 and very usefull.
It is not comfortable to be limited in abilities with VDP software.
Ok, I have one more question.
How can i jump to some Context/Extension/Priority/ from one context to another ?
In GoTo component I see only Context and Extension arguments. But i need to jump to exact place in dialplan.
