FOP2 not functional on certain extensions.

[nbains]

Hi,

I've noticed that when using FOP2 on our FreePBX installation to monitor calls, that some of the extensions in the FOP2 admin panel.

Basically, I have about 100 extensions in my organization. About 80% of the extensions you can click on on anytime and hit the "Listen" icon, and the phone will ring and you'd successfully be able to listen to a phone call. However, there are about 7-10 extensions that are not functional when you click on them to listen in on them.

Looking at the real time error logs, the only difference is, when issuing a 'listen' signal from FOP2 to extensions that listen in works on, the asterisk log shows a 'ChanSpy on ext xxxx' message. When hitting 'listen' and one of the affected extensions, I do not see any Asterisk ChanSpy message. Seems like the ChanSpy signal is not being sent. It seems like it is failing before even hitting the ChanSpy aspect of the process.

I have configured FreePBX extension config details between the extensions that work and don't and have not found anything outstanding.

I've tried creating multiple FOP users and different browsers, and all have proved to be unsuccessful.

Any ideas would be much appreciated, if you guys need more information regarding the problem, please let me know.

Thanks again,

Neil.

[nicolas]

Did you set privacy for the affected extensions ?

You can start fop2_server in debug mode and check the output once an unsuccessful test is made:

service fop2 stop
cd /usr/local/fop2
script capture.log
./fop2_server -X 511
(do your failed test).
ctrl-C
exit
service fop2 start

At this point you will have a big capture.log file to inspect in /usr/local/fop2

You can search for "tospy" on that log and go from there.

Best regards,

[nbains]

Hi Nicolas,

Thanks for the reply.

It's funny, I tried reloading FOP2, via a service fop2 restart, and ever since then, every extension seems to ring back to my phone. I suspect that it maybe just required a restart to re-sync to the server as I had made quite bit of changes from the last fop2 restart, but I will definitely keep that troubleshooting method in mind for next time.

Thanks for your help!

• Neil