FOP2 Community Forum

Hi,

I run into a little problem with multiple parking lots. The lots display correctly, show parked calls correctly but do not detect the pickup of a parked call, the call appears to stay in the lot until the person who unparked the call hangs up.

If you unpark the call using FOP2 it works fine, but this appears to be because that uses a transfer event rather than actually unparking the call?

If I go back to just using the default parking lot it works fine.

My Features.conf looks like this:

parkext=6000
parkpos=-7
context=parkedcalls
parkingtime=45

[parkinglot_bml_default]
parkpos=6170-6178
context=bml_default
parkingtime=120

[parkinglot_bml-deult23]
parkpos=3270-3278
context=bml-deult23
parkingtime=120

FOP2.cfg looks like this:

[PARK/parkinglot_jam_default]
type=park
label=JAM Default Lot
extension=6000
context=jam_default

Anyone got any ideas what i'm doing wrong?

Simon.

Hi Nicolas,

I've PMed you about this but I haven't heard a response.

Are you still okay to let me have an advance copy of the new FOP2 code that nativity supports device and user. Very happy to test it!

Simon.

Hi,

In the past I've used FOP 1 with FreePBX in device and user mode to show which extensions are logged in or not. I achieved this by modifying the Perl script that ships with FreePBX to first correctly support device and user mode, made the script check if a user was logged in or not and then fiddled with the FreePBX macro to reload FOP each time a user logon / logoff event occurred.

This was great for outbound call centres where I used device and user mode in lieu of some sort of outbound queue, call centre managers could get a live view of everyone logging in and out - great.

In your documentation I noted a HUP signal is all that is required to get FOP2 to reload it's config, this does work correctly, but end users web pages do not refresh automatically, they have to refresh the page and then log back in again to see the changes. In the mean time the buttons on the page behave rather oddly as the front end display and the back end configuration don't match up I imagine...

I have found with FOP2 the only way to make clients web pages reload when button files are changed is to restart the FOP2 service (kill fop2_server completely and reload), this has a much longer delay to refresh the page than with FOP1, something I wanted to make shorter. I'm wondering if there's a less 'violent' way I could go about forcing a web page refresh that has a shorter reload time?

I've been testing this using Safari and Firefox on an OSX system if the web browser version makes a difference.