ASwingler

Member

Last active 13 years ago

  1. 13 years ago
    Wed Mar 16 19:07:16 2011
    ASwingler started the conversation Feature Request: Request VM Prefix set in FreePBX.

    We're using FOP2 2.20 on Asterisk 1.4 with Fop2Admin / FreePBX.

    I've been wondering why our transfer-to-voicemail feature was failing. It turns out that the autoconfig-buttons-freepbx.sh script has the default direct-to-VM prefix hard-coded as "*" and thus creates button-file entries such as "extenvoicemail=*<EXTEN>@default'. We changed our prefix and so this is incorrect for our environment.

    Would it be possible to update the script to include a check for the "Direct Dial Voicemail Prefix" value that's stored in the General Settings in FreePBX?

    I noticed that someone else had a similar issue last year: View Post 528 .

    In case it helps, the value is stored in extensions_additional.conf - the key is "VM_PREFIX".
    It's also stored in the DB in asterisk.globals with the key "VM_PREFIX".

    Thanks so much - we really appreciate the hard work you've put into FOP2 !!

  2. Fri Mar 11 21:36:28 2011

    I'll check into that. Thanks for getting back to me!

  3. Fri Mar 11 21:36:05 2011

    Perhaps an active/inactive flag instead?

  4. Thu Mar 10 18:21:26 2011
    ASwingler started the conversation BUG: Empty labels get re-populated in FreePBX Module.

    FOP 2.20.

    If I clear a label in the FreePBX Module it appears to get saved properly but the input box gets re-populated and so the next time I make a change the label gets re-added.

    I tested a user and a trunk and the behavior is the same in each case.

  5. Thu Mar 10 17:31:57 2011
    ASwingler started the conversation Default Permissions when using FreePBX Module.

    Hello.

    We're just starting to use FOP2. It's installed, licensed and working well. We have installed the FreePBX module which appears to be working correctly. FOP 2.2 on Asterisk 1.4.

    We'd like to be able to set the default permission for users so that certain buttons (recording, listen etc.) do not appear unless we specifically add them to the user. I know we can set the permission for each individual user to remove the unwanted buttons but we'd prefer to have a lower access level by default to ensure our environment is as secure as possible. Can this be done?

    Regards, Andrew.