Skip to content

World

Topics from outside of this forum. Views and opinions represented here may not reflect those of this forum and its members.

A world of content at your fingertips…

Think of this as your global discovery feed. It brings together interesting discussions from across the web and other communities, all in one place.

While you can browse what's trending now, the best way to use this feed is to make it your own. By creating an account, you can follow specific creators and topics to filter out the noise and see only what matters to you.

Ready to dive in? Create an account to start following others, get notified when people reply to you, and save your favorite finds.

Register Login
  • S

    Hello,
    I (re) installed fop2 on a freepbx17 debian12 server (asterisk 21)
    I get an MySQL error in the Call History popup.
    I had to install asterisk and dahdi with phreakscript as I needed an old dahdi driver and had to more or less manually install freepbx17 (without asterisk) on top.
    All seems to be working, the only error I get is this :

    Fatal error: Uncaught mysqli_sql_exception: Unknown column 'direction' in 'having clause' in /var/www/html/fop2/lib/dblib.php:96 Stack trace: #0 /var/www/html/fop2/lib/dblib.php(96): mysqli_query() #1 /var/www/html/fop2/lib/dbgrid.php(826): dbcon->consulta() #2 /var/www/html/fop2/lib/dbgrid.php(1685): dbgrid->set_pagination() #3 /var/www/html/fop2/lib/dbgrid.php(1182): dbgrid->print_grid() #4 /var/www/html/fop2/calldetailrecords.php(600): dbgrid->show_grid() #5 {main} thrown in /var/www/html/fop2/lib/dblib.php on line 96

    The asteriskcdrdb database is the old one I reimported from the old centos freepbx16 server .
    The call history is working for both inbound and outbound calls .
    Does anybody know where the column 'direction' is supposed to be ?
    I guess there has been a change in the table structure which I missed by importing the old table
    Thanks


    Well it took me some time too look at it again, but yes finally I found the problem. I think I have not done it properly in the first place as I have not imported the table before updating FOP2. But I discovered some more problems e.g. regular segfaults on debian 12 and a few php8.2 (freepbx17) deprecations with caused this error and others like plugins in the admin not showing up properly. I put a modified / adapted version of fop2 on github. It's split between webroot for php files and server/systemd It' here : https://github.com/schiffsratte/fop2-modernize
  • K

    I have wallboard plugin installed on issabel4, fop2_server is running ok. But the agents table is not shoing their statistics like: Inbound, Outbound, Refused calls, and session times. I have moved the board from one server to a new one, it was working fine on the old one. Please advise how I can get these stats to show.

    Thank you

    Terah


    Since it worked on the old server, I'd check the AMI connection and credentials first. After a server migration, that's often the culprit. Have you also tried restarting the Wallboard service after verifying the configuration?
  • N

    We have created a Telegram channel to post updates and news about FOP2. You are invited to join!


    Thanks for creating the Telegram channel. It's a convenient way to keep up with updates, especially for users who already use Telegram. It would be even more useful if it included more frequent posts and links to important announcements or support resources. Keep up the good work!
  • S

    The Live Chat Bot is useless and cannot get me to a human, but also does not know how to get me to a human. It keeps saying to check the Portal, but there's nothing on the Portal for support. I need to get my Licence Code revoked. I cannot do it on the old VPS as it is dead. I cannot do it on the Portal as it claims I've done it 4 times or something. Can someone please help me?


  • S

    In FOP2 version 2.31.40, calls to users are showing as coming in on line 2-4 and not on line 1. There is one user where the calls show on line 4 and 5 only and nothing before that. We have reloaded the panel and asterisk as well as disabled the Button and enabled it again. Has anyone seen this before?


    I should mention that FOP2 is running on FreePBX 15.
  • A

    A penas instale Issabel 5 e intento abrir el FOP2 me sale el error "Could not connect to port 4445 using regular websocket protocol", pero el FOP2 Manager si me abre. Tengo desactivado el firewall en Issabel, y en el firewall del Linux tengo habilitada la regla par el puerto 4445.
    Cuando ejecuto:
    netstat -lnp | grep 4445
    Este es el resultado:
    tcp 0 0.0.0.0:4445 0.0.0.0:* LISTEN 9076/fop2_server
    Probe desactivando temporalmente el firewall para probar:
    systemctl stop firewalld
    Pero sigue saliendo el mismo error.
    Alguna idea de donde revisar o que configuración adicional toca realizar?
    Muchas gracias


    Aca esta funcionando haciendo proxy reverso con nginx server { listen 4440 ssl http2; server_name tudomino.com; root /var/www/html/; ssl_certificate "/certificado.crt"; ssl_certificate_key "/certificado.key"; ssl_session_cache shared:SSL:1m; ssl_session_timeout 10m; ssl_ciphers HIGH:!aNULL:!MD5; ssl_prefer_server_ciphers on; location / { proxy_pass http://127.0.0.1:4445; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } error_page 404 /404.html; location = /40x.html { } error_page 500 502 503 504 /50x.html; location = /50x.html { } } map $http_upgrade $connection_upgrade { default upgrade; '' close; } En el archivo de configuracion de FOP2 usr/local/fop2/fop2.cfg deshabilita el certificado SSL. listen_ip = 127.0.0.1 listen_port = 4445 sslproxy=1 proxy_port=4440 Con esto debe funcionar haciendo offloading SSL en el nginx cambiando el wss a ws internamente. Saludos,
  • N

    We have listen/whisper set up on FreePBX. Panel Manager version 1.2.4.
    When a user is listening into a call, is there a visual indicator to show this?


  • N

    Fresh install of freepbx version 17.0.28 with FOP2 2.31.50, presence manager installed but doesn't seem to be changing extensions to DND.


  • S

    Is there an update soon for the fop2 extension for Chrome?
    I have some users reporting that the extension is no longer supported, with this message from Google Chrome:
    **This extension is no longer be supported because it doesn't follow best practices for Chrome extensions.
    **All users are reporting this message for the last month or so:
    This extension may soon no longer be supported
    Remove or replace it with similar extensions from the Chrome Web Store


    you can use edge, there is an extension/addon for edge and works fine there.
  • F

    Hi. As wrote in the title, FOP2 presence state and Sangoma Phone presence state don't match.
    I read very old topic in this forum, but no solution
    Any idea how to fix it? Thanks


    Did you ever find a solution for this? I'm in the same situation, setup the sangoma phone app for PC, doing some testing before rolling it out and they do not show active on the panel even when adding the extra channel
  • I

    please after fop2 remove ad install it from adds on in issabel it not working and i already added ssl certificate on /usr/local/fop2/fop2.cfg


    Greetings! We'd love to hear your opinion. Leave your suggestions, it's important to us. http://tr35.ru/bitrix/redirect.php?event1=&event2=&event3=&goto=https://mature-ptv.com/c/slave/ http://vladtv.ru/bitrix/rk.php?goto=https://mature-ptv.com/c/vietnam/ http://pinkycar.ru/bitrix/redirect.php?event1=&event2=&event3=&goto=https://mature-ptv.com/c/creampie/ http://www.hannobunz.de/url?q=https://mature-ptv.com/c/skirt/ http://diskont-foto.ru/bitrix/rk.php?goto=https://mature-ptv.com/c/striptease/
  • R

    fop2 not loading and times out but fop2 manager loads fine I am running FreePBX 16.0.45
    fop2 Version: 2.31.29 Panel Server Status: OK
    I rebooted the FreePBX server and Reloaded the fop2 Panel but nothing is working.
    How do I fix?


  • K

    Hi Dears

    We have FOP2 V.2.31.49 with FreePBX 16.0.41.4 and Astrisk 20.4.0
    fop2.service restarted every 80 Seconds.
    Every 80 Seconds FOP2 panel in user side will disconnected and after 5 seconds it will reconnect.
    but every Caller ID in User panel will lost.

    Dec 11 19:41:54 freepbx.sangoma.local systemd[1]: Starting Flash Operator Panel 2...
    Dec 11 19:43:25 freepbx.sangoma.local systemd[1]: fop2.service start operation timed out. Terminating.
    Dec 11 19:43:25 freepbx.sangoma.local systemd[1]: Failed to start Flash Operator Panel 2.
    Dec 11 19:43:25 freepbx.sangoma.local systemd[1]: Unit fop2.service entered failed state.
    Dec 11 19:43:25 freepbx.sangoma.local systemd[1]: fop2.service failed.
    Dec 11 19:43:30 freepbx.sangoma.local systemd[1]: fop2.service holdoff time over, scheduling restart.
    Dec 11 19:43:30 freepbx.sangoma.local systemd[1]: Stopped Flash Operator Panel 2.
    Dec 11 19:43:30 freepbx.sangoma.local systemd[1]: Starting Flash Operator Panel 2...
    Dec 11 19:45:00 freepbx.sangoma.local systemd[1]: fop2.service start operation timed out. Terminating.
    Dec 11 19:45:00 freepbx.sangoma.local systemd[1]: Failed to start Flash Operator Panel 2.
    Dec 11 19:45:00 freepbx.sangoma.local systemd[1]: Unit fop2.service entered failed state.
    Dec 11 19:45:00 freepbx.sangoma.local systemd[1]: fop2.service failed.
    Dec 11 19:45:05 freepbx.sangoma.local systemd[1]: fop2.service holdoff time over, scheduling restart.
    Dec 11 19:45:05 freepbx.sangoma.local systemd[1]: Stopped Flash Operator Panel 2.
    Dec 11 19:45:05 freepbx.sangoma.local systemd[1]: Starting Flash Operator Panel 2...
    Dec 11 19:46:36 freepbx.sangoma.local systemd[1]: fop2.service start operation timed out. Terminating.
    Dec 11 19:46:36 freepbx.sangoma.local systemd[1]: Failed to start Flash Operator Panel 2.
    Dec 11 19:46:36 freepbx.sangoma.local systemd[1]: Unit fop2.service entered failed state.
    Dec 11 19:46:36 freepbx.sangoma.local systemd[1]: fop2.service failed.
    Dec 11 19:46:41 freepbx.sangoma.local systemd[1]: fop2.service holdoff time over, scheduling restart.
    Dec 11 19:46:41 freepbx.sangoma.local systemd[1]: Stopped Flash Operator Panel 2.
    Dec 11 19:46:41 freepbx.sangoma.local systemd[1]: Starting Flash Operator Panel 2...
    Dec 11 19:48:11 freepbx.sangoma.local systemd[1]: fop2.service start operation timed out. Terminating.
    Dec 11 19:48:11 freepbx.sangoma.local systemd[1]: Failed to start Flash Operator Panel 2.
    Dec 11 19:48:11 freepbx.sangoma.local systemd[1]: Unit fop2.service entered failed state.
    Dec 11 19:48:11 freepbx.sangoma.local systemd[1]: fop2.service failed.
    Dec 11 19:48:16 freepbx.sangoma.local systemd[1]: fop2.service holdoff time over, scheduling restart.
    Dec 11 19:48:16 freepbx.sangoma.local systemd[1]: Stopped Flash Operator Panel 2.
    Dec 11 19:48:16 freepbx.sangoma.local systemd[1]: Starting Flash Operator Panel 2...


  • A

    "Could not connect to port 4445 using regular websocket protocol"
    this message show every 1 or 2 minute t
    hen start to reload fop2 panel
    https://uploadkon.ir/uploads/65bd18_25Screenshot-2025-11-18-090212.png


    We have the same problem. The Exact Refresh time and socket reset is 80 seconds. Every 80 Seconds FOP2 panel in user side will disconnected and after 5 seconds it will reconnect. but every Caller ID in User panel will lost.
  • C

    I followed installation instructions for both main program and wallboard and registered the product, but FOP2 does not start it just keeps trying to restart. FOP2 panel and admin panel can be reached while it is restarting, but it reloads browser whenever it restarts.

    after running:
    root@pbx:/# journalctl -xeu fop2.service
    Subject: A start job for unit fop2.service has failed
    Defined-By: systemd
    Support: https://www.debian.org/support

    A start job for unit fop2.service has finished with a failure.

    The job identifier is 2754 and the job result is failed.
    Nov 11 14:29:36 pbx.thedocs.md systemd[1]: fop2.service: Consumed 5.239s CPU time.
    Subject: Resources consumed by unit runtime
    Defined-By: systemd
    Support: https://www.debian.org/support

    The unit fop2.service completed and consumed the indicated resources.
    Nov 11 14:29:42 pbx.thedocs.md systemd[1]: fop2.service: Scheduled restart job, restart counter is at 29.
    Subject: Automatic restarting of a unit has been scheduled
    Defined-By: systemd
    Support: https://www.debian.org/support

    Automatic restarting of the unit fop2.service has been scheduled, as the result for
    the configured Restart= setting for the unit.
    Nov 11 14:29:42 pbx.thedocs.md systemd[1]: Stopped fop2.service - Flash Operator Panel 2.
    Subject: A stop job for unit fop2.service has finished
    Defined-By: systemd
    Support: https://www.debian.org/support

    A stop job for unit fop2.service has finished.

    The job identifier is 2825 and the job result is done.
    Nov 11 14:29:42 pbx.thedocs.md systemd[1]: fop2.service: Consumed 5.239s CPU time.
    Subject: Resources consumed by unit runtime
    Defined-By: systemd
    Support: https://www.debian.org/support

    The unit fop2.service completed and consumed the indicated resources.
    Nov 11 14:29:42 pbx.thedocs.md systemd[1]: Starting fop2.service - Flash Operator Panel 2...
    Subject: A start job for unit fop2.service has begun execution
    Defined-By: systemd
    Support: https://www.debian.org/support

    A start job for unit fop2.service has begun execution.

    The job identifier is 2825.
    Nov 11 14:29:43 pbx.thedocs.md fop2_server[59336]: Using enp1s0 interface for license binding as configured in init script options file.
    Nov 11 14:29:43 pbx.thedocs.md fop2_server[59336]: If you want to specify a different interface, please use the -i command line option.
    lines 1485-1528/1528 (END)

    Any help would be appreciated.


    Thanks a lot, this worked for me. The first step was not necessary. The service does keep restarting but the web pages are not refreshed on each restart so it is fine.
  • W

    Finally rebuilt our phone system, coming from Elastix 2.5. I got FOP2 running and registered... but every few minutes, I get the One Moment Please. It takes a try or two and reconnects. The service appears to be restarting on it's own. What logs can I review to troubleshoot?


  • J

    Updated a FreePBX 15 / Asterisk 18.26.4 server to a new FreePBX 17 / Asterisk 22.5.2 setup. I installed a new FOP2 license and then used the instructions at https://www.asternic.net/docs/knowledgebase/migrate_fop2_config/ to move the FOP2 configuration to the new server. When we run the import command on the new server, we get an error.

    Importing groups
    PHP Fatal error: Uncaught mysqli_sql_exception: Field 'context_id' doesn't have a default value in /var/www/html/fop2/lib/dblib.php:96
    Stack trace:
    #0 /var/www/html/fop2/lib/dblib.php(96): mysqli_query()
    #1 /usr/src/fop2/server/import_fop2_configs.php(107): dbcon->consulta()
    #2 /usr/src/fop2/server/import_fop2_configs.php(385): import_groups()
    #3 /usr/src/fop2/server/import_fop2_configs.php(21): main()
    #4 {main}
    thrown in /var/www/html/fop2/lib/dblib.php on line 96

    Any suggestions on getting the config import to work, or do we need to rebuild the configs from the GUI?


  • S

    As per title, I upgraded to 2.31.39 and have rebooted. After that users can no longer remove themselves from a queue.
    No other changes were made to FreePBX. All affected users are still in the Dynamic Agents in the FreePBX queue. No other updates have been applied to FreePBX.
    How to debug?


    I'm using version 2.31.48 and the issue is still in place. No remove from queue.
  • F

    Hi,
    I got the paid plugin Queue Login and all looks OK but it's not working, even though I have enabled auto login etc. I played around with various setting combinations but non work.
    I'm using Panel Server Status: OK - Version: 2.31.47
    Anybody have any idea or can help?

    You help is much appreciated.


  • T

    Hi everyone, new here and desperately need advice. I have a tampered call recording from a Holiday Tour Operator, a spectragram analysis has been done, from the image is this horizontal bar normal? This section of the recording has a long bleep, I believe where some content was removed, thanks for your feedback