[test-results] [Bamboo] No agents to build plan Asterisk - Trunk - Ubuntu Hardy (8.04) - amd64
Bamboo
bamboo at asterisk.org
Tue Dec 27 14:17:30 CST 2011
-------------------------------------------------------------------------------
ASTTRUNK-HARDY-AMD64-189 has been queued, but there's no agent capable of building it.
-------------------------------------------------------------------------------
http://bamboo.asterisk.org/browse/ASTTRUNK-HARDY-AMD64/log
--------------
Code Changes
--------------
kmoore (348994):
>Fix missing doc tags found while fixing ASTERISK-18689
>
>Add missing <variable></variable> tags in app_dial documentation.
>........
>
>Merged revisions 348992 from http://svn.asterisk.org/svn/asterisk/branches/1.8
>........
>
>Merged revisions 348993 from http://svn.asterisk.org/svn/asterisk/branches/10
>
seanbright (349046):
>Merged revisions 349045 via svnmerge from
>https://origsvn.digium.com/svn/asterisk/branches/10
>
>................
> r349045 | seanbright | 2011-12-23 12:32:33 -0500 (Fri, 23 Dec 2011) | 25 lines
>
> Merged revisions 349044 via svnmerge from
> https://origsvn.digium.com/svn/asterisk/branches/1.8
>
> ........
> r349044 | seanbright | 2011-12-23 12:25:01 -0500 (Fri, 23 Dec 2011) | 18 lines
>
> In ChanSpy, don't create audiohooks that will never be used.
>
> When ChanSpy is initialized it creates and attaches 3 audiohooks:
>
> 1) Read audio off of the channel that we are spying on
> 2) Write audio to the channel that we are spying on
> 3) Write audio to the channel that is bridged to the channel that we are
> spying on.
>
> The first is always necessary, but the others are used only when specific
> options are passed to the ChanSpy application (B, d, w, and W to be specific).
>
> When those flags are not passed, neither of those audiohooks are ever sent
> frames, but we still try to process the hooks for each voice frame that we
> recieve on the channel.
>
> So in short - only create and attach audiohooks that we actually need.
> ........
>................
>
jrose (349097):
>chan_sip autocreatepeer=persist option for auto-created peers to survive reload
>
>This patch moves destruction of sip peers to immediately after the general section of
>sip.conf is read so that autocreatepeer setting can be read before deletion of peers.
>If autocreatepeer=persist at reload, then peers created by the autocreatepeer setting
>will be skipped when purging the current SIP peer list.
>
>(closes ASTERISK-16508)
>Reported by: Kirill Katsnelson
>Patches:
> 017797-kkm-persist-autopeers-1.8.patch uploaded by Kirill Katsnelson (license 5845)
>
>
--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/test-results/attachments/20111227/638c79f2/attachment-0001.htm>
More information about the Test-results
mailing list