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

S

synergy

@synergy
Unfollow Follow
About
Posts
4
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • I moved from Trixbox to Elastix
    S synergy
    Support

    Nicolas,

    I have not successfully been able to get FOP2 running on elastix. I cannot log in it just hangs. With trixbox it worked just fine. Is FOP2 compatible?


  • User permissions
    S synergy
    Support

    I am not familiar with shell script's commands but can someone help me rewrite this:

    for A in cat /etc/asterisk/voicemail.conf | grep "=>" | cut -d, -f1 | sed 's/ => /:/g'; do echo user=$A:all; [/color:2dq5m1pf]

    so it will check for an extension or a group of extensions so that different permissions can be set?

    something like this:

    for A in cat /etc/asterisk/voicemail.conf | grep "=>" | cut -d, -f1 | sed 's/ => /:/g'; do [/color:2dq5m1pf]if ($A=extn1) echo user=$A:all else echo user=$A:dial,hangup,pickup,record,transfer fi[/color:2dq5m1pf];[/color:2dq5m1pf]

    user=extn1:pass:all
    user=extn2:pass:dial,hangup,pickup,record,transfer
    user=extn3:pass:dial,hangup,pickup,record,transfer

    The reason for why this is need is the voicemail passwords will change and the FOP2 user password will not be in sync. Unless there is something else that can automate this that I am missing


  • User permissions
    S synergy
    Support

    Aww I see what you mean. Here is what I did to make it work.

    1. Commented out line from autoconfig-users-freepbx.sh
      #for A in cat /etc/asterisk/voicemail.conf | grep "=>" | cut -d, -f1 | sed 's/ => /:/g'; do echo user=$A:all; done

    That will allow USERS defined in /usr/local/fop2/fop2.cfg not to get overridden by the execution of the shell script.

    Muchos Gracias Nicolas!

    Basil


  • User permissions
    S synergy
    Support

    After editing the config file and setting the permissions and restarting the fop2 service I still see the listen and whisper buttons. Please advise.

    /usr/local/fop2/fop2.cfg
    user=EXT:PASS:dial,hangup,meetme,pickup,record,transfer

  • 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