FOP2 Community Forum

Panel Manager - Version 1.2.4 My browser is stuck at **Connecting to server, attempt number : 1 ** After some time, I get the message "System is not available right now". FOP2 is hosted on a https://panel.mydomain.com/panel/ Please help. Thanks

My extension state shows MEETING. I'm not even sure how it changed. How can I change it to AVAILABLE? Thanks

Latest FreePBX ISO installation Asterisk 16.6.2 FOP Version 2.31.27 Panel Manager - Version 1.2.2 I've created a user: 9000 User Preferences > Automatic Popup = YES User Preferences > Ringing = https://www.google.com/search?q=#{CLIDNUM} User Preferences > Notification = YES. [Accept] [Submit Changes] [Reload Panel] Now if I go back to "User Preferences", Notification shows NO. I've tried this multiple times. In /usr/local/fop2/fop2.cfg, I have set notify_on_ringing=1 Is there anything I have missed? I'm unable to get the call popup to work. I do get sound alerts whenever a call enters a queue. Any help is appreciated, Thanks!! Vaisam

To remove the Dialpad dropdown and Dial box and Dial action button then do not assign the "Dial" permission to the user. To remove the "available" dropdown, do not assign "Change Presence Menu" plugin to the user To remove the Filter box, try adding the following code in /var/www/html/fop2/css/custom_theme/theme.css #navinputfilter nopad { display: none; visibility: hidden; width:0; padding:0; margin:0; }

What do you mean by grey? Not registered? Are they registered? Do you see status when you make calls, etc?

Hi, No, there is no way to do it. It would be also difficult to make it happen as you might have 20 queues with a different number of waiting calls in each. It will also conflict with the chat feature as the chat does manipulate the title if you receive a message and you have the window minimized. Best regards,

Si pones usuario y clave incorrectos y te vuelve a preguntar, entonces la conexion al puerto 4445 esta ok, ahora, si pones usuario y clave correctos y se queda pensando, entonces el cliente javascript esta roto. Quizas tengas en cache la version vieja corriendo con un servidor nuevo. Un cliente version 2.20 puede tener problemas conectando con el servidor 2.22. En cualquier caso, prueba siempre con un navegador diferente, eso te permitira tambien ir descartando posibilidades. Y si la aplicacion javascript esta rota por algun motivo, ese motivo lo veras casi con seguridad abriendo la consola javascript de safari/chrome, o bien instalando firebug para firefox y mirando alli. Incluso la consola javascript de IE9 funciona bien. Gracias por contestar Nicolas. en realidad, ya probe con Iexplore, chrome y firefox. Tengo otro servidor mas viejo con fop2.11 (64bits) y funciona perfecto. Sin embargo con este mas nuevo tengo dicho inconveniente. No te entiendo a que te referis con Un cliente version 2.20 puede tener problemas conectando con el servidor 2.22. es decir, si instalo fop2.22 , entiendo que se instala el servidor 2.22 y el cliente 2.22 en /usr/local/fop/ y en /var/www/html/fop2 respectivamente. digo bien? porque asi es como lo tengo instalado

Thx for your detailed reply. I am using fop2-2.20-centos5-i386.tgz I will test with the JavaScript Debug console and update you. Thx again. Sans

ok. Thx Sans

fop2 will not pass more variables that the ones it is already sending, and none of them is related to a user preference. You must solve your issue with using php sessions or hardcoding allowed extensions in your checkdir.php script. You can very well store preference in a mysql table and check that table in checkdir.php. mysql will persist "forever" and you wont have the problems you are facing with php sessions. Best regards,

Since FOP 2.30, settings can be configured via FOP2 Manager (http://your.server/fop2/admin). That for global options. Or open up preferences when logged into FOP2 for each user and you can turn on/off all sound types (ring, queue, chat).

Yes, commending #exec autoconfig-users-freepbx.sh did the trick. Its working as expected now. Thx a ton.

yep, create a group and include only that queue then go to fop2 users and assign that group to some user, login as that user and you will only see that queue

One way: create a group in fop2admin that does not include those buttons, and then assign the group to all your users. Another way (need access to the command line and know what you are doing): modify autoconfig-buttons-freepbx.sh and setup the mysql query as to not include trunks or park type buttons. operator.css can also work, you can set display:none to the trunk and park divs in index.html Best regards,

Hi Sanjay, The queue buttons display that information themselves. If you want to limit the view to only queue buttons, you can do so by defining groups. I will reply to your email later today, I am having a complicated week and I cannot keep up with all emails.

The problem is this: There are not standard events sent via AMI regarding extra variables.. parsing CDR events via manager is overkill for that feature. In FOP(1) there is the option to save every channel variable that is "Set" and then pass that to the panel itself, but it is quite expensive on CPU as it has to inspect every event looking for the "set" application, etc. The next release will have a command "setvar" that can be sent to the client, and that will pass the key/value pair to the notification scripts. But you will have to custom code the event processing in FOP2Callbacks.pm and return a setvar event accordingly. It will consume quite a lot of cpu, but should be possible to do (on a custom basis, and programming it specifically). The callerid name is handy for passing simple values like this one, many people do not like the idea but sometimes it makes perfect sense, it does not consume CPU and it is easy to implement without disrupting anything.