[test-results] [Bamboo] No agents to build plan Asterisk Testing - Asterisk 1.8 Branch - Asterisk 1.8 CentOS 6 64-Bit

[Bamboo]

-------------------------------------------------------------------------------
TESTING-ASTERISK18BRANCH-AST18CENTOS64-190 has been queued, but there's no agent capable of building it.
-------------------------------------------------------------------------------

http://bamboo.asterisk.org/browse/TESTING-ASTERISK18BRANCH-AST18CENTOS64/log

--------------
Code Changes
--------------
kmoore (365398):

>Fix many issues from the NULL_RETURNS Coverity report
>
>Most of the changes here are trivial NULL checks.  There are a couple
>optimizations to remove the need to check for NULL and outboundproxy parsing
>in chan_sip.c was rewritten to avoid use of strtok.  Additionally, a bug was
>found and fixed with the parsing of outboundproxy when "outboundproxy=," was
>set.
>
>(Closes issue ASTERISK-19654)
>

mmichelson (365460):

>Fix findings 0-3, 5, and 8 for Coverity MISSING_BREAK errors.
>
>(Issue ASTERISK-19662)
>
>

mjordan (365474):

>Support VoiceMail d() option when extension does not exist in channel's context
>
>The VoiceMail d([c]) option is documented to accept digits for a new extension
>in context <c>, if played during the greeting.  This option works fine if the
>extension being redirected to has an extension with the same initial digit in
>the channel's current context.  If that digit did not happen to exist in some
>extension, a dialplan match would fail and the user would not be redirected.
>
>This patch fixes it such that if the <c> option is used, the extensions are
>matched in that context as opposed to the caller's original context.
>
>(closes issue ASTERISK-18243)
>Reported by: mjordan
>Tested by: mjordan
>
>Review: https://reviewboard.asterisk.org/r/1892


--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/test-results/attachments/20120508/b764744c/attachment-0001.htm>