On Wed, 28 Dec 2011, Risto Vaarandi wrote: > On 12/28/2011 05:05 PM, sylver_b wrote: >> >> How could we continuously listen to unix sockets with SEC as calls come >> in and achieve the following : >> >> *a)*alert (or run script) if the call limit per caller (I_ACCOUNT) >> and per period have been exceeded and CC_STATE:Connected >> *b)* alert and run script if same destination number (CLD) with same >> CLI is called more than once -- a "normal" user doesn't call the >> same number more than once > > hi, > > I think the best way of getting data from UNIX socket would be a small > Perl program which would read the socket and print received events as > lines to standard output. If SEC starts this program at its startup with > 'spawn' action, it will be able to receive events from the socket. > Another approach would be to let the program write into a file, and > configure the file as input source with --input option.
do you really need a unix socket, or would a named pipe work for you? David Lang ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Simple-evcorr-users mailing list Simple-evcorr-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
