FOP2 Community Forum

Tthere is no way or plugin that does that. And it would be a problem to have such module/plugin, as I already envision people complaining about agents being logged out "for no reason". You could write some scripts and use cron jobs on the server to do that with a little bit of work. Best regards,

In index.html you have something like this: <div style='float: left; padding-top: 10px;'> <select id='presence' name='presence' onChange='setState(this);'> change it to: <div style='float: left; padding-top: 10px; display:none;'> <select id='presence' name='presence' onChange='setState(this);'>

Hey Guys, I have now had a number of customers ask that the ACTION buttons have text under them explaing what the acions are. I do realise that you can "mouse over" the buttons, but the users would rather have the buttons with a smaller logo and a text describer of the action... Are there any options for these buttons??

The only way to debug is to start fop2_server in debug mode (level 15) and stop capturing just after a call is cut off... it will be quite hard to do on a production system. It is important to identify the call that was cut off somehow, as the manager is very verbose. A big file with no indications of the call that had the problem is not really useful. To start fop2 in debug mode: /usr/local/fop2/fop2_server -X 15 Best regards,

Hi Alan, The autoconfiguration scripts work on the local server only. You will have to modify them in order to read data from other servers. Best regards,

Is it possible to show if an extension is call forwared? If so how? If not is this function in the next release? Thanks

You can copy the app-cf-toogle on the override file and add the exact bits of noficiations for the dnd-on and dnd-off on the correct places. It is not a "fix" but just a dialplan that needs to be set. In any case, here is a modified script to handle also the app-cf-toggle macro, let me know if it works fine so I can included it on the next release: http://download.fop2.com/generate_overr ... xts.pl.txt

Hi, The "start, stop, restart" are only available on the init script, not on fop2_server itself. If the init script works fine, your #exec script will be executed. Remember that you have to set the execute permissions to your script too... Best regards, PS: I am online now, and will be online for one more hour.

Hi Alan, The autoconfig-users-freepbx.sh script is there for you to modify and do whatever you want. You do not need to keep it untouched, you can modify it so it extract users, password and permissions from somewhere else. The next release is around the corner (have to add one more feature, write docs, package and release), you can download the beta right now, together with the freepbx module that lets you manage users, permissions, groups, etc. The fop2.cfg on the beta has new features, keeping backwards compatibility in format, but is not exactly the same, as there are new permissions and as a new features the option to define group and assign groups to users. The new config options are described here: View Post 209&p=813&hilit=fop2admin+1.0.tgz#p813

You will have to tweak the autoconfig button script. If you want ONE button for a user, and serveral channels, you can use a construct like this: [SIP/100] type=extension label=John extension=100 context=from-internal channel=IAX2/100 channel=SIP/cell100 You can list as many channels as you want, they will update status on the same button on the panel. Anyways, you did not say how are you adding those cell phones. You can also list them individually, but you will have to add some lines to the auto config button script so it shows your custom ones.

If you do not want to use blind transfers, your asterisk version must support the atxfer manager command, and you can tell fop2 to use it by setting in fop2.cfg: supervised_transfer=1 blind_transfer=0 Another setting that must be set, but this time in asterisk's sip.conf file ( or sip_general_custom.conf file in freepbx), is callevents=yes Without this event, you might have issues with transfers. In order to debug why a transfer fails, you must start fop2 server in debug mode and capture the output, and stop capturing when the problem happens. It is kind of cumbersome but the only way to find out. You can also look at the asterisk full log at that moment, and search for clues there too. Please be sure you have callevents set to yes, as that might be a probable cause of your issues. Best regards,

After taking a long the time to review 255 problem, it happened to be a silly problem. But it was good to improve the daemon so it fails gracefully in case of a misconfiguration. In this particular case, the autobuttons.cfg file was missing. There was a backup in place with the tilde at the end, so I first though everything was ok. So, the automatic configurator script for users run ok, but pointed to an unexistant button file. So the buttons where actually missing, and the daemon crashes when there is no button configured. So, I will work on fixing the daemon to not crash and give a proper error on the console.