the above does not make much sense. Dahdi replaced Zap, so you can just remove the channel line, if you want to catch both zap/dahdi appeareances in ami events , you might want to set the channel number the same as the button itself.. (zap/2, dahdi/2).

Now, the autoconfig-buttons-freepbx.sh script will override the changes you add by hand in the buttons.cfg file. Either add your zap lines manually by modifying the script, or you can also go "all manual" and write your own buttons.cfg file.

The #exec line will execute the script/program you put there, and it will read stdout and parse it as regular configs for fop2. So it is not STORED anywhere, it is executed and parsed when you start or reload fop2.

You can add a bunch of

echo "[ZAP/2]"
echo "type=trunk"
echo "label=line 2"

at the end of the autoconfig-buttons-freepbx.sh script for example.

One last thing: the latest beta lets you mix #exec and static configs with no problems.

Best regards,

Where does it create the button.cfg file when it runs?

I need to show it each line separate with the number as the line label, something like this maybe but this does not work.
[DAHDI/2]
type=trunk
label=123-456-7890
channel=ZAP/11