It should be possible to modify both the application forward in freepbx to also set a fop2presence astdb entry and userevent as it is done with DND. I am not sure if that would be the best approach anyways, but yes, it is possible to do it.

Not in the standard distribution, at least not by using the presence information. You can hack your way through it, just download the beta and look what I did on the app_dnd in freepbx, and do the same for call forwarding.

Feature implemented on FOP 2.20. customastdb to track for special values and display an extra information icon on the extension button.

Hi,

Since version 2.20 fop2 will show call forward state in extension buttons. If you use freepbx you should not do anything to see them, its a curved arrow icon that shows the call forward number when mouse over.

You cannot change call forwarding state, but you can see if its forwarded or not. It is done by monitoring the CF astdb entry that is set by FreePBX.

If you do not see it, it might be because user events are filtered because of insufficient manager permissions, in that case, try to add "all" both to read/write in /etc/asterisk/manager.conf for the user fop2 is using to connect to AMI. Trixbox has a bug that filters user events even if you have the user permission set, only adding "all" or "hud" will get the userevents back.

Best regards,

Add "all" permissions to your /etc/asterisk/manager.conf read and write lines, then try again.

FOP2 shows status change with no reload or poll interval. So I do not have to add anything. Did you update the freepbx contexts with the generate_override_contexts.pl script ? If so, you probably have a bad configuration for your buttons, or Asterisk 1.6 is not broadcasting the correct UserEvents, Are you using Trixbox, trixbox asterisk 1.6 phonecore is broken. Or you are not giving the complete information about your system. if you did not run the generate_override_contexts.pl script, do it as described here:

http://www.fop2.com/documentation-insta ... arball.php

I forgot, please leave poll_interval at is default value. It is not really needed anymore, only if your asterisk is misbehaving, it might do more harm than good.

Best regards,

Here is a post telling you how to start fop2 in debug mode:

View Post 1170&p=4462#p4462

Below there is the log after I deactivate the call forward:

** QUERY CUSTOM ASTDB 9803 CF

127.0.0.1 -> Action: DBGet
127.0.0.1 -> Family: CF
127.0.0.1 -> Key: 9803
127.0.0.1 -> ActionID: getvar!custom!CF/9803

127.0.0.1 <- Response: Success
127.0.0.1 <- ActionID: getvar!custom!CF/9803
127.0.0.1 <- Message: Result will follow
127.0.0.1 <- Server: 0

Are you sure that is when you deactivate call forward? Here is a sane response when you query a variable that is not present:

127.0.0.1 <- Response: Error
127.0.0.1 <- ActionID: getvar!custom!CF/609
127.0.0.1 <- Message: Database entry not found
127.0.0.1 <- Server: 0

If you see something else, your asterisk is broken. What UserEvents do you see when dialing the cf feature codes?

In any case, I have to mention that Asterisk 1.6 was a devel branch, you should be using 1.8.

Best regards,

I have replied to your email, your capture does not show the userevents that are inserted via generate_override_contexts.pl for the fop2 dialplan. Did you run that at all? Do you have an extensions_override_fop2.conf file? Is that file included in extensions_override_freepbx.conf file ? Did you modify the cf macros by hand in some way? For instant notification of status change, fop2 inserts a dialplan step to fire a UserEvent. In the capture you sent there is no UserEvent being sent, so the dialplan is not changed or you have some strange issues with manager permissions. But I think the dialplan changes made by the generate_override scripts were not applied correctly.

Glad you have it working!

Best regards,