What events can be safely filtered out using the asterisk 1.8 AMI event filtering and still retain all of the FOP functionality?

Thanks,
Ty

Yes, I had to try a few variations with the user_login_out.agi to get the data formatted correctly for fop2. It seems that under this version of freePBX, the line for asterisk 1.6.0 is correct.

//if(version_compare(get_var("ASTVERSION"), "1.6.1", "ge")) {
//      $user_event_body = "\"UserDeviceAdded|Data: {$user}\\,{$device}\"";
//} else if(version_compare(get_var("ASTVERSION"), "1.6.0", "ge")) {
//      $user_event_body = "UserDeviceAdded,\"Data: {$user}\\\\,{$device}\"";
//} else {
//      $user_event_body = "\"UserDeviceAdded|Data: {$user},{$device}\"";
//}
$user_event_body = "UserDeviceAdded,\"Data: {$user}\\\\,{$device}\"";

...

//if(version_compare(get_var("ASTVERSION"), "1.6.1", "ge")) {
//     $user_event_body = "\"UserDeviceRemoved|Data: {$current_user}\\,{$device}\"";
//} else if(version_compare(get_var("ASTVERSION"), "1.6.0", "ge")) {
//     $user_event_body = "UserDeviceRemoved,\"Data: {$current_user}\\\\,{$device}\"";
//} else {
//     $user_event_body = "\"UserDeviceRemoved|Data: {$current_user},{$device}\"";
//}
$user_event_body = "UserDeviceRemoved,\"Data: {$current_user}\\\\,{$device}\"";

Now I just have to remember to replicate this change for any core FreePBX updates.

Thanks Nicolás.

On the dev box I setup, I initially had issues getting the agent to update successfully on logon/off. Now that I'm setting up the production systems I cannot seem to resolve the issue. Previously, it required modifying the user_login_out.agi as per the post [url:3nci2ste]http://www.fop2.com/forum/View Post 129[/url:3nci2ste]. Didn't help this time.

FOP2.20 final
FreePBX 2.9.0.7
Asterisk 1.8.3.3
Debian squeeze

Running fop2 in debug (./fop2_server -X 15), I do see the user events that, I believe, should be updating the client.

127.0.0.1       <- Event: UserEvent
127.0.0.1       <- Privilege: user,all
127.0.0.1       <- UserEvent: UserDeviceRemoved|Data: 219
127.0.0.1       <- 3219
127.0.0.1       <- Server: 0


127.0.0.1       <- Event: UserEvent
127.0.0.1       <- Privilege: user,all
127.0.0.1       <- UserEvent: UserDeviceAdded|Data: 219
127.0.0.1       <- 3219
127.0.0.1       <- Server: 0

Any help would be great.
Thanks

In the manager.conf settings, both read and write are set to all. I am using the fop2admin plugin. I'll flush browser cache and verify buttons are working correctly with the permissions set. But call status doesn't work unless I explicitly specify event types in the event_mask config item.

With the default configuration setting, where the event_mask line is commented out, the status of calls would be sporadic. For example, an inbound call would show on the queue but would not always show as ringing to a user or even picked up by the user. When this happened, the call would also never appear to hang up in the queue button until a new call comes in. I was able to resolve this by specifying items in the event_mask.

The fop2_server doesn't appear to be able to handle the entirety of what is being spit out by the asterisk manager or maybe the volume of real-time messages on the version of asterisk is clogging up the works. I can only get normal fop2 functionality by filtering events.

My question regarding this issue, what event items are needed for what FOP2 functionality?

freepbx 2.8.0.4
asterisk 1.8.2.1
fop2 2.20_beta
fop2_admin 1.2.2

Additionally, not all of the items appear for all users like the preferences and logout buttons for example. It doesn't matter if I specify all or specific permissions for the user in question. This isn't as big a deal as long as the call controls work (transfer, listen, record, etc) but any thoughts would be appreciated.

I know... I'm living on the bleeding edge, but most everything appears to be working well.

Thanks,
Ty