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

#6040 |

I am not sure why you insist on macros, instead of subroutines. Subroutines provide the very same functionality as macros and they have much better performance. Please see the quote from the Asterisk dev team:

“Well, Macro is officially deprecated, but not in the “it’s going away” sense of deprecated, merely in the way that we encourage new users to use Gosub, when they implement dialplan subroutines.”

Also, see the following link for macro deprecation information: https://wiki.asterisk.org/wiki/display/AST/app_macro+Deprecation.(external link)

Regarding the Goto to the particular priority, Visual Dialplan does not support that, but you can easily achieve that by redesigning your context (e.g. splitting the one context into two).

Raman

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

#6041 |

Hello, Raman.
Wiki page which you pointed is unaccessable – see attached screenshot. 🙂

Ok.
Probably my conservatism doesn’t allow me to depart from habitual methods of dialplan construction.

Ok. I did so. I add another unique, unaccessable extension to which i jump from Macro and from there i goto my priority.

All these methods makes resulting dialplan hard in understanding and analyzing.

Are you planning to extend functions of VDP?
To add priority jumping to GoTo component.
May be ExecIf component?
Add intergration with func_odbc ?
Add standart variables support ?

VDP don’t know about a lots of standart variables like ${CALLERID(num}, ${EPOCH}, ${DIALSTATUS}, ${READSTATUS}
It is uncomfortable to add this standart variables as my channel variables to be able to use it.

Currently I feel very often limited by abilities of this software.

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

#6042 |

Raman, unfortunately your trick with splitting context is not working.
I will explain.
In attach my test dialplan.

This is how it should be: main extension 457, and this trick ‘vdptrick’ as entrance point for jump to special priority in main dialplan.
I use main extension in further for different actions (store in database cdr data from macro for statistics etc.)
i.e. for saving amount of calls to some IVR line, store history of navigation etc.
I use variable ${EXTENSION} or ${MACRO_EXTENSION}

But the result dialplan looks surprising:
”
exten => vdptrick,1(lbl_test_exten_1),Macro(ivrread,457_info,)
exten => vdptrick,n,Macro(ivrread,457_info,)
exten => vdptrick,n,Hangup()
exten => 457,1,NoOp(CALLERID ${CALLERID(num)})
exten => 457,n,Macro(ivrread,welcome,nowait)
exten => 457,n,Macro(langselect)
exten => 457,n,Goto(vdptrick,lbl_test_exten_1)”

So… VDP moved main block to trick extention. It will broke my statistics.
How can i solve this problem?

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

#6043 |

Raman?
Any comments?

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

#6044 |

Can anybody explain me such VDP behavior?

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

#6045 |

Mthawk,

As for the question about additional functionalities in VDP, I’m sorry, but I’m not the right person to answer that question, you should contact Apstel support in this regard.

Regarding the Goto to the particular priority, I’m not seeing two contexts in the screenshot only one is present. Basically the idea is to create two contexts instead of one, so you could easily jump from the one to another by using Goto block.

Raman