Forum Replies Created
-
very strage… it looks like encoding issue, did you try with default wav format?
I did something similar on one of my project in the past – first I did the database query to read options and voice files to be played for each option (voice files were already recorded on the system) and then dinamically play it to the caller to choose one option (option by option in the loop). Options were stored in the database and voice files recorded on the system.
Dial plan logic was build with VDP and database queries done with IS.
It is not so complicate to build with VDP.
Try samples that comes with VDP and you’ll figure it out.— Mark
Can you share it with us?
–Mark
Thanks,
I have recorded with SodelsCot in Spanish and it is very good.
Hi Ateneahost,
The dialplan sample that demonstrate Integration Server payment gateway functionality is bundled with Visual Dialplan and comes with English voice promptos. There are three voice prompts used in this dialplan: EnterCardNumber.gsm, EnterExpMonth.gsm, and EnterExpYear.
We do not have these prompts recorded in Spanish.
However, all you need to do is to record it in Spanish, in GSM file format, and upload it to /var/lib/asterisk/sounds folder.Best regards,
Daniel MinitchApstel support team
I use background without context as well.
There is no pre-seltected first context from the drop down, just empty field where I can type anything or select from the drop down options.
I guess you should upgrade to the latest VDP.Regards,
MarkRegarding the Background widget, the context field is a drop down which can’t be blank and by default selects the first context from the list you’ve created.
Regarding the Gosub widget, obviously the context can’t be blank it’s the argument passed in as “” which was allowed in 3.0 that I’m asking about. See the syntax:
Gosub([context,]exten,]priority[(arg1,…,argN)])
I use VDP 3.2 and Background block does not require context to be specified, just the voice file (gsm).
Maybe I am missing something but there is no field to insert context in Backgroun block in my version.Just curious, why would you use gosub to jump to subroutine without specifying which subroutine (empty string)?
I mean, the purpose of gosub is to ‘go to subroutine’, not to nowhere ;).— Mark
Put both call flows in one VDP file, not in two separate VDP files.
–Mark
Thanks for your help !
I’ll continue to play around…
Type=SIP, IAX2, DAHDI etc.
Device=extension defined for selected typeYou can fill in those filds as you wish but the proper way is to define the connection to the Asterisk server first and THEN start the dial plan development.
That way VDP will read the configuration and will fill in drop downs with exact configuration data from the Asterisk server, and you will not take care if you typed extension properly ;).
Select Edit, then Preferences option from the top menu to open preferences window.Check this tutorial:
http://www.apstel.com/visual-dialplan-tutorials/how-to-connectot-to-asterisk/Mark
-
This reply was modified 10 years, 6 months ago by
admin.
Thanks for the reply
I figured it was the Dial Block, but what parameters do I put in ?
Is it “Type = EXTEN” , “Resource = EXTEN” and “Extension = EXTEN”
or is it something else ?Thanks again…
Use dial block and select target resource in the drop down menu.
Or check this tutorial if target resource is outside the asterisk:
http://www.apstel.com/while-loop/dial-voip-provider/-
This reply was modified 10 years, 6 months ago by
admin.
Hello, Mark
At this time it is all inconveniences which i found.One more wish – make something like dialplan attribute “included” (i.e. not create sections globals and general when publishing dialplan to server.)
Because when I work over some dialplan file which is included to main extensions.conf i must remove this sections each time i make changes in file and publish it to serverMithawk, I am not sure how experienced you are in software development but in my 10+ years of development in various tools I had never find the tool that implemented all I want ;). In case of Asterisk, where you have new version almost every year, with number of new dial plan applications coming with it, the Visual Dialplan would be very unfriendly tool if these guys have had support it all.
I am actually very happy they didn’t do that ;).
Said that, I am using Visual Dialplan for two years now and I also had to use custom code from time to time.
My most wanted app to be support is hint.
Here is compiled list with apps/functions you need:
ODBC functions (BTW, I use Integration Server for this, much easier for maintenance)
GoTo to exact context-extension-proirity
Context name / Macro name as variable in GoTo/GoSub/Macro
Standard variables (their list is present in each Asterisk web resource)
HintAdd here if you have something more and let’s send it to apstel and ask them for the release date.
They listen. I had correspondence with them in the past and got impression they are very eager to improve visual dialplan.Mark
-
This reply was modified 10 years, 6 months ago by