fop2 trixbox no trunks

Comments

• nicolas

  June 2012

  Hi,
  
  The Free/Lite version is limited to 15 buttons on screen. If you reach that limit, any other button (no matter what kind) won't be displayed.
  
  You can disable buttons via the disable checkbox in fop2admin fop2 buttons page if you want to disable some to "make room" for other types, or you can register to see all buttons with no limits.
• evgenv

  June 2012

  Hello. I'm using free version. I know about 15 buttons limit - I didn't reach this limit.
  I temporarily solved the problem by manually editing fop2.cfg and making buttons.cfg file.
  Seems like FreePBX fop2admin module can't pass config to fop2...
• nicolas

  June 2012

  Hi,
  
  If you have doubts about the autoconfiguration script, run it by hand and inspect the output:
  
  /usr/local/fop2/autoconfig-buttons-freepbx.sh
  
  The first 15 buttons you see on that configuration files are the ones you are going to see. If turnks are below, you are NOT going to see them. This limitation is performed regardless of group or contexts configurations. If you want to disable buttons to make room, you can do so by checking the disabled checkbox on the fop2 buttons page.
• mulderlr

  March 2015

  I have this issue of no trunks displaying on trixbox CE. I have full licensed version installed on two different systems. autoconfig-buttons-freepbx.sh runs without errors, but doesn't produce trunk button information regardless of what type of trunk it is. One system has SIP trunk with no buttons produced, the other has a sangoma card with ZAP trunks and on neither system does FOP2 2.28 scripts find the trunks. So, I created buttons.cfg manually and the gui for any extension with 'all button' permissions will not show the trunk button. It isn't critical but would be nice to see it there. Is this a limitation of trixbox ce because it is so old or doing something wrong with FOP2?
• nicolas

  March 2015

  Hi mulderlr,
  
  You did not have the same issue, but a different one. If you run fop2 without registering, it has a hard limit of 15 buttons, that will left out trunks, queues, parks, etc, unless you disabled extensions/conferences to make room for them, or if you register your copy to avoid that limit.
  
  Trixbox is quite old, its freepbx version is modified and outdated, it is possible that trunks are not stored in the asterisk database in the way fop2manager expects it to be, so it won't produce the trunk button in itself. You can very well edit functions-freepbx.php and look for the function that extracts trunk info from the DB, and compare to your own database schema and see if you can fix it or add support for it. It should not be that hard *if* trunks are stored in a database somehow.
  
  Best regards,
• mulderlr

  March 2015

  I am referring to the registered version, so not restricted by the 15 button limit. I will look in the code and if I find a fix, I will update this thread. Thanks for the tip!
• nicolas

  March 2015

  Function is trunks_check_extensions_freepbx() , it includes a newer version and an older version to query for trunks in a database.
• mulderlr

  March 2015

  so, trixbox ce doesn't appear to have a 'trunks' table in the asterisk database at all. It has a zap table and a zapchandids table, but no trunks table. I can understand why that would not allow the autoconfig-buttons-freepbx.sh script to create the button, but if the button is created manually, it still doesn't work.
• nicolas

  March 2015

  Hi,
  
  Trunk buttons will work if defined correctly. If you have a button that fails to display states is just because the channel/device name used does not match the channel/device name broadcasted by asterisk via AMI.
  
  Do a
  
  asterisk -rx "show channels"
  
  To see the channel names when you have ongoing calls via your trunk, that name, minus the -xxxxx suffix (session) is the one you have to use in a button definition in fop2.
  
  Best regards,
  
• mulderlr

  March 2015

  I would be happy if I could get a trunk button to show up in the GUI - monitoring the state would be icing on the cake at this point. Manually defining the button as so many examples and forum posts have indicated and defining a buttons.cfg file and pointing to it in fop2.cfg don't yield the trunk button in the GUI.
  
  Here is a sample capture from my show channels:

  Channel              Location             State   Application(Data)
  SIP/109-0a0706c0     (None)               Up      Bridged Call(Local/109@from-in
  Local/109@from-inter s@macro-dial:7       Up      Dial(SIP/109|15|trwWM(auto-blk
  Local/109@from-inter 701@from-internal:1  Up      Bridged Call(Zap/1-1)
  Zap/1-1              701@ext-queues:20    Up      Queue(701|t|||120)
  
• nicolas

  March 2015

  If you use automatic config, there is no point in doing anything in buttons.cfg. You can add something to buttons_custom.cfg, but then, you won't be able to use group filtering, so in order to actually see whatever you add in buttons_custom.cfg by hand you must also edit the user in the manager users tab and unclick/deselect all groups. In buttons custom you can try
  
  [ZAP/1]
  type=trunk
  label=zap trunk
  extension=1
  context=from-trunk
  channel=ZAP/2
  channel=ZAP/3
  channel=ZAP/4
  
  Then restart fop2, and be sure your fop2 user does not have any groups selected.
  
  Best regards,
  
  
• mulderlr

  March 2015

  Working great! Thanks for the help. I added the zap channel info to the buttons_custom.cfg and left the user that I wanted to see this information with all button groups unchecked in the admin and that did the trick!