After Upgrade FOP Client/Server Version Mismatch

After upgrading from 2.5.x to 2.6.0 Beta2, on the Panel, I get a FOP CLIENT/SERVER Version Mismatch message displaying in the gray bar just above the Extensions list.

In addition, I now have no trunks displaying in FOP even though I have added descriptions to the trunks. Trunk names displayed prior to the upgrade.

OK. I shut down my PIAF server with an amportal stop and then did an amportal start and went to the FOP. It no longer shows the mismatch message.


though it makes me think, I wonder if there doesn’t need to be some cleanup needed in the install of the new FOP as several directory structures changes. Also, there may have been a need to do a CTL+SHIFT+REFRESH after the upgrade, do you recall if you had done that?

Yes. I did the refresh and when that did not work, I shut down and restarted.

How about no trunks displaying after the upgrade?

no trunks at all? did you use the module or the the tarball?

The trunks changed significantly, they are now kept in a trunks table in sql, did you see any errors during the upgrade? It should do the migration (and it has been tested, I hope there is not something broken there :frowning: - others have done it successfully)

Let me know.

p.s. it is possible to try and redo the upgrade from the tarball to see if it will force the trunks to get migrated. If it did not migrate them to the table, then it should not have gotten rid of the old data either which was kept in the globals table since the same migration code removes the old data.

Anyone else run into this? (btw - if this really is an issue, start a new thread with the proper titles so it draws other people’s attention)

I got the same trouble here. After the upgrade there are no trunks shown on the FOP. I did not get any error during the upgrade using the module admin.

ok - no trunks on FOP, I feel much better about that then no trunks elsewhere. What happens if you do an amportal do an “Apply Configuration Changes” orange bar and then after that, if it still does not look right, do an ‘amportal restart’?

Philippe -

Same here on FOP trunks.

This may help:

Notice: no sip trunks defined
Notice: no iax trunks defined
Notice: no AMP Users defined

Opening ticket on issue.

#3291 and #3835

grab the new retireve_conf and retrieve_op_conf_from_mysql.php from svn 2.6 branch if you can’t wait for me to roll a new module upgrade with those in it which should be coming within a day or two.

Problem solve after the update. Thanks.

I still don’t see any dahdi trunks. Sip are working.

From Sky’s post above, not sure of the path but I found the file 2 times.

[[email protected] bin]# /var/lib/asterisk/bin/
Notice: no sip trunks defined
Notice: no iax trunks defined
Notice: no AMP Users defined
[[email protected] bin]#

[[email protected] bin]# /var/www/html/admin/modules/fw_fop/bin/
Name “main::numbuttonsx” used only once: possible typo at /var/www/html/admin/modules/fw_fop/bin/ line 44.
Can’t locate in @INC (@INC contains: /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 . /var/www/html/admin/modules/fw_fop/bin) at /var/www/html/admin/modules/fw_fop/bin/ line 13.
[[email protected] bin]#

Sorry I don’t know how to format that better. Looks like one of the many files doesn’t have a path set correctly. I am not sure if this is an elastix 1.5 or freepbx issue.

I have 2 dahdi and 3 sip trunks.


after amportal stop and amportal start
It no longer shows the mismatch message
Thanks kenn10