[Migrated from old forumParticipant April 12, 2015 at 1:25 pm Post count: 327]

in reply to: HASH() function is not present #6050 |

Mark, with Custom code i can write any raw dialplan 🙂
I can do it even in any text editor 🙂 And it will be free of charge development environment.
So why i need VDP? To write raw dialplan in single custom code block?

The question is: i bought this software and i want to use it with all Asterisk abilities. Why i can’t?
Custom code should be used for some situations when i add something non-standard to asterisk. Like JSON-support via custom module res_json.so. But not for well-known native functions.

ODBC functions – custom code.
GoTo to exact context-extension-proirity – custom code
Context name / Macro name as variable in GoTo/GoSub/Macro – custom code
Standard variables (their list is present in each Asterisk web resource) – need to be created as custom channel variable to be able to be used.

This is the top-inconveniences list. And day-by-day it becomes longer.

[Migrated from old forumParticipant April 12, 2015 at 1:25 pm Post count: 327]

in reply to: HASH() function is not present #6049 |

Did you try with Custom code block?

Mark

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

in reply to: is_email example not working #6047 |

I had the same issue and then tried with Gmail and it worked fine.

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

in reply to: How to call Macro from Dialplan? #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

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

in reply to: How to call Macro from Dialplan? #6044 |

Can anybody explain me such VDP behavior?

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

in reply to: How to call Macro from Dialplan? #6043 |

Raman?
Any comments?

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

in reply to: How to call Macro from Dialplan? #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]

in reply to: How to call Macro from Dialplan? #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]

in reply to: How to call Macro from Dialplan? #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:11 am Post count: 327]

in reply to: How to call Macro from Dialplan? #6039 |

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.

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

in reply to: How to call Macro from Dialplan? #6038 |

Mthawk,

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.

Raman

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

in reply to: How to call Macro from Dialplan? #6037 |

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.

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

in reply to: How to call Macro from Dialplan? #6036 |

Mthawk,

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.

I hope this helps.

Raman

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

in reply to: How to call Macro from Dialplan? #6035 |

Thanx.
So i’m waiting for official support answer.

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

in reply to: How to call Macro from Dialplan? #6034 |

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.

Kevin