Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Support
  3. ZAP Buttons

ZAP Buttons

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 73 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    S
    sergiocesar
    wrote on last edited by
    #1

    I use a digium card with 4 lines
    How can I make a ZAP button for each of our incoming lines where the label would say the number:
    I try this but did not work too well
    [ZAP/1]
    type=trunk
    label=(123)456-7890

    [ZAP/2]
    type=trunk
    label=(123)456-7891

    1 Reply Last reply
    0
    • S
      S
      sergiocesar
      wrote on last edited by
      #2

      I just discovered that the ZAP will show as DAHDI. looking at the code in autoconfig-buttons-freepbx.sh I see all has the DAHDI heading, is there a reason for it?

      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

      1 Reply Last reply
      0
      • N
        N
        nicolas
        wrote on last edited by
        #3
        [ZAP/2]
        channel=DAHDI/11
        

        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,

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups