[asterisk-dev] Feature Request: Macro LOCK

Donny Kavanagh donnyk at gmail.com
Tue Aug 7 14:34:39 CDT 2007

see func_lock in asterisk-trunk.


On 8/7/07, Nicholas Blasgen <nicholas at blasgen.com> wrote:
> I've been having a problem with copies of my Macro() script being run at the
> same time.  I just recently found out about MacroExclusive() that almost
> solves my problem (actually, it likly will, but will take some re-tooling).
> But for future additions, I really feel what would be nice would be a way to
> make a macro "exclusive" or locked for only part of the code, much like you
> can lock a table in SQL.
> My current macro does some line testing and then Dial() the next available
> line.  The line testing is what needs to be exclusive in the dialplan.  But
> the Dial() functionality needs to be able to stay outside of that lock.  I'd
> really like it if there was a command to Lock() and Unlock() a macro as
> needed.
> Food for thought.
> --
> /Nick
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev

More information about the asterisk-dev mailing list