<![CDATA[Fop2 ChanSpy Options]]>I'm wondering how the 'ChanSpy Options' entry in the Fop2 Buttons setup works? Can I use a group names? an extension?, queue? what is the syntax for the entry?

I've tried simply entering a group name that includes a group of my sales agents but it doesn't limit it to just the group..can still listen to everyone.

Also, I restarted the Fop2 service each time I made a change..not sure I needed to but..

I'm using Fop2 2.27
asterisk 11.8.1

thanks in advance for any help!!
dt

]]>http://localhost:4567/topic/1768/fop2-chanspy-optionsRSS for NodeTue, 27 Oct 2026 09:54:16 GMTThu, 17 Jul 2014 01:19:57 GMT60<![CDATA[Reply to Fop2 ChanSpy Options on Tue, 29 Jul 2014 20:36:15 GMT]]>Thank you very much Nickolas! Much appreciated! 🙂

]]>http://localhost:4567/post/7667http://localhost:4567/post/7667Tue, 29 Jul 2014 20:36:15 GMT<![CDATA[Reply to Fop2 ChanSpy Options on Tue, 29 Jul 2014 19:43:15 GMT]]>chanspy options should be passed the same way you do it to the application chanspy in your dialplan. It is not something made up in fop2, they are straight options for the chanspy application.

You also have global spy options you can set in fop2.cfg

To see the list of available options in your asterisk version run:

asterisk -rx "core show application chanspy"

Now, if you want to limit the spy action to some extensions within fop2, not matter your asterisk configuration, then you should create a fop2 group containing the extensions you want spy to be allowed, then a fop2 permission with a special name limited to that group, and finally edit the fop2 user and be sure it does not have the "spy" permission but your custom permission. In that way, a fop2 user will be able to spy only to the extensions listed on the group the custom permission is assigned to.

Best regards,

]]>http://localhost:4567/post/7666http://localhost:4567/post/7666Tue, 29 Jul 2014 19:43:15 GMT<![CDATA[Reply to Fop2 ChanSpy Options on Tue, 29 Jul 2014 18:14:33 GMT]]>Hello... Is this forum monitored at all? Haven't seen any replies.. Is there a better way to limit who users can and cannot listen to?

Thanks

]]>http://localhost:4567/post/7665http://localhost:4567/post/7665Tue, 29 Jul 2014 18:14:33 GMT