Fop2 stop working after Elastix upgrade

[thiagocpv]

Hi there!

After Elastix upgrade from 2.4 to 2.5, the Fop2 stopped working.
It's try to connect to server, but no connect.
Maybe some conf file need reconfiguration after the upgrade?

Thanks.

[nicolas]

There is very little information in your problem report to tell you anything useful.

What fop2 version?

[fixed]
/usr/local/fop2/fop2_server -v
[/fixed]

Is fop2 running?

[fixed]
pgrep fop2
[/fixed]

Did you enable the firewall allowing port tcp/4445? If the elastix firewall is enabled, try disabling it and try again.

[thiagocpv]

So Sorry !!!!

Here you are!
fop2_server version 2.28

The service is not running. When I started the service, after 3 seconds, the service goes down.
The firewall is disabled.

netstat -nat | grep 4445
tcp 0 0 0.0.0.0:4445 0.0.0.0:* OUÇA
tcp 0 0 192.168.2.17:4445 192.168.2.73:50113 ESTABELECIDA
tcp 0 0 192.168.2.17:4445 192.168.2.73:50111 ESTABELECIDA

Thanks.

[runlevel6]

I had a similar problem the other night. I upgraded to Elastix 2.5 (from 2.4 release and that broke FOP2... More importantly, any changes I made in the PBX would throw errors when I tried to "apply" them.

That is the reason I registered for this forum. While waiting for my registration to be approved, I uninstalled FOP2 from the Elastix addons and that seemed to fix the PBX issues.

I then rebooted and installed FOP2 again, and FOP2 worked, but the PBX would still throw an error about selecting parked calls from the database whenever I attempted to apply changes...so i uninstalled FOP2 again until I could reach support about the issue.

Anyway, as of this morning, In preparing to document the issue for support, I re-installed FOP2 again (and it seems there was a repository update this time) in which the installation seems successful. FOP2 is running, and PBX changes are applying without errors.

[nicolas]

The parking erros you saw are because you do not have the park module installed in freepbx, a requirement for the deprecated fop2 admin freepbx module. installing the park module and queues modules are mandatory for fop2 admin to work.

The latest fop2 version has its own standalone and bundled manager, and does not rely anymore on FreePBX. So my suggestion is not to install the old rpm/market version but the newer version from tarball until we get the new version in the elastix repositories.

Best regards

[thiagocpv]

Ok OK, guys, but what's the best way to do?
Unistall fop2? Wait for new releases??

@runlevel6, my Elastix now is just with freepbx theme. I don't know why, but I'm enjoying.

Thanks.

[nicolas]

thiago, in your case, you have to disable the old FOP1:

[fixed]
amportal stop_fop
[/fixed]

Then edit /etc/amportal.conf and set

[fixed]
FOPRUN=false
[/fixed]

And edit /etc/rc.d/rc.local and remove the line that says "amportal start_fop"

Then start fop2 and try again:

[fixed]
service fop2 start
[/fixed]

Best regards,

[thiagocpv]

Hi Admin,

Now, it's working fine!

Thank you!