In the following example
exten => _1NXXNXXXXXX,1,Set(GROUP(outbound)=myprovider)
exten => _1NXXNXXXXXX,n,Set(COUNT=${GROUP_COUNT(myprovider@outbound)})
exten => _1NXXNXXXXXX,n,NoOp(There are ${COUNT} calls for myprovider)
exten => _1NXXNXXXXXX,n,GotoIf($[ ${COUNT} > 2 ]?denied : continue)
exten => _1NXXNXXXXXX,n(denied),NoOp(There are too many calls up)
exten => _1NXXNXXXXXX,n,Hangup()
exten => _1NXXNXXXXXX,n(continue),GoSub(callmyprovider,${EXTEN},1)
instead of sequentially numbering the priorities, the "n" construct is
used. I find that when I attempt this in the realtime extensions table
only, the first priority step is recognized. If I sequentially number
the priorities and add a label, the step is no longer recognized.
Is this behavior by design or an error?
Thanks in advance
Bruce
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
