FOP2 Community Forum

Hi everyone! Recently I went through the installation procedure for installing the full Wallboard here: https://www.fop2.com/docs/wallboard_guide.php Which also referenced this page: http://www.asternic.net/docs/#OutboundCallTrackingandFreePBX After following that very carefully, I was able to see outbound calls in Asternic Call Center Stats, but the count for outbound calls was always zero in the full wallboard. After turning on the debugging in the getstatsfromasternic.php script (located in /var/www/html/fop2/admin/plugins/fullwallboard on a standard FreePBX installation), I found that the problem existed in the database where Asternic keeps its settings and statistics. getstatsfromasternic.php looked for the settings for what the outbound call queue was called with the following MySQL call: SELECT * FROM setup WHERE keyword='call_flow' OR keyword='sla_answered'; +----+--------------+------------+----------+ | id | keyword | parameter | value | +----+--------------+------------+----------+ | 45 | call_flow | queue_name | outbound | | 23 | sla_answered | | 60 | +----+--------------+------------+----------+ 2 rows in set (0.00 sec) However, for the wallboard to work properly, it requires that both the parameter AND value fields be set to the name you gave your outbound queue. I had to do the following MySQL query to fix the problem: UPDATE setup SET parameter='outbound' WHERE keyword='call_flow'; So far, I haven't noticed any bad side effects to this change, but I remain wary. I'm sure that other people will find this documentation helpful. I'm not sure if there's any way to make this change except by updating the database directly through the MySQL console.

Same here. I have tried to change user and password in database and in config files to no avail. What can we do ?

Thanks for posting details! The default is indeed "bq", some people want to spy even when the call is not bridged (on ivr or similar, so they use just q). Best regards,

Hola! FOP 2.27 under https requires ssl certificates to be configured, the same certificates you use for your web server, by default the config is this: ssl_certificate_file=/etc/pki/tls/certs/localhost.crt ssl_certificate_key_file=/etc/pki/tls/private/localhost.key If you have those files (/etc/pki/tls/certs/localhost.crt and /etc/pki/tls/private/localhost.key) you can uncomment/set those lines in fop2.cfg and then restart fop2. (browsers should enforce a secure web socket connection when using ssl, firefox does that, chrome not yet, but it will in the future, so fop2 defaults to secure websockets if you connect via https). Another option is to disable websockets in /var/www/html/fop2/js/presence.js , that way the old xmlsocket feature from adobe flash will be used instead, that works no matter the protocol, because of flash. Regarding confbridge, fop2 supports it but asterisk only has confbridge manager support since version 11, not in version 10. You should install the meetme module in freepbx to get rid of that warning.

Seems you fixed the manager issue... That is because asterisk disconnected you, you can get around that by setting writetimeout to the manager user, or using eventmasks and eventfilters to reduce the verbosity.. generally, by setting a writetimeout=1000 will do. You can check the blog for a brief article discussing that setup: http://www.fop2.com/blog/make-fop2-snap ... ventfilter

Hi, You searched too hard, and missed the first chapter in the installation guide: http://www.fop2.com/documentation-insta ... arball.php Specifically. the manager credentials section, I will copy the relevant part here: Manager Credentials Before starting the service, some basic configuration is required in fop2.cfg and probably in /etc/asterisk/manager.conf, because the FOP2 daemon connects via TCP to the Asterisk Manager Interface (AMI) using a username and secret. The basic daemon config is covered [url=http://www.fop2.com/documentation-configuration-server.php:nii0nnwn]here[/url:nii0nnwn]. [strip...] You can always check if the manager credentials are correctly configured, and also verify if your license is ok, by running the command: #> /usr/local/fop2/fop2_server --test