Ticket #2782 (closed Bugs: fixed)

Opened 8 months ago

Last modified 5 months ago

FOP Panel flashing red and green

Reported by: marioja Assigned to: asternic
Priority: minor Milestone: 2.5
Component: Flash Operator Panel Version: 2.4-branch
Keywords: FOP flashing red green Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

Once I installed Flash Player 9.0.124.0 (from 9.0.115.0) FOP panel stopped working. After uninstalling 9.0.124.0 and re-installing 9.0.115.0 from Adobe archive the FOP panel started working once again. After looking at the network traffic from the 9.0.124.0 and 9.0.115.0 case I noticed the following:

With the 9.0.115.0 player, the FOP panel would initiate two connections to the FOP server at port 4445. In the case of the 9.0.124.0 player, only the first connection would be done and it would be identical as the first connection with the 9.0.115.0 case.

I have reported this to Adobe but I don't have a support agreement with them so if anyone does they may have more pull then me.

Attachments

freepbx_fop_patch.txt (1.3 kB) - added by tonym on 05/07/08 20:19:08.
Patch for FOP wrt new versions of Flash Player 9

Change History

04/22/08 03:43:58 changed by vgster

  • priority changed from major to minor.
  • confirmation changed from Unreviewed to Need Feedback.

This does seem to be the case. However it does appear to be a Flash player problem. have you tried updating the panel to .28?

05/07/08 20:18:12 changed by tonym

A fix for this has been commited to FOP but not part of a release there yet.

http://www.asternic.org/archives/msg03086.html explains the problem better than I could.

I've attached a patch that applies the fix from the snapshot mentioned in that message to the .27 distributed with FreePBX 2.4.0.0

05/07/08 20:19:08 changed by tonym

  • attachment freepbx_fop_patch.txt added.

Patch for FOP wrt new versions of Flash Player 9

05/16/08 16:19:28 changed by asternic

Hi there,

A better fix would be to use the latest FOP version altogether... there is an option in op_server.cfg "use_amportal_conf=1" to read the config variables from freepbx config instead of op_server.cfg.

I just want to help adapt FOP to freepbx without you guys taking to patch or modify it in any way.

05/20/08 09:02:38 changed by marioja

Why is this a minor issue. FOP does not work so I think it should be left a major issue. It is not possible for some people to downgrade to the older flash once they have updated and hence it remains an issue for them. I would strongly suggest to keep it a major priority.

(follow-up: ↓ 8 ) 06/12/08 05:13:53 changed by lazytt

marioja: While some may concider not being able to "see" what us happening in their pbx a major problem, this issue is not marked major as many people dont use the fop, and even to thoes that do it does not inhibit the core pbx functions (making and reciving calls) when it doesnt work.

That being said and after scanning the related thread it seems that all that is nesesary is to drop in the new fop and add "use_amportal_conf=1" to op_server.cfg to solve the issue.

Philippe?

06/12/08 05:17:27 changed by lazytt

p.s. kudos to asternic for working closly to help resolve the issue!

06/12/08 11:09:10 changed by marioja

IMHO I think it should be major since FOP does not work and I have seen enough traffic on Trixbox, freepbx and other places to know that lots use it. Given that there is a fix I don't really care if you set it to major or not just having an idea when it will be fixed would suffice.

(in reply to: ↑ 5 ) 06/12/08 12:06:29 changed by asternic

Hi, the FOP version that solves the problem is 0.29, not 0.28. So, if you just replace op_server.pl and operator_panel.swf in freepbx, and add "use_amportal_conf=1" as the 1st parameter in op_server.cfg just below the [general] section... thtat will fix the problem.

http://www.asternic.org/files/op_panel-0.29.tar.gz

Replying to lazytt:

marioja: While some may concider not being able to "see" what us happening in their pbx a major problem, this issue is not marked major as many people dont use the fop, and even to thoes that do it does not inhibit the core pbx functions (making and reciving calls) when it doesnt work. That being said and after scanning the related thread it seems that all that is nesesary is to drop in the new fop and add "use_amportal_conf=1" to op_server.cfg to solve the issue. Philippe?

06/12/08 18:34:05 changed by p_lindheimer

  • milestone changed from Cut Line to 3.0.

asternic, do you want me to give you svn access. You can update trunk and then after we get a few people to confirm that all is well, we can merge it to the main 2.4 release? I would much prefer to keep completely in sync with your proper version and not make changes to the FOP we have packaged with FreePBX if possible. Let me know and I can arrange that for you.

06/15/08 01:30:11 changed by lazytt

  • owner changed from lazytt to asternic.

06/17/08 14:47:13 changed by p_lindheimer

  • confirmation changed from Need Feedback to Need testing.

r5779 - can we get a few testers to pull the change from trunk and manually apply it. If we get good feedback we will role this into 2.4 and get it published in a framework update.

06/23/08 03:05:39 changed by lazytt

  • confirmation changed from Need testing to Confirmed.

ive updated a client with the latest changes and he's reporting that all is well!

06/23/08 20:50:56 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to fixed.

it works for me too. I'm going to close this bug as I have merged the updates from trunk to 2.3. It will be published next time framework is published. I would like to still hear from more testers as it may make me pull the publish trigger quicker, so please comment even though the ticket is closed and nudge me along.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads