Post a Reply
1347 views

Zap vs Dahdi Trunks/extensions from Autoconfig-buttons scrip

  1. 13 years ago

    jtshows

    4 Jun 2011

    I am having a little problem with "autoconfi-buttons-freepbx.sh"
    Environment: Elastix v 2.0.0.62
    FOP2: version 2.20

    When I run autoconfig-buttons-freepbx.sh it outputs a section like this:

    ------------- cut ------------
    [ZAP/5]
    type=extension
    extension=1202
    label=Cordless
    context=from-internal
    queuecontext=from-queue
    privacy=none
    group=Home
    queuechannel=Local/1202@from-queue/n
    customastdb=CF/1202
    ------------------------------------

    This is true for both extensions and trunks connected using ZAP/DAHDI Cards.

    The problem is that the status of these buttons are not displayed on the FOP2 panel (never shows they are off hook). If I disable the autoconfig-buttons script and manually configure the extensions and trunks using [DAHDI/5]then the extension/trunk works as expected.

    I have tried my best to figure out why the autoconfig-button script is putting out ZAP instead of DAHDI, but I must admit I am getting nowhere.

    Can anyone help me fix this? I would prefer NOT to move to manual configuration for my buttons if possible.

  2. admin

    4 Jun 2011 Administrator

    the script takes the device name as stored in FreePBX database, you should modify the freepbx database records. Or ask freepbx to fix the problem as you are using dahdi, not zap. It is possible to write exceptions on the .sh script, but not wise. This problem is a freepbx problem. Best regards,

or Sign Up to reply!