FOP2 Community Forum

Chrome is deprecating interfaces with every release, there is no stable desktop notification api available as of now. No idea what could be happening. I will test myself and see if it happens to me also. It was a rush release to overcome the deprecation of rich web notifications, so it might have some bugs I did not notice. I will let you know if I find something.

meetme is the original asterisk's conference application. if you have the "meetme" permission in fop2, you can manage users that are participating in that conference (mute/unmute/kick/lock). meetme is not related at all with queues. Queues are another standard asterisk application. With the queueagent permission you will have menu options in your action submenu (related to your own extension), to add/remove/pause/unpause yourself from any queue. The queuemamager permission lets you do the same for any extension, and also pause/unpause/remove from the submenu that appear when clicking on the queue members list (in the queuee button itself).

This is now resolved. I was missing the definition of the custom permission I had defined. The output of /usr/local/fop2/autoconfig-users.sh should include, in the Permissions section: perm=check_queue_voicemails:voicemailadmin:VIRTUAL/399,VIRTUAL/299,VIRTUAL/199 Initially I could not get these permissions to work as there were no extensions defined. It simply read: perm=check_queue_voicemails:voicemailadmin: We re-created the custom permission, checked the output of autoconfig-users.sh and all was working properly. Thanks for the help!

Most notably support for websockets hiby 10, used by the latest google chrome. Best regards,

Not without coding, currently the freepbx integration sets DND to DND, you can look at extensions_override_fop2.conf file that is generated on the latest fop2 versions, look at the context to set dnd, and alter it to create your custom codes with custom modes. Best regards,

Hello Dimitry, Have you set the queuechannel for the extensions you are adding ? In freepbx, go to tools -fop2 users.. you can set it there. The queue member can be set the same as it is set in freepbx itself, something like Local/xxx@from-queue/n. That should work the same way and probably set the sip headers you already have in place. best regards,

Hi Dimitry, I understand your question now. Unfortunately, fop2 has a fixed timeout for notifications. It does not make a difference. You might want to post this as a feature request. Best regards,

I have 3 sip trunks 1 inbound 1 outbound 1 bidirectional inbound works great outbound - shows the sip/trunk-hex# of call and either s or blank directional shows inbound/outbound mostly correct, but occasionally will show the correct hex code, but the wrong outbound information my buttons.cfg has [att_trunk1] type=trunk label=att-in channel=SIP/att_trunk1 [att_trunk2] type=trunk label=att-out channel=SIP/att_trunk2 [telnet] type=trunk label=telnet channel=SIP/telnet