[asterisk-dev] Feature Request: Macro LOCK

Nicholas Blasgen nicholas at blasgen.com
Tue Aug 7 14:17:56 CDT 2007

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

Food for thought.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20070807/fd65b0c0/attachment.htm 

More information about the asterisk-dev mailing list