wikipbx-dev team mailing list archive

[Stas Shtin <antisvin@xxxxxxxxx>]

 On 25.06.2010 16:22, Dmytro Mishchenko wrote:
>> I'd say that those are two biggest features that wikipbx is missing. For
>> 0.9 we were planning to work mostly on infrastructural changes to get it
>> in line with modern version of django. We would probably add feature #1
>> in version 1.0 then. If you're interested in working on it, we can
>> either release it in 0.9. Or maybe we'll skip that release number and
>> call it 1.0 as the amount of changes gets rather big.
>>
>>     
> We are interested in stable release with #1 feature. #2 can wait,
> initially it'll be enough to have possibility to turn off IVR scripting
> in admin backend.
>
> If you think the current trunk is ready for release it's fine for us
> too. It can be released while we are working on Extensions configurator.
>   

No I didn't mean to release it too soon. There's a lot of tasks that I'd
like to finish first.

>> We've been thinking about that some time ago. Traun had the general idea
>> and I've written my thoughts about implementing it. What we wanted to do
>> is to create a way to add templates for extensions that could prompt
>> user for values. It looks like that would do just what you want, so I'll
>> create a blueprint for that issue later and we'll discuss it then. I
>> think it can be done in reasonable amount of time.
>>
>>     
> Sounds ok to me. Lets create blueprint asap so we can move on with it.
>
>   
Done - https://blueprints.launchpad.net/wikipbx/+spec/extension-templates

There's a link to wiki page with actual description, it would be more
convenient to work in the wiki.
> I'm thinking about more simple solution. Except general IVR settings
> like announcement, timeout, etc. we allow customer to choose action
> performed when digit is pressed. List of these action is limited.
> E.g.:
> - another IVR
> - extension
> - ... action based on pre-configured template. E.g. Playing certain
> instructions.
>
> Action - can be implemented using the same kind of templates "that
> prompt for values" as you describe in extension configurator.
>
> Examples of templates:
> name: ivr; parameters: ivr_name
> name: extension; parameters: ext #
> name: play_file; parameters: recording_file_name
> name: speak_text; parameters: type_of_voice, text_to_speak
> ...
>
> That should be enough for 90% of customers. Templates for combined cases
> like "play_file then speak_text" can be created by admin on customer
> request.
>
> These actions will be building blocks for IVR and they can be put
> together in some visual way.
>   
It looks like extension templates can be enhanced to handle DTMF keys.
It would give us a less complicated solution. Also, we could use XML
dialplan rather than embedded python or other language - it's less
resource hungry.

> I'm thinking about scripting library as an addition to IVR actions
> described above. They can be used together for more complicated stuff
> where dialplan XML is not enough. Scripts should be editable only by
> wikipbx admin (initially even outside web gui) if he knows what he is
> doing.
>   
Scripting in what language? We already support python and JS. Perhaps
what you actually want is to make them read-only for unprivileged users.
Django supports model permissions
http://docs.djangoproject.com/en/dev/topics/auth/#id1 , we could just
create interface for admin users for setting them and check them in
user's IVRs page.

Stas.