One thing is button status, and another thing is performing actions across servers. Forget about fop2, first think on your setup locally. If you have two servers, you must have a dialplan that lets you dial from one server to the other and viceversa. In that dialplan, extensions MUST be unique and dial should be done directly with no prefixes if you plan to use fop2 to spy other servers extensions.

Your extension is on server A
The extension you intend to spy on is on server B

In that case, chanspy must be performed on server B, using Local/xxxx as the originator of the command, where xxxx is the extension you must dial from server B so your extension on server A rings. So, originatechannel for your extension must be set to Local/xxxx.

If on server A you dial yyyy to ring your extension, and on server B you dial xxxx, then it will not work with fop2 as you expect.

And finally, chanspy sometimes does not work. If the chanspy command is issued on the correct server, using local/xxx to ring the remote server extension, everything else is setup but you get no sound. then it is not a fop2 issue, but an asterisk/networking/chanspy issue. fop2 is the command center, once the command is launched, from then on is asterisk/network/setups.

Best regards,

Server A = 192.168.1.1, extensions 1XX
Server B = 192.168.1.2, extensions 2XX

In your dialplan you should be able to dial 1XX from any server extension so that specific extension rings on server A.

Fop2 button configuration:

[SIP/100]
type=extension
extension=100
context=from-internal
server=192.168.1.1
originatechannel=Local/100@from-internal

[SIP/200]
type=extension
extension=200
context=from-internal
server=192.168.1.2
originatechannel=Local/200@from-internal

With that setup and FOP 2.24, you should be able to Listen to 200 in server B from 100 in server A and viceversa.

And if you want to see the action buttons, you must have a fop2 user defined for every extension on every server

user=100:password:all
user=200:password:all

And both 100 and 200 should be visible for the user in their extension list. If you log as an extension that does not have a matching button, you will not see the action buttons in the toolbar.

Best regards,

You can find the fop2 version by looking at the fop2 footer in the web, or via command line

/usr/local/fop2/fop2_server -v

Best regards,

To upgrade:

Backup your /usr/local/fop2 and /var/www/html/fop2 directories, so you have a separate backup just in case.

Try to rememeber your customized files, as you might need to restore them after the upgrade, like FOP2Callbacks.pm or js/presence.js, buttons.cfg, etc. the fop2.cfg file will not be replaced.

Then download version 2.24, extract the tarball, cd fop2 and run "make"

Then restore your customized files, or make a diff between the new ones and the old ones to check for differences.

Remember that upgrades are free for one year, after that, the upgrade cost is $20 (annual maintenance fee on www.fop2.com/buy.php ).

Best regards,

I cannot give you a direct link as I do not know your linux distribution. Look at the download page and choose yours:

www.fop2.com/download.php

Do you have an upgrade code yet? Please contact me via the live help, do not post any codes in the forum.

I usually go to sleep, take dinner, a shower, I spend a little time with my family, etc. It's been a while since I unpluged the wire that sends emails directly to my brain. ;)

I hope you can write a post later explaining the solution I provided after giving you free remote support for several hours.

Hi,

The email reply I sent to you was rejected by your mail server. I am *every* day on the live help, you can contact me there, as many many users do.

Fop2 does not touch databases in a way it would break anything, much less making a server crash, it seems you are implying that because of fop2 your server crashed. I'll bet that is not the case.

You know where to find me: the live help. I do respond. Check this forum, people comments, etc. And you forget to mention the free remote support I gave you. Saying things like "I do not respond" is rude, really rude. Even if you purchased licenses. A little bit of etiquette would be nice from your part.

If you have a problem, post the exact error you are getting, and describe what you did to reach to that situation. With no description/report, it is impossible to help or give a proper reply.

In any case, according to your email, I think the problem is that you did not install the FreePBX fop2admin module, but it is just a guess because your mail was vague on details.

Please email me to asternic at gmail dot com or catch me on the live help. Your mail server does not like mails from mine.