FOP2 Community Forum

Hi, once session is initiated in FOP2, it will make some ajax calls to set session variables to setvar.php, you can troubleshoot those using the developer console on your browser, network tab for xhr requests. Those session variables are there for security to not let malicious users attempt to retrieve other files from the system.

Hi, The best option is to use the FOP2 Manager to configure settings for each tenant. If you do not run a supported multi tenant backend, you will have to modify functions-custom.php and configure the proper functions. function "custom_populate_context" must populate an index based array with your fop2 contexts, supose you have "tenant1" and "tenant2" you should make that function return just that: function custom_populate_contexts_from_tenants() { $panelcontexts[0]='tenant1'; $panelcontexts[1]='tenant2'; return $panelcontexts; } With that, if you log into the FOP2 manager you will have the option to chose between the two and set Settings for each distinctively. Best regards,

We have FOP2 connected to multiple asterisk manager interfaces Is there a way that we can use the FOP2Callbacks.pm and when it sees an event on Server 1, that we can instruct it to send an action to Server 2 Example: A user logs into a queue on Server 1 and we want to issue a DevState command to server 2 Here is an example FOP2Callbacks.pm which works perfectly when we have a single server. The user logs into a queue and we set the DevState on the server. What I need to do now is see the user logged into the queue determine which server saw the event send the DEVSTATE action to the other server here is an example of my FOP2Callback.pm sub amiCommand { # Received an event from Asterisk Manager Interface $command = shift; #We see this come in on the AMI #How do we know which server this came from? #is there a variable that tells us the Asterisk Server that the AMI event came in on if( ($command eq "QueueMemberAdded") { %event = @_; my $return = ""; my @allreturn = (); my $tiempo = time(); $tiempo = $tiempo + 30; my $uniid = $event{Uniqueid}; my $queue = $event{Queue}; my $member = $event{Location}; #Can we define which SERVER to send this ACTION to #For example if this ABOVE "QueueMemberAdded" came from server A we want to post the following ACTION to SERVER B #How do we instruct the system to send the Action to a specific server $return = "Action: DevState\r\n"; $return .= "DevState: ".$member.$queue."\r\n"; $return .= "Value: 2\r\n"; $return .= "\r\n"; push @allreturn, $return; return @allreturn; } Thanks for any insight. ~ron

I have updated the plugin to a new version, you can pass the #{EXTEN} variable to the initial url now.

Exten is passed only to checkdir.php, the next FOP2 release will pass it also to the configured url in preferences.

Basically I am trying to see what even block FOP is using to gather the Variables that it sends to the browser. I have Found AgentConnect, but I suspect that there are other blocks. ~ron

Just like you stated Added the permissions and all is well and functional. THX

# 1st command: $return = "My command\r\n"; push @allreturn, $return; # 2nd command: $return = "Another command\r\n"; push @allreturn, $return; # send back all to server: return @allreturn; Best regards,

There is no way to prevent those popups currently. Your extension is attached to serveral devices, and all of them are ringing and generating a ring event, so you will get the popup for each. Now, you could modify checkdir.php in some way, and try to keep some kind of state on popups to prevent the call on any javascript code that you might output directly in checkdir.php (but you should not be using the preferences popup url in that case).

You must add eventwhencalled=yes To your queues.conf entry for every queue. Only then you will see the info icon showing the queue when an agent is connected to a queue call. Best regards,

sorry All i found the issue to being that the server was a different version than the html section. Once i got them both on the same version all is working well

Hi Andrea, The payload too big is EXCLUSIVELY a websockets error. So in your case, websockets are still being used. Maybe your presence.js file was cached somehow. The solution is NOT to use websockets or upgrade to 2.27. If your code is older than a year, then the upgrade has a cost, maybe that is why it is not taking your code? What is the exact message you get when trying to upgrade, does it say EXPIRED? If you try to reuse the code without an upgrade or with the old version running, then it will say that the code is not available. In any case, the payload error happens ONLY when websockets are in use, there is no payload limitations in flash xmlsockets, so be sure it is disable if you are unable to upgrade FOP to version 2.27