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

J

jpc

@jpc
Unfollow Follow
About
Posts
10
Topics
5
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Flash end of life
    J jpc
    Support

    I just looked it it seems to already using HTML5 web sockets. Nevermind!


  • Flash end of life
    J jpc
    Support

    FOP has served our company well for many years so I hate to see its namesake technology go. Maybe we’ll call it Fantastic Operator Panel going forward. HTML5 migration would be great but sounds like a massive undertaking. Call stats it static enough to for an easier migration.


  • Flash end of life
    J jpc
    Support

    In less then a year flash will be removed, not just disabled by default, from all major browsers. What are you plans moving forward?


  • DAHDI Trunk w/FreePBX 2.10 + Asterisk 1.8.10 not working
    J jpc
    Support

    Just setup a system with the latest FreePBX (2.10.0.3) and Asterisk 1.8 (1.8.10.0) and I’m having issues with getting the DAHDI trunks showing any activity in FOP2.

    Running a "core show channels concise" shows the DAHDI channel being reported as “DAHDI/i1/7700843635-3f4”, “DAHDI/i1/4827465532-3f5”, “DAHDI/i1/8370262141-3f6”, and so on. So it seems like the DAHDI channels now report as “DAHDI/interface number/phone number-uniqueID”.

    How would I get my DAHDI trunks to display in FOP2 now?


  • Queue Channel in Fop2Admin 1.2.9
    J jpc
    Support

    I am running freepbx 2.9 but with a custom login/out queue script for BLF support. Thanks for your help, option 1 worked great!


  • Queue Channel in Fop2Admin 1.2.9
    J jpc
    Support

    I just upgraded to FOP 2.24 & Fop2Admin 1.2.9 and now I unable to set my correct queue channel for login. Users are getting logged in as "Andy (Local/305@from-queue/n)" and it needs to be "Local/305@from-internal/n". In the prior version it worked fine since I was able to use the ‘queuechannel’ field in the FOP2Admin 1.1 to set it. It’s no longer in the FOP2Admin 1.2.9. I tried to manually add “queuechannel=Local/305@from-internal/n” to the op_buttons_additional.cfg just to test and still had no effect.


  • Queue Member Penalty
    J jpc
    Feedback

    It would be helpful when adding members to a queue that you could also set the members penalty. You can currently set the members “Queue Channel”, maybe some syntax “Queue Channel, Penalty” to allow FOP2 to set the members penalty level. “Queue Channel” without the extra option wouldn’t set a penalty and would function as is. Penalty is an integer zero or greater.

    All you would need to do is add one additional parameter to your AddQueueMember call.

    Asterisk <=1.4
    AddQueueMember(queuename[|interface[|penalty…
    Asterisk >=1.6
    AddQueueMember(queuename[,interface[,penalty…

    Full functions.
    AddQueueMember(queuename[|interface[|penalty]]): (1.0)
    AddQueueMember(queuename[|interface[|penalty[|options]]]): (1.2)
    AddQueueMember(queuename[|interface[|penalty[|options[|membername]]]]): (1.4)
    AddQueueMember(queuename[,interface[,penalty[,options[,membername[,stateinterface]]]]])): (1.6+)


  • Queue Penalty
    J jpc
    Support

    When adding or removing members to a queue, fop2 uses the default AddQueueMember/RemoveQueueMember commands. Is there any way that I can set the members penalty? AddQueueMember(queuename[,interface[,penalty[,options[,membername[,stateinterface]]]]]))


  • Listen and Listen&Whisper doesnt work With astersk 1.6
    J jpc
    Support

    Works great, Thx.


  • Listen and Listen&Whisper doesnt work With astersk 1.6
    J jpc
    Support

    Runing 2.11 for i386 Centos 5 and still getting this from Asterisk:
    The application delimiter is now the comma, not the pipe. Did you forget to convert your dialplan? (ChanSpy(SIP/339|w))

  • 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