Answ.Mach.Construction Kit

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Gert Doering <gert@greenie.muc.de> wrote:
> Basically a good idea.  Don't make it hierarchical only - make it possible
> to return to something ("main menu").

This is what mvm does, indeed.

You create a file /usr/spool/voice/main/commands

and you put into menu item types:

0 goodbye 0
1 read_mail 1
2 send_mail 0
3 create_account 0
4 cookie 0
5 random_sample 0
6 play 0 /usr/spool/voice/messages/internet_introduction_francais
7 record_and_exec 100 /usr/spool/voice/scripts/play_pchp.sh
8 param_cmd 1 /usr/spool/voice/main/fax_operation_description_file
9 edit_menu 0
+ identify 0
# message_to_operator 0

The edit_menu function allows to add new entries even while connected
by phone (also sub-menus).

> Add checks for "if the caller ID is ... go to node ...".

This is not here: user will be identified and an access level is set
(0 unindentified, 1 identified, bigger levels are per-user-definable).
This is the third number. 

However, mvm can have multiple instances, one per number, with its
own menu structure and/or mailboxes.

> Add time based checks.  Add external programs to do checks ("if gert is
> logged in and not idle more than 10 minutes, play different text").

This could be added. At this time mvm is only menu driven, not event
driven.